Archive for the 'Support' Category

Adobe Acrobat 8 Serious Error - Windows Terminal Server

I’m not about to go into all of the 10,000+ possible things you can do to attempt to fix whatever is causing this, including, but not limited to, firing a semi-automatic at your server. But you shouldn’t do that, since it’s not your hardware’s fault that Adobe Acrobat can’t work right. You could, however, go skeet shooting with the Acrobat CD! I’m only going to share what we did that seems to work for us.

To clarify our configuration:

Windows 2003 Server x86 Terminal Server
Adobe Acrobat Professional 8.1 (with 8.1.3 update)

We have been fighting the dreaded “Serious Error” message in Acrobat for a few months. It all started when we changed the processors in one of our terminal servers. The error I’m referring to is the one in Adobe Acrobat where it suddenly hangs for some unknown amount of time and then crashes with a “Serious Error has occurred” message.

My system administrator and I searched and searched with no luck in the Adobe forums. We tried it on a clean terminal server install, we tried messing with permissions, filemon, procmon, etc.

Finally, I had noticed a pattern, in the registry, HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\8.0\AVGeneral has a bActivated and bLastExitNormal which was setting itself to 0 (false). I think Acrobat was thinking it wasn’t actived, and since my users weren’t admins, they key must not have been able to rewrite itself. But this key only changed when Acrobat locked up and gave the serious error. If you killed the acrobat.exe process before the error, the key stayed. Once we remotely changed everyone’s keys, it worked, until we started adding more users who didn’t have this key.

Finally, we thought we had everyone, but we received the error again. We went through and fixed them all again. This time, I felt like the only thing “patch”-related we didn’t do was this licensing service patch from Adobe: http://www.adobe.com/support/downloads/detail.jsp?ftpID=3750.

We also created a login script addendum as follows:

AdobeAcroFix.bat

REGEDIT /s \\orourke.local\sysvol\orourke.local\scripts\Acro8RegFix.reg

AdobeAcroFix.reg

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\8.0\AVGeneral]
 "bLastExitNormal"=dword:00000001
 "bActivated"=dword:00000001

So in summary, here’s what we did:

  1. If on terminal server run change user /install from the command line
  2. Install Acrobat Professional 8
  3. Reboot if necessary
  4. Make sure/update to 8.1.3
  5. Reboot if necessary
  6. If on terminal server run change user /install from the command line
  7. Install the Adobe Licensing patch, following the instructions exactly at the bottom of the page
  8. Reboot (if you followed the directions)
  9. On your DC, or local machine, setup the above batch file and registry file.
  10. Cross your fingers!

I sincerely hope this helps some of you suffering for as long as we did (or longer).

Exchange 2007: Corrupt MMC Queue Viewer

This is to help out anyone that receives the following error with Microsoft Exchange 2007. When you are in the Exchange Management Console, and click Toolbox and Queue Viewer, the following error is displayed:

MMC cannot open the file {Exchange Install Folder}\Bin\Exchange Queue Viewer.msc.

This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file.

To resolve, assuming you have the proper authority, delete the following file:

C:\Documents and Settings\{yourusername}\Application Data\Microsoft\MMC\Exchange Queue Viewer

Support: Can’t Connect to Printer

I was trying to install my networked color-laser printer on my daughter’s laptop this weekend. She is running Vista Ultimate, my printer is a Dell 3110cn Color Laser, and it is connected and shared via Windows 2003 R2 server.

My laptop connected to the printer fine as a network printer, but her computer kept throwing the following exception:

Windows cannot connect to the printer. Operation could not be completed (error 0×000003e3).

The resolution was the following:

  1. Install the drivers for the printer on the computer
  2. Start button > Printers > Add Printer
  3. Add a local printer
  4. Create a new port > local port
  5. Enter the name to the shared printer. If the name has spaces, rename the printer’s share name on the host/server.
  6. Choose the correct drivers that were installed (from step 1)
  7. If prompted, choose to use the existing driver
  8. Name the printer for the local machine
  9. The rest of the steps are self-explanatory

I hope this helps any who struggle with this annoyance.