Software Update Point woes

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Software Update Point woes

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Software Update Point woes

Page: [1]

Message

<< Older Topic Newer Topic >>

Software Update Point woes - 1/17/2008 10:08:52 AM

jrensink947

Posts: 21
Score: 2
Joined: 9/30/2005
Status: offline

I am testing out SCCM and I'm running into an issue that I can't seem to get around in getting the software upate point component to work. WSUS and SCCM are on the same server. I set things up as directed in the help files. Here is my setup.

Windows 2003 server SP2 and updates
SQL server 2005 SP2 on the box
WSUS3 full install, installed in separate site w/ ports 8530/8531, using local SQL database, do not download local copy of updates
SCCM installed, added SUP component, no proxy, specified ports 8530/8531 , made it active SUP on site server, sychronize directly from MS

The SUP is never able to get any updates to synchronize. In the SMS_WSUS_CONFIGURATION_MANAGER logs, I get these errors when the server boots and every hour after that.

SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "USRTC-SCCM01".

Possible cause: WSUS Server version 3.0 and above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.

I did verify the ports in use in IIS are correct and double-checked the SUP config settings. They do match.

In the SMS_WSUS_SYNC_MANAGER logs, it shows that it starts the sync process. But 5 minutes later, it always returns the error below.

SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error

In my searching, I did find others getting this error and it was related to the proxy auto-config. That doesn't seem to be my issue. I never see any access attempts in the logs coming from my proxy. It's always from the SCCM server IP. In the IIS logs, I do see some failures right after boot as shown below.

2008-01-17 14:38:56 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 2 2148074254
2008-01-17 14:38:56 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 2 2148074254
2008-01-17 14:38:56 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 1 0
2008-01-17 14:38:56 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 1 5
2008-01-17 14:38:56 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 1 0

After these messages, I start seeing successful access attempts.

2008-01-17 14:39:08 W3SVC298875502 155.177.115.199 GET /selfupdate/iuident.cab - 8530 - 155.177.115.199 - 200 0 0
2008-01-17 14:39:19 W3SVC298875502 155.177.115.199 POST /reportingwebservice/reportingwebservice.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 200 0 0
2008-01-17 14:39:19 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 EPM-NA\USRTC-SCCM01$ 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 200 0 0
2008-01-17 14:39:19 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 1 0
2008-01-17 14:39:21 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 EPM-NA\USRTC-SCCM01$ 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 200 0 0
2008-01-17 14:39:21 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 - 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 401 1 0
2008-01-17 14:39:21 W3SVC298875502 155.177.115.199 POST /ApiRemoting30/WebService.asmx - 8530 EPM-NA\USRTC-SCCM01$ 155.177.115.199 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.832) 200 0 0

I do see the following in the WSUSCtrl.log file.

Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~ $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.188 2008 Central Standard Time><thread=4024 (0xFB8)>
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0~ $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.188 2008 Central Standard Time><thread=4024 (0xFB8)>
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6000.1)~ $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.188 2008 Central Standard Time><thread=4024 (0xFB8)>
Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.188 2008 Central Standard Time><thread=4024 (0xFB8)>
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.240 2008 Central Standard Time><thread=4024 (0xFB8)>
Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.240 2008 Central Standard Time><thread=4024 (0xFB8)>
There are no unhealthy WSUS Server components on WSUS Server USRTC-SCCM01~ $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.257 2008 Central Standard Time><thread=4024 (0xFB8)>
Successfully checked database connection on WSUS server USRTC-SCCM01~ $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.309 2008 Central Standard Time><thread=4024 (0xFB8)>
~Waiting for changes for 57 minutes $$<SMS_WSUS_CONTROL_MANAGER><Thu Jan 17 08:39:21.309 2008 Central Standard Time><thread=4024 (0xFB8)>

I find it odd that it would say that the proxy settings are correctly "configured as Proxy Name and Proxy Port 80". No proxy name and a port of 80. We do have a proxy server, but its specification is not required to get out to the Internet.

I've tried many reinstalls of both SCCM and WSUS. Even wiped the server and started fresh. I've tried specify using our proxy server. I've specified using the SCCM server as the proxy. If I go into WSUS itself, it has no problem grabbing updates from MS.

This seems like it should be pretty staright forward, but evidently I'm special enough to have this issue. Anyone out there have any ideas?

< Message edited by jrensink947 -- 1/17/2008 10:12:16 AM >

Post #: 1

RE: Software Update Point woes - 1/21/2008 1:37:06 PM 1 votes

jrensink947

Posts: 21
Score: 2
Joined: 9/30/2005
Status: offline

I was able to get the issue resolved with some help from Microsoft. The solution can be found at http://support.microsoft.com/kb/896861/en-us. I used method 1, which is described below. This only applies when SCCM and WSUS are on the same server. Hope this helps someone.

Method 1: Disable the loopback check loadTOCNode(2, 'workaround');Follow these steps:1.Click Start, click Run, type regedit, and then click OK.2.In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa3.Right-click Lsa, point to New, and then click DWORD Value.4.Type DisableLoopbackCheck, and then press ENTER.5.Right-click DisableLoopbackCheck, and then click Modify.6.In the Value data box, type 1, and then click OK.7.Quit Registry Editor, and then restart your computer.

(in reply to jrensink947)

Post #: 2

RE: Software Update Point woes - 1/21/2008 2:46:10 PM

kev147

Posts: 138
Score: 2
Joined: 1/28/2007
Status: offline

This looks really promising, we have had this issue in test and in live and it is the most annoying and time consuming bug I have ever come accross.

I will give it a go and post my findings as well.

(in reply to jrensink947)

Post #: 3

RE: Software Update Point woes - 1/23/2008 5:39:24 PM

mlindsey

Posts: 401
Score: 2
Joined: 7/27/2004
Status: offline

I had this same exact thing.

My question is.. How and when do you start seeing the updates in the SMS Console? Not sure if I get how it all works... No need to edit the GPO and have the client point to the WSUS server right? The client should take care of all this correct? I see updates in the WSUS console but none of my machines. On SMS console I run a sync and it shows succesful yet I see no updates or anything. I guess my question is what do I do now that SMS isnt throwing crazy WSUS errors.

(in reply to kev147)

Post #: 4

RE: Software Update Point woes - 1/23/2008 8:21:41 PM

mhudson

Posts: 509
Score: 10
Joined: 4/1/2007
From: College Station, TX
Status: offline

When I had this problem I solved it by matching the FQDN in the updates panel and what was on the Web certificate. Also make sure the port settings in SCCM (WSUS) and the IIS (WUS) ports were correct. Also you MUST run it in SSL so make sure it is enabled.

_____________________________

Matthew Hudson
http://sms-hints-tricks.blogspot.com/
http://www.sccm-tools.com

(in reply to mlindsey)

Post #: 5

RE: Software Update Point woes - 1/24/2008 12:38:37 PM

mlindsey

Posts: 401
Score: 2
Joined: 7/27/2004
Status: offline

Oh my god... still getting this crap. IM not sure what is up... YOu would think they would make this easy. I guess not as I am not the only person having this issue.

NOt sure what to try now.

SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "CONFIGMGR".
Possible cause: WSUS Server version 3.0 and above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.

Got this in the SYnc Manager log.

SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error

< Message edited by mlindsey -- 1/24/2008 12:54:36 PM >

(in reply to mhudson)

Post #: 6

RE: Software Update Point woes - 1/24/2008 2:25:05 PM

mlindsey

Posts: 401
Score: 2
Joined: 7/27/2004
Status: offline

OK well... I think I am going to do another full reinstall of WSUS...

Anyone have a good doc that actually works? Like a step by step?

Since its a hit and miss it seems like getting this to work.

Update.... I reinstalled with no luck.. Went the route of enabling SSL on the WSUS site and that made it worse. Once I enabled SSL my WSUS console cannot connect to the site anymore.

This is sad :(

< Message edited by mlindsey -- 1/24/2008 4:28:30 PM >

(in reply to mlindsey)

Post #: 7

RE: Software Update Point woes - 3/22/2008 4:47:16 PM

jkuta

Posts: 11
Score: 0
Joined: 9/13/2007
Status: offline

A big thank you to jrensink947 for his post! I spent hours troubleshooting this issue and the KB896861 method 1 solution worked like a charm.

(in reply to mlindsey)

Post #: 8

RE: Software Update Point woes - 3/25/2008 10:21:26 AM

TimA

Posts: 32
Score: 0
Joined: 11/3/2006
Status: offline

Also want to add a thank you for posting back the resolution to the issue. Wish that happened more often!

(in reply to jkuta)

Post #: 9

RE: Software Update Point woes - 6/13/2008 10:21:35 AM

cmaurice

Posts: 21
Score: 0
Joined: 6/2/2004
From: Madison, WI
Status: offline

Wow...this worked great. I wasnt having the problem described in the KB article, but I tried it out of despiration anyways. It worked like a charm! Thanks jrensink947!

(in reply to TimA)

Post #: 10