I have found several similar posts about this but no solution.

Well, We have recently implemented ZAM7.5 and were also experiencing some
problems with the collection client on a few computers (<10%)

I was able to trace this back to two issues!

1. Some machines have SCSI-hardware and a WNASPI32.DLL in the system32
folder for the ASPI layer.

By adding a Diagonostic=1 to the cps.ini file which shows the DIAG window
during the scan i could tell that the scan stops while enumerating the SCSI

As a quick workaround i just removed the WNASP32.DLL and the scan finally
finished. I have not investigated further if e.g. only specific ASPI-version
are affected, etc.

2. Some machines still got stuck in the NOT-YET-SCANNED state. (Error
[2.6.42]) The umxlater.exe task caused high cpu load and rendered the
machine practically unusable.

I could solve this too, but i am not really happy with the result.

Creating a umxlator.txt file before running a scan makes umxlater.exe to
append detailed information during its operation.

The problem became quite obvious by looking at the umxlator.txt file:

ALL machines having trouble with umxlater.exe not finishing had some LOCAL
program started by UNC path and not by drive letter. (mostly from the
Autostart folder)

e.g. HOTSYNC.EXE from Palm. Hotsync.exe itself has nothing to do with the
problem itself, it was just started from:

\\machinename\C$\Palm\HOTSYNC.EXE and not as C:\Palm\HOTSYNC.EXE

This start method has the following effect for umxlator.exe
(text from the umxlater.txt logfile)
- cut -
Starts: 1
Runtime: 141
Searching remote applications.
Excluding \\machinename\C$\Palm\HOTSYNC.EXE
Excluding \\machinename\C$\Palm\HOTSYNC.EXE
Excluding \\machinename\C$\Palm\HOTSYNC.EXE
this goes on FOREVER
- cut -

Changing the start method to drive-letter immediately resolves the
umxlator.exe issue.

BUT: This can only be a workaround! As it is perfectly legal to start local
programs by UNC path - and this will happen again! The umxlater.exe
SHOW-STOPPER will surface again.

Why is umxlater.exe BROKEN, What the heck is going on? Excluding some local
program as a network application?

Can someone please confirm this BUG. Should be quite easy to duplicate.
BTW, Win2000SP4, ZAM75, Novell Client 4.83

Georg Fritsch