keimpe
asked on
Access Report won't print on shared printer (error 2212) unless I reboot
Dear experts,
this may very well be a network question, but I'll ask it here first. Every couple of minutes my Access reports refuse to print on a shared printer that's on another computer (all WXP in a W2K domain network). The report gives error 2212 and fails.
The shared printer on the other PC is still functional, but on the PC where I want to run the report from, the shared printer in control panel says "opening" instead of "ready". I am unable to print a test page.
If I reboot the workstation running Access and try again, it works (also printing test pages works again). After a couple of minutes it starts failing again.
Your suggestions are much appreciated!
Kind regards,
Keimpe Wiersma
this may very well be a network question, but I'll ask it here first. Every couple of minutes my Access reports refuse to print on a shared printer that's on another computer (all WXP in a W2K domain network). The report gives error 2212 and fails.
The shared printer on the other PC is still functional, but on the PC where I want to run the report from, the shared printer in control panel says "opening" instead of "ready". I am unable to print a test page.
If I reboot the workstation running Access and try again, it works (also printing test pages works again). After a couple of minutes it starts failing again.
Your suggestions are much appreciated!
Kind regards,
Keimpe Wiersma
1.Go to printer setup on WinXP and make sure the network priniter is your default printer.
2.From the Access Command Menu, Select tools>options>general tab>default db folder and make sure that it shows the mapped network drive path or the UNC path.
3. for the report you trying to print, go to file>page setup on access command menu and make sure it shows print to default printer.
2.From the Access Command Menu, Select tools>options>general tab>default db folder and make sure that it shows the mapped network drive path or the UNC path.
3. for the report you trying to print, go to file>page setup on access command menu and make sure it shows print to default printer.
ASKER
Thanks for the quick response. Drivers should be OK. The problem is occurring on several workstations.
And I can't set the shared printer as default on the machines attaching to it, because Access is making them default printer for one specific report on-the-fly. Or could this 'making-a-shared-printer-d
Perhaps (if there are no more suggestions) I should reinstall those printers.
And I can't set the shared printer as default on the machines attaching to it, because Access is making them default printer for one specific report on-the-fly. Or could this 'making-a-shared-printer-d
Perhaps (if there are no more suggestions) I should reinstall those printers.
Have you tried a ping test? If printer is on STATION1 and STATION2 says "Opening", try this on STATION2.
Start/Run CMD
PING STATION1 /t
Does it say something to the effect of "Reply" or "Request time out"?
This doesn't sound like the cause is from Access changing the default printer. I've used code like that before too - it should not hurt the original printer an any way (assuming it's just changing the default printer).
The ping test will help lead into which network problem you're having (169 IPs for example from lack of DHCP or static IPs).
Also - check Event Viewer on both machines. You might find a good reason there.
-Chad
Start/Run CMD
PING STATION1 /t
Does it say something to the effect of "Reply" or "Request time out"?
This doesn't sound like the cause is from Access changing the default printer. I've used code like that before too - it should not hurt the original printer an any way (assuming it's just changing the default printer).
The ping test will help lead into which network problem you're having (169 IPs for example from lack of DHCP or static IPs).
Also - check Event Viewer on both machines. You might find a good reason there.
-Chad
How many users do you suspect use the shared printer machine (STATION1) before your report fails on STATION2?
Try a DOS command
NET CONFIG SERVER
Perhaps it's an XP Pro workstation concurrent connectivity limit issue.
-Chad
Try a DOS command
NET CONFIG SERVER
Perhaps it's an XP Pro workstation concurrent connectivity limit issue.
-Chad
ASKER
Thanks for all the suggestions so far - I haven't been able to try them out yet, but will report back if I can.
I may however, have accidentally solved the problem: there was one particular Access Form requesting SQL Server data that took ages to load. I then changed the Access query into a SQL Server view and now it takes one second. It seems this has also made the error 2212 go away (knock on wood).
If it stays away for a day or two more, I guess this network load was the problem and speeding up the query was the solution.
Still, I find it hard to believe that I'm the only one on experts exchange that's been experiencing this particular problem. Anyone out there with the same problem??
I may however, have accidentally solved the problem: there was one particular Access Form requesting SQL Server data that took ages to load. I then changed the Access query into a SQL Server view and now it takes one second. It seems this has also made the error 2212 go away (knock on wood).
If it stays away for a day or two more, I guess this network load was the problem and speeding up the query was the solution.
Still, I find it hard to believe that I'm the only one on experts exchange that's been experiencing this particular problem. Anyone out there with the same problem??
I'm glad thenelson asked about "Is it just the Access report that causes the printer to hang? Or will other software cause it to hang?" - that helped with the response - "The problem is occurring on several workstations.".
This helped me with my post. Although I'd like part of the points, it doesn't sound like puppydogbuddy or my comment helped with resolving the issue.
Overall it sounds like he solved it himself. I'm not sure how much, if any of the additional comments helped him solve it himself.
I'm ok all of the points retract back to him (or get dispersed).
-Chad
This helped me with my post. Although I'd like part of the points, it doesn't sound like puppydogbuddy or my comment helped with resolving the issue.
Overall it sounds like he solved it himself. I'm not sure how much, if any of the additional comments helped him solve it himself.
I'm ok all of the points retract back to him (or get dispersed).
-Chad
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The control panel saying "opening" instead of "ready" would point to a problem with the driver. Check for a never version and reinstall it.