Iman v3.2 Sage300PrintSpooler (1 reply)
I have a number of clients who use iman to print documents like orders/invoices from Sage 300. In these situations we get one of two errors: Method of Object call failed, or something that indicates the Sage300printspooler has blown up midway through running the job. One of my clients did some digging and has resolved the issue (i.e. her job was blowing up daily and it's now been 2 weeks without error). She did 3 things on the iman virtual: 1)Turned of DEP for the Sage 300 print spooler 2) Ran System File Checker from a DOS command to fix any registry corruption issues 3)Ran DISM from a DOS command to fix any windows update issues. Please see the attached zip file/word doc for details on this procedure. I don't know that this will fix it for sure for all of my client's, but I'm certainly going to try it for this one.
I have a client who only has a few jobs set up and those jobs aren't large. One of the jobs prints/emails invoices at 5:30 pm daily. Occasionally this job will blow up with this message: The Accpac data import incurred an unrecoverable error and is quitting. [Automation error: The remote procedure call failed.]
The client's IT team looked into it and found that it seemed to have to do with the Sage300printspooler.exe. Here is their commentary (and see attached screenshot)... Any ideas on how to stop this? Thanks! (P.S. - yes, we are working on getting an upgrade plan approved to move forward but with COVID, not sure how long that might take on the customer's side...)
IT Commentary:
The Yellow marked text lead me to a report Queue. It looks like this was not the first crash of Sage300PrintSpooler.
Yesterday 6:31:02 PM the Sage300PrintSpooler crashed
Faulting application name: Sage300PrintSpooler.exe, version: 2.1.0.0, time stamp: 0x590c38cc
Faulting module name: ntdll.dll, version: 6.3.9600.18821, time stamp: 0x59ba8666
Exception code: 0xc0000005
Fault offset: 0x0002addb
Faulting process id: 0x1474
Faulting application start time: 0x01d644362dad17e1
Faulting application path: C:\inetpub\wwwroot\IMan\bin\Sage300PrintSpooler.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 704bf178-b029-11ea-80ed-000c29449f98
Faulting package full name:
Faulting package-relative application ID:
On 6:31:04 PM the Windows Error Reporting Kicked in
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Sage300PrintSpooler.exe
P2: 2.1.0.0
P3: 590c38cc
P4: ntdll.dll
P5: 6.3.9600.18821
P6: 59ba8666
P7: c0000005
P8: 0002addb
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Sage300PrintSpoo_a779e4284c7581f6cfef1332a94a2810eafc71fa_6af3a7d5_0d18271a
Analysis symbol:
Rechecking for solution: 0
Report Id: 704bf178-b029-11ea-80ed-000c29449f98
Report Status: 4100
Hashed bucket:
I Also Checked the .WER Files (Windows Error Report) and got some detailt information about the Crash.
So it looks like the Sage300PrintSpooler.exe has a problem