Posted by Barbara Brazil on March 27, 2017 at 08:34:53:
In Reply to: Re: CA Host crash...> posted by Tom fulton on March 25, 2017 at 12:53:33:
This is what I was wondering if we'd see. We first came across this a few months ago but apparently it's been an issue since the beginning of Comet32. Printing from a CA client's background partition can cause Comet to get into a loop reporting E31s. In our tests it seems this happens when using the # printer. This is the reason in REL 17.00 that we disallowed selection of a # printer for text doc unspooling in background from DocMgr.
In your case it seems the program that starts this process is called WWMP. Does that make sense? Can you determine if a # printer is used? If so, at least for now, is it possible they could use a network printer instead? It would be helpful to know if that solves the problem.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.