Re: WSUS and WSS 3.0 broken

A Standard CD set is:
4 CDs (CD1-4) which is, basically, SBS 2003 Sp1.
CD5 is Outlook
CD6 is R2 Technologies (This is the one you want)
(These 6 CDs are numbered as such in folders on the DVD)

Premium has 2 additional CDs.
Premium Technologies (which may or may not have R2 on it, haven't got a set
in front of me to check)
FrontPage

"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FF50D0E8-B324-4704-8637-D879C0581D8F@xxxxxxxxxxxxxxxx
There are the 4 SBS r2 cd's and 2 SBS r2 Premium Technologies cd's. I take
it
that I am using the 1 SBS r2 cd.

Thanks for the clarification.

--
Hugh


"Dave Nickason [SBS MVP]" wrote:

I'm not sure what you mean when you ask which CD? I'm at work and
apparently my R2 disks are at home, but it would be the R2 CD from your
SBS
disks (not Premium Technologies, that should be a separate one).


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D680A54-8246-436F-9851-A8586BF2C9F3@xxxxxxxxxxxxxxxx
I uninstalled WSUS from the CP but when I reinstall (not from the CD) it
try
to look for the Microsoft##SSEE instance.

Do you happen to know which Premium Technologies R2 CD I can run the
WSUS
setup from?

I will continue to google and let you know if I find a resolution.

Thanks for your help.

--
Hugh


"Dave Nickason [SBS MVP]" wrote:

You don't need to reinstall WSUS, but then you'll need to come up with
an
alternative method of patching your workstations (and just as
importantly,
verifying that they are patched).

You might want to look at the WSUS release notes - I'm pretty sure
there's
some information about recovering from a failed upgrade that might
apply
here. Or, google the exact text of the error message you get when the
installation fails. What happens if you try to uninstall WSUS from CP
Add/Remove, then reinstall?



"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEB91083-B04E-4960-AFDE-5D7A88932251@xxxxxxxxxxxxxxxx
Dave,

I was able to work on the issue last evening - ended up being an all
nighter
:)

Short story: I was able to uninstall SBS r2 components which made
the
WSUS
421 errors go away and allowed the system to be more responsive
(users
were
seeing applications freezing up). However, I was unable to reinstall
the
r2
components - servername\Microsoft##SSEE error said something like
cannot
find
instance...

However, SBS monitoring & reporting now works as does WSS 2.0. I
have
uninstalled WSS 3.0 and have yet to reinstall it to see if it works.

Question - Do I need to reinstall WSUS and will it have any negative
impact
if I do not?

Any suggestions or information what might be preventing me from
reinstalling?

Thanks again for all guidance.

Regards,
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

No, I'd just uninstall/reinstall the broken parts. You can do WSS
3.0
with
the same documentation you originally installed it with. I can't
think
of a
reason the installation order would matter, but ultimately you'll
find
out
when you try it. I'd do a good full backup before starting (unless
you've
already got a recent enough one).


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B42F768F-A111-4BDD-9EDB-777F4328BEA6@xxxxxxxxxxxxxxxx
Dave,

I failed to mention that the WSS 2.0 and companyweb are
accessible,
but
the
WSS 3.0 that is a standalone install and WSUS 3.0 are not?

Do I still need to uninstall WSS 2.0/companyweb?

Thanks.
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

I'm not sure if there's a recommended order for doing this. I'd
read
the
documentation first, and then if you don't find specific
guidance,
I
would
uninstall both, then reinstall companyweb, then reinstall WSUS.

How to remove and how to install the Windows Small Business
Server
2003
SharePoint Services 2.0 companyweb Web site
http://support.microsoft.com/kb/829114

Is this R2? If so, just uninstall WSUS, then reinstall from the
R2
CD.
Otherwise, do the reinstall this way:

Installing Windows Server Update Services 3.0 on Windows Small
Business
Server 2003
http://technet.microsoft.com/en-us/library/cc708091.aspx


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B6D56962-D8DF-4A83-92D0-A4E0B805C461@xxxxxxxxxxxxxxxx
Dave,

I do not have data in the companyweb so I would consider going
the
reinstall
route for companyweb and WSS. I would appreciate your
assistance
with
this.

Also, I do not have shadow copy enabled on any of the hard
drive.

Thanks for the help.
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

I'm assuming you have data in your companyweb site that you
don't
want
to
lose. In that case, I'd recommend calling CSS (Microsoft
support)
and
letting them walk you through the restore procedure.

If you don't have data at risk, you could just reinstall
companyweb
and
WSUS. Please post back if you need help going that route.

By the way, you might be able to get those database files
back
from
shadow
copies if they're enabled on the drive where the database was
installed.

"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F289A62-C152-40DA-9091-9CF42BB90B6F@xxxxxxxxxxxxxxxx
Nick,

Unfortunately the documentation just gave me the command
line
string
but
did
not provide the files and paths to the uninstalled db.

I appreciate your input and will post the solution when I
find
one.

Regards.
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

Sorry, I don't know the path offhand. My own server has a
custom
WSUS
install to its own drive, and it was upgraded from WSUS 2,
so
I
can't
say
for sure where they belong. Can you tell from the
document
that
recommended
deleting the database?

"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A7AE7B7-5C01-44EE-A59F-EDE2BBE80519@xxxxxxxxxxxxxxxx
Dave,

Thanks for the prompt reply. I run a full daily backup
but
am
unsure
as
to
the correct path that I need to restore to. I did not
want
to
restore
the
incorrect files.

Any ideas as to what the correct path might be?

Thanks again for your assistance.
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

Can you restore a backup of that database? That
database
is
shared
by
things other than WSUS, which I believe is what you're
running
into
here -
WSS uses that database in addition to WSUS, so you're
going
to
have
to
restore it in order to get WSS working again.


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:513C1BE1-BA8C-450E-9F81-FEAD8AB52325@xxxxxxxxxxxxxxxx
In trying to troubleshoot WSUS 3.0, I saw a post that
directed
me
to
remove
the Windows Internal Database and reinstall WSUS. Now
my
WSS
3.0
and
WSUS
applications are broken. I have tried reinstalling
both
WSS
and
WSUS
but I
get a message that "failed to start the database
service
MSSQL$Microsoft##SSEE".

Also, my event log is a sea of red - Windows Server
Update
Services
Event
421: Connection to database failed. Reason=SQL Server
does
not
exist
or
access denied...:

Any suggestions or assistance as how to fix these
applications
is
greatly
appreciated.

--
Hugh
















.

Relevant Pages

  • Re: WSUS and WSS 3.0 broken
    ... Do you happen to know which Premium Technologies R2 CD I can run the WSUS ... Add/Remove, then reinstall? ... SBS monitoring & reporting now works as does WSS 2.0. ... How to remove and how to install the Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... Thanks for clarifying - I'll check for CD6 R2 Technologies and use it. ... You might want to look at the WSUS release notes - I'm pretty sure ... Add/Remove, then reinstall? ... SBS monitoring & reporting now works as does WSS 2.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... I was able to uninstall SBS r2 components which made the WSUS ... SBS monitoring & reporting now works as does WSS 2.0. ... uninstalled WSS 3.0 and have yet to reinstall it to see if it works. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... Do you happen to know which Premium Technologies R2 CD I can run the WSUS ... Add/Remove, then reinstall? ... I was able to uninstall SBS r2 components which made the WSUS ... SBS monitoring & reporting now works as does WSS 2.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... I'd read the documentation first, and then if you don't find specific guidance, I would uninstall both, then reinstall companyweb, then reinstall WSUS. ... you might be able to get those database files back from shadow ...
    (microsoft.public.windows.server.sbs)
Loading