Skip to main content
dvulyak
Inspiring
April 14, 2017
Answered

Why are the URLs in the SCUP catalogs still wrong and still 404 when trying to publish them???

  • April 14, 2017
  • 2 replies
  • 1847 views

This has been broken for months.

Someone please provide the proper locations for downloading the patch content so I can manually edit the SCUP catalog.

This is WRONG

Download file: http://armdl.adobe.com/pub/adobe/acrobat/win/AcrobatDC/1700920044/AcrobatDCUpd1700920044.msp failed with message "The remote server returned an error: (404) Not Found." Updates Publisher 4/14/2017 9:09:53 AM 9 (0x0009)

Download file: http://armdl.adobe.com/pub/adobe/acrobat/win/11.x/11.0.20/misc/AcrobatUpd11020.msp failed with message "The remote server returned an error: (404) Not Found." Updates Publisher 4/14/2017 9:09:52 AM 9 (0x0009)

This topic has been closed for replies.
Correct answer dvulyak

It is a DNS issue. On two of my networks that use BIND, armdl.adobe.com does not resolve. It resolves if we do a lookup using google's free DNS servers: 8.8.8.8 and 8.8.4.4

We have created conditional forwarders for adobe.com to use google DNS in order to resolve armdl.adobe.com correctly. Still sucks that we have to do this, but at least it works.

If anyone else is having the same issue, try doing this: nslookup 8.8.8.8 armdl.adobe.com to see if it works.

2 replies

Participating Frequently
April 18, 2017

Hi,

I can not see any issue in catalog files,

i checked all the paths in catalogs , everything is fine.Also published Acrobat_Catalog.cab using SCUP 2011 successfully.

Can you please extract the .xml files from cab files and check if you are able to access paths mentioned in there.

Paths will be:

Acrobat_Catalog.cab : http://armdl.adobe.com/pub/adobe/acrobat/win/AcrobatDC/1700920044/AcrobatDCUpd1700920044.msp 

As these are the valid paths, you must be able to download patch files from this.

Check on your machine whether you are able to download patches from these links or not.

Regards,

Sourab Sharma

dvulyak
dvulyakAuthorCorrect answer
Inspiring
April 18, 2017

It is a DNS issue. On two of my networks that use BIND, armdl.adobe.com does not resolve. It resolves if we do a lookup using google's free DNS servers: 8.8.8.8 and 8.8.4.4

We have created conditional forwarders for adobe.com to use google DNS in order to resolve armdl.adobe.com correctly. Still sucks that we have to do this, but at least it works.

If anyone else is having the same issue, try doing this: nslookup 8.8.8.8 armdl.adobe.com to see if it works.