/build/static/layout/Breadcrumb_cap_w.png

Changing Asset Type Names

Recently upgraded to 7.0 and whenever I try to edit the fields in our asset types I get an Oops! Something Went Wrong! error. I have narrowed it down to any asset type that has a "/" in the name such as A/V Equipment, for example. 

The PHP Error is as follows: 

PHP Error: Uncaught Unhandled Exception in /kbox/kboxwww/include/AssetType.class.php on line 363: mysqli error: [1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '/V_Equipment' at line 1] in EXECUTE("drop view if exists ASSET_DATA_VIEW_A/V_Equipment ")

I am unable to change the asset type name, make any changes to it, or even duplicate and delete it. 

Anyone have any suggestions? 

1 Comment   [ + ] Show comment
  • We have three administrators on our KACE 1100, and two out of the three receive this same error since upgrading to 7.0.121306, but not immediately. It's been about two weeks before the error started appearing.

    Since it started we also cannot edit roles for users, and receive errors when accessing the Assets menu.

    I opened a support case last night. - dweiskir 7 years ago

Answers (1)

Posted by: chucksteel 7 years ago
Red Belt
0
It looks like you found a bug! I would submit this to support. 

Comments:
  • Submitted a ticket to Quest. They advised it is a known issue and are looking into repairing. - mkantorski 7 years ago
    • Curious if you got any resolve on this? Just ran into this myself. - cb3inco 7 years ago
      • Support ended up tethering in and resolving the issue for me. - mkantorski 7 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ