SBS 2008 80070002 Window update error

All is cool Richard, :thumbsup2: Sorry for being too straight forward/aggressive and I hope that I wasn't too harsh. I think Steff will really have to contact and ask for professional assistance. A Server is a Server and things can be overly complicated sometimes.

Steff - usually the first thing to check your Server's Event Viewer logs and look for all critical errors/warnings on the Event IDs. These are the ones that Microsoft Support will be looking at to better assist you.
 
Last edited:
2xg said:
All is cool Richard, :thumbsup2: Sorry for being too straight forward/aggressive and I hope that I wasn't too harsh. I think Steff will really have to contact and ask for professional assistance. A Server is a Server and things can be overly complicated sometimes.

Steff - usually the first thing to check your Server's Event Viewer logs and look for all critical errors/warnings on the Event IDs. These are the ones that Microsoft Support will be looking at to better assist you.
Click to expand...

It is a shame. I guess part of the problem is that I hate not fixing something like this. I have been studying Windows Update errors, and specifically fixing up corruptions based on CheckSUR.log for years. There is absolutely nothing particularly special about a server. The mechanism behind Windows Update is identical, and the exact cause of his failure is easily apparent from CBS.log + CheckSUR.log.

If this was a Vista/7 computer, I would have fixed it by now. The errors detected are easy to diagnose and fix. If only I can track down someone else with an updated SBS 2008 server to grab a few pieces of info off.

I guess I was just slightly frustrated that I know exactly what is going on, I know exactly what needs to be done to fix this computer, I know exactly what piece of data I need to track down, and yet I am powerless to help.

Richard
 
Hi guys,

Thanks first of all to[FONT=meiryo ui, serif] 2xg, however I work with SBS on a daily basis and currently support somewhere in the region of 25 SBS servers from 2003 > 2011. This forum was my very last shot before doing an in place upgrade (oh my god it will make me cry), I'm not ringing Microsoft because they are slow useless and generally the "fix" is to reinstall or do an in place upgrade (grrr Microsoft !!!).

Thanks Niemiro for trying, if you really think with access to a working 2008 sbs server this could be fixed thats very easy for me to sort out for you (thankfully this is the only broken [/FONT][FONT=meiryo ui, serif]server I currently have!), if not with your workload then no worries and I will sheepishly suggest an in place upgrade as the only fix.
[/FONT][FONT=meiryo ui, serif]

[/FONT]
 
Steff said:
Hi guys,

Thanks first of all to 2xg, however I work with SBS on a daily basis and currently support somewhere in the region of 25 SBS servers from 2003 > 2011. This forum was my very last shot before doing an in place upgrade (oh my god it will make me cry), I'm not ringing Microsoft because they are slow useless and generally the "fix" is to reinstall or do an in place upgrade (grrr Microsoft !!!).

Thanks Niemiro for trying, if you really think with access to a working 2008 sbs server this could be fixed thats very easy for me to sort out for you (thankfully this is the only broken server I currently have!), if not with your workload then no worries and I will sheepishly suggest an in place upgrade as the only fix.
Click to expand...

Hello Steff :)

If you want to have one last shot, then great!

Following the instructions I previously provided you, can you please export and upload a COMPONENTS hive from both your broken server (I lost it, sorry), and a working server. The working server needs to be SBS 2008, of the same bit rate, and fully updated. I can then perform a transformation via CheckSUR.log to make a fix specific for the broken server, based on information from the working server.

Next, just in case it becomes necessary, can you please tell me which of these files I need to download, if you know: Download: SBS 2008 Trial Software Download - Microsoft Download Center - Download Details

Which bit rate are you (x86/x64/ia64)? And I am a bit confused by DVD1. I will invesitage over the weekend, but do you know off the top of your head whether I need DVD1 + one of DVD2/3, or just DVD2/3, or what? If you don't know off the top of your head, don't worry.

Thanks!

Richard

P.S. Microsoft Support can be amazingly good, and I have seen them work absolute miracles on stuff I previously thought was completely unfixable. It really depends whether you end up at unescalated outsourced Home Support, which is varied in its quality, or Premier/escalated support, though.

EDIT: Or the closest COMPONENTS hive you can get. For example, a COMPONENTS hive from a SBS 2008 of wrong bit rate, or not fully updated (!), is better than nothing.
 
Last edited:
Hello again Steff :)

Whilst the DVD is downloading, I had a slight problem downloading the COMPONENTS hives. Can you please confirm that they are publicly accessible, otherwise I shall assume it is a problem at my end and take a look.

Thank you!

Richard
 
Since you most certainly know your way around computers, I thought you might like to see something rather cool.

This is the first time I have ever seen this happen before.

Open up your broken COMPONENTS hive in notepad.exe, and search for "x86_microsoft-windows-p..-wsman-pluginworker_31bf3856ad364e35_none_9a4e9c942522ba6c". Now, I was expecting a fairly standard bitflip in the key's permissions, or ownership data, or similar.

What I actually saw surprised me greatly...CBS.log...:confused2:

I wonder whether this is NTFS metadata corruption. I don't know how well you know NTFS. Anyway, I will do my best to fix up the registry hive, and a bit of dataloss in CBS.log is not important.

Just thought I would share...

Richard
 
I wish I could pretend it was a surprise but this server seems to have been used and abused by a 3rd party company
 
Hello again Steff :)

I have tried everything I can think of, but I cannot fix this :( The corruptions are just too large, and I cannot make the parser accept the repaired registry hive. With simple point corruptions, I can sometimes fix the issue, but this corruption is really large and in multiple locations throughout the file. I have tried hard, but I cannot get it to work. I am really sorry, but you are going to have to Repair Install, and maybe even Clean Install if that won't work.

Richard
 
Hi there,

I can thank you enough for your efforts I shall now break the news to them

thanks

Steffan
 
Steff said:
Hi there,

I can thank you enough for your efforts I shall now break the news to them

thanks

Steffan
Click to expand...

You are more than welcome. Again, I am really sorry I was unable to fix this.

Richard
 
niemiro said:
Since you most certainly know your way around computers, I thought you might like to see something rather cool.

This is the first time I have ever seen this happen before.

Open up your broken COMPONENTS hive in notepad.exe, and search for "x86_microsoft-windows-p..-wsman-pluginworker_31bf3856ad364e35_none_9a4e9c942522ba6c". Now, I was expecting a fairly standard bitflip in the key's permissions, or ownership data, or similar.

What I actually saw surprised me greatly...CBS.log...:confused2:

I wonder whether this is NTFS metadata corruption. I don't know how well you know NTFS. Anyway, I will do my best to fix up the registry hive, and a bit of dataloss in CBS.log is not important.

Just thought I would share...

Richard
Click to expand...

I've finally found a few minutes spare to have a look at the hive and it completely stunned me - I've never seen anything like that before! So, so strange.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top