Autosequence Reports Not Printing

[GreekBeak]

I installed a new printer, made it the default printer in Windows as well as in Micros but the autosequence reports just won't print. I've made changes and rebooted the system to no avail. Before I deleted the old printer Micros would throw an error whenever the autosequence was suppose to print so somehow it still wanted to use the old printer. If you re-print the same autosequence report it prints just fine on the new printer.

Yesterday I went in and deleted the printer in Windows as well as pulling any instances of it from the registry. Now Micros doesn't throw an error but it still doesn't print. I even went into the autosequence steps and assigned an over ride printer to be the new printer and still no luck on any of the 3 autosequence reports.

All the posts I found just said to change the settings and make sure you reboot the system but this guy is being stubborn and won't print!

 

[DrZogg]

After changing the System printer in micros, a reboot is needed. Not a reload of the DB

 

[GreekBeak]

I did reboot the system as in shutting down Windows, powering off, and restarting the computer. I'm not sure where you got that I was reloading the DB

 

[pmegan]

Take a look in the 3700d log and windows event viewer. There should be errors in one of those places that should point you in the right direction.

 

[GreekBeak]

I didn't see any events in the log to point me to what happened but we just did the following and it appears to have worked (even without a reboot).

1) Went into the registry and navigated to:

[HKEY_USERS\S-1-5-21-484763869-436374069-1343024091-500\Software\Microsoft\Windows NT\CurrentVersion\Windows]

copied the printer instance and then navigated up to:

[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\Windows]

and pasted the printer there.

I was on the phone when the printer got installed in Windows and since they were logged in under the Administrator name the printer was installed for that user. Possibly the default installation for that HP OfficeJet350 was not installed for all users and only the administrator or perhaps the Auto Sequence reports run under a different user than what the system boots up with (which I'm fairly certain is Administrator).

 

[DrZogg]

All micros printers, devices, licencing, interfaces etc are written to registry when teh DB is loaded. Manual entry of registry is generally futile as settings are rewritten on the next startup or DB reload. Look in the DB logs.

 

[jd11111]

What is the printer? We have problems with certain printers (usually Sharp) not working with scheduled autosequences, like EOD. However, the same printer will print fine if you manually execute the autosequence.

 

[GreekBeak]

The actual printer he's using now is a OfficeJet L7580 but the drivers loaded in Windows are for an OfficeJet 350 since finding drivers for current printers for WinNT is next to impossible.

The registry changes we made are more of a Windows "fix" than monkeying with Micros. All the autosequence reports have been printing since we made this change but according to DrZogg the real test will be when we reboot the server on Sunday and confirm that the autosequence reports still print.

I'll also try to confirm what user is running each service in WinNT to add to this thread for reference.

 

[POSPro]

Every time you install or use a new printer in Micros, you need to log in and out as Microssvc in order to "capture" the new printer in Autosequences- for versions older than 4.x.

While logged in as Microssvc, go to Control Panel | Printers and make sure the default printer is set properly. Then log off.

This should work everytime without all of the above registry change.

 

[GreekBeak]

Thanks for the tip, to the best of my knowledge this hasn't been mentioned on this forum before. Looks like this user is created during the Micros install, is there a password for this user?

 

[pmegan]

Try microssvc

 

[GreekBeak]

yes, that is the correct password for microssvc, thanks!