Configuration wizard error "One or more types failed to load" on Win7RC

rated by 0 users
Answered (Verified) This post has 1 verified answer | 17 Replies | 7 Followers

Top 500 Contributor
4 Posts
Points 118
ricalo posted on Tue, Jun 30 2009 2:18 PM

Hi,

I'm running Windows 7 RC and tried to install MOSS 2007 SP2; the binaries installed without issues but configuration wizard fails with the following error in the ULS log:

06/27/2009 14:34:23  7  INF          Creating a new farm with config db SharePoint_Config content db Admin_Content server ricalowin7\sql2005 for farm mode
06/27/2009 14:34:34  7  ERR          Task configdb has failed with an unknown exception
06/27/2009 14:34:34  7  ERR          Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: One or more types failed to load. Please refer to the upgrade log for more details.

   at Microsoft.SharePoint.Upgrade.SPDelegateManager.RegisterAssembly(Assembly asm, UInt32 nOrder)
   at Microsoft.SharePoint.Upgrade.SPDelegateManager.get_InitialTypeDictionary()
   at Microsoft.SharePoint.Upgrade.SPDelegateManager.GetDelegateTypes(Type tpObject)
   at Microsoft.SharePoint.Upgrade.SPDelegateManager.GetDelegates(Object o)
   at Microsoft.SharePoint.Upgrade.SPDelegateManager.GetUpgraders(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgradeFalse(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.set_NeedsUpgrade(Boolean value)
   at Microsoft.SharePoint.Administration.SPPersistedObject.Update()
   at Microsoft.SharePoint.Administration.SPFarm.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.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword)
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
06/27/2009 14:34:34  7  INF          Entering function Common.BuildExceptionMessage
06/27/2009 14:34:34  7  INF            Entering function StringResourceManager.GetResourceString
06/27/2009 14:34:34  7  INF              Resource id to be retrieved is ExceptionInfo for language English (United States)

Looks like it fails to register some assemblies but I don't know how to correct the error or which assemblies are failing.

PSConfigUI (or psconfig) is running with elevated privileges; has anyone found something like this?

Thanks!

Answered (Verified) Verified Answer

Not Ranked
2 Posts
Points 81
Verified by Jonas Nilsson

Its finally running on my Windows 7 RTM x64 machine!!

My first guess that Visual Studio 2010 Beta1 was the culprit was wrong ... Uninstalling it didn't help. It seems the cause of the problem was Office 2010! I had Office 2010, Visio 2010 and Info Path 2010 (Technical Preview) installed. After uninstalling all of them the configuration wizard finally succeeded! Moss SP2 is running!

Good luck! Cool

 

 

All Replies

Top 10 Contributor
509 Posts
Points 14,327

ricalo,

I have seen similar things when custom services have been installed and then uninstalled WITHOUT the installer cleaning up the registration.

/Jonas

Top 500 Contributor
4 Posts
Points 118
ricalo replied on Tue, Jun 30 2009 5:49 PM

OMG, then my installation could be messed... thanks, I'll check and post if I find anything.

Not Ranked
2 Posts
Points 27
johntroo replied on Tue, Aug 11 2009 11:27 PM

Was there any successful resolution to this one?  I am having the same problem, although WSS works just fine.  Any help would be appreciated.

Thanks!

Top 10 Contributor
509 Posts
Points 14,327
Do you have the exact same call stack? If not can you post it here. I don't know about a fix for this and I have never seen it before.
/Jonas
Not Ranked
3 Posts
Points 71

Hi Jonas,
I have the same Error/CallStack on my Windows 7 RTM. The config DB is being created, the Admin DB not.

René

Edit:
Fusion Log did not reveal any errors except ressource files running the configuration wizard.

Top 10 Contributor
509 Posts
Points 14,327

René,

I will try to install on Windows7 RTM and see if I can reproduce this. I will post an update later.

Thanks

/Jonas

Not Ranked
3 Posts
Points 71

Hi Jonas,

I tried to install every patch in the SP2 (WSS and MOSS). But that did not help.
Permissions on the registry did not help either Sad

René

Not Ranked
2 Posts
Points 27
johntroo replied on Sat, Aug 15 2009 12:56 PM

Jonas-

Ditto for me as well.  I have installed all available patches and I still receive the error.  I have also turned off UAC and ran a procmon to see if I could find any registry access errors.  Nothing.

Thanks for your help.

Not Ranked
2 Posts
Points 81

I'm having the same issue with Windows 7 RTM x64. WSS 3.0 runs perfectly. The installation of MOSS is working but the configuration wizard gives the error.

I tried MOSS SP1 + Upgrades and even a MOSS SP2 slipstreamed. Nothing worked. Its a pity that the error log does not show which assemblies cannot be registered ...

Not Ranked
2 Posts
Points 81
Verified by Jonas Nilsson

Its finally running on my Windows 7 RTM x64 machine!!

My first guess that Visual Studio 2010 Beta1 was the culprit was wrong ... Uninstalling it didn't help. It seems the cause of the problem was Office 2010! I had Office 2010, Visio 2010 and Info Path 2010 (Technical Preview) installed. After uninstalling all of them the configuration wizard finally succeeded! Moss SP2 is running!

Good luck! Cool

 

 

Top 10 Contributor
509 Posts
Points 14,327

eric,

Thanks for posting the solution here. 

/Jonas

Not Ranked
3 Posts
Points 71

I got it working, too Big Smile

Except Outlook, I uninstalled all of the Office 2010 Technical Preview.

Then I installed all except Outlook from Office 2007 SP2 again.

After that, the configuration wizard went through all steps.

René

Not Ranked
1 Posts
Points 5
Ravi G replied on Sat, Aug 29 2009 11:51 AM

Hi!
I am facing the same problem on windows 2008 R2 X64. I recently upgraded to SQL 2K8 R2 and had to rerun the SP products and technologies configuration wizard. I am consistently getting the same error. No O2K10 installed. Any pointers.

Ravi Gokulgandhi

Top 500 Contributor
4 Posts
Points 118
ricalo replied on Thu, Sep 10 2009 11:06 PM

Eric,

Thanks a lot, now the wizard runs through all its steps.

Just to add, I uninstalled Office in "batches" cause I have all the suite, here's what I did (maybe we can narrow the problem a little bit)

  1. Uninstalled Visio, Project, SharePoint Designer and OWC 2003.
  2. Tried the wizard... error.
  3. Uninstalled Communicator 2007, LiveMeeting 2007, Access, InfoPath, OneNote, Publisher and SharePoint Workspace.
  4. Tried the wizard... success!

No need to uninstall Word, Excel, PowerPoint, Outlook or any of the shared components or "Tools".

Tomorrow I'll try installing Visio, Project, Designer, OWC, Communicator, LiveMeeting, InfoPath and OneNote back.

Thanks again!

Page 1 of 2 (18 items) 1 2 Next > | RSS
Bamboo Solutions Corporation, 2002-2012