/build/static/layout/Breadcrumb_cap_w.png

An asset already exists Version: 6.0.101863

After upgrading to Kace v.6.0 on K1000 box we are now experiencing issue with Asset where error message "an asset already exists" when we select a different phone model with the inventory field we have set.

Has anyone got this issue with Version: 6.0.101863

 


4 Comments   [ + ] Show comments
  • We have the same issue when trying to edit a computers location or the user assigned - dalook 9 years ago
    • Have you got a workaround on this? or solution? - hjansari 9 years ago
      • no was told by support to just make a change to the Asset name and re save. but that does not keep our history of our asset. - dalook 9 years ago
  • We have the same issue. We are speaking with an KACE engineer and it is a bug. Call KACE and ask for the fix. - jmurray 9 years ago
    • No fix as yet, might be available on next release or service pack.. - hjansari 9 years ago
  • So are you saying, that if you have a Computer asset that has fields for Location and Assigned User, and those fields are also assets, then you cannot change the location or user in the computer asset without creating a duplicate asset for the computer? - H2OFan 9 years ago
  • Depends how you have setup the Assets within K1000. You cant have same duplicate name apparently. - hjansari 9 years ago

Answers (1)

Answer Summary:
Posted by: cblake 9 years ago
Red Belt
0
Same names aren't allowed for multiple assets of the same type. Trainers generally recommend using the serial number as the asset name and mapping field for computers. 

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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