MMC could not create the snap-in

Hi.

Our WSUS installation has been running smoothly for a long time, but all of
a sudden I can't launch the console.

Launcing the console fails with "MMC could not create the snap-in" and a ref
to a CLSID: FX:{bla bla bla...}

It's WSUS 3 sp1 running on a Server 2003 R2 Std.

The server seems to be running just fine. It seems to be dowwnloading
updates and the clients can connect and downlaod updates.

Only issue is the damn console, which is a problem since I can't administer
anything

Tried to connect remotely, but The WSUS is not listening on any ports.

I tried reinstalling the WSUS sp1, but I keep geting an error after the
fileextraction - something about a command line value that is unvalid !!!

Any help would be greatly appriciated

"Jannik" <> wrote in message
news:853C3E3B-7E7C-4084-87AC-...

> Tried to connect remotely, but The WSUS is not listening on any ports.

Well, this is not normal, and probably explains why the server console
cannot connect either.

> I tried reinstalling the WSUS sp1, but I keep geting an error after the
> fileextraction - something about a command line value that is unvalid !!!

That's not helping either, I'm certain.

> Any help would be greatly appriciated

Providing *exact* error messages would be a good start.

Describing exactly what you are doing can often be helpful as well.

And, of course, the same basic question that always applies to "It worked
but now it doesn't".... What Changed!?



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thx for the answer )

I am not sure I can provide that much more info, since I am in the dark as
well.

But let me try.

What changed:
Well I can't rly say. No operators has logged on to the server for the last
month and thus no apps has been installed or removed.
The only thing, which actually is a bit scary come to think about it, is a
series of automatic Windows file protection actions taken a month ago.
I can find no cause to theese being made. Again - no operators has been
logged on to the system, and no patches or apps has been installed.
Is this related ?? I dunno. I just realised the error 3 days ago and I can't
seem to establish a presice timeline.

Error msg.

The only thing I have omitted is the errormsg from the reinstall which I
find irelevant since the problem is related to why the current installation
failed.
But this is the setuplog from the reinstall:
2009-07-30 10:48:45 Error MWUSSetup ParseCommandLine: Failed
to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error
0x80070002: The system cannot find the file specified.)
2009-07-30 10:48:47 Error MWUSSetup DoInstall:
ParseCommandLine failed (Error 0x80041453)

What was I doing:
I opened the MMC - nothing fancy in that

On google I can see others with the same problem dating back to 2007, and
without any solutions

Again - the WSUS it self seem to be running just fine, but I can't connect
because of a faulty MMC snap-in.

Basically it should be a simpel fix. All I need is the Snap-in to be
fixed/reinitiated. No need to reinstall servers or databases. )

I am not sure how much more I can contribute, so please ask away.

/Jannik





"Lawrence Garvin [MVP]" wrote:

> "Jannik" <> wrote in message
> news:853C3E3B-7E7C-4084-87AC-...
>
> > Tried to connect remotely, but The WSUS is not listening on any ports.
>
> Well, this is not normal, and probably explains why the server console
> cannot connect either.
>
> > I tried reinstalling the WSUS sp1, but I keep geting an error after the
> > fileextraction - something about a command line value that is unvalid !!!
>
> That's not helping either, I'm certain.
>
> > Any help would be greatly appriciated
>
> Providing *exact* error messages would be a good start.
>
> Describing exactly what you are doing can often be helpful as well.
>
> And, of course, the same basic question that always applies to "It worked
> but now it doesn't".... What Changed!?
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"Jannik" <> wrote in message
news:C7E1C085-EE67-4102-9499-...
> Thx for the answer )
>
> I am not sure I can provide that much more info, since I am in the dark as
> well.

Then you'll have to figure out a way out of the dark, because if you can't
provide details, we cannot possibly assist in finding a solution.

> What changed:
> Well I can't rly say.

Okay.. that's your first assignment. Find out what was changed and who
changed it. Sometimes the who is easier than the what. Find out if anybody
changed anything in the entire network environment, and then narrow it down
from there.

> The only thing, which actually is a bit scary come to think about it, is a
> series of automatic Windows file protection actions taken a month ago.

That's not good.

> I can find no cause to theese being made.

I would imagine this is something you'll want to find the cause for.

> Again - no operators has been
> logged on to the system,

Do you have remote consoles installed?

What's logged in the Change.LOG at \Program Files\Update Services\Logfiles?

> But this is the setuplog from the reinstall:
> 2009-07-30 10:48:45 Error MWUSSetup ParseCommandLine: Failed
> to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key
> (Error
> 0x80070002: The system cannot find the file specified.)

If you were attempting to do a reinstall after an uninstall, and the
uninstall was defective, this key may have been removed when the installer
expected to see it.

I'd suggest first, since you've already gone down the uninstall/reinstall
road, go back and make sure the UNinstall is fully completed. The following
resources should be non existent:

\Program Files\Update Services
HKLM\Software\Microsoft\Windows\Update Services
\WSUS\UpdateServicesDBFiles\SUSDB.mdf and SUSDB_log.LDF

> Again - the WSUS it self seem to be running just fine, but I can't connect
> because of a faulty MMC snap-in.

Actually much more is faulty now -- you apparently have a failed
uninstall/reinstall, so the failure of the console connect at this point is
not really relevant to much at all.

The one question you've not answered is to describe the configuration of the
WSUS Server.
What OS?
What SP?
What version of WSUS?
What else is running on the machine?
Are there any other WSUS servers?
What hardware?

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" wrote:

> "Jannik" <> wrote in message
> news:C7E1C085-EE67-4102-9499-...
> > Thx for the answer )
> >
> > I am not sure I can provide that much more info, since I am in the dark as
> > well.
>
> Then you'll have to figure out a way out of the dark, because if you can't
> provide details, we cannot possibly assist in finding a solution.

Comments like that is not excatly helping out - u know
>
> > What changed:
> > Well I can't rly say.
>
> Okay.. that's your first assignment. Find out what was changed and who
> changed it. Sometimes the who is easier than the what. Find out if anybody
> changed anything in the entire network environment, and then narrow it down
> from there.

Since I am the only one with access, I can pretty much rule out changes.

> > The only thing, which actually is a bit scary come to think about it, is a
> > series of automatic Windows file protection actions taken a month ago.
>
> That's not good.

I know - but Windows has logged nothing detailed about this - besides that
it has been done - Bug in SVR 2003 ??

>
> > I can find no cause to theese being made.
>
> I would imagine this is something you'll want to find the cause for.

Yes - but since The OS is not very informative I kinda have a problem there.
>
> > Again - no operators has been
> > logged on to the system,
>
> Do you have remote consoles installed?

Yes - which only I can Access.

>
> What's logged in the Change.LOG at \Program Files\Update Services\Logfiles?
>

Only normal loginfo, Nothing out of the ordinary

> > But this is the setuplog from the reinstall:
> > 2009-07-30 10:48:45 Error MWUSSetup ParseCommandLine: Failed
> > to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key
> > (Error
> > 0x80070002: The system cannot find the file specified.)
>
> If you were attempting to do a reinstall after an uninstall, and the
> uninstall was defective, this key may have been removed when the installer
> expected to see it.
>
> I'd suggest first, since you've already gone down the uninstall/reinstall
> road, go back and make sure the UNinstall is fully completed. The following
> resources should be non existent:
>
> \Program Files\Update Services
> HKLM\Software\Microsoft\Windows\Update Services
> \WSUS\UpdateServicesDBFiles\SUSDB.mdf and SUSDB_log.LDF
>
> > Again - the WSUS it self seem to be running just fine, but I can't connect
> > because of a faulty MMC snap-in.
>
> Actually much more is faulty now -- you apparently have a failed
> uninstall/reinstall, so the failure of the console connect at this point is
> not really relevant to much at all.

Yes it is relevant !
Did u think I did all the install/reinstall on the actual production machine
??
I did a P2V and moved the VM into the testing env.

>
> The one question you've not answered is to describe the configuration of the
> WSUS Server.
> What OS?
> What SP?
> What version of WSUS?
> What else is running on the machine?
> Are there any other WSUS servers?
> What hardware?

Lawrence - I appreciate the effort but I think this is kinda going no where.

- You are not reading the info I provide.
- Your answers are patronizing

I think someone else would be better off with your assistance.

Once again thank you for taking the time.

/Jannik

>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

Jannik;
Did you ever resolve this? I'm having the same issue ( see my new thread)
rgds
S

"Jannik" wrote:

>
> "Lawrence Garvin [MVP]" wrote:
>
> > "Jannik" <> wrote in message
> > news:C7E1C085-EE67-4102-9499-...
> > > Thx for the answer )
> > >
> > > I am not sure I can provide that much more info, since I am in the dark as
> > > well.
> >
> > Then you'll have to figure out a way out of the dark, because if you can't
> > provide details, we cannot possibly assist in finding a solution.
>
> Comments like that is not excatly helping out - u know
> >
> > > What changed:
> > > Well I can't rly say.
> >
> > Okay.. that's your first assignment. Find out what was changed and who
> > changed it. Sometimes the who is easier than the what. Find out if anybody
> > changed anything in the entire network environment, and then narrow it down
> > from there.
>
> Since I am the only one with access, I can pretty much rule out changes.
>
> > > The only thing, which actually is a bit scary come to think about it, is a
> > > series of automatic Windows file protection actions taken a month ago.
> >
> > That's not good.
>
> I know - but Windows has logged nothing detailed about this - besides that
> it has been done - Bug in SVR 2003 ??
>
> >
> > > I can find no cause to theese being made.
> >
> > I would imagine this is something you'll want to find the cause for.
>
> Yes - but since The OS is not very informative I kinda have a problem there.
> >
> > > Again - no operators has been
> > > logged on to the system,
> >
> > Do you have remote consoles installed?
>
> Yes - which only I can Access.
>
> >
> > What's logged in the Change.LOG at \Program Files\Update Services\Logfiles?
> >
>
> Only normal loginfo, Nothing out of the ordinary
>
> > > But this is the setuplog from the reinstall:
> > > 2009-07-30 10:48:45 Error MWUSSetup ParseCommandLine: Failed
> > > to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key
> > > (Error
> > > 0x80070002: The system cannot find the file specified.)
> >
> > If you were attempting to do a reinstall after an uninstall, and the
> > uninstall was defective, this key may have been removed when the installer
> > expected to see it.
> >
> > I'd suggest first, since you've already gone down the uninstall/reinstall
> > road, go back and make sure the UNinstall is fully completed. The following
> > resources should be non existent:
> >
> > \Program Files\Update Services
> > HKLM\Software\Microsoft\Windows\Update Services
> > \WSUS\UpdateServicesDBFiles\SUSDB.mdf and SUSDB_log.LDF
> >
> > > Again - the WSUS it self seem to be running just fine, but I can't connect
> > > because of a faulty MMC snap-in.
> >
> > Actually much more is faulty now -- you apparently have a failed
> > uninstall/reinstall, so the failure of the console connect at this point is
> > not really relevant to much at all.
>
> Yes it is relevant !
> Did u think I did all the install/reinstall on the actual production machine
> ??
> I did a P2V and moved the VM into the testing env.
>
> >
> > The one question you've not answered is to describe the configuration of the
> > WSUS Server.
> > What OS?
> > What SP?
> > What version of WSUS?
> > What else is running on the machine?
> > Are there any other WSUS servers?
> > What hardware?
>
> Lawrence - I appreciate the effort but I think this is kinda going no where.
>
> - You are not reading the info I provide.
> - Your answers are patronizing
>
> I think someone else would be better off with your assistance.
>
> Once again thank you for taking the time.
>
> /Jannik
>
> >
> > --
> > Lawrence Garvin, M.S., MCITP:EA, MCDBA
> > Principal/CTO, Onsite Technology Solutions, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2009)
> >
> > MS WSUS Website: http://www.microsoft.com/wsus
> > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
> >
> >

Hi DemoDog.

I'm affraid I have bad news 4 u

If u google the net for this issue u will find refs dating back 2 years.
Microsoft still has no solution for this issue, and they seem to be ignoring
it.

I installed WSUS on a different machine.
Stopped the services
copied the database
Started services.

And guess what !! Now it is working and all the settings and approvals from
the old installation is working just fine on the new

So - from an interlectual point of view I would like to find the cause, but
IRL ...- Don't wate u'r time with Microsoft - reinstall WSUS and just move
the database.

/Jannik

"DemoDog" wrote:

> Jannik;
> Did you ever resolve this? I'm having the same issue ( see my new thread)
> rgds
> S
>
> "Jannik" wrote:
>
> >
> > "Lawrence Garvin [MVP]" wrote:
> >
> > > "Jannik" <> wrote in message
> > > news:C7E1C085-EE67-4102-9499-...
> > > > Thx for the answer )
> > > >
> > > > I am not sure I can provide that much more info, since I am in the dark as
> > > > well.
> > >
> > > Then you'll have to figure out a way out of the dark, because if you can't
> > > provide details, we cannot possibly assist in finding a solution.
> >
> > Comments like that is not excatly helping out - u know
> > >
> > > > What changed:
> > > > Well I can't rly say.
> > >
> > > Okay.. that's your first assignment. Find out what was changed and who
> > > changed it. Sometimes the who is easier than the what. Find out if anybody
> > > changed anything in the entire network environment, and then narrow it down
> > > from there.
> >
> > Since I am the only one with access, I can pretty much rule out changes.
> >
> > > > The only thing, which actually is a bit scary come to think about it, is a
> > > > series of automatic Windows file protection actions taken a month ago.
> > >
> > > That's not good.
> >
> > I know - but Windows has logged nothing detailed about this - besides that
> > it has been done - Bug in SVR 2003 ??
> >
> > >
> > > > I can find no cause to theese being made.
> > >
> > > I would imagine this is something you'll want to find the cause for.
> >
> > Yes - but since The OS is not very informative I kinda have a problem there.
> > >
> > > > Again - no operators has been
> > > > logged on to the system,
> > >
> > > Do you have remote consoles installed?
> >
> > Yes - which only I can Access.
> >
> > >
> > > What's logged in the Change.LOG at \Program Files\Update Services\Logfiles?
> > >
> >
> > Only normal loginfo, Nothing out of the ordinary
> >
> > > > But this is the setuplog from the reinstall:
> > > > 2009-07-30 10:48:45 Error MWUSSetup ParseCommandLine: Failed
> > > > to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key
> > > > (Error
> > > > 0x80070002: The system cannot find the file specified.)
> > >
> > > If you were attempting to do a reinstall after an uninstall, and the
> > > uninstall was defective, this key may have been removed when the installer
> > > expected to see it.
> > >
> > > I'd suggest first, since you've already gone down the uninstall/reinstall
> > > road, go back and make sure the UNinstall is fully completed. The following
> > > resources should be non existent:
> > >
> > > \Program Files\Update Services
> > > HKLM\Software\Microsoft\Windows\Update Services
> > > \WSUS\UpdateServicesDBFiles\SUSDB.mdf and SUSDB_log.LDF
> > >
> > > > Again - the WSUS it self seem to be running just fine, but I can't connect
> > > > because of a faulty MMC snap-in.
> > >
> > > Actually much more is faulty now -- you apparently have a failed
> > > uninstall/reinstall, so the failure of the console connect at this point is
> > > not really relevant to much at all.
> >
> > Yes it is relevant !
> > Did u think I did all the install/reinstall on the actual production machine
> > ??
> > I did a P2V and moved the VM into the testing env.
> >
> > >
> > > The one question you've not answered is to describe the configuration of the
> > > WSUS Server.
> > > What OS?
> > > What SP?
> > > What version of WSUS?
> > > What else is running on the machine?
> > > Are there any other WSUS servers?
> > > What hardware?
> >
> > Lawrence - I appreciate the effort but I think this is kinda going no where.
> >
> > - You are not reading the info I provide.
> > - Your answers are patronizing
> >
> > I think someone else would be better off with your assistance.
> >
> > Once again thank you for taking the time.
> >
> > /Jannik
> >
> > >
> > > --
> > > Lawrence Garvin, M.S., MCITP:EA, MCDBA
> > > Principal/CTO, Onsite Technology Solutions, Houston, Texas
> > > Microsoft MVP - Software Distribution (2005-2009)
> > >
> > > MS WSUS Website: http://www.microsoft.com/wsus
> > > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
> > >
> > >

"Jannik" <> wrote in message
news:4057514D-4A5B-4657-8312-...
> Hi DemoDog.
>
> I'm affraid I have bad news 4 u
>
> If u google the net for this issue u will find refs dating back 2 years.
> Microsoft still has no solution for this issue, and they seem to be
> ignoring
> it.

They're not ignoring it. It's not a problem with the *product*.

In *every* instance I've seen where this type of issue has appeared, the
solution was ultimately traced to an implementation-specific issue.

The most common issue is that the MSC file is corrupted.
The second most common issue is that either the client or the server are
misconfigured.

Just recently a thread that had gone for several weeks was ultimately traced
to an issue where the database had been migrated from WID to SQL Server, but
the wYukonIsInstalled registry value had never been reset to false. This
caused a whole host of issues, including the ability to connect to the
console.

> I installed WSUS on a different machine.
> Stopped the services
> copied the database
> Started services.
>
> And guess what !! Now it is working and all the settings and approvals
> from
> the old installation is working just fine on the new

Which suggests something was FUBAR on the original WSUS SERVER.... yes?


> So - from an interlectual point of view I would like to find the cause,
> but
> IRL ...- Don't wate u'r time with Microsoft - reinstall WSUS and just move
> the database.

Blaming the vendor for issues that, based on your own comments, are
obviously an issue with your *specific* installation will not endear you to
those of us in this group who *volunteer* our time to help you. Remember
this in the future, as I'll remember your disposition to blame the vendor,
rather than accept the possibility that your own server is the cause.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Everone's help help is always appreciated, of course, but in my own case
WSUS3SP1 had been up and running for more than a year. This week it stopped.

Uninstall/reinstall went nowhere for me. At this time, it's broken to the
point where I can no longer even uninstall it, owing to an error, no other
reference. I had, rather foolishly I guess, tried to unstall update services
from the control panel and that led to no end of problems.
I installed WSUS on another server, but WSUS was unable to recognize the db
I copied from the old server. At this point I'm rebuilding my update services
environment from scratch.
rgds
S



"Lawrence Garvin [MVP]" wrote:

> "Jannik" <> wrote in message
> news:4057514D-4A5B-4657-8312-...
> > Hi DemoDog.
> >
> > I'm affraid I have bad news 4 u
> >
> > If u google the net for this issue u will find refs dating back 2 years.
> > Microsoft still has no solution for this issue, and they seem to be
> > ignoring
> > it.
>
> They're not ignoring it. It's not a problem with the *product*.
>
> In *every* instance I've seen where this type of issue has appeared, the
> solution was ultimately traced to an implementation-specific issue.
>
> The most common issue is that the MSC file is corrupted.
> The second most common issue is that either the client or the server are
> misconfigured.
>
> Just recently a thread that had gone for several weeks was ultimately traced
> to an issue where the database had been migrated from WID to SQL Server, but
> the wYukonIsInstalled registry value had never been reset to false. This
> caused a whole host of issues, including the ability to connect to the
> console.
>
> > I installed WSUS on a different machine.
> > Stopped the services
> > copied the database
> > Started services.
> >
> > And guess what !! Now it is working and all the settings and approvals
> > from
> > the old installation is working just fine on the new
>
> Which suggests something was FUBAR on the original WSUS SERVER.... yes?
>
>
> > So - from an interlectual point of view I would like to find the cause,
> > but
> > IRL ...- Don't wate u'r time with Microsoft - reinstall WSUS and just move
> > the database.
>
> Blaming the vendor for issues that, based on your own comments, are
> obviously an issue with your *specific* installation will not endear you to
> those of us in this group who *volunteer* our time to help you. Remember
> this in the future, as I'll remember your disposition to blame the vendor,
> rather than accept the possibility that your own server is the cause.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"DemoDog" <> wrote in message
news:F67B5A7D-72ED-4228-B8A5-...
> Everone's help help is always appreciated, of course, but in my own case
> WSUS3SP1 had been up and running for more than a year.

*EXCELLENT*

> This week it stopped.

The good news here is that we know definitively that "it stopped" because of
something that happened at your site, and not something with the product
itself. Furthermore, applications don't just "stop".. some *external* event
is almost always responsible. In these situations the BEST "First Step" is
to identify the time period in which the problem first appered. The shorter
the time window, the better. Then survey every human being that could have
had any contact with any system involved in the WSUS environment, and
enumerate everything they did to those system(s) during the identified time
frame. Then ask them again -- because about 50% of the time it's something
somebody "thought" would have no effect -- and they were simply wrong. (Btw,
this is why organizations implement Change Management -- so potential
changes are discussed with all parties before the change is implemented.
Change Management prevents a lot of these scenarios.)


> Uninstall/reinstall went nowhere for me.

Uninstall/reinstall *rarely* fixes a configuration issue caused by something
done somewhere else -- which about 70% of the time is the cause when "WSUS
... stops working". Reinstalling software into a misconfigured network
environment won't fix a software installation that wasn't broken to begin
with. In fact, doing anything in the name of remediation/repair without
having a specific reason and a specific cause it's designed to repair,
usually results in nothing but wasted time...

> At this time, it's broken to the
> point where I can no longer even uninstall it, owing to an error,

....Or something like this: The uinstallation has issues -- sometimes a
direct cause of the real problem not being resolved -- and then countless
hours are spent trying to fix the uninstallation, and the *real* problem
gets lost in the mix.

Identify the problem first -- usually this requires a fair amount of
investigation, diagnostics, and analysis. Then identify appropriate
solutions, the expected results, and *document* everything done in the name
of the repair, so it can be safely undone at the first sign of a less than
perfect progression of events.


> I installed WSUS on another server, but WSUS was unable to recognize the
> db
> I copied from the old server.

Yeah.. that's quite possible. "Copying" a database from one server to
another requires a very specific procedure or it'll end up in a corrupted
copy of the database -- and possibly corrupting the original database as
well. I suspect that is what's happened here -- the copy is defective. Do
you still have the *original* database? Assuming the original database is
still available, and not corrupted, I can help you to get the original
database restored to your new WSUS server.

> At this point I'm rebuilding my update services environment from scratch.

Or... you could do this.

But don't forget.. the *original* issue is probably still present

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin