Issue upgrading Sharepoint 2003 sp2 to MOSS 2007 trial version
in [Windows Services]
|
Prev: logs filling up with "Preserving template record ....." messages
Next: WSS - Error using stsadm "-o deletesite", (corrupted site?)
From: ocon4ms on 7 Feb 2007 13:51 I downloaded the trial version of MOSS 2007 until my CD and license comes in. I have a test environment with 1 server which is the front end webserver, the 2nd server is the job server and indexer and the 3rd server is running SQL 200 sp4. In my actual environment its a 3 server farm as opposed to the 2 server farm I have in my test environment. I ran all windows updates on all 3 boxes including grabbing the DST update for Sharepoint 2003. I ran the prescan.exe and cleared all errors. I installed .NET 3.0 on both the front end and job/indexer. I also enabled .NET 2.0 in IIS.I upgraded the frontend first without running the config wizard. I then upgraded the job/index server second and stopped at running the config wizard. Ran the config wizard on frontend and it bombed on step 2 with the following error: "Failed to initiate the upgrade process" Logfile has the following error: 02/07/2007 13:44:45 8 ERR Task upgradebootstrap has failed with an unknown exception 02/07/2007 13:44:45 8 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 12.0.1.0 of Microsoft.Office.Server.Search.Upgrade.SearchServiceInstanceSequence failed. ---> System.ArgumentNullException: Value cannot be null. Parameter name: path at System.IO.DirectoryInfo..ctor(String path) at Microsoft.Search.Administration.Security.BinFolder.EnsureACL(String username) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision() at Microsoft.Office.Server.Search.Upgrade.ProvisionSearchServiceInstance.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() I called MS and the tech had me run the config wizard on the job/ indexer and it ran successfully (even though there documentation says to run it on the front end first). Next, he had me run it on the front- end again and it bombed with the same error. I sent him all of my logs and have yet to hear from him. I have been unable to find a solution to this error message either by my own accord or through MS. Hopefully, someone out here has had this issue before and can tell me how to resolve it. Thanks for any help.
From: Mike Walsh on 8 Feb 2007 00:51
This is the WSS newsgroup (typically the WSS 2.0 product unless stated) and is not for MOSS 2007 (or SPS 2003) questions. Please post MOSS 2007 installation and admin questions like this one to the new newsgroup for this kind of question. microsoft.public.sharepoint.setup_and_administration where as it is for all SharePoint products there is no problem with whether a question is a MOSS 2007 or a WSS 3.0 question. The only other newsgroup that covers MOSS questions (still) is the old microsoft.public.sharepoint.portalserver newsgroup. Mike Walsh WSS FAQ: www.wssv3faq.com / wss.collutions.com No private questions please (additions to FAQ welcome) <ocon4ms(a)gmail.com> wrote in message news:1170874283.418962.139030(a)q2g2000cwa.googlegroups.com... >I downloaded the trial version of MOSS 2007 until my CD and license > comes in. > > I have a test environment with 1 server which is the front end > webserver, the 2nd server is the job server and indexer and the 3rd > server is running SQL 200 sp4. In my actual environment its a 3 server > farm as opposed to the 2 server farm I have in my test environment. > > I ran all windows updates on all 3 boxes including grabbing the DST > update for Sharepoint 2003. I ran the prescan.exe and cleared all > errors. I installed .NET 3.0 on both the front end and job/indexer. I > also enabled .NET 2.0 in IIS.I upgraded the frontend first without > running the config wizard. I then upgraded the job/index server second > and stopped at running the config wizard. Ran the config wizard on > frontend and it bombed on step 2 with the following error: > "Failed to initiate the upgrade process" > > Logfile has the following error: > 02/07/2007 13:44:45 8 ERR Task > upgradebootstrap has failed with an unknown exception > 02/07/2007 13:44:45 8 ERR Exception: > Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 12.0.1.0 of > Microsoft.Office.Server.Search.Upgrade.SearchServiceInstanceSequence > failed. ---> System.ArgumentNullException: Value cannot be null. > Parameter name: path > at System.IO.DirectoryInfo..ctor(String path) > at > Microsoft.Search.Administration.Security.BinFolder.EnsureACL(String > username) > at > Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision() > at > Microsoft.Office.Server.Search.Upgrade.ProvisionSearchServiceInstance.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() > > I called MS and the tech had me run the config wizard on the job/ > indexer and it ran successfully (even though there documentation says > to run it on the front end first). Next, he had me run it on the front- > end again and it bombed with the same error. I sent him all of my logs > and have yet to hear from him. > > I have been unable to find a solution to this error message either by > my own accord or through MS. Hopefully, someone out here has had this > issue before and can tell me how to resolve it. > > Thanks for any help. > |