Printing from Space Manager causes Windows Print Spooler SPOOLSV.EXE to terminate
Hint Ref: 020810030012
Hint Date: 03/10/2008
Hint Details:
PROBLEM:
When printing from Space Manager to some specific printers (low end HP LaserJet or Xerox 6115 Multi Function) the Printer Spooler service can unexpectedly terminate. In addition, some document templates will still print correctly, but once a problem template document has been sent to the print queue, the service repeatedly terminates every time it is restarted and the print queue is accessed.
SOLUTION:
The issue would appear to be that some of these printers with an old printer driver can have trouble with the contents of templates with large SQL pipelines or complex graphics on the design. If an update is not available for the printer driver in use, then a solution is usually to find the SQL, section of SQL or design graphic that is causing the issue and amending or remove it. In the case of SQL queries, sometimes using the CAST as CHAR() function on LISTs can solve the issue.
NOTE: In order to correct the issue and amend the template, the current print queue job must be deleted; however this can be troublesome as the Print Spooler must be running to do so. We have found that if you delete the two print files from the directory:
C:\WINDOWS\system32\spool\PRINTERS
You can then delete the print job from the queue.
(Please Note: This procedure can be destructive and should only be used by Advanced Users who know what they are doing. RADical Systems (UK) Limited or its Partners cannot be held responsible, in anyway, for any consequence of following any advise in this or any other Hint, or by using any other Database Function, Procedure or SQL command. Responsibility resides solely with the user.
IT IS HIGHLY RECOMMENDED THAT A FULL AND VALID SPACE MANAGER DATABASE BACKUP IS TAKEN AND VERIFIED AS VALID BEFORE MAKING ANY CHANGES TO THE DATABASE.)