Re: Cannot upgrade WSS 2.0 to 3.0
- From: "Mike Walsh" <englantilainen@xxxxxxxxxxx>
- Date: Tue, 28 Nov 2006 07:43:31 +0200
(So you spotted the Ernie thread :) )
The only thing I have is to wonder whether your problems are being caused by
having WSUS on the same server.
I remember seeing some threads about problems with WSUS and WSS v3 (I think
it was v3).
But that's all I have. I have WSSv3 (but only that) running on a VM with
less than 400MB so a clean install with the built-in db system is possible
with that amount of memory.
Mike Walsh
(I agree with your assessment of the error message - if you sign up for MSDN
managed newsgroups then you would have the attention (here) of people within
the Microsoft sphere who might be able to "translate" that error message.)
"MondaleA" <fud@xxxxxxx> wrote in message
news:OMxUOomEHHA.4024@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Mike, sorry about the cross-posts (or am I really Ernie?).
The server is W2K3EE *R2* which had the "built-in" WSS 2.0 with (W)MSDE
(2000). WSUS 2.0 was also installed with its own instance of (W)MSDE. The
server has a mere .5 GB RAM, and the SQL2005 "upgrade advisor" gave a
warning about borderline low RAM. I proceeded anyway, and then moved the
WSS2.0 DB from WMSDE to SQL 2005 with detach/attach. I attempted to do so
with the WSUS DB (so as to remove all the MSDE installations and free up a
bit of RAM).
It all seemed to function correctly at that point in terms of WSS
useability and admin. Then I upgraded to WSS3.0 and DotNetFX 3.0. The
wizard auto-ran but never gets past step 1. See errors I posted at the top
of the post. They aren't too useful (sadly, this is typical) by any but an
MS Professional Services Support person.
"Mike Walsh" <englantilainen@xxxxxxxxxxx> wrote in message
news:eViqsyXEHHA.3768@xxxxxxxxxxxxxxxxxxxxxxx
It's a pity you didn't add this information (SQL 2005 developer edition)
to the existing thread where you already posted the error message in full
and also added (on request) the information about step 1 as now we have
two open threads - seemingly from different people.
Could you say everything you did on this server before starting to
install WSS 3.0 and als when you installed WSS 3.0 did you select Basic
or Advanced Installation. Also which edition of Wondows Server 2003 this
was - i.e. was it perhaps Web Edition?
Finally when you installed SQL Server 2005 developer edition which
authority did you install it under and did you select Windows
Authentication or Mixed.
Finally how much memory do you have.
All might help to get to grips with this. It is very unusual for WSS
installs to fail at Step 1.
Mike Walsh
WSS FAQ www.wssv3faq.com / wss.collutions.com
No private questions please (additions to FAQ welcome)
"news.microsoft.com" <almo@xxxxxxxxxx> wrote in message
news:Ox0YkiXEHHA.348@xxxxxxxxxxxxxxxxxxxxxxx
Step 1 of the wizard completes with the following errors, have a SQL2005
developer edition running as backend to WSS 2.0 on same server. Anyone
have ideas?
Thanks!
Alex
---------- WSS3.LOG
11/26/2006 11:20:01 6 ERR The process
C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\bin\prescan.exe exited with return code 1
11/26/2006 11:20:01 6 ERR Detected that the
prescan.exe has not been run yet.
11/26/2006 11:20:01 6 ERR Task initialize
has failed with a PostSetupConfigurationTaskException An exception of
type
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException
was thrown. Additional exception information: The pre-upgrade scan tool
has not yet been run successfully on all content databases in the server
farm. The pre-upgrade scan tool must complete without errors before you
can continue with the upgrade process.
11/26/2006 11:20:01 6 ERR An exception of
type
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException
was thrown. Additional exception information: The pre-upgrade scan tool
has not yet been run successfully on all content databases in the server
farm. The pre-upgrade scan tool must complete without errors before you
can continue with the upgrade process.
11/26/2006 11:20:01 6 ERR Task initialize
has failed
11/26/2006 11:20:01 1 ERR Task
initialize has stopped and failed. Total failed is now 1
11/26/2006 11:20:02 5 ERR Task initialization
failed, so stopping execution of the engine
11/26/2006 11:20:02 5 ERR Failed to initialize
SharePoint Products and Technologies upgrade.
11/26/2006 11:20:02 5 ERR One or more
configuration tasks has failed or some tasks were not run
11/26/2006 11:20:04 5 ERR One or more
configuration tasks has failed to execute
11/26/2006 11:20:04 5 ERR Configuration of
SharePoint Products and Technologies failed. Configuration must be
performed in order for this product to operate properly. To diagnose the
problem, review the extended error information located at C:\Program
Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS\PSCDiagnostics_11_26_2006_11_19_48_25_462277996.log,
fix the problem, and run this configuration wizard again.
.
- References:
- Re: Cannot upgrade WSS 2.0 to 3.0
- From: Mike Walsh
- Re: Cannot upgrade WSS 2.0 to 3.0
- From: MondaleA
- Re: Cannot upgrade WSS 2.0 to 3.0
- Prev by Date: Re: Send to document library
- Next by Date: Re: Search functionality
- Previous by thread: Re: Cannot upgrade WSS 2.0 to 3.0
- Next by thread: Change Modifiy date to 'Date Picture taken'
- Index(es):
Relevant Pages
|
