Answered by:
Failed to create Configuration Database for MOSS 2007 on Windows Server 2008 R2 + SQL Server 2008 SP1

Question
-
I Create a new slipstream build for SharePoint Server 2007 to install it on Windows Server 2008 R2. it installed successfully. then I create the Configuration Database through 'SharePoint Products and Technologies Configuration Wizard'. it prompt 'Failed to create the Configuration Database'.
My Evironment is:
Windows Server 2008 R2
SQL Server 2008 SP1
MOSS 2007Thanks, but I don't know which part of log you want to see. I just copy a part fo log to here.
Log:07/30/2010 18:39:14 6 INF Entering function StringResourceManager.GetResourceString
07/30/2010 18:39:14 6 INF Resource id to be retrieved is ConfigurationDatabaseTaskCreateFailConfigDisplayLabel for language English (United States)
07/30/2010 18:39:14 6 INF Resource retrieved id ConfigurationDatabaseTaskCreateFailConfigDisplayLabel is Failed to create the configuration database.
07/30/2010 18:39:14 6 INF Leaving function StringResourceManager.GetResourceString
07/30/2010 18:39:14 6 ERR Failed to create the configuration database.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.
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()
07/30/2010 18:39:14 6 INF Entering function TaskDriver.NotifyTaskSummary
07/30/2010 18:39:14 6 INF Entering function StringResourceManager.GetResourceString
07/30/2010 18:39:14 6 INF Resource id to be retrieved is TotalTasksRan for language English (United States)
07/30/2010 18:39:14 6 INF Resource retrieved id TotalTasksRan is Total number of configuration settings run: {0}
07/30/2010 18:39:14 6 INF Leaving function StringResourceManager.GetResourceString
07/30/2010 18:39:14 6 INF Entering function TaskDriver.OnTaskDriverNotify
07/30/2010 18:39:14 6 INF Sending a task driver notify event: TaskDriverEventArgs.EventCriticalityType: info, TaskDriverEventArgs.EventMessageType: totalran, TaskDriverEventArgs.EventType.notify, message: Total number of configuration settings run: 2- Edited by f4f16 Wednesday, August 4, 2010 9:40 AM
Wednesday, August 4, 2010 4:02 AM
Answers
-
Hi,
after checking the logs I did not find anything else. You already published the exception in the first posts of this thread.
I looked a while also in the net. The most common issues related to this exception are an installation of SharePoint 2010 or Office 2010 on the same machine.
However, I would check a list time the slipstreamed version of your installation disc. Ensure that you use the same version (32bit or 64bit) of the SP2 you are slipstreaming into your installation.
Slowly, my ideas are vanishing
Patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NET- Proposed as answer by Patrick Lamber (Old Profile) Wednesday, August 11, 2010 7:41 AM
- Marked as answer by f4f16 Wednesday, August 11, 2010 12:27 PM
Tuesday, August 10, 2010 10:25 AM
All replies
-
Hi,
try to open in HIVE 12 the logs and check for details. There you should see more information. Could you post the logs to get more information?
Best regards,
patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NETWednesday, August 4, 2010 5:47 AM -
is it a farm install or integrated without a domain account? in the latter case, there is additional config.
You're always better off using domain accounts. Mandatory in a farm, ofc.
Wednesday, August 4, 2010 9:11 AM -
Hi,
is the user you are specifying in the configuration an administrator for SQL Server 2008? If not, please add this user as an admin.
Some months ago I wrote a web post serie about this topic: Installing Moss 2007 on Windows Server 2008 + SQL Server 2008: http://patricklamber.blogspot.com/2010/01/sharepoint-server-2007-on-windows.html.
You can use it to see if you configured the SQL Server in a similar way.
Hope this helps,
patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NETWednesday, August 4, 2010 10:23 AM -
good point patrick :)
always beware of UAC in 2008!
Wednesday, August 4, 2010 11:03 AM -
Hi,
did you solve your problem? Could you tell us?
Best regards,
Patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NETSunday, August 8, 2010 5:16 AM -
Thanks Patrick. But I canot open your giving link. I don't yet resolve this issue. I try below solution. but none can resolve my issue.
S1: Make a new slipstream build based on MOSS 2007 SP2 Service Pack, WSS 3.0 SP2 Service Pack.
http://thecommunicator.co.cc/2009/12/18/windows-2008-r2-server-sharepoint-2007-kb962935-2/S2: Run this command to create configuration Database.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\PSCONFIG.EXE" -cmd configdb -create -database <uniquename>S3: Install 'SQL_Server_2008_SP1_Cumulative_Update_2' for SQL server 2008 SP1.
All are invalidate.
I try to install MOSS 2010. It can create the configuration DB, but only after installing 'SQL_Server_2008_SP1_Cumulative_Update_2' for SQL server 2008 SP1.
But my projects are based on MOSS 2007. I have to install MOSS 2007.Any suggestions?
Monday, August 9, 2010 8:22 AM -
Hi,
strange that you are not able to open the link. I tried before: http://patricklamber.blogspot.com/2010/01/sharepoint-server-2007-on-windows.html
Anyway, i try to sum up what you need to do:
Please do following:
check that the database access account has administrative priviledges in your SQL Server 2008 installation. It is not enough that you put him as administrator in the operating system. You have to specify it in SQL Server 2008 explicitly. Also check that the collation settings of your SQL Server are set to accent-sensitive, kana-sensitive, width-sensitive. Here a link how to do a step by step installation of SQL Server: http://patricklamber.blogspot.com/2010/01/sharepoint-server-2007-on-windows_14.html
Ensure that the SQL Ports are reachable between your front-end and back-end machine.
Prepare your front-end server for the SharePoint installation. Here a link that explains step by step what to do: http://patricklamber.blogspot.com/2010/01/sharepoint-server-2007-on-windows_08.html
Install the binaries of SharePoint 2007 on your machine and execute the configuration wizard. Specify the dataaccess account that you specified before in SQL Server.
I hope that this solves your issues
Patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NETMonday, August 9, 2010 8:51 AM -
It is not solved. I still get the same issue. I restalled SQL and selecting Latin1_General with checking accent-sensitive, kana-sensitive, width-sensitive. My using account have been given 'sysadmin' and 'public' priviledge.
Your post mentioned '1 x SharePoint Server 2007 Standard or Enterprise - x64'. It cannot be installed on Windows Server 2008 R2. It need to make a slipstream build. Please refer this post http://thecommunicator.co.cc/2009/12/18/windows-2008-r2-server-sharepoint-2007-kb962935-2/.
So I follow above link to make a new slipstream build. I use this build to get that issue. This issue prompt as following:
http://alkyna.bay.livefilestore.com/y1pCyGePzVcpEbnc71agta7l2AYdDWw8opetpSqVj3xzuVB85SLzT80DBIvxyYyjNtpg2fIh_sYlT9Fzz35TDwfjIAebuTnhkYi/Untitled.jpg?psid=1But I am seeing this SharePoint_Config database has been created in SQL Server.
Tuesday, August 10, 2010 2:14 AM -
Hi,
this with the slipstream is ok. Perfect with SQL Server. Now, we have to stick on the logs. In your screenshot you are seeing the PSCDiagnosticLogs. They tell you more. You could post some of them here. This could be easier for us.
With the logs above, I found some interesting posts:
- https://connect.microsoft.com/SQLServer/feedback/details/486316/one-or-more-type-failed-to-load?wa=wsignin1.0
- http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/183b5ab9-dc4b-4c27-aecd-55df60167a68
- http://blogs.msdn.com/b/tmathis/archive/2009/11/03/spupgradeexception-one-or-more-types-failed-to-load-exception-when-running-configuration-wizard.aspx
By looking carefully in the PSCDiagnosticLogs, you may be able to get more information.
If you have any Office or SharePoint software on your machine except 2007, try to uninstall them if possible.
Hopefully, we find soon your problem
patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NETTuesday, August 10, 2010 5:59 AM -
Hi,
after checking the logs I did not find anything else. You already published the exception in the first posts of this thread.
I looked a while also in the net. The most common issues related to this exception are an installation of SharePoint 2010 or Office 2010 on the same machine.
However, I would check a list time the slipstreamed version of your installation disc. Ensure that you use the same version (32bit or 64bit) of the SP2 you are slipstreaming into your installation.
Slowly, my ideas are vanishing
Patrick
follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NET- Proposed as answer by Patrick Lamber (Old Profile) Wednesday, August 11, 2010 7:41 AM
- Marked as answer by f4f16 Wednesday, August 11, 2010 12:27 PM
Tuesday, August 10, 2010 10:25 AM -
Thanks Patrick. You fix it. Removing Office 2010 installation is the answer. I have successfully created the configuration database. Thanks for your help.Wednesday, August 11, 2010 6:08 AM
-
I am also getting same problem.Thanks Patrick. You fix it. Removing Office 2010 installation is the answer. I have also successfully created the configuration database. Thanks lotfor your help.Sunday, September 11, 2011 5:34 PM