Creative Cloud Desktop app PAC file issue

Report · Jul 10, 2013

The Adobe Creative Cloud Desktop app doesn't seem to work if you have a PAC file specified in Internet Explorer - Error "No Internet Connection"

Log file: -

IMSLibHelper | | | 6096 | setting authproxy credentials in fetchAccessTokenForDeviceToken

OPM | | | 6096 | No Record found for the input fields in opm_getValueForKey

OPM | IMSLib_OPMWrapper | | | 6096 | Failed in getting value for key in OPMGetValueForKey domain:OOBE subDomain:ProxyCredentials key:ProxyUsername

OPM | IMSLibHelper | | | 6096 | Failed to get proxy user name from local db in getProxyCredentialsFromLocalStore

OPM | IMSLibHelper | | | 6096 | Failed to get proxyCredentials from local store in setProxyCredentialsForHTTPRequest

OPM | IMSLibHelper | | | 6096 | Failed in setting authproxy credentials in fetchAccessTokenForDeviceToken

OPM | HTTPConnector | | | 6096 | GetIEProxyInfo - No default proxy present on the user machine

OPM | HTTPConnector | | | 6096 | GetIEProxyInfo - autoconfig url on the machine is : (I've removed the address to the PAC file but it is here)

OPM | HTTPConnector | | | 6096 | GetIEProxyInfo - Failed to get proxy for the url, error:12006

OPM | HTTPConnector | | | 6096 | GetIEProxyInfo - proxy Url is

OPM | HTTPConnector | | | 2712 | WINHTTP_CALLBACK_STATUS_REQUEST_ERROR...

OPM | HTTPConnector | | | 6096 | The http request returned HTTP_Status:0 HttpCommunicator error:68

OPM | IMSLibHelper | | | 6096 | user has not selected 'Remember Me', proxy data is not saved in local store

OPM | IMSLibHelper | | | 6096 | Failed in HTTPRequest in fetchAccessTokenForDeviceToken

OPM | IMSLib | | | 6096 | Unable to generate accessToken while performing fetchAccessTokenForDeviceToken

OPM | IMSLib | | | 6096 | Invoking client callback function with response and status : 22

OPM | P7Native | | | 6096 | Proceeding with fetchAccessToken callback...

OPM | P7Native | | | 6096 | IMSLib returned error during fetchAccessToken callback function, errorCode: 22

If a proxy server is specified and the Use automatic configuration settings are unticked the application works. Is there a way to get the app to work using a PAC file?

Report · Jul 10, 2013

We're having the same problem as described by dlbowen. We're a 6000+ user environment and a Proxy Auto-Configuration (PAC) file has a number of benefits for us in terms of Internet access/filtering. If we uncheck the PAC URL and set explicit proxy settings, the Creative Cloud updater/downloader works fine. If we try to use the PAC URL it just spins and eventually times out indicating it can't connect to the Internet (we don't allow direct Internet connectivity - it must pass through our proxy server).

If Adobe is inheriting Internet Explorer proxy settings but ignoring the PAC settings, this seems like an oversight/bug. Could someone from Adobe please address this?

Report · Jul 11, 2013

Same problem.

Report · Jul 11, 2013

The other Mgmt Tool worked fine. Once they switched to the Adobe Creative Cloud interface everything died. Now I get a warning giving me 90 days to connect and it won't download updates anyother way but through the Adobe Creative Cloud interface which is clearly not working. Good Job, Looks like Adobe needs to fire their QA team.

...Robert

Report · Jul 23, 2013

Same issue here. Spent four hours with "tech support" over two days and they had no clue what to do or what options to provide. All software is completely unusable since the CCApp can't connect to verify the subscription. The old Adobe Application Manager worked fine with proxies, but the new one is proxy stupid it seems. Still looking for a solution on this end, in contact with Adobe.

The only solution we've found internally is to allow http and https traffic for any machines running Adobe software to the following servers ... and we're still testing this since it requires serious security clearance when you're in a secure corporate environment:

ccmdls.adobe.com:443

ims-na1.adobelogin.com:443

na1r.services.adobe.com:443

prod-rel-ffc-ccm.oobesaas.adobe.com:443

lm.licenses.adobe.com:443

ccmdl.adobe.com:80

swupmf.adobe.com:80

swupdl.adobe.com:80

Report · Jul 23, 2013

Well, adding those to the settings on our systems didn't work. Our techs are still looking for a way to achieve this and it seems the only potential option may be to allow http and https access for specific machines (by IP) to access those servers directly -- if the servers change though then it won't work again.

We're still testing it at our office. Unfortunately doing that isn't really an ideal option since I'm at a healthcare company and that could leave a security hole and removing the proxy is not an option at all.

If anyone else has figured out a work around please post it.

Report · Nov 19, 2014

Same issue, PAC-file, automatic discovery, NTLM/Proxy Squid configuration; Govt organisation.

Desktop application doesn't reach proxy server.

I've made exceptions in firewall, but our juniper SRX has problems (?) with resolving domain swupmf.adobe.com. To make it work, I used its IP address (23.197.62.115) instead of domain within firewallpolicy

Report · Mar 05, 2015

It seems that the issue still exists. We have the same problems. The desktop app is not able to use pac files.

A shame that Adobe does not fix it. Its essential for bigger companies.

Report · Apr 03, 2015

same issue here, we have 3000 devices global network and can't make use of the software we already paid for - this is very bad - adobe needs to understand how corporate networks are designed and modify their creative cloud agent asap!!!

Report · Apr 08, 2015

This change resolved it for me, until Adobe recognizes the .pac file for its proxy settings again.

APPDATA\LOCAL\TEMP\PDApp.log

Example of a failure:

04/08/15 14:08:37:331 | [WARN] | | ASU | EnterpriseNative | EnterpriseNative | | | 7544 | Unable to validate the signature of CCPConfig xml

04/08/15 14:08:37:332 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | GetIEProxyInfo - No default proxy present on the user machine

04/08/15 14:08:37:332 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | GetIEProxyInfo - autoconfig url on the machine is :http://XXXXXX.XXXXXX.gov/config/autoproxy.pac

04/08/15 14:08:37:332 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | GetIEProxyInfo - Failed to get proxy for the url, error:12006

04/08/15 14:08:37:332 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | GetIEProxyInfo - proxy Url is

04/08/15 14:09:37:337 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | The http request returned HTTP_Status:0 HttpCommunicator error:0

04/08/15 14:09:37:337 | [INFO] | | ASU | EnterpriseNative | EnterpriseNative | | | 7544 | CCP FFC FES return status is (0) server-response()

04/08/15 14:09:37:337 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 4216 | WINHTTP_CALLBACK_STATUS_REQUEST_ERROR... : (12017)

Fixed by specifying a proxy in IE, leaving Autoconfigure and Use Automatic Configuration script UNCHECKED

04/08/15 14:16:18:966 | [WARN] | | ASU | EnterpriseNative | EnterpriseNative | | | 7596 | Unable to validate the signature of CCPConfig xml

04/08/15 14:16:18:967 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7596 | GetIEProxyInfo - proxy fetched is :wwwproxy.XXXXXXXXXX.gov:80

04/08/15 14:16:19:779 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 8064 | WINHTTP_CALLBACK_STATUS_HEADERS_AVAILABLE...

04/08/15 14:16:19:779 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 8064 | HTTP Request Status code 200.

04/08/15 14:16:19:779 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7596 | The http request returned HTTP_Status:0 HttpCommunicator error:0

04/08/15 14:16:19:779 | [INFO] | | ASU | EnterpriseNative | EnterpriseNative | | | 7596 | CCP FFC FES return status is (0) server-response(<?xml version="1.0" encoding="UTF-8" standalone="yes"?><feature-response .................etc

Obviously not a fix for the enterprise but it will allow me to do a serialized CC package for my enterprise

Report · Apr 24, 2015

Please test with a simple PAC configuration to ensure that the issue is not within the JavaScript of the file itself:

function FindProxyForURL(url, host) {

return "PROXY 10.2.3.4:8080";

}

PAC files specified by filename (e.g. C:\config\proxy.pac) are not supported, the PAC configuration should be loaded from a URL, which appears to be the case for most such setups.

At present, NTLM is unfortunately not supported as an authentication mechanism.

If you are still seeing problems with this, please confirm you have tested with a simple PAC configuration and provide details of the software/hardware version of your proxy server.

Report · Jun 18, 2015

I just did what you recommended, but I still get this:

06/18/15 14:44:14:464 | [INFO] | | ADM | | ApplicationContext | | | 12244 | GetIEProxyInfo - autoconfig url on the machine is :http://.....

06/18/15 14:44:14:464 | [INFO] | | ADM | | ApplicationContext | | | 12244 | GetIEProxyInfo - Failed to get proxy for the url, error:12006

06/18/15 14:44:35:570 | [WARN] | | ADM | | WorkflowManager | HttpConnector | | 4736 | WINHTTP_CALLBACK_STATUS_REQUEST_ERROR : error : 12002

06/18/15 14:44:35:570 | [FATAL] | | ADM | | WorkflowManager | HTTPConnectorError | | 12244 | Error occurred while getting application xml: -190 extended error: 12002

Report · Jun 18, 2015

Please log a support request via the portal at http://www.adobe.com/support/ if you're having problems here, so we can track the common issues. Feel free to mention this thread and the details of your proxy server; you can collect log files using this tool for submitting at the same time:

Log Collector Tool‌

Report · Jun 18, 2015

Good point, but we have no premium support contract.

Anyway, I would have liked to know if someone else followed through:

Manually updating flash using a .pac file (using http) success or failure?
How about the Adobe Flash player update service/scheduled task and updating using .pac file (using http)?

I wonder what is the difference between ADM / ASU / OPM in the logs above?

Also does it make use of the WinHTTP proxy configuration or the regular IE settings? As it mentions WinHTTP in the logs above.

Report · Jun 18, 2015

PAC configurations are only supported if a URL is used to specify the location, if a file is specified, this will not work. This is a limitation of the Microsoft library used, WinHTTP.

If you are able to connect from the relevant application having specified the proxy manually, then unfortunately the proxy server or its configuration is unsupported at this time. You may be able to whitelist the various domains as suggested earlier in this thread.

Report · Jun 18, 2015

Dear Dominic,

I used http:// format of an URL in IE settings for AutoConfigURL.

I did as you suggested a pac file with only this:

function FindProxyForURL(url, host) {

return "PROXY x.x.x.x:80";

}

Report · Jun 18, 2015

Apologies, I meant to say that if you specify the proxy server's hostname and port number and are able to connect, that this points to the authentication method on the server or some other aspect of the server itself not being supported.

Report · Jun 18, 2015

no authentication required on the proxy for this.

but the software does not connect to the proxy but tries to connect directly to one of adobe's servers:

TCP x.x.x.x:49717 192.150.16.58:443 SYN_SENT

-> get-du1.adobe.com:https

I can see that it reads the AutoConfigURL from the registry
I see the error messages in the log that the update program sees it, but then it says Failed to get proxy for the url, error:12006
I made sure that I only have the minimum PAC file recommended

Report · Jul 04, 2015

Dominic,

There aren't any issues with the PAC file or authentication. Everything works flawlessly if one specifies the proxy explicitly in the Internet Configuration. Error 12006 indicates ERROR_WINHTTP_UNRECOGNIZED_SCHEME according to this MSDN doc: Error Messages (Windows).

Yet, the URL for the PAC is http://...., and it actually indicates so in the log:

04/08/15 14:08:37:332 | [INFO] | | ASU | EnterpriseNative | HTTPConnector | | | 7544 | GetIEProxyInfo - autoconfig url on the machine is :http://XXXXXX.XXXXXX.gov/config/autoproxy.pac

This points to some error in the application that either doesn't pass autoconfig url parameter to WinHTTPRequest, or somehow mangles it.

Either way, the problem is pretty severe since it requires manual modification of the proxy configuration which doesn't work for the environments were PAC is a must for proper traffic routing.

Thanks.

Report · Aug 06, 2015

We are having the same issue with our users. Can't seem to figure out what to put in the PAC file.

Report · Aug 12, 2015

We have released an updated version of Creative Cloud Desktop which addresses some PAC-configuration related problems, please ensure you are running the latest version by reinstalling from the following link:

Download Adobe Creative Cloud apps | Free Adobe CC trial

Report · Aug 21, 2015

Has this issue been resolved? We are experiencing the same issue where we can only use the Adobe Creative Cloud Packager if we have our Proxy server specified in IE. If we try and use our PAC file which is what all our users have we are unable to use the packager

Report · Aug 24, 2015

I managed to get this to work, I had to run the following from the command line and change the WinHTTP proxy from default to our IE Proxy.

netsh winhttp set proxy proxy-server yourproxyserver:80

Hope this helps

Report · Mar 09, 2016

In case someone else comes across this posting while trying to troubleshoot proxies. The PAC file seems to work (http://wpad/wpad.dat), however adobe appears to have recently started checking the certificate they are presented by the connection through the proxy so software downloads stopped working until we exempted the traffic from SSL interception. We did this for adobe.com and adobe.io to be safe based upon URL requests that were showing up in the logs.

Report · Jun 30, 2018

IMSLib returned error during fetchAccessToken callback function, errorCode: 23

how to solve?