-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotfix service is down #44
Comments
Not sure what you mean. Do you have any references/links? I actually work for Microsoft and haven't heard about this. |
Well, the problem occurred on downloading SharePoint 2013 April 2013 CU. When I try to go to the address on AppSourceBuilder.xml, I get the error DNS_PROBE_FINISHED_NXDOMAIN. It's obvious that it's not about the file or a part of url, but about the hotfixv4 CNAME. It doesn't exist anymore. Then I took a look on the first page of Google Search and I see these articles 1, 2, 3. Microsoft Update Catalog does not have all the updates because of the ex hotfix service. I had to delete every line that includes the hotfixv4 and go on with that for testing. That's just a workaround though. The issue is bigger than the script, so it might be a good way to use a workaround at all. |
This also affects the prerequisites based on the https://hotfixv4.trafficmanager.net url. SP2013 Without having these files already in the target directory any fresh build of a SP2013 slipstreamed install media will fail. (As mentioned: download will fail) |
Umm, I believe we need to test if the installation can be completed without the erroring hotfixes and updates. If not, we might need to find somewhere else distributing the missing ones. |
Hi. Any news? |
You should give the current version a try (build a fresh slipstreamed media). The hotfixes located at https://hotfixv4.trafficmanager.net/... are commented out. Maybe the hotfix is no longer required or applicable for a fully patched Windows Server OS. |
As of November 2018, Microsoft shut down the Hotfix service. That causes many of the SP 2013 updates crash and retry. I am not sure if it would be ok updating without them.
The text was updated successfully, but these errors were encountered: