S
Syed S. Ahmad
All
Superior Termite receives the following error on their server when they try
to print Reports from Access:
“There was an error found when printing the document "R_orderCUSTOMER" to
IP_192.168.20.137.â€
The printer in question is a HP LaserJet 4200 and the server is SBS2000.
They also use a Dymo LabelWriter 300 to printer labels, which is also
installed on the same server.
When I first saw the error, one of the first things I noticed on the
printer’s LCD was an message stating that it needs paper for the label tray
(Tray 1). This printer only has two trays and the client doesn’t use the
manual feed, just Tray 2 (plain paper). I set the Manual feed to “Not
Installed†in the Device Settings and everything seemed to work fine. The
error returned and after doing more research I ran into this MS KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816924. I tried the
suggested work around as the server was already upgraded to Service Pack 4
and again this temporary fix seemed to help. The problem has crept up again.
I'm starting to think that it is an issue with MS Access as the problem only
exists when a Report from the said Access database is printed. Any thoughts?
Thanks.
Superior Termite receives the following error on their server when they try
to print Reports from Access:
“There was an error found when printing the document "R_orderCUSTOMER" to
IP_192.168.20.137.â€
The printer in question is a HP LaserJet 4200 and the server is SBS2000.
They also use a Dymo LabelWriter 300 to printer labels, which is also
installed on the same server.
When I first saw the error, one of the first things I noticed on the
printer’s LCD was an message stating that it needs paper for the label tray
(Tray 1). This printer only has two trays and the client doesn’t use the
manual feed, just Tray 2 (plain paper). I set the Manual feed to “Not
Installed†in the Device Settings and everything seemed to work fine. The
error returned and after doing more research I ran into this MS KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816924. I tried the
suggested work around as the server was already upgraded to Service Pack 4
and again this temporary fix seemed to help. The problem has crept up again.
I'm starting to think that it is an issue with MS Access as the problem only
exists when a Report from the said Access database is printed. Any thoughts?
Thanks.