1 of 1 people found this helpful
Thanks for the detailed information. I have a couple of questions that should lead us to a solution.
- Can you confirm if the the cab file exists in the content folder location above on your WSUS server? If it does not, your issue is likely that the signing certificate is not in the proper stores on the WSUS server. It should be in Trusted Root and Trusted publishers. The softwaredistribution log on the WSUS server should confirm if this is the issue. If this is the issue new updates you publish will work. Our support team will have to help with existing updates you published and the cab file does not exist.
- If the cab file does exist and you are using a proxy then we have a proxy issue where the account running the ADR is not hitting the WSUS server. This can happen if you configured the proxy settings in Config manager and you need to bypass local.
Thank you for your answer.
I wrote in my problem description that the files do not exist on the specified path on the WSUS server http://fqdn:8530/content/XX/*.cab but i was wrong. I checked again and if I search for a third party update
and look at the content information the files are there.
We do not use a proxy and have not enabled it in SCCM:
I have found quite a few articles that describe a similar issue to the one I am having and there is a lot of mentions of proxy settings: http://scug.be/valerie/2012/11/20/config-manager-software-updates-download-failed/
I have tried changing the setting mentioned in this article ( proxy settings for local system context) by using a GPO but it has not made any difference.
Regards Emile Risberg
Sorry for the delay.
Can you paste the url to the cab file into a browser and get to it?
On the WSUS server can you send us the softwaredistribution log?
The problem is solved, when we installed the WSUS role on the SCCM server we specified a content path without a backslash, please see attached file:
After changing the content path in the IIS to F:\ the ADR is now downloading successfully, the confusing part is that if you click on run in windows and paste F:%PATH% without backslash it actually finds the path correctly but not if you open windows explorer and paste the %PATH% with the missing backslash which is how I tested it.
In other words this was not a ShavLik issue but an underlying WSUS problem, sorry for wasting your time!
I appreciate you following up with how you resolved the issue.
I am also experiencing the above issue. Has there been no resolution? I am currently working with support on this but not making progress.