This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

Unable to import an update from MU Catalog to WSUS

Question
0

Sign in to vote
Hi,

We have a working WSUS installation that is synchronising and importing WSUS updates correctly. However there has been a recent hotfix rollup released for enterprises that is available on the MU Catalog, but not via WSUS. A number of the issues addressed in this rollup are affecting nodes in our organisation

The KB Article is 2775511, and it is available on the MU Catalog, however when we try to import it in to WSUS via the MU Catalog site we see the following results..

Status sits on WAITING for a number of minutes. Often the IE window becomes unresponsive
The status will eventually move to FAILED, which is a link to a page which lists the following reasons for the failure.

If you use a proxy, be sure that it is the same proxy being used by your Windows Server Update Services (WSUS) server.
Your WSUS server might not be configured correctly. Contact your WSUS administrator.

In the first instance the proxy server is a transparent proxy server that does nothing to the traffic and requires no authentication - the same proxy server is used by the server, the service, and IE.

In the second instance, the WSUS server is working otherwise correctly. I am the administrator, and am at a bit of a loss about what the problem could be

Any help would be greatly appreciated.

Many thanks, J R Brewin
- Edited by jrbrewin Tuesday, April 9, 2013 11:14 AM formatting, typo
Tuesday, April 9, 2013 10:52 AM

All replies

0

Sign in to vote

What version of WSUS? What version of Windows? Make sure you are running WSUS 3 SP2 and try installing the latest KB 2734608. If you are on WS2012, check Windows Update and make sure all available updates are installed.

-Ben

Tuesday, April 9, 2013 7:20 PM
0

Sign in to vote

Thanks for the response Ben,

We're running Windows Server 2003 SP2, with WSUS3 SP2 and IE8. Every WSUS update listed in WSUS is installed where required. I wasn't running with 2734608 update, but I have installed that, rebooted and tried again. No Joy.

I've also tried installing all missing updates from the Microsoft Update site.

Still no joy. Are there any log files I can check for the windows catalog, or the WSUS process that's doing the import?

thanks, J R Brewin

Wednesday, April 10, 2013 10:57 AM
0

Sign in to vote

Still no joy. Are there any log files I can check for the windows catalog, or the WSUS process that's doing the import?

Are you doing the import from the WSUS LOCAL console, or from a remote console?

Can you *download* the contents of your shopping cart from the Microsoft Update Catalog instead of importing them to WSUS. This can help isolate where the issue might be: If you cannot download the update independent of WSUS, then it's likely a proxy server interfering.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Sunday, May 26, 2013 4:46 PM
0

Sign in to vote

I'm having the same issue with the same update. WSUS 3.0, SP2, installed the HF, no luck. I can download the files fine manually, they just refuse to import into WSUS.

Thursday, July 18, 2013 8:58 PM
0

Sign in to vote
I am having the same issues, I am trying to import IE10 for Windows 7 but it keeps failing. I can download them without importing into WSUS but I really need it to import!
- Proposed as answer by Phil Hemstock Friday, July 19, 2013 11:42 AM
- Unproposed as answer by Phil Hemstock Friday, July 19, 2013 11:42 AM
Friday, July 19, 2013 10:39 AM
0

Sign in to vote
OK just sorted my problem! Our server is a downstream replica of the WSUS server of our ISP. If I change the setting to point directly to MS update and then try the import it works! Then I just changed the update source back to our ISP's
- Proposed as answer by Phil Hemstock Friday, July 19, 2013 11:43 AM
Friday, July 19, 2013 11:43 AM
0

Sign in to vote

That is not the case for me. I have always been pointing to Microsoft servers.

Friday, July 19, 2013 1:07 PM
0

Sign in to vote

OK just sorted my problem! Our server is a downstream replica of the WSUS server of our ISP. If I change the setting to point directly to MS update and then try the import it works! Then I just changed the update source back to our ISP's

Hmmm.. a couple of fatal flaws here.

First.. yes.. you can only IMPORT updates to an UPSTREAM server. Importing updates to a downstream server (particularly a replica), will be problematic. Congrats you now have the update, but if it's a replica server, you have no way to approve the update! (Which begs the question: How are you approving updates anyway?)

Second, your ISP providing update synchronization for WSUS is, first, probably a violation of the WSUS licensing terms. You should be getting your updates DIRECT from Microsoft. Furthermore, why would you allow your **ISP** to determine what updates you do or do not synchronize, or do or do not approve/deploy into your environment.

All the way around, I gotta say.... synchronizing WSUS from an ISP is not something I would think is a very good practice at all.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Friday, July 19, 2013 2:00 PM