Adobe DC: Cannot get custom protocol working

[craigw53659048]

Hi,

I have created an application that processes a custom protocol hyperlink, for example foo://test

I have added the protocol to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown\cDefaultLaunchURLPerms

tSchemePerms     version:2|shell:3|hcp:3|ms-help:3|ms-its:3|ms-itss:3|its:3|mk:3|mhtml:3|help:3|disk:3|afp:3|disks:3|telnet:3|ssh:3|acrobat:2|mailto:2|file:1|rlogin:3|javascript:4|data:3|jar:3|vbscript:3|foo:2

In my environment this works fine. Yet in some other environments it is not working.

Going through Process Monitor I can see that in my environment Adobe Reader DC is looking for the correct registry keys:

HKEY_CLASSES_ROOT\foo

(Default)     URL:foo

URL Protocol     <blank>

HKEY_CLASSES_ROOT\foo\shell\open\command

(Default)     "C:\Program Files (x86)\Foo.exe" "%1"

In the other environment, with the same version of Adobe Reader DC and the same registry keys set, Adobe does not look for the keys above and so never executes the program for processing the hyperlinks.

It seems that Adobe Reader is, in the non-working environments, treating the link as a http address.

Thanks in advance,

Craig.

NB: We are testing in 2019.010.20069

2019.010.20069

[Test Screen Name]

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0 is not the right place for Reader DC.

[craigw53659048]

Sorry, I copied it from my non-test machine which has Adobe Reader XI installed.

The key I am using is HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\cDefaultLaunchURLPerms

[BrabantseDelta]

Same problem here. Added the policy in registry entry but it is not working.

I am using reader version : 2019.008.20071

Any help would be appreciated.

In MS word it all works fine. Adobe reader does not open the custom protocol

[ls_rbls]

craigw53659048,

You said in your environment this works well and in another environment it doesn't

Can you describe what environment are you using your Acrobat with, and on  which type of environment(s) is this registry modification being used with?

Is this tested in only two different computers or over a network? What operating systems?

[ls_rbls]

I also forgot to add that in the non-working test environment, you might want to check if the default browser and mail applications are the same as the ones you are using in your environment that is currently working.

And see and compare if  the Trust Manager settings of your known-good working environment are different when you open the Trust Manager in the non-working environment

And which one is the default email client in the non-working environment, here:

And what are the Internet settings that are setup in the non-working environments:

[BrabantseDelta]

ls_rbls

I have the same issue. In windows 7 it works fine in Windows 10 I have problems opening the custom file protocol.

Both same version of Adobe Reader.

[ls_rbls]

See where the "Foo.exe" script is  located in your windows7:

Is it here:

"C:\Program Files\Foo.exe"

or in here:

"C:\Program Files (x86)\Foo.exe"

I am not very knowledgeable in batch scripting, python , JScript, vbscript, etc. but I am curious; did you updated your Java RunTime  in the win7 machine.

And did you checked if the script that is working in Windows10 should be modified or edited in anyway to make it work in Windows7 ?

[hgordon99]

The custom protocol handler only works for me if I make Internet Explorer the default browser. It doesn't work for me with Chrome or Edge. I'm on Windows 10 and Reader version 2019.012.20040.

[ls_rbls]

Try and run the windows 10 troublshooter for your custom protocol handler and see if by selecting an older version of windows environment just for that program coul resolve the issue. By reading you answer it is starting to look more like a 32bit ver 64 bit application conflict... but I may be wrong.

Neverthless, is the Internet Explorer that works with the custom protocol a 32bit or 64 bit version of IE? 

If it is a 32bit version of IE  just run the ttoubleshooter and select an older version of windows environment for your protocol handler program and do the same for the browsers that you want to test, and for the Adobe Acrobat .

[ls_rbls]

I have to clarify, when I said to run the troubleshooter I meant to goto settings (or  Control Panel) and run the Compatibility Mode Troubleshooter just for the application that is misbehaving.

Even though  Adobe Acrobat is inherently a 32bit application that has been tested to run in 64bit Windows family of operating systems,  the application may behave with newer updates that are now aimed to support 64bit only environments. That said, quite afew announcements has been published by Microsoft in regards of End-of-Support or End-of-Life for some products that were previously supporting 32bit applications such as Adobe Acrobat , for example.

Since the Adobe Acrobat was working before, we want to test an earlier version of Windows with it with the Compatibility Mode troubleshooter; this will reveal or rule out if the problem is actually related to  a bug in Adobe Acrobat (like many users are claiming) ; I suspect is more related to a 32bit vs 64 bit  compatibility issue rather than a bug