Computer freezes when printing from Adobe Reader 6.0

Chiz

Chiz

Chiz

Soldato
Joined
2 Nov 2002
Posts
3,304
Location
Aberdeen
Windows Professional 2000, Service Pack 4
Adobe Reader 6.0

I am having problems printing PDF's.

Whenever this is attempted the computer hangs.

This is evident over various computers on our network.

I have managed to close ArcoRD32.exe, which then allows the PDF to print, but this isn't really a solution, and isn't to practical.

A clean install of Reader doesn't seem to solve the problem as it comes back.

This is a wierd one, and i have no idea why this happens!
 
I think that is the next step to be honest. I was just wondering if there was a solution without rolling out a new version of Reader.
 
I had this problem at a company I visited on one of their PCs.

Try updating Adobe Reader from the 'Check for updates' failing that, I installed Adobe Reader 5.0 which solved the problem. They needed a quick fix.
 
I've seen a fairly similar issue with Acrobat Professional 6, although that was when printing to PDF using distiller. It turned out that Acrobat needed write access to a printspool registry entry which, as a non-admin user, it didn't have.

So to troubleshoot this issue:

1. See if it works as an admin user
2. Run sysinternals tools such as Filemon, Regmon and Process Explorer to see if there are any failures/ processes becoming stuck
3. Try amending file rights/ registry permissions and see if it now works as a non-admin user.

Its probably also worth mentioning that Acrobat 6 is a bit long in the tooth now, so it may be worth considering an upgrade
 
The problem isn't user specific as many users have reported this as a problem.

The initial problem is when the users try to launch a PDF from a web based application. This then freezes, while still running the system file.

When trying to open a PDF afterwards, the application fails to load. This is due to the system file already running. This can easily be sorted by closing the runing app, which i think is AdobeRd32.exe (Or close enough).

That i guess is a simple solution, but not a permanent one, and also doesn't explain why this has just started to happen.

There could be a potential issue with the latest windows update though, as this was installed around about the time as the error (or so one user says).

Also by accesing the default settings within Reader, (edit > preference, selecting 'Internet') then unticking the 'Open in browser' box may also supply a solution. This has not been tested though and neither has the previous suggestion.

This is the path i'm taking, but i'm yet to get the users to test this..

Upgrading to the latest versions isn't an option just now, so we can forget about that obvious, and most probable solution.

Any more info would be greatly appreciated!
 
M0KUJ1N said:
So to troubleshoot this issue:

1. See if it works as an admin user
2. Run sysinternals tools such as Filemon, Regmon and Process Explorer to see if there are any failures/ processes becoming stuck
3. Try amending file rights/ registry permissions and see if it now works as a non-admin user.
Click to expand...

1. This cannot be tested as such because the problem isn't consistent, therefore granting admin rights isn't feasible. I do not think this is the problem though as 90% of users have not reported a problem.
2. We do not have these tools on our network at the momment. I have installed all three though, but not sure how i'd install and run them on a hanging system.
3. File rights and permissions are all in place, and are working correctly.
 
Seen something very similar before.

On the machines where it is not working correctly, check which network printers are installed, you may find some are installed which are no longer live. If there are any decommission printers installed still on a workstation in question, delete them and try again.
 
It's got no relation to the printer, or print spoolers as this isn't a consistent problem, and can happen once in 6 attempts, therefore eliminating that problem.

Along with that, the users have had only the necessary printers installed.

No reports of the problem though in the past couple of days, so again, unable to attempt any of the fixes brought up previously.
 
You must log in or register to reply here.
Back
Top Bottom