This from R&D:
Quote:
This occurs when, at the end of the install, the install checks for, but cannot find, a “long file name”, that is a filename longer than 8.3 format. Each module’s script has one test name (unless no such EXEs are that long for that module). for AR it is Receivables.exe. You will get the message if at the install’s end, Receivables.exe is no found (some O/S, starting back with Novell, would use its short name, Receiv~1.exe, which would cause short-cuts to fail, etc.

Anyway if such a message occurs one should look in the folders indicated, and rename any such ??????~?.exe to their full name (if an end user, their dealer ought to know the correct filename via the file sizes).

In the exact case mentioned (using Win10 Pro), it seems very odd that it couldn’t find the most critical file. Does Receivables.exe actually exist in the folder? If not, that is the reason for the message. If the file does exist (without any other intervention), then some type of caching may have played a very weird & unsettling effect (though extremely rare, given the number of Win10’s now out there, let alone that is my main test machines).

I suppose the other possibility (& perhaps more likely, though I have never encountered it) is that if he used the actual SP install, then it would have “Smart-Patched Receivables.exe) and if anything hung that up, the Recivables.exe file may have been temporarily renamed, & thus would be missing.

If you want us to pursue, we need:

1. Dir of Softrak\Receivables (or Ledger)
2. Dir of softrak\system
3. Do a Chksys and give us a Snapshot
4. The type of server they are using
5. What anti-virus is in use

Since this is sporadic, I'd rather not spend a ton of time figuring out what's going on, but perhaps we could gather what was the cause of the message (given R&D's list of possibilities above) and that would help us track it down.
_________________________
Andrew Bates