- SBS
- Microsoft SharePoint
- Microsoft SQL Server 2005
Windows Sharepoint Services 3.0 SP2 problem
I recently applied SP2 to WSS 3.0 and came across the problem that from what I can find has been pretty widespread.
I'm currently getting "Cannot connect to configuration database"
I have:
* Restarted Microsoft##SSEE service, W3C service and Sharepoint Service
* Rebooted the server (required to apply updates)
* Run "psconfig -cmd upgrade -inplace b2b -wait -force"
* Been through http://support.microsoft.com/kb/944154 which failed, see below:
<snip>
Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies...
Failed to upgrade SharePoint Products and Technologies.
An exception of type Microsoft.SharePoint.Upgra
Additional exception information: Upgrade completed with errors. Review the u
pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\12\Logs\Upgrade
d at the end of the upgrade log file.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiag
65996320.log and the application event log.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
dm -o upgrade -inplace -url http://intranet
Database state cannot be changed while other users are using the database 'Share
Point_Config_3f2203a2-d36f
ALTER DATABASE statement failed.
sp_dboption command failed.
* Checked DB permissions in Microsoft SQL Server Management Studio Express, Sharepoint_Config database seems to be inaccessible, see below.
==========================
The database SharePoint_Config_3f2203a2
--------------------------
Program Location:
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
Event log shows the following, I know this can be a permission problem but since it doesn't mention the login details maybe something else?
SQL Database 'SharePoint_Config_3f2203a
Cannot open database "SharePoint_Config_3f2203a
I also get the following but have had these for a while and they've never caused issues although getting a lot more of them at the moment especially when trying any operations on the databases.
The description for Event ID ( 17137 ) 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: Lansweeper32.
I'm no database/Sharepoint guru so if anyone out there with more knowledge of this problem can point me in the right direction would be greatly appreciated.
I'm currently getting "Cannot connect to configuration database"
I have:
* Restarted Microsoft##SSEE service, W3C service and Sharepoint Service
* Rebooted the server (required to apply updates)
* Run "psconfig -cmd upgrade -inplace b2b -wait -force"
* Been through http://support.microsoft.com/kb/944154 which failed, see below:
<snip>
Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies...
Failed to upgrade SharePoint Products and Technologies.
An exception of type Microsoft.SharePoint.Upgra
Additional exception information: Upgrade completed with errors. Review the u
pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\12\Logs\Upgrade
d at the end of the upgrade log file.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiag
65996320.log and the application event log.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
dm -o upgrade -inplace -url http://intranet
Database state cannot be changed while other users are using the database 'Share
Point_Config_3f2203a2-d36f
ALTER DATABASE statement failed.
sp_dboption command failed.
* Checked DB permissions in Microsoft SQL Server Management Studio Express, Sharepoint_Config database seems to be inaccessible, see below.
==========================
The database SharePoint_Config_3f2203a2
--------------------------
Program Location:
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
at Microsoft.SqlServer.Manage
Event log shows the following, I know this can be a permission problem but since it doesn't mention the login details maybe something else?
SQL Database 'SharePoint_Config_3f2203a
Cannot open database "SharePoint_Config_3f2203a
I also get the following but have had these for a while and they've never caused issues although getting a lot more of them at the moment especially when trying any operations on the databases.
The description for Event ID ( 17137 ) 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: Lansweeper32.
I'm no database/Sharepoint guru so if anyone out there with more knowledge of this problem can point me in the right direction would be greatly appreciated.
Exert from PSCDiagnostics_6_15_2010_1
65996320.log:
An exception of type Microsoft.SharePoint.PostS
Failed to detect if this server is joined to a server farm. Possible reasons for this failure could be that you no longer have the appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessible or this server has been removed from the server farm. To diagnose this problem further, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiag
Microsoft.SharePoint.PostS
Again this seems to point to the config database.
I have also tried to run the Sharepoint Products and technologies Wizard but was forced to cancel it since it tried to restart iis and ended up freezing the inetinfo process which subsequently meant I had to kill and restart the process. As a cascade effect this kills the SMTP process.
If it's worth running it through (apparently it can fix a lot of issues) please suggest.
Lastly I have also tried to run the SQL BPA but was unable to connect to the MIcrosoft##SSEE database using the credentials.
65996320.log:
An exception of type Microsoft.SharePoint.PostS
Failed to detect if this server is joined to a server farm. Possible reasons for this failure could be that you no longer have the appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessible or this server has been removed from the server farm. To diagnose this problem further, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiag
Microsoft.SharePoint.PostS
Again this seems to point to the config database.
I have also tried to run the Sharepoint Products and technologies Wizard but was forced to cancel it since it tried to restart iis and ended up freezing the inetinfo process which subsequently meant I had to kill and restart the process. As a cascade effect this kills the SMTP process.
If it's worth running it through (apparently it can fix a lot of issues) please suggest.
Lastly I have also tried to run the SQL BPA but was unable to connect to the MIcrosoft##SSEE database using the credentials.
Any failure of a monthly patch, Service Pack, etc is a free call to MS support
This issue has been a real pain. I'd encourage you to work with MS Support to resolve it.
One of my customers spent 4 hours on the phone yesterday with MS Support
This issue has been a real pain. I'd encourage you to work with MS Support to resolve it.
One of my customers spent 4 hours on the phone yesterday with MS Support
What's the best number to call Microsoft on for this kind of issue? Im afraid if I look for myself im going to end up being stuck in a transfer hell.
Sorry I was after the Australian phone number.
I have tried checking the Microsoft site but it said my product ID was most likely an OEM so to contact them, they are just a whitebox provider and would be useless.
I did find some number which seems to be a support number but was on hold for 10 minutes and had to hang up as it cut into a meeting.
Will try again now and see how it goes.
I have tried checking the Microsoft site but it said my product ID was most likely an OEM so to contact them, they are just a whitebox provider and would be useless.
I did find some number which seems to be a support number but was on hold for 10 minutes and had to hang up as it cut into a meeting.
Will try again now and see how it goes.
I was unable to find a support number in Austrailia but I'll check with the Austrailian MVPs I'm sure they have it.
I managed to get through to Microsoft support but although I could hear them find they couldn't hear me so I had to hang up.
I have also tried Microsoft support online support (https://support.microsoft.com/oas/default.aspx?&gprid=3208&&st=1&wfxredirect=1) but because it's OEM Microsoft say to call your manufacturer, I have checked their site and they to say to call your reseller.
I have spoken to them and they suggested:
Removing the Service Pack (This SP cannot be removed)
Rolling back the database (Don't have current backup)
Calling Microsoft again (Which I will try now)
Sending all my notes to them to look at
Back on the technical front I'm currently getting my application log filled with:
SQL Database 'SharePoint_Config_3f2203a
Cannot open database "SharePoint_Config_3f2203a
I have also tried Microsoft support online support (https://support.microsoft.com/oas/default.aspx?&gprid=3208&&st=1&wfxredirect=1) but because it's OEM Microsoft say to call your manufacturer, I have checked their site and they to say to call your reseller.
I have spoken to them and they suggested:
Removing the Service Pack (This SP cannot be removed)
Rolling back the database (Don't have current backup)
Calling Microsoft again (Which I will try now)
Sending all my notes to them to look at
Back on the technical front I'm currently getting my application log filled with:
SQL Database 'SharePoint_Config_3f2203a
Cannot open database "SharePoint_Config_3f2203a
I have managed to get a hold of Microsoft and said that the decision of charging is up to the technician if the problem matches the KB article.
Since the current ID's im getting do not match it I decided to hold off and see if I can fix the problem with the Sharepoint config database first.
If I still have the problem after moving to 2008 R2 I'll re-consider contacting them.
Since the current ID's im getting do not match it I decided to hold off and see if I can fix the problem with the Sharepoint config database first.
If I still have the problem after moving to 2008 R2 I'll re-consider contacting them.
I have backed up the content database (although it seems multiple exist using stsadm and a backupfull method seemed to get one in particular.
I have re-installed WSS 3.0 and reboot when I get a chance and see how it goes.
I have re-installed WSS 3.0 and reboot when I get a chance and see how it goes.
-
![]()
received a Solution
Upgrading SharePoint Services 2 to SharePoint Services 3 -
![]()
wrote an Article
![]()
How to Migrate SharePoint to SharePoint Online 2013, 2010, 2007
-
![]()
created a Video
![]()
Repair Corrupt SQL Database with Stellar Phoenix SQL Database Repair Software
-
Explore Cloud Class® ![]()
SharePoint Foundation 2010: Advanced
Premium Content
You need an Expert Office subscription to comment.Start Free Trial