G
Guest
We have been experiencing an intermittent problem using the Access XP runtime
with an HP4650 printer on a Windows 2003 Terminal Server.
The problem occurs if the HP4650 is set as the default printer and we try
and print or preview any report that is set to go to the default printer.
What happens is that we get error 2213, 'There was a problem retrieving
printer information for this object. The object may have been sent to a
printer that is unavailable.', and the report does not appear or print.
If the default printer is changed to an HP4600 or some other printer then
the problem does not occur. The problem is intermittent in that sometimes
printing will work for the whole duration of the session. We have changed the
printer driver used for the printer from an HP4650 to an HP4600 driver and
that seems to work fine.
The user it occurs for is a member of the Administrators group and we have
deleted and recreated their account to no effect. All of the printers have
been setup as local printers on server and the mapping of client printers has
been disabled on the server.
We have tested using Access 2003 instead and that works fine.
Are there any known problems with Access XP and certain printer drivers? If
not, then how is it that Access 2003 does not have any problems?
with an HP4650 printer on a Windows 2003 Terminal Server.
The problem occurs if the HP4650 is set as the default printer and we try
and print or preview any report that is set to go to the default printer.
What happens is that we get error 2213, 'There was a problem retrieving
printer information for this object. The object may have been sent to a
printer that is unavailable.', and the report does not appear or print.
If the default printer is changed to an HP4600 or some other printer then
the problem does not occur. The problem is intermittent in that sometimes
printing will work for the whole duration of the session. We have changed the
printer driver used for the printer from an HP4650 to an HP4600 driver and
that seems to work fine.
The user it occurs for is a member of the Administrators group and we have
deleted and recreated their account to no effect. All of the printers have
been setup as local printers on server and the mapping of client printers has
been disabled on the server.
We have tested using Access 2003 instead and that works fine.
Are there any known problems with Access XP and certain printer drivers? If
not, then how is it that Access 2003 does not have any problems?