Changed my server name - Database problems

Hi:
I had to change my server name to meet company naming conventions.
Unfortunately, I forgot about WSUS beforehand.

Was running 3.0 SP1. Now can't install 3.0 SP2.
The SQL server instance won't start. I've tried uninstalling it using
msiexec as described in a Technet article, but that didn't work.
That article then referred me to KB 925976, but those instructions are
pretty vague.

Can anyone help me get WSUS working again?
Thanks,
Tony

"Tone-man 123" <> wrote in message
news:0E5F4A17-7618-461C-9001-...

> I had to change my server name to meet company naming conventions.
> Unfortunately, I forgot about WSUS beforehand.
>
> Was running 3.0 SP1. Now can't install 3.0 SP2.
> The SQL server instance won't start. I've tried uninstalling it using
> msiexec as described in a Technet article, but that didn't work.
> That article then referred me to KB 925976, but those instructions are
> pretty vague.
>
> Can anyone help me get WSUS working again?

Start here:
http://blogs.technet.com/sus/archive...l-of-wsus.aspx

SKIP the steps related to uninstalling the Windows Internal Database
(hopefully it's still intact on your server)

Refer to the Release Notes for the necessary remediation procedure to deal
with changing the server name after installing WSUS.
Then reinstall WSUS v3 SP1 and then upgrade to WSUS v3 SP2.

If previously existing WSUS v3 SP1 database no longer exists, or the Windows
Internal Database has been damaged (as a result of the previous attempt to
uninstall), then abort the installation, run the steps in the blog post for
uninstalling the WID, and install WSUS v3 SP2 and create a new database.

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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

thanks for the reply...

I followed the instructions on that page, and still no go.
The install log has errors on connecting to the instance of the
<sername>\microsoft##ssee database instance.

I even performed the steps that pertained to the database, and still no go.

Is there anything else that can completely wipe out the database?

Alternately, can I install an instance of SQL server express and use that
instance for WSUS? (If so, should I use 2005, 2008, other?)

thanks,

Tony





"Lawrence Garvin [MVP]" wrote:

> "Tone-man 123" <> wrote in message
> news:0E5F4A17-7618-461C-9001-...
>
> > I had to change my server name to meet company naming conventions.
> > Unfortunately, I forgot about WSUS beforehand.
> >
> > Was running 3.0 SP1. Now can't install 3.0 SP2.
> > The SQL server instance won't start. I've tried uninstalling it using
> > msiexec as described in a Technet article, but that didn't work.
> > That article then referred me to KB 925976, but those instructions are
> > pretty vague.
> >
> > Can anyone help me get WSUS working again?
>
> Start here:
> http://blogs.technet.com/sus/archive...l-of-wsus.aspx
>
> SKIP the steps related to uninstalling the Windows Internal Database
> (hopefully it's still intact on your server)
>
> Refer to the Release Notes for the necessary remediation procedure to deal
> with changing the server name after installing WSUS.
> Then reinstall WSUS v3 SP1 and then upgrade to WSUS v3 SP2.
>
> If previously existing WSUS v3 SP1 database no longer exists, or the Windows
> Internal Database has been damaged (as a result of the previous attempt to
> uninstall), then abort the installation, run the steps in the blog post for
> uninstalling the WID, and install WSUS v3 SP2 and create a new database.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"Tone-man 123" <> wrote in message
news:818B16EA-8E6A-4BD1-8D89-...

>> > Can anyone help me get WSUS working again?
>>
>> Start here:
>> http://blogs.technet.com/sus/archive...l-of-wsus.aspx
>>
>> SKIP the steps related to uninstalling the Windows Internal Database
>> (hopefully it's still intact on your server)

> I followed the instructions on that page, and still no go.
> The install log has errors on connecting to the instance of the
> <sername>\microsoft##ssee database instance.
>
> I even performed the steps that pertained to the database, and still no
> go.
>
> Is there anything else that can completely wipe out the database?

Well, yes, the steps in the blog post that I told you to skip will
completely wipe out the database. :-)

> Alternately, can I install an instance of SQL server express and use that
> instance for WSUS? (If so, should I use 2005, 2008, other?)

You can, but you Should Not. SQL Express Edition has a cap of 1GB RAM and a
4GB max database size. In most WSUS environments you'll run out of room in
the database and have to convert back within a matter of months, if not
weeks.

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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

OK.
Any other ideas?


"Lawrence Garvin [MVP]" wrote:

> "Tone-man 123" <> wrote in message
> news:818B16EA-8E6A-4BD1-8D89-...
>
> >> > Can anyone help me get WSUS working again?
> >>
> >> Start here:
> >> http://blogs.technet.com/sus/archive...l-of-wsus.aspx
> >>
> >> SKIP the steps related to uninstalling the Windows Internal Database
> >> (hopefully it's still intact on your server)
>
> > I followed the instructions on that page, and still no go.
> > The install log has errors on connecting to the instance of the
> > <sername>\microsoft##ssee database instance.
> >
> > I even performed the steps that pertained to the database, and still no
> > go.
> >
> > Is there anything else that can completely wipe out the database?
>
> Well, yes, the steps in the blog post that I told you to skip will
> completely wipe out the database. :-)
>
> > Alternately, can I install an instance of SQL server express and use that
> > instance for WSUS? (If so, should I use 2005, 2008, other?)
>
> You can, but you Should Not. SQL Express Edition has a cap of 1GB RAM and a
> 4GB max database size. In most WSUS environments you'll run out of room in
> the database and have to convert back within a matter of months, if not
> weeks.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"Tone-man 123" <> wrote in message
news:AB99D424-62DA-49C9-B934-...
> OK.
> Any other ideas?

If none of the idea already presented resolve your issue, then your next
option would be to reinstall the operating system because there is no reason
I can think of that these procedures, properly followed, will not clean
every possible bit of WSUS off of a server.


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

After reading a bit more on this, I realize there's one more bit of info that
might help....

I didn't just do a server name change.
I demoted it from a DC to a member server, changed the domain, and then
re-promoted it to a DC. Does that make a difference?

Also, what would be the gotcha's in using SQL server express? I don't have
time to wipe the server, and would love to just get this working now.

thanks,

Tony
"Lawrence Garvin [MVP]" wrote:

> "Tone-man 123" <> wrote in message
> news:AB99D424-62DA-49C9-B934-...
> > OK.
> > Any other ideas?
>
> If none of the idea already presented resolve your issue, then your next
> option would be to reinstall the operating system because there is no reason
> I can think of that these procedures, properly followed, will not clean
> every possible bit of WSUS off of a server.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

Oh, well I see you already answered my question.
I'll run out of room in months, if I use SQL server express.

I may just have to go with that for now, though.
Thanks,
Tony


"Tone-man 123" wrote:

> After reading a bit more on this, I realize there's one more bit of info that
> might help....
>
> I didn't just do a server name change.
> I demoted it from a DC to a member server, changed the domain, and then
> re-promoted it to a DC. Does that make a difference?
>
> Also, what would be the gotcha's in using SQL server express? I don't have
> time to wipe the server, and would love to just get this working now.
>
> thanks,
>
> Tony
> "Lawrence Garvin [MVP]" wrote:
>
> > "Tone-man 123" <> wrote in message
> > news:AB99D424-62DA-49C9-B934-...
> > > OK.
> > > Any other ideas?
> >
> > If none of the idea already presented resolve your issue, then your next
> > option would be to reinstall the operating system because there is no reason
> > I can think of that these procedures, properly followed, will not clean
> > every possible bit of WSUS off of a server.
> >
> >
> > --
> > Lawrence Garvin, M.S., MCITP:EA, MCDBA
> > Principal/CTO, Onsite Technology Solutions, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2009)
> >
> > My Blog: http://onsitechsolutions.spaces.live.com
> > Microsoft WSUS Website: http://www.microsoft.com/wsus
> > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
> >

"Tone-man 123" <> wrote in message
news4482D4A-0B0D-4000-A256-...
> After reading a bit more on this, I realize there's one more bit of info
> that
> might help....
>
> I didn't just do a server name change.
> I demoted it from a DC to a member server, changed the domain, and then
> re-promoted it to a DC. Does that make a difference?

L.O.L.

It makes a difference like whether the engine works in the race car or not!

You need to uninstall / reinstall Internet Information Services (and all of
the webapps sitting on top if it, like WSUS).


> Also, what would be the gotcha's in using SQL server express?

SQL Server Express has hard-limitations on resource usage.
It can only use 1 CPU, it can only use 1GB RAM, and it has a maximum
database size of 4GB.

I recommend against using SQL Server Express for WSUS.
I know of no scenario in which the use of SQL Express for WSUS would be
advantageous.


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin