*** <Update 2010-07-15> ***
The announced SharePoint security fix (MS10-039) had some effects after installing it. since yesterday, we updated the KB Article KB983444 to give you more insights when problems after installing it happens.
Note! The KB 979445 is not updated because the cause of the known issues are more WSS related than MOSS.
For more troubleshooting we published also the KB article:
944267 How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007
Related posts:
- Security Bulletin MS10-039
- MS10-039: Description of the security update for Windows SharePoint Services 3.0: June 8, 2010
- MS10-039: Description of the security update for Microsoft Office SharePoint Server 2007: June 8, 2010
- MS10-039: Vulnerabilities in Microsoft SharePoint could allow elevation of privilege(KB 2028554)
*** </Update 2010-07-15> ***
I wrote in my previous post (Security Bulletin MS10-039) that my colleague, Joerg Sinemus already posted some more information about the HotFix.
Now we are starting to see a significant increase in call volumes due to the release of SharePoint Security Updates KB 983444 and KB 979445.
To clarify some confusions and questions, here is an updated information about the known issues and possible resolvers:
Remember, applying a patch, cumulative update or service pack to SharePoint is a two-step process:
1. Install the binaries
2. Run psconfig (or SharePoint Products and Technologies Configuration Wizard) to update the databases
This public update was flagged as Important. (See Microsoft Security Bulletin MS10-039 ). This means on stand-alone installations with automatic updates configured, the update is automatically downloaded and the binaries are installed. However, psconfig still needs to be run.
Please visit as well the SBS Blog about the issue.
*** <Update 2010-07-01> ***
Currently there are widely spread issues on Small Business Servers (SBS) with a similar error observed:
”when running psconfig -cmd upgrade -inplace b2b -wait -force the following errors may shown:
…Access to table dbo.TableName is blocked because the signature is not valid…
observed errors in Event application log:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Date: 10/17/2007
Time: 8:09:40 PM
User: N/A
Computer: HOME
Description:
The database WSS_Content on <SERVER_NAME>Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
(SSEE = SQL Server Embedded Edition, which is what you get when you install WSS 3.0 without using a seperate SQL instance. SSEE is also know as WYUKON, WSSEE, WID or Windows Internal Database).
The problem occurs on all installations that use the Windows internal database engine
Cause:
It seems that the patch installs a new signature file. When psconfig wizard validates the old database against the new signature it fails.
Resolution:
Currently the only way to fix this, is to reinstall or repair the setup of the WSS. The mentioned workarounds in the SBS Blog article or other linked content does not work in this case. So unfortunately we still have no fix for that by now.
Please see more information and how-to’s on TechNet:
Repair WSS on SBS 2008
Repair the Windows SharePoint Services database
SBS Repair documentation!—->
As soon as we will have a proper resolution other than reinstall/repair install, I’ll update this post here!
So stay tuned!
*** </Update 2010-07-01> ***
The following scenarios have been identified until yet on Windows SharePoint Server 3.0:
· Users are prompted for authentication when trying to browse a SharePoint site
· Psconfig fails to provision SPSearchServiceInstance with the following error in the Upgrade.log
Note!!!
Please ensure that you always have a full functional backup before applying any updates, Hotfixes or patches! This is highly recommended in any cases!
The below troubleshooting and resolution descriptions are without any warranty and are currently just workarounds! Make sure that your issue does match exactly the given error messages and symptoms before proceeding the steps described!
All mentioned workarounds are applying to WSSv3!! If you are having same or similar issues on a MOSS environment, it may work as well but to be sure, please open a service request and collect the Event Logs (Application, Security, System), ULS, PSCDiagnostics and Upgrade logs to be attached to the SR as well as in any other case, that is not covered here!
Symptom #1:
Unable to browse Central Administration or SharePoint site. You get the following error message in the browser:
Server Error: http://go.microsoft.com/fwlink?LinkID=96177
Or the following Error in the Application log:
Event Type: Error
Event Source: Windows SharePoint Server
Event Category: Topology
Event lD: 5617
Description:
The schema version (3.x.x.x) of the database SharePoint_AdminContent_123fda45-f456-fad5-de45-7891d2asd455 on ComputerName is not consistent with the expected database schema version (3.x.x.x) on ComputerName. Connections to this database From this server have been blocked to avoid data loss. Upgrade the web Front end or the content database to ensure that these versions match.
Solution:
1. Open a Command Prompt window and at the command prompt change to the following directory:
%COMMONPROGRAMFILES%Microsoft sharedWeb server extensions12Bin
2. Type the following command: psconfig -cmd upgrade -inplace b2b -wait -force
Symptom #2:
Unable to browse Central Administration or SharePoint site. You get the following error message in the browser:
HTTP 404 Not Found
Or the following Error in the Application log:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Description: The database WSS_Content on ComputerName Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
Solution:
1. Open a Command Prompt window and at the command prompt change to the following directory:
%COMMONPROGRAMFILES%Microsoft sharedWeb server extensions12Bin
2. At the command prompt, type the following command, and then press ENTER to stop the SPWebService service:
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”
3. After the SPWebService service has stopped, type the following command, and then press ENTER to start the SPWebService service:
stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”
4. After the SPWebService service is started, type the following command to complete the hotfix process or the update process:
psconfig -cmd upgrade -inplace b2b -wait -force
Symptom #3:
Unable to browse Central Administration or SharePoint site. You get the following error message in the browser:
“Cannot connect to the configuration database”
Or the following Error SQL :
Event Type: Error
Event Source: Windows SharePoint Services 3
Event ID: 3760
Event Category: Database
Description:
SQL Database ‘SharePoint_Config_’ on SQL Server instance ‘ComputeNameMicrosoft##SSEE’ not found. Additional error information from SQL Server is included below.
Cannot open database “SharePoint_Config_” requested by the login. The login failed.
Errors in the Studio Express: Cannot show requested dialog.
ADDITIONAL INFORMATION: Cannot show requested dialog. (Microsoft.SqlServer.Express.SqlMgmt)
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)
Database ‘SharePoint_Config_’ is already open and can only have one user at a time. (Microsoft SQL Server, Error: 924)
Cannot connect to the configuration database. The database SharePoint_Config_ is not accessible. (Microsoft.SqlServer.Express.ObjectExplorer)
Solution:
1. Change the database mode from Single_User to Multi_User
For SQL Server Express, execute the following query against the database:
ALTER DATABASE <DatabaseName> SET MULTI_USER
For SQL Server 2005 or 2008:
a. Go to the property of the database.
b. Select Options.
c. Under State, Restricted Access, set the value to MULTI_USER.
2. Open a Command Prompt window and at the command prompt change to the following directory:
%COMMONPROGRAMFILES%Microsoft sharedWeb server extensions12Bin
3. At the command prompt, type the following command, and then press ENTER to stop the SPWebService service:
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”
4. After the SPWebService service has stopped, type the following command, and then press ENTER to start the SPWebService service:
stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”
5. After the SPWebService service is started, type the following command to complete the hotfix process or the update process:
psconfig -cmd upgrade -inplace b2b -wait -force
Symptom #4:
Users are prompted for authentication when trying to browse a SharePoint site.
Solution:
Disable the authentication loopback check:
1. Click Start , click Run , type regedit , and then click OK .
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa
3. Right-click Lsa , point to New , and then click DWORD Value.
4. Type DisableLoopbackCheck , and then press ENTER.
5. Right-click DisableLoopbackCheck , and then click Modify .
6. In the Value data box, type 1 , and then click OK .
7. Exit Registry Editor.
8. Restart the computer.
(From KB 926642, Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: “Access denied” or “No network provider accepted the given network path”, http://support.microsoft.com/default.aspx?scid=kb;EN-US;926642)
Symptom #5:
Users are receiving an error when installing KB979445 (MS10-039): “The update is already installed on this system.”
The KB979445 is dated for 4th of June 2010 which is after the April 2010 CU date of 27.04.2010.
Additional information:
When you have already applied the WSS/MOSS April 2010 cumulative update, the binaries version of the hotfix though are lower than April CU (12.0.6535.500). Because of very extensive testing’s of security hotfixes it may come to overlapping with our CU’s. the KB979445 has been created and tested before Feb. 2010 and after Dec. 2009 where as the April CU already took place. This means, the security fix is included in the April CU and you don’t need to worry about further.
If you have installed the February or April cumulative update for WSSv3 / MOSS, you should be OK and no further action is required unless you still have to run PSConfig Wizard!
We are offering our updates in a cumulative update cycle so our February Update already contains the fix mentioned in the security bulletin. Unfortunately not all SharePoint environments worldwide are updated regularly so just a reminder to think about an update.
Please visit also the blog here from Joerg Sinemaus and read the comments below the post for further information’s.
greets, Steve Chen – GTSC SharePoint Support Engineer
SharePoint mysteries and more... 
Thanks a lot!
LikeLike