Re: Can WSS SP2 be installed by automatic Windows Updates?
- From: KC Matt <KCMatt@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 12:34:02 -0700
FYI - Here's what worked:
I installed Server 2003 SP1 and that made it obvious that wss sp2 had been
at least partially installed. Then a ran "stsadm -o upgrade" from a command
prompt and that seemed to "finish" the installation. After that, I didn't
get the site creation error from SPS.
"KC Matt" wrote:
Englebert,.
Thanks for the posting advice; it makes sense and I'll be sure to update
both groups when I figure out a solution.
Thanks also for the link, but I'd seen those numbers before. As I said, the
wss admin pages say that I'm only using sp1, but the error I'm getting is
attributable to wss sp2 and the file versions match those of sp2. So do I
have sp1 installed, or sp2? I _think_ I have a failed/partial installation
of wss sp2, I'm just not sure how to fix it.
I'm also not sure how it would have been installed to begin with. According
to the MS download page for wss sp2, the recommended method of installation
is to let the Windows Updates site scan the PC and install what's required.
So does that mean that it could be installed as a routine update if
"automatic updates" are enabled on the server? Has anyone else had a similar
experience?
Thanks,
--KC Matt
"Engelbert" wrote:
[This was also posted under a different title to the SPS newsgroup.
I've now seen your PS - it's just best to post to just one newsgroup and
second best to do genuine cross-posts (i.e. the same single message goes to
both newsgroups and replies are this seen in both so there is no duplication
of effort between the two newsgroups). As SPS always contains WSS this would
however lead to all SPS postings being sent to the WSS newsgroup making it
hard to find WSS only postings. So I'd post them to the SPS newsgroup if
given the choice.]
------------
What I would do is instead of checking the file versions would be to just
check the version number the SPS 2003 installation (and maybe separately
it's WSS part) is showing you.
This WSS FAQ item gives both WSS and SPS version numbers for various levels
of installations and how to find the version number(s)
http://www.asaris.de/sites/walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=71
and now will someone tell them in the SPS newsgroup that this attempt at an
answer has been posted here :) ?
Engelbert
"KC Matt" <KCMatt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B48BDF64-7D97-49DF-81CF-148810F9E307@xxxxxxxxxxxxxxxx
Here's my problem in a nutshell: I suspect that wss sp2 has been
incorrectly
applied to my sharepoint server via automatic updates and now I'm not sure
how to clean up the mess.
We have a Windows Server 2003 box (w/out SP1) running WSS 2.0 and SPS
2003.
Automatic Updates is enabled on this server.
I recently got this error when trying to create a new SPS area: "An error
has occurred in the portal site. Contact the portal site administrator for
assistance." I found this KB article
(http://support.microsoft.com/Default.aspx?id=910764) which basically
blames
it on wss sp2.
I've never explicitly installed wss sp2, but according to the sp2
description (kb id=887624) of how to tell whether the service pack is
installed, most of my files match the sp2 version numbers (e.g. stsadm.exe
=
11.0.6551.0, owssvr.dll = 11.0.6568.0, etc).
But when I go to the SPS Central Administration site and click the
"Configure virtual server settings from the Virtual Server List page"
link,
it loads a WSS Virtual Server List page that seems to say that I'm on WSS
sp1
because the version number associated with my portal site is 6.0.2.6361
and
the rightmost column says "upgrade". And when I click the site link I
don't
get the "Virtual Server Settings" page as expected, I get a help file page
implying I should run "stsadm.exe -o upgrade".
So I think I have a half-installed service pack, but I'm not sure where to
go from here. Should I simply upgrade the virtual server via stsadm?
e.g. stsadm.exe -o upgrade -url http://SPSsite (wss help page)
or stsadm.exe -o upgrade -forceupgrade (KB id=910764).
Or should I download wss sp2 and start the install from scratch? I'm
assuming I have to move forward because sp2 apparently can't be
uninstalled.
Also, how does Windows Server 2003 SP1 affect things? It's not currently
installed on that server, but it will be sooner or later. Should I
install
it before I install the Sharepoint stuff, or does it matter?
Note, I'm primarily a developer (who still has a lot to learn about server
admin); any advice will be appreciated. Thanks,
-- KC Matt
p.s. my apologies for cross posting such a long post, but I truly wasn't
sure which forum was more appropriate. I think the root of my problem is
WSS, but the error occurs in SPS and any solution/advice can't ignore the
existance of my portal.
- References:
- Can WSS SP2 be installed by automatic Windows Updates?
- From: KC Matt
- Re: Can WSS SP2 be installed by automatic Windows Updates?
- From: Engelbert
- Re: Can WSS SP2 be installed by automatic Windows Updates?
- From: KC Matt
- Can WSS SP2 be installed by automatic Windows Updates?
- Prev by Date: Re: Can WSS SP2 be installed by automatic Windows Updates?
- Next by Date: Re: WSS on same box as IIS?
- Previous by thread: Re: Can WSS SP2 be installed by automatic Windows Updates?
- Next by thread: adding a webpartpage by code result in unghosted page...
- Index(es):
Relevant Pages
|
