Severe client error encountered. No software or hardware recognition

  • Document ID:3469585
  • Creation Date:15-Feb-2007
  • Modified Date:27-Apr-2012
    • Micro Focus Products:
      ZENworks Asset Management

Environment


Novell ZENworks Asset Management 7

Situation

The symptoms will be similar. No hardware or software will be collected for a workstation during the scan cycle due to the collector crash running the software portion of the scan. There are three reasons for this error:
1. Invalid path - Directory path name is longer than 260 characters. When viewing the Process control panel you will see a reference to Error 52563631. The error will also indicate the location of the Invalid Path.
Windows Explorer does not support an absolute path over 260 characters. By mapping to this long folder structure from a client it is possible to create additional folders and exceed this limit.
This situation terminates the software scan and the client will terminate with an error52563631and the text of the error message is: "Invalid path (too long): " where is the actual path that is too long OR second message you would see is;

If doing a Scan Now from the Manager there will be an error message. The last portion of the error will read "The collection client reported a fatal error with one of the field applications."

2. If the Software scan checkbox is disabled within a collection option set. If doing a Scan Now from the Manager there will be an error message. The last portion of the error will read "The collection client reported a fatal error with one of the field applications."
3. An informational error code handling was changed and when encountered the collector considers it a Fatal error and crashes the scan. No hardware or software components will be written during the scan cycle. The error will indicate that the client encountered a Fatal error and you will see high numbers of Errors this Cycle within the Process Control Panel. If doing a Scan Now from the Manager there will be an error message. The last portion of the error will read "The collection client reported a fatal error with one of the field applications."

Resolution

Issues 2 and 3 as listed above arefixed in ZAM 7.0 IR10.

If downloading the Interim Release manually from download.novell.com, the filename is ZAM700SP1IR10.EXE. The Interim releases can also be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section for details of how to set up automatic downloads if desired.

Each interim release is cumulative. If Interim Release 10 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.


Issue 1 has been handled as such in that if an Invalid path is encountered the collector will fail the software scan gracefully, complete and load in only the hardware components.

As a workaround for the Invalid directory path: Based on the information from the Process Control Panel, View Workstation errors, each machine listed as having an Invalid path would need to be corrected.

If the Invalid directory paths are common the directory can be excluded from the software scan.

  • Corporate wide - within the option set > Collector > Software Collection > Skip Directories During Application and File Scan.

  • Per Server - within the \bin\options.txt enter"skipdir:"

Status

Top Issue

Additional Information

Steps To Duplicate:
1) Create a long folder structure from the root of C: on a Windows server (create the folders until the maximum is reached)
2) Share the last folder in the path.
3) Map a drive to that folder.
4) From the client create some extra folders.
5) Copy an executable file to this extended path.
6) Run a Software Inventory Scan on the on the server.

Notes:
When the maximumlimit size is reached unless an error is thrown by Windows the scan will not continue.