MICROS 3700: Autosequences And Reports: Printing: An Error Has Occurred

[Kniteschaed]

For whatever reason my autosequence print job decided to stop working over the weekend.
From autosequences and reports all I see is: "Sequence # 9000001 Step # 2An Error Has Occurred. Status="
From the 3700d log it appears that it is trying to print to an "invalid printer" - though nothing has changed with our printers...

This is an excerpt from my 3700d log after I tried to manually run the autosequence:

Mon Jun 11 05:29:47 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Sequence # 9000001 Step # 1 <REPORT> |
Mon Jun 11 05:29:47 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Daily SYS Sales Detail2 |
Mon Jun 11 05:29:47 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Date Range = 6/10/2018 to 6/10/2018 |
Mon Jun 11 05:29:47 2018 | MCRSLDC | Autosequence.dll | 0 | WaitForSingleObject( g_hmutex, 60000 ) |
Mon Jun 11 05:29:47 2018 | MCRSLDC | Autosequence.dll | 0 | Continuing After Waiting For Mutex [g_hmutex]. |
Mon Jun 11 05:29:47 2018 | MCRSLDC | Autosequence.dll | 0 | Template Filename = D:\MICROS\Res\Pos\Reports\Custom\sys_102c.rpt |
Mon Jun 11 05:29:48 2018 | MCRSLDC | OCBServer | 0 | CDeviceInterface:eviceThread() : Failed to reconnect to device 1 |
Mon Jun 11 05:29:50 2018 | MCRSLDC | CrystalEngine | 0 | Exception Caught - Invalid printer specified. sys_102c {22D10685-2DBE-480D-A6A0-4FD1B304B5D5}.rpt |
Mon Jun 11 05:29:50 2018 | MCRSLDC | CrystalEngine | 0 | Could not print report. |
Mon Jun 11 05:29:50 2018 | MCRSLDC | ReportExporter | 0 | Exception Caught - Could not print report. |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | ***ERROR*** Msg from PrintEngine: |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | ***ERROR*** |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Sequence # 9000001 Step # 1An Error Has Occurred. Status= |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Autosequence # 9000001 Step # 1 Failed |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | ReleaseMutex( g_hmutex ) |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | Step completed. |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | Autosequence 9000001 step 1 of type R has completed in 3 seconds. |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | -------------------------------------------- |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Sequence # 9000001 Step # 2 <REPORT> |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Return/Void Reason Code |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Date Range = 6/10/2018 to 6/10/2018 |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | RVC Start Range =1 End Range =9999999 |
Mon Jun 11 05:29:50 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Object Start Range =1 End Range =9999999 |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | WaitForSingleObject( g_hmutex, 60000 ) |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | Continuing After Waiting For Mutex [g_hmutex]. |
Mon Jun 11 05:29:50 2018 | MCRSLDC | Autosequence.dll | 0 | Template Filename = VoidReason.RPT |
Mon Jun 11 05:29:52 2018 | MCRSLDC | CrystalEngine | 0 | Exception Caught - Invalid printer specified. VoidReason {6206D476-7489-4F57-A90F-45AEBD0AC18F}.rpt |
Mon Jun 11 05:29:52 2018 | MCRSLDC | CrystalEngine | 0 | Could not print report. |
Mon Jun 11 05:29:52 2018 | MCRSLDC | ReportExporter | 0 | Exception Caught - Could not print report. |
Mon Jun 11 05:29:52 2018 | MCRSLDC | Autosequence.dll | 0 | ***ERROR*** Msg from PrintEngine: |
Mon Jun 11 05:29:52 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | ***ERROR*** |
Mon Jun 11 05:29:52 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Sequence # 9000001 Step # 2An Error Has Occurred. Status= |
Mon Jun 11 05:29:52 2018 | MCRSLDC | AUTOSEQEXEC.EXE | 0 | Autosequence # 9000001 Step # 2 Failed |
Mon Jun 11 05:29:52 2018 | MCRSLDC | Autosequence.dll | 0 | ReleaseMutex( g_hmutex ) |
Mon Jun 11 05:29:52 2018 | MCRSLDC | Autosequence.dll | 0 | Step completed. |
Mon Jun 11 05:29:52 2018 | MCRSLDC | Autosequence.dll | 0 | Autosequence 9000001 step 2 of type R has completed in 2 seconds. |

Tried restarting the server - no change.
Tried restarting some of the services - no change.
Wondering if it could have something to do with the database?

Any thoughts/advise would be greatly appreciated.

 

[Wildbar]

Find your auto sequence 9000001 and on the print step try override default printer.
Or better yet just print to a pdf file taht you can print if you need to.

 

[Kniteschaed]

@Wildbar
I tried overriding the default printer in the autosequence - no change. Still errors out.
I do have a separate sequence that successfully produces a PDF - so I was able to get the documents that I needed...
That being said - I would like to "fix" this printing issue.
My Finance department relies on this paperwork to be waiting for them every morning.

 

[Wildbar]

We have the reports printed to pdf, , date stamped, backed up off site and emailed to whoever needs them through the auto sequence schedluer. Does not matter if printers change or go wonky like they always seem to do with 3700.
You may need to reinstall the printer.