Why do our NS's fail to save data for new resource items as this is preventing new resources from becoming an object in the database via the CreateResource.aspx page?
Last Updated February 11, 2007
We have noticed that new resources are failing to obtain a GUID once they connect to the CreateResource.aspx page. The verbose a.log files indicate that the NS fails to save these items.
Priority: 8 Date: 09/08/2006 14:30:13 Tick Count: 1709747453 Host Name: NS1 Process: aexsvc.exe (2536) Thread ID: 4976 Module: AltirisNativeHelper.dll Source: Item::Save Description: An unexpected exception has occured (Item: 3d171717-ec95-48ef-88b2-18a3cbf2ffef, Exception: Altiris.NS.Exceptions.AeXException: Failure in save for Resource item. [Error in the application.] ---> Altiris.NS.Exceptions.PrimaryKeyViolationException: Error in the application. at Altiris.NS.ResourceManagement.Resource.OnSave(Boolean bExistingItem) --- End of inner exception stack trace --- at Altiris.NS.ResourceManagement.Resource.OnSave(Boolean bExistingItem) at Altiris.Resource.ResourceItem.OnSave(Boolean bExistingItem) at Altiris.NS.ItemManagement.Item.Save())
When the server was built, the System Environment Variable 'Temp' was configured to use the largest drive. It was found that the variable was correctly set to D:\Temp, but unfortunately there was no D:\Temp directory. As the NS could not find a Temp directory, it could not create the temporary files necessary in order to create a new resource.
Once this directory was created, the NS functioned correctly again.
Applies To NS 6.0 6074, R1, CMS 6.0 and 6.1, AMS
Imported Document ID: TECH26300
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe