*** Problem Description ***
BEHAVIOR/SYMPTOMS:
====================
PSConfigUI failing after installing WSS 3.0 SP2
Environment:
===============
Wss 3.0 on a stand alone system
Customer is using the windows internal database
Issue :
After the installation of the sp2 which is included as a critical update in the windows update we face connection issues with Sql
Error message :
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
When we run the psconfig
Symptoms:
======
It will start creating n number of sharepoint_config databases without any tables
We will not be able to access the dbo.versions when we try checking the version of the database
We might be able to check for the version of the config database
Resolution :
Download management studio express
Set SQL express to allow tcp/ip and named pipes
Open the connection with the following address
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Backup all the databases from the sql server management studio .
Check with the customization as it will be lost
Tak e a screen shot of
Solution management
AAM
Topology
Databases in the Sql server management studio
Uninstall windows internal database from the add remove programs
Uninstall SharePoint and reboot the server
Install back SharePoint with windows internal database (standalone installation )
Restore all the databases
Attach the database back to the farm
The server should be up and running
BEHAVIOR/SYMPTOMS:
====================
PSConfigUI failing after installing WSS 3.0 SP2
Environment:
===============
Wss 3.0 on a stand alone system
Customer is using the windows internal database
Issue :
After the installation of the sp2 which is included as a critical update in the windows update we face connection issues with Sql
Error message :
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
Access to table dbo.spt_values is blocked because the signature is not valid.
When we run the psconfig
Symptoms:
======
It will start creating n number of sharepoint_config databases without any tables
We will not be able to access the dbo.versions when we try checking the version of the database
We might be able to check for the version of the config database
Resolution :
Download management studio express
Set SQL express to allow tcp/ip and named pipes
Open the connection with the following address
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Backup all the databases from the sql server management studio .
Check with the customization as it will be lost
Tak e a screen shot of
Solution management
AAM
Topology
Databases in the Sql server management studio
Uninstall windows internal database from the add remove programs
Uninstall SharePoint and reboot the server
Install back SharePoint with windows internal database (standalone installation )
Restore all the databases
Attach the database back to the farm
The server should be up and running
No comments:
Post a Comment