Gatt Posted November 22, 2006 Posted November 22, 2006 just started getting this error in WSUS: [b]Check your server configuration[/b] One or more Update Service components could not be contacted. Check your server status and ensure that the Windows Server Update Service is running. Non-running services: SelfUpdate The event log on the server reveals: Event Type: Error Event Source: Windows Server Update Services Event Category: Update Services Service Event ID: 506 Date: 22/11/2006 Time: 13:19:13 User: N/A Computer: COPPER Description: The SelfUpdate Tree is not working. Clients may not be able to update to the latest WUA client software and communicate with the WSUS Server. For more information, see Help and Support Center at [url]http://go.microsoft.com/fwlink/events.asp[/url]. I restart the Update Services service and all seems fine for about 5 mins then it goes down... BUT the Services MMC still has the service as running?
Geoff Posted November 22, 2006 Posted November 22, 2006 What port is the WSUS website running on? The default site on port 80? or did it create a new site on port 8530?
Gatt Posted November 22, 2006 Author Posted November 22, 2006 Yep and Yep - Default on 80 & WSUS on 8530
Geoff Posted November 22, 2006 Posted November 22, 2006 Does the SelfUpdate folder exist on the port 80 default site?
Gatt Posted November 23, 2006 Author Posted November 23, 2006 Sorry been busy with a network fail today.. the selfupdate folder does indeed exist on port 80 default site.
Gatt Posted November 23, 2006 Author Posted November 23, 2006 Integrated Windows Authentication is checked....
alonebfg Posted November 23, 2006 Posted November 23, 2006 i had this problem it seem the sp1 for the wsus does not like 8530 i reinstalled it using port 80 and it works fine now dont know what caused it contacted microsoft about it and they told me to put it on 80 and see if it work and it did. but they would not tell me why.
Gatt Posted November 23, 2006 Author Posted November 23, 2006 isn't port 8530 used for the WSUSAdmin Virtual Directory? (Which i have set) and Port 80 for the default website (again its set to that) Might try re-installing IIS & WSUS...
tosca925 Posted November 23, 2006 Posted November 23, 2006 I've had a weird issue with our WSUS box this week. I had to re-install Net Framework, well actually i just went for the 2.0 version. I admit my problem was not the same as yours but its just something to bear in mind.
Geoff Posted November 23, 2006 Posted November 23, 2006 Integrated Windows Authentication is checked.... Machines don't authenticate when they check for updates. Disable Authentication on the SelfUpdate Folder
Gatt Posted November 24, 2006 Author Posted November 24, 2006 What about anonymous? should that be enabled?
Gatt Posted November 24, 2006 Author Posted November 24, 2006 OK WSUS is up and running again! However - I had been planning to let IE7 rollout to all the PC's So disabled the blocker in GP, went to WSUS - IE7 for XP is now showing Expired!! It wont let me approve it only decline it WTF!?!?
Geoff Posted November 24, 2006 Posted November 24, 2006 The blocker tattoo's the registry. Disabling it isn't sufficient. You need to remove the registry key entirely manually or via a script.
Gatt Posted November 24, 2006 Author Posted November 24, 2006 Ta Geoff - but i think this is seperate from the Blocker.. WSUS itself is denying me the right to approve IE7 for XP as it says it has expired. IE7 for WS03 CAN be approved and has been deployed to my servers - its the XP version thats screwed. The IE7 Blocker ADM was a seperate GPO that was applied to my main Computer OU wich contains Servers, Staff PC's and Pupil PCs So far only the Servers have recieved IE7..
Geoff Posted November 24, 2006 Posted November 24, 2006 You're probably looking at the wrong update then. Does it indicate if it's been superseded?
Gatt Posted November 24, 2006 Author Posted November 24, 2006 I'm pretty certain its the right Update- there are no other references to Windows IE7 for Windows XP.. It's not been superseded - this is what WSUS says about it: The selected update has expired and cannot be approved for installation or detection. It is recommended you decline this update. Title: Windows Internet Explorer 7.0 for Windows XP Description: This free upgrade to Internet Explorer for genuine Windows customers offers improvements such as: enhanced security to help protect you from malicious software and fraudulent websites; a cleaner look, including tabs for browsing multiple pages in one window; features to make everyday tasks such as printing and searching the web easier. This upgrade preserves your current home page, search settings, favorites, and compatible toolbars, and can be uninstalled if you decide to do so. This update includes Windows Genuine Advantage validation. Classification: Update Rollups Products: Windows XP Release date: Tuesday, November 21, 2006 More information: http://go.microsoft.com/fwlink/?LinkID=71727 KB article number: 926874 MSRC number: None MSRC severity rating: Unspecified Update ID: 73246d69-2d1f-4e99-894b-ec3995cb5e5d Installation InformationRemovable: No May request user input: No Restart behavior: Can request restart Must be installed exclusively: No Includes: None Included by: None Supersedes: None Superseded by: None Languages supported: English, Finnish, French, German EULA: The End User License Agreement (EULA) for this update has been accepted. View EULA
MkII Posted November 24, 2006 Posted November 24, 2006 Exactly the same here Craig - just happy with restictions enough to roll it out - and it's gone expired - I've searched the available updates and there's no other IE7 update. Nathan just called and he's getting IE7 Spanish - that has deployed around his system and can't be removed. Perhaps MS have stuffed up and are in the process of pushing out the correct version - I hope so anyway!!
MkII Posted November 24, 2006 Posted November 24, 2006 Saw this over on SpywareSucks: To immediately address the spread of this (Spanish) issue, the IE7.0 update package has been expired effective 5:00PM PST, Wednesday, 11/22/06. Synchronizing WSUS servers after 5:00PM PST will ensure the expiration status is applied to the latest IE7.0 update rollup package, released 11/21/06.
MkII Posted November 24, 2006 Posted November 24, 2006 Ah - also on the same post: A new update rollup package for this IE 7.0 release will be available for synchronization early next week. We regret the inconvenience and confusion this issue may have caused WSUS customers. Thank you for your reports and enabling us to get this issue headed off so quickly.
Gatt Posted November 24, 2006 Author Posted November 24, 2006 Thanks Mark - At least I know why now!! Guess we'll need to wait for M$ to release it again!
alonebfg Posted November 24, 2006 Posted November 24, 2006 this is the second time first was relice on 1st nov and the second on the 21st nov have contacted them and they have a issue with pusshing out at the moment you ned to log onto everymachine to install they are trying to sort this issue befor next week.(so they say)
tosca925 Posted November 24, 2006 Posted November 24, 2006 Just out of interest how does the deployment go? If itis auto pushed out buy WSUS does the end user have any input or is it auto installed. Is there a delay on logging on/off on the PC for anyone?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now