Archive for the ‘Packaging’ Category

I’ve recently been dealing with a problem with Adobe Acrobat Pro where the Adobe PDF Printer won’t install and work correctly. I’ve worked through a number of steps and have gotten the driver and printer to the point where it will install and print to any locally accessible location (not a network location).

Just like a bunch of others, installing Acrobat completed successfully and the program works, but the Adobe PDF printer isn’t available in other programs. I tried some of the standard steps, adding the printer manually, using the printUI.dll command line options, but I’d still get an error like Element not found

Reading the AdobePDF.inf file and finding that it required core printer driver {D20EA372-DD35-4950-9ED8-A6335AFE79F1} and finding that it was missing led me to track down missing or different items on a computer that was working. I gather that the Adobe items listed below would be delivered by the installation if the Core Printer drivers were correctly in place. I should note that some of the files copied in the first step were Adobe files, but some are PS* files. Here is a list of the files copied in that step

Mode LastWriteTime Length Name
—- ————- —— —-
-a— 23/09/2012 5:43 PM 66 ADGELP.INI
-a— 23/09/2012 5:43 PM 55432 AdobePdf.dll
-a— 23/09/2012 5:43 PM 26768 AdobePDFUI.dll
-a— 28/06/2015 9:50 AM 20292 ADPDF9.BPD
-a— 23/09/2012 5:43 PM 28058 ADPDF9.PPD
-a— 23/09/2012 5:43 PM 39048 ADREGP.DLL
-a— 23/09/2012 5:43 PM 1294472 ADUIGP.DLL
-a— 22/08/2013 10:31 PM 2899968 PrintConfig.dll
-a— 5/12/2014 3:01 PM 885248 PS5UI.DLL
-a— 19/06/2013 12:44 AM 26038 PSCRIPT.HLP
-a— 19/06/2013 1:09 AM 1062732 PSCRIPT.NTF
-a— 5/12/2014 3:01 PM 649216 PSCRIPT5.DLL
-a— 19/06/2013 1:09 AM 1293180 PSCRPTFE.NTF
-a— 19/06/2013 1:09 AM 5561 PS_SCHM.GDL

The steps I’ve undertaken to get a functional Adobe PDF printer created are:

1. Copied Adobe files from “C:\Windows\System32\spool\drivers\x64\3” on a working PC
2. Copied adobepdf.inf_amd64_8372a4bb5d1330af.cab from “C:\Windows\System32\spool\drivers\x64\PCC” on a working PC
3. Added registry keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows x64\CorePrinterDrivers\{D20EA372-DD35-4950-9ED8-A6335AFE79F1}]
4. Added registry keys in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\Adobe PDF Converter]
5. I tried restarting the Print Spooler, but could only add the printer manually, not using the rundll32 printui.dll,printUIEntry commands
6. Added the registry keys in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\Adobe PDF]
7. Restarted print spooler

The two main things I’m not sure about are why the Core Print Drivers weren’t installed and functional and why a command like rundll32 printui.dll,printUIEntry /if /b “Adobe PDF” /f”C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Xtras\AdobePDF\AdobePDF.inf” /r “Documents/*.pdf” /m “Adobe PDF” didn’t work automatically.


Read Full Post »

I’ve been seeing these errors with a range of App-V sequences installed to Windows 7 PCs with App-V 5.0 SP2 installed. Trying both Hotfix 2 and Hotfix 5 didn’t make a difference.

Troubleshooting info on the 0x5 indicated Access Denied and using procmon, this ultimately led back to Access Denied errors when trying to CreateFile in C:\ProgramData. Granting Domain Users special permissions on This folder only to Create files / write data appears to have resolved this.

Read Full Post »

Visual C++ 1603 errors

A number of applications including Acrobat Pro, ArcGIS, Visual Studio and AutoCAD can at times fail with error 1603. It’s been a little while since I saw this, but the symptoms are something like:

  • Software installations on the machine fails without a clear error message (In our case it was: “Micro​soft Visual C++ 2005 Redistributable Failed Installation aborted, Result=1603”). (From OpenLM Software Licensing Blog)

The resolution for this is to set the Registry Size Limit to “unlimited” and then reboot:

Value: 0xffffff (4294967295)

Read Full Post »

As ever, Adobe refuse to make things straight forward in installing their Creative Suite. To their credit, the Adobe Application Manager Enterprise Edition (AAMEE) is getting better, but there’s still this tricky point that you need to install help separately to the main installation.

What happens si you step through AAMEE creating an installation and you wind up with 2 folders, Build and Exceptions. The Build folder contains the stuff you selected in the install and an msi to execute. So far, sounds good. However to have Help available via the menus you’ll need to install AIR and then install the Help content. Once you’ve got AIR installed, you can get your content installed by running something like:

“C:\Program Files\Common Files\Adobe AIR\Versions\1.0\Adobe AIR Application Installer.exe” -silent -eulaAccepted “%PATH%\32\Exceptions\AdobeHelp\AdobeHelp.air”

What happens with the Help content is that it doesn’t download to a single location on the machine, but goes into the user’s profile in a folder called “%APPDATA%\chc.4875E02D9FB21EE389F73B8D1702B320485DF8CE.1”. You can try co-ordinating this centrally, but it may not function correctly (as in display anything) for all CS programs.

Read Full Post »

So you’ve got a problem with your app running on Vista or Windows 7? It might run fine on XP or as an admin or something similar, so that being the case, often you can shim it up to make it work.
What you’ll want to do is:

  1. Install Microsoft’s Application Compatibility Toolkit, currently at v5.6
  2. Install the Application Verifier
  3. Install your app, shortcut, whatever it is you want to make work
  4. Run the Standard User Analyzer (SUA) from the Developer and Tester Tools menu
  5. Step through running your app, doing whatever you do to test, then close it down and have a look at what it generates

Read Full Post »

Inno Setup unpack

A couple of weeks ago I came across a vendor setup I was trying to install silently. I identified this as an Inno Setup by finding the uninstall command line in the registry being unins….exe /SILENT.

So trying the /SILENT switch worked on the installation worked fine except that the nested MDAC 2.6 installation wasn’t using an unattended switch, so it would still require a click. I tried installing MDAC beforehand, but the installation still behaved the same waiting for a click. I could have captured the installation of MDAC along with the rest of the installation, but I prefer to install this type of standard prerequisite with the vendor’s standard setup, so I attempted to find some way to dig into the Inno Setup.

I found an Inno setup unpacker called innounp, which extracted the installation. I also downloaded the latest version of InnoSetup so that I could view and compile the installation. What I ended up doing was finding the prerequisites in the installation, grabbing the files and finding the silent install commands and then removing them from the installation. I compiled the installation then, but still got a few more errors, in particular with:

  • InnoSetupVersion=5.1.7 (which I removed)
  • and a couple of duplicated file copies.

Once I removed all of these, I recompiled the installation.

I could then:

  • install the prerequisites (Jet, MDAC, VB6)
  • start a SetupCapture of my recompilation
  • run my recompilation
  • close capture

And then the capture held only the program installation that I was interested in.

Read Full Post »

Java 6 Runtime installations will automatically upgrade older Java 6 version through the beauty of the msi upgrade table. However, if you need to install a specific Java version, Sun has some documentation.

Basically run the setup.exe with the parameter STATIC=1 and the install will generate a different msi that will install a standalone version. You can then use your standard installation of other versions (extracted or otherwise) for a different update version.

Read Full Post »

Older Posts »