Acrobat Distiller 6 OLE Automation Issue with Non-Admin User

[Mike_Grice@adobeforums.com]

We're creating a PDFDistiller object (ACRODISTXLib.PdfDistiller) in a VB6 project using Acrobat Pro 6 and at the line in the code that creates the new object (Set AcroDistiller = New ACRODISTXLib.PdfDistiller), if the user is logged in as non-admin, we get: Error 429, ActiveX component can't create object.

I've tried CreateObject with the same error and GetObject pointing to the acrodist.exe and received a different error (432, Filename or classname not found during automation operation).

If the user is logged in as admin it works fine. If we use Acrobat 7 or 8, it works fine with both user types.

We've compared registry GUIDs for the class object and both user types have identical reg settings.

Does anybody have any idea how to correct this?

Thanks,
Mike Grice

[Leonard_Rosenthol@adobeforums.com]

Given that works correctly in Acrobat 7 or 8, I would have to say that it was a bug in that old version of the software that was corrected.

So the solution is to use modern versions of the software.

[Mike_Grice@adobeforums.com]

Thanks but that's not a solution when 100s of people from various companies are using anything from Acrobat version 5 and up.

[PDL@adobeforums.com]

If it's a bug in the software, there will be no solution.

Acrobat 6 is EOSL - End of Service Life. Adobe will be producing no more updates, patches or fixes for Acroabt 6 or older (this is stated on their website, see the support section).

If it's in 6 and it's a bug, they won't be fixing it so you need to advise your customer of it and live with it, or have them upgrade to a version that doesn't have the bug in it.

[Leonard_Rosenthol@adobeforums.com]

I believe that the number of people running Acrobat 6 today is bordering on 0, as it was a pretty poor release of the product. In addition, Adobe no longer officially supports it (or earlier) versions.

So I don't really know what you are looking for...

[Mike_Grice@adobeforums.com]

In some instances of a problem that might be similar to this, a solution might be with a change in the registry or the re-registering of a COM DLL. That was what I was hoping to find here.

Thanks