Inventory Scan Fails when USB Flash Drive is connected

  • 7022802
  • 02-Apr-2018
  • 09-Oct-2018

Environment

ZENworks Configuration Management 2017 Update 1 Inventory
ZENworks Configuration Management 2017 Update 2 Inventory

Situation

  • Inventory scan generates excessive warning messages in ZCC
  • USB Flash Drive is connected during inventory scan
The following files may be found in %ZENWORKS_HOME%\work\inventory\ :
  • zenBackup.xml
  • zenDeltaBackup.xml
The following message may be seen in ZCC:

Novell.ZENworks.InventoryManager RunFieldApplications problem: RunFAProblemUnexpectedException (The file 'C:\Program Files (x86)\Novell\ZENworks\work\inventory\zenBackup.xml' already exists.)

The following or similar may be seen in zmd-messages.log:

[ZenworksWindowsService] [98] [rlm] [InventoryManager] [] [RunFAProblemUnexpectedException: (System.IO.IOException: The file 'C:\Program Files (x86)\Novell\ZENworks\work\inventory\zenBackup.xml' already exists.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
   at Novell.Zenworks.InventoryManager.UMXLatorZENHelper.backUpWifs()
   at Novell.Zenworks.InventoryManager.InventoryScan.RunScan(ScanType type, String eventid))] [] [] [] [ZENworks Agent]
[ZenworksWindowsService] [98] [rlm] [InventoryManager] [InventoryManager.RunFAProblem] [Novell.ZENworks.InventoryManager RunFieldApplications problem: RunFAProblemUnexpectedException (The file 'C:\Program Files (x86)\Novell\ZENworks\work\inventory\zenBackup.xml' already exists.)] [] [] [] [ZENworks Agent]
[ZenworksWindowsService] [98] [] [ZenCache] [] [(Thread 98) PutObject(Inventory.LastScanEnd, UserContext{_LocalId=none; _RemoteId=(Public)}) called] [] [] [] [ZENworks Agent]


The following or similar may also be seen in zmd-messages.log:

[ZenworksWindowsService] [96] [] [InventoryManager] [] [WifAccess exceptionSystem.InvalidOperationException: There is an error in XML document (203, 32). ---> System.Xml.XmlException: '', hexadecimal value 0x03, is an invalid character. Line 203, position 32.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
...
[ZenworksWindowsService] [96] [] [InventoryManager] [] [Exception in GetHtmlFromWIF : '', hexadecimal value 0x03, is an invalid character. Line 204, position 32.]
...
[ZenworksWindowsService] [78] [] [InventoryManager] [] [Exception while trying to compare if previous scan was hardware only scan : There is an error in XML document (203, 32).]
[ZenworksWindowsService] [78] [] [InventoryManager] [] [Exception while trying to compare if previous scan was software only scan : There is an error in XML document (203, 32).]
...
[ZenworksWindowsService] [78] [] [InventoryManager] [Failed to read in provided path :C:\Program Files (x86)\Novell\ZENworks\work\inventory\384d956bf1b4474c84ee2660ee030d37-last.xml] [xml]
[ZenworksWindowsService] [78] [] [InventoryManager] [] [There is an error in XML document (203, 32).]
[ZenworksWindowsService] [78] [] [InventoryManager] [Failed to read in provided path :C:\Program Files (x86)\Novell\ZENworks\work\inventory\zenBackup.xml] [xml]
[ZenworksWindowsService] [78] [] [InventoryManager] [] [There is an error in XML document (203, 32).]
[ZenworksWindowsService] [78] [] [InventoryManager] [] [Exception : While dumping Usage into Wif : The process cannot access the file 'C:\Program Files (x86)\Novell\ZENworks\work\inventory\zenBackup.xml' because it is being used by another process.]


The following or similar may be seen in %ZENWORKS_HOME%\work\inventory\<GUID>-full.xml file:

<SerialNumber>&#x3;C</SerialNumber>

Resolution

This is partially fixed in version 2017 Update 2 (17.2) - see KB 7022513 "ZENworks Configuration Management 2017 Update 2a and 2 - update information and list of fixes" which can be found at https://www.novell.com/support .
In version 2017 Update 2 or 2a, the zenBackup.xml and zenDeltaBackup.xml files may still be present.

If needed, please contact Micro Focus Customer Support for a patch for this issue on ZENworks 2017 Update 1 or ZENworks 2017 Update 2a and 2.