Cannot upgrade WSS 2.0 to 3.0

This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C7114E.BB22A680
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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.PostSetupConfigurationTaskExc=
eption 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.PostSetupConfigurationTaskExc=
eption 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.

------=_NextPart_000_000A_01C7114E.BB22A680
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.2795" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Step 1 of the wizard completes with the =
following=20
errors, have a SQL2005 developer edition running as backend to WSS 2.0 =
on same=20
server. Anyone have ideas?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Alex</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><BR><FONT face=3D"Courier New" size=3D2>---------- =
WSS3.LOG<BR>11/26/2006=20
11:20:01  6 =20
ERR           &nbs=
p;           &nbsp=
;     =20
The process C:\Program Files\Common Files\Microsoft Shared\Web Server=20
Extensions\12\bin\prescan.exe exited with return code 1<BR>11/26/2006=20
11:20:01  6 =20
ERR           &nbs=
p;           &nbsp=
;   =20
Detected that the prescan.exe has not been run yet.<BR>11/26/2006 =
11:20:01 =20
6 =20
ERR           &nbs=
p;           &nbsp=
;   =20
Task initialize has failed with a PostSetupConfigurationTaskException An =

exception of type=20
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskExc=
eption=20
was thrown.  Additional exception information: The pre-upgrade scan =
tool=20
has not yet been run successfully on all content databases in the server =
farm.=20
The pre-upgrade scan tool must complete without errors before you can =
continue=20
with the upgrade process.<BR>11/26/2006 11:20:01  6 =20
ERR           &nbs=
p;           &nbsp=
;   =20
An exception of type=20
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskExc=
eption=20
was thrown.  Additional exception information: The pre-upgrade scan =
tool=20
has not yet been run successfully on all content databases in the server =
farm.=20
The pre-upgrade scan tool must complete without errors before you can =
continue=20
with the upgrade process.<BR>11/26/2006 11:20:01  6 =20
ERR           &nbs=
p;           &nbsp=
;     =20
Task initialize has failed<BR>11/26/2006 11:20:01  1 =20
ERR           &nbs=
p;           &nbsp=
;           =20
Task initialize has stopped and failed.  Total failed is now=20
1<BR>11/26/2006 11:20:02  5 =20
ERR           &nbs=
p;           &nbsp=
; =20
Task initialization failed, so stopping execution of the =
engine<BR>11/26/2006=20
11:20:02  5 =20
ERR           &nbs=
p;           &nbsp=
; =20
Failed to initialize SharePoint Products and Technologies =
upgrade.<BR>11/26/2006=20
11:20:02  5 =20
ERR           &nbs=
p;           &nbsp=
; =20
One or more configuration tasks has failed or some tasks were not=20
run<BR>11/26/2006 11:20:04  5 =20
ERR           &nbs=
p;           =20
One or more configuration tasks has failed to execute<BR>11/26/2006=20
11:20:04  5 =20
ERR           &nbs=
p;           &nbsp=
; =20
Configuration of SharePoint Products and Technologies failed. =20
Configuration must be performed in order for this product to operate=20
properly.  To diagnose the problem, review the extended error =
information=20
located at C:\Program Files\Common Files\Microsoft Shared\Web Server=20
Extensions\12\LOGS\PSCDiagnostics_11_26_2006_11_19_48_25_462277996.log, =
fix the=20
problem, and run this configuration wizard =
again.<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_000A_01C7114E.BB22A680--

Mike
Sun Nov 26 11:02:34 CST 2006

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@nospam.com> wrote in message
news:Ox0YkiXEHHA.348@TK2MSFTNGP06.phx.gbl...
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.

jasonyip
Mon Nov 27 04:59:31 CST 2006

I have the same problem but it is not the first step.

I am running Windows Server 2003 with the latest service pack. WSS 2.0
with SQL Server 2005 Enterprise Edition SP1.

The configuration wizard failed with the above error on prescan.exe.

I have 2 customized sites with the shared document template modified.

After the first setup and rebooting I got the following error message
from the files that automatically put into startup:

Trying to create list/library named: "Tasks"
List/Library Tasks opened
Content successfully migrated to Tasks
Critical error! Invalid template URL

The template must exist in the Forms directory of this document
library. Create the template in the Forms directory, and then re-type
the Web address. Note that you cannot move or copy a template into the
Forms directory.. Halting import, check log file for details.
Exception type System.Runtime.InteropServices.COMException
at Microsoft.SharePoint.Library.a.i(String A_0, String A_1)
at Microsoft.SharePoint.SPList.Update()
at SharePoint2003Import.Importer.Process(String sourceFolder, String

portalRootParam, Boolean allowImportIntoExistingSite, Boolean
allowImportIntoExistingLibrary, Boolean importSecurity, Boolean
createListTemplates, Boolean importDesign, Boolean
updateExistingListItems)

And then I ran the configuration wizard and it gave me the above
prescan error.

So I ran prescan /all. And now I am stuck on this error:

11/23/2006 06:45:09 9 ERR Task upgradebootstrap has
failed with an unknown exception
11/23/2006 06:45:09 9 ERR Exception:
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 3.0.2.0 of
Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed.
---> System.ArgumentException: The id
f6aa1c2b-4947-4265-b41d-05d0cd71b644 is in use. An
Microsoft.SharePoint.Administration.SPServer named "USPROFILINGDEV" is
using the same id as the new object named "USPROFILINGDEV" of type
Microsoft.SharePoint.Administration.SPServer. Every object must
contain a unique id. Either update the new object's id or delete the
existing object and try again.
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject
obj, Boolean storeClassIfNecessary, Boolean ensure)
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject
obj, Boolean ensure)
at Microsoft.SharePoint.Administration.SPPersistedObject.Update()
at Microsoft.SharePoint.Administration.SPServer.Update()
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.RegisterDefaultDatabaseServices(SqlConnectionStringBuilder
connectionString)
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.Provision(SqlConnectionStringBuilder
connectionString)
at
Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder
configurationDatabase, SqlConnectionStringBuilder
administrationContentDatabase, IdentityType identityType, String
farmUser, SecureString farmPassword)
at
Microsoft.SharePoint.Upgrade.InitialFarmCreation.CreateFarm(SqlConnectionStringBuilder
connectionString)
at Microsoft.SharePoint.Upgrade.InitialFarmCreation.Upgrade()
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
bRecurse)
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean
recursively)
at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
at
Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at
Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Mike Walsh wrote:
> 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@nospam.com> wrote in message
> news:Ox0YkiXEHHA.348@TK2MSFTNGP06.phx.gbl...
> 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.

Mike
Mon Nov 27 05:55:02 CST 2006

You'd be better off posting (with a slightly different title to avoid a
Newsreader posting it to this thread anyway!) as a new message because it
seems that all you really have in common with the first poster in this
thread is the fact that WSS 2.0 to WSS 3.0 isn't working !

There are so many different reasons why that might be (not) happening.

Mike Walsh

<jasonyip@gmail.com> wrote in message
news:1164625171.913840.186090@14g2000cws.googlegroups.com...
>I have the same problem but it is not the first step.
>
> I am running Windows Server 2003 with the latest service pack. WSS 2.0
> with SQL Server 2005 Enterprise Edition SP1.
>
> The configuration wizard failed with the above error on prescan.exe.
>
> I have 2 customized sites with the shared document template modified.
>
> After the first setup and rebooting I got the following error message
> from the files that automatically put into startup:
>
> Trying to create list/library named: "Tasks"
> List/Library Tasks opened
> Content successfully migrated to Tasks
> Critical error! Invalid template URL
>
> The template must exist in the Forms directory of this document
> library. Create the template in the Forms directory, and then re-type
> the Web address. Note that you cannot move or copy a template into the
> Forms directory.. Halting import, check log file for details.
> Exception type System.Runtime.InteropServices.COMException
> at Microsoft.SharePoint.Library.a.i(String A_0, String A_1)
> at Microsoft.SharePoint.SPList.Update()
> at SharePoint2003Import.Importer.Process(String sourceFolder, String
>
> portalRootParam, Boolean allowImportIntoExistingSite, Boolean
> allowImportIntoExistingLibrary, Boolean importSecurity, Boolean
> createListTemplates, Boolean importDesign, Boolean
> updateExistingListItems)
>
> And then I ran the configuration wizard and it gave me the above
> prescan error.
>
> So I ran prescan /all. And now I am stuck on this error:
>
> 11/23/2006 06:45:09 9 ERR Task upgradebootstrap has
> failed with an unknown exception
> 11/23/2006 06:45:09 9 ERR Exception:
> Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 3.0.2.0 of
> Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed.
> ---> System.ArgumentException: The id
> f6aa1c2b-4947-4265-b41d-05d0cd71b644 is in use. An
> Microsoft.SharePoint.Administration.SPServer named "USPROFILINGDEV" is
> using the same id as the new object named "USPROFILINGDEV" of type
> Microsoft.SharePoint.Administration.SPServer. Every object must
> contain a unique id. Either update the new object's id or delete the
> existing object and try again.
> at
> Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject
> obj, Boolean storeClassIfNecessary, Boolean ensure)
> at
> Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject
> obj, Boolean ensure)
> at Microsoft.SharePoint.Administration.SPPersistedObject.Update()
> at Microsoft.SharePoint.Administration.SPServer.Update()
> at
> Microsoft.SharePoint.Administration.SPConfigurationDatabase.RegisterDefaultDatabaseServices(SqlConnectionStringBuilder
> connectionString)
> at
> Microsoft.SharePoint.Administration.SPConfigurationDatabase.Provision(SqlConnectionStringBuilder
> connectionString)
> at
> Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder
> configurationDatabase, SqlConnectionStringBuilder
> administrationContentDatabase, IdentityType identityType, String
> farmUser, SecureString farmPassword)
> at
> Microsoft.SharePoint.Upgrade.InitialFarmCreation.CreateFarm(SqlConnectionStringBuilder
> connectionString)
> at Microsoft.SharePoint.Upgrade.InitialFarmCreation.Upgrade()
> at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
> --- End of inner exception stack trace ---
> at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
> at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
> bRecurse)
> at
> Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean
> recursively)
> at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
> at
> Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
> at
> Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
>
>
>
> Mike Walsh wrote:
>> 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@nospam.com> wrote in message
>> news:Ox0YkiXEHHA.348@TK2MSFTNGP06.phx.gbl...
>> 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.
>

MondaleA
Mon Nov 27 15:21:44 CST 2006

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@hotmail.com> wrote in message
news:eViqsyXEHHA.3768@TK2MSFTNGP06.phx.gbl...
> 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@nospam.com> wrote in message
> news:Ox0YkiXEHHA.348@TK2MSFTNGP06.phx.gbl...
> 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.
>

MondaleA
Mon Nov 27 17:38:34 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_0020_01C71253.3E813870
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Same results (fails on prescan, step 1) on a reasonably "virgin" WSS 2.0 =
with MSDE 2000. Is it possible I somehow got hold of a "pre-release" =
version of the binaries? Where do I go for help if I can't find anything =
on this board?
"news.microsoft.com" <almo@nospam.com> wrote in message =
news:Ox0YkiXEHHA.348@TK2MSFTNGP06.phx.gbl...
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.PostSetupConfigurationTaskExc=
eption 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.PostSetupConfigurationTaskExc=
eption 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. Configur

Cannot upgrade WSS 2.0 to 3.0

Re: Cannot upgrade WSS 2.0 to 3.0 by Mike

Re: Cannot upgrade WSS 2.0 to 3.0 by jasonyip

Re: Cannot upgrade WSS 2.0 to 3.0 by Mike

Re: Cannot upgrade WSS 2.0 to 3.0 by MondaleA

Re: Cannot upgrade WSS 2.0 to 3.0 by MondaleA