asked on

Sharepoint Produce and Technologies Configuration Wizard Error Failed to connect to configuration database are reinstall

I had a problem with Sharepoint Services 3 on SBS2003 and decided to reinstall. The re-install failed. A technet article suggested removing SS2 first then SS3 then reinstalling.
This worked but now when I run the "Sharepoint Products and Technologies Configuration Wizard" I get an error.

"Failed to connect to configuration database. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Access to module dbo.proc_getObjectsByClass is blocked because the signature is not valid"

The event log lists:

Event ID :1000 #50070: Unable to connect to the database STS_Config_22525 on ABSERVER\SharePoint. Check the database connection information and make sure that the database server is running.

Event ID: 33002 The description for Event ID ( 33002 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: module, dbo.proc_getObjectsByClass.

EventID: 104 Failed to connect to the configuration database.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Access to module dbo.proc_getObjectsByClass is blocked because the signature is not valid.
System.Data.SqlClient.SqlException: Access to module dbo.proc_getObjectsByClass is blocked because the signature is not valid.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.FetchId(QualifiedObjectName qName)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(String name, Guid parentId, Type type)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder connectionString, Boolean enableCaching)
at Microsoft.SharePoint.Administration.SPFarm.Open(SqlConnectionStringBuilder connectionString, String username, SecureString password)
at Microsoft.SharePoint.Administration.SPFarm.Open(String connectionString)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

It seems to be a problem with SQL Express, but the MICROSOFT##SSEE Database Instance is running.

Other than Sharepoint what is MICROSOFT##SSEE used for in SBS 2003?
Can I reinstall SSEE?
When I installed Sharepoint Services 2 I used a downloaded file not the SBS 2003 disks. Should I remove Sharepoint 3 & 2 and start again. If so what is the best method of re-installing Sharepoint in SBS without doing a complete rebuild?

SOLUTION

Justin Smith

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

EICT

ASKER

Thanks ACH1LLES for your reply.

I created a Sharepoint account in Active Directory which I called ProjectServiceAcc which is a member of the Admins Group on the Server. I then logged in with this account to install Sharepoint. When I installed WSS it never asked me for any user accout details. How do I check if it has access to the Instance without having the MSSQL Management Studio Installed?

Thanks.

ASKER CERTIFIED SOLUTION

Justin Smith

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

EICT

ASKER

Thanks.
Ok. This is my plan
To uninstall WSS2, then WSS3. Then remove SQL Desktop Engine (SHAREPOINT) . I'll have to leave SQL because its used by other SBS stuff such as SBSMonitoring.
Remove IIS Sharepoint Application Pools and Websites - I noticed last time I uninstalled WSS it left these. Restart and install WSS2 and 3 again.

I wonder if there is a clean up tool?

Justin Smith

You could delete the web applications through Central Admin, before uninstalling, which should remove them from IIS.

Unless you can't access Central Admin.

EICT

ASKER

After a lot of trial an error I managed to fix this by
1. Install Microsoft SQL Server Management Studio Express, free download
here:
2 - Connect to the following server :
\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
3 - When I looked at the Permission of the WSS3 databases : Sharepoint_AdminContent, Sharepoint_Config, WSS_Content, WSS_Config I noticed that there weren't any and it through an error which I tried to view properties.
After a bit of playing I managed to delete the above databases
4- Repaired WSS 2
5 - Run WSS3 Sharepoint Products and Technologies Wizard

All ok now

EICT

ASKER

Thanks ACH1LLES you pointed me in the right direction but I needed to do a bit more research to completely resolve the issue