SBS Console Connection Broken 1

[snotty54]

I've searched the database on this one with no results. I've recently had to completely uninstall/re-install WSUS and I've got green on Console Home Screen. Going to Security and Updates, and then to "Change the Software Update Settings" crashes the console, error code below:


Prog event: clr20r3
sig 1: console.exe
sig 2: SBS version
sig 3: 4d24e3fe
sig 4: mscorlib
sig 5: 2.0.0.0
sig 6: 4ef6c2e7
sig 7: 20c8
sig 8: 143
sig 9: n3ctrye2kn3c34sgl4zqyrbfte4m13nb
OS ver: 6.0.6002.2l2l0.305.9
Locale ID: 1033

Can anyone suggest how I can re-connect the Console to the update services settings dialog?

Thanks,

Scott

 

[snotty54]

1 Week Later

Dear All:

Disappointed I don't have a reply to this thread. Since I've reintalled WSUS and had the above problem, Self Update is also not operating with the WSUS. I've researched online and several suggestions about changing the port in the firewall from 80 to 443 becausse Sharepoint 3.0 and WSUS can't share port 80 or enabling the Default Web Site, etc. scares me into thinking I'll break the Exchange Server or something else, has stopped me from doing any other remedies to get WSUS working. There certainly seems to be a lot of posts regarding WSUS not working, but no clearcut solution for remedy, or clear cut solutions, step by step.

Any suggestions or comments appreciated.

Running SBS2008 sp2

Scott

 

[ShackDaddy]

Have you gone through this document:

http://technet.microsoft.com/en-us/library/gg680316.aspx

Typically you can have a working WSUS and still not have it work in the SBS Console, since it's pretty picky about the WSUS config conditions being exact in order for it to integrate into the console.

The port used by WSUS is defined in the Group Policy, and it is usually TCP 8530, so there shouldn't be a reason to mess with 80 or 443 in relationship to WSUS.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[snotty54]

Thanks Dave. I looked at that document but at the time my WSUS Admin Console was dead so I eventually did the re-install. Now time to go back through it, thanks for reminding me.

I will come back once I've gone through the doc.

Thanks,

Scott from Cayman

 

[snotty54]

Update:

I went completely through the technet repair WSUS document and everything was correct with the settings specified in the document. SBS Console still crashes when I select "Change the Software Update Settings" on the Updates Tab in Security. Self Update is also not working.

Any other trouble shooting ideas on where to look? I have been googling this for several days and havne't found the answer yet.

Any suggestions appreciated.

Scott

 

[ShackDaddy]

Scott, did you look at this:

http://www.vistax64.com/sbs-server/...software-update-settings-crashes-console.html

And do you have all the Computer Groups listed as follows?

Unassigned Computers
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers

I know that if you don't have these groups spelled exactly as they are here, the console will crash like you've described.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[snotty54]

Hi Dave:

Thanks for the additional info. I checked the spellngs carefully and all is correct. I followed the 2nd procedure carefully then upon finishing and waiting 15 mins for the group policies to repopulate, closed and then re-opened the console and still crashes on Security/Updates/Change the software update settings

In the home page of the console I have green on security - updates - backup - red on other alerts which points to a BPA finding of dns error (common one I understand) been going on for long time. I'm presently working through your Trainsignal SBS course hoping the solution to the dns error will be in there somewhere (dns a resource record points to incorrect IP address)

Other than that, not sure where to look next. I know this sounds defeatist, but WSUS has never worked on my server, up for 1 year 8 months.

Scott

 

[snotty54]

I've decided to forget about the Console crashing right now when opening "Security/Updates/Change" and instead focus on trying to get WSUS working. I must be close because I have all green on the home Screen in the Updates area under Network Essentials Summary. I am getting the Self update error id 13042. Following a link to MS Support

http://support.microsoft.com/kb/200059

shows a procedure to fix this problem:


1.) Open IIS Manager
2.) Make sure the Selfupdate virtual directory has Anonymous authentication enabled and "Require SSL" should be unchecked.
3.) Make sure the Default Web site has Anonymous authentication enabled and "Require SSL" should be unchecked.
4.) Remove the SSL (HTTPS) site binding for the Default Web Site.
5.) Stop and start the Default Web site

Examining the selfupdate virtual directory under Default Web site, and going to SSL Settings shows the require ssl and require 128 bit ssl checked and grayed out, with an alert in alert pane on top of the actions panel area stating "This site does not have a secure binding (https) and cannot accept ssl connections". So I figure this is a dead end.

I go down to the Selfupdate Virtual directory under WSUS Administration Virtual Directory and selecting the ssl settings shows require ssl and require 128 bit ssl unchecked and ignore selected under client certificates. Authentication shows anonymous enabled. If this is the selfupdate directory referenced above, then all is good.

Going to Default Web site, Anonymous authentication is enabled, and viewing the ssl settings shows the require ssl and require 128 bit ssl selected and grayed out, so obviously this is wrong but must be changed elsewhere?

Also, when right clicking ssl settings for Default Web site, and choosing basic settings, and testing connection, authentication pass through is good but alert on authorization "cannot verify access to path (C:\inetpub\

http://wwwroot).

The only binding I can uncover for the Default Web Site is http port 80. I can't find an https binding associated with the Default Web site

So I guess my questions are:

1) How do I get the ssl required and 128 bit ssl required unchecked in Default Web site's ssl settings?
2) How do I remove the SSL (HTTPS) site binding for the Default Web Site without breaking something?

Thanks for any help,

Scott

 

[snotty54]

One more note on this:

At the bottom of the help article for above, they describe a procedure to add an ssl binding to Default Web site, then uncheck require ssl and then delete binding but upon attempting to add an ssl binding a warning comes up about the binding being used elsewhere and do I want the other location to use a new certificate. I'm afraid I'll break something so haven't done this procedure.

Can anyone advise?

Thanks,

Scott

 

[ShackDaddy]

I wouldn't worry about the Default Web Site settings if the Self-Update virtual directory is already disabled for SSL. That overrides the inheritable settings.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[snotty54]

Hi Dave:

OK, any idea of where else I should look to get self update working? BPA consistently brings it up as an error "Self Update Not Working"

The clients on the network have not been updated since I last manually updated them last April, but many updates since then have been applied to my remote machine, not managed by SBS/WSUS

Thanks,

Scott

 

[ShackDaddy]

This is an issue that would be difficult to troubleshoot in a forum. The easiest way to get to a working state would be to edit the WSUS group policy for clients to have them download their updates directly from the internet and stop using WSUS. I'm not sure if you have flat-rate internet in Cayman, but if you do and you have fewer than 5 workstations, I'd just stop using WSUS if it's starting to get you so far behind on the updates. The primary benefit of WSUS is with lots of workstations and/or per-gb internet billing.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[snotty54]

Thanks Dave, that makes sense as I only have 3 clients and one remote. I will look at the Group Policy and if the policy change is not obvious I'll google it and come back with how it went.