Hello together! We are encountering a very big problem after installing KB983444 on Windows Server 2008 x64 running WSS v3 (using Windows Internal Database) - none of our sites is accessable anymore (even not Central Administration)! The error is always: "Access to table dbo.sysdiagrams is blocked because the signature is not valid. " This error and "Access to table dbo.Versions is blocked because the signature is not valid" are also logged in the event viewer. When we try to execute "Select * from dbo.versions" via SQL Management Studio, we get the same error, although the user is a db_owner. We have already gone through different posts (http://blogs.msdn.com/b/sharepoint/archive/2010/06/22/installing-kb938444.aspx or http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx ) and followed the instructions (tried several times to execute "psconfig –cmd upgrade –inplace b2b –wait –force" from an evaluated command prompt) but the second step always fails and we find the error named above in the logs. Is there any chance to get our system back running? Any help is greatly appreciated!!!

Did you follow the steps after psconfig –cmd upgrade –inplace b2b –wait –force failed, listed below?? Did you review the the next doc and To help troubleshoot this problem, obtain the following SharePoint log files: PSCDiagnostics_<var>Datecode</var>.log By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS" folder. Upgrade.log By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS" folder. What do the logs say at the time of psconfig failing? -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

Dear Ivan, thanks for your fasst response. Yes, We did follow the steps buth that did not change anything. The logs include the same error "Exception: System.Data.SqlClient.SqlException: Access to table dbo.sysdiagrams is blocked because the signature is not valid." Please find part of the logs below: SPConfigurationDatabase Name=SharePoint_Config_0186972a-73d3-470d-b6f8-b7e9e9c21ffc Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE to Online. [SPManager] [ERROR] [30.06.2010 03:50:29]: SPManager.Initialize failed. [SPManager] [ERROR] [30.06.2010 03:50:29]: Access to table dbo.sysdiagrams is blocked because the signature is not valid. [SPManager] [ERROR] [30.06.2010 03:50:29]: bei System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) bei System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) bei System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) bei System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) bei System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) bei System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) bei System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) bei System.Data.SqlClient.SqlCommand.ExecuteNonQuery() bei Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command) bei Microsoft.SharePoint.Upgrade.SPSqlCommandFactory.GetRowCount(String strTable) bei Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.LogTableRowCounts() bei Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.PreUpgrade() bei Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) bei Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) bei Microsoft.SharePoint.Upgrade.SPManager.Initialize() [SPManager] [INFO] [30.06.2010 03:50:29]: Upgrade Boot Strap finishes. 2 errors and 0 warnings encountered. 06/30/2010 03:50:29 1 ERR Fehler beim Initiieren der Updatesequenz. Fehler beim Update von SharePoint-Produkten und -Technologien. Weitere Informationen zu diesem Fehler erhalten Sie unter 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log'. Eine Ausnahme vom Typ 'System.Data.SqlClient.SqlException' wurde ausgelöst. Weitere Ausnahmeinformationen: Access to table dbo.sysdiagrams is blocked because the signature is not valid. System.Data.SqlClient.SqlException: Access to table dbo.sysdiagrams is blocked because the signature is not valid. bei System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) bei System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) bei System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) bei System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) bei System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) bei System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) bei System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) bei System.Data.SqlClient.SqlCommand.ExecuteNonQuery() bei Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command) bei Microsoft.SharePoint.Upgrade.SPSqlCommandFactory.GetRowCount(String strTable) bei Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.LogTableRowCounts() bei Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.PreUpgrade() bei Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) bei Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) bei Microsoft.SharePoint.Upgrade.SPManager.Initialize() bei Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run() bei Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Do you have any third party things added like Groupboard? I've seen where groupboard has needed to be uninstalled, then the psconfig run the groupboard reinstalled.

Dear Susan, thanks for your input but we have no 3rd party tools installed. We have already talked to a support guy from MS who is currently checking the logs. If (or hopefully when) we solve the issue - I will share the necessary steps with you all.

looking forward to see this reply myself as I too was adversely affected by this patch - fortunately I had a sytem image I reverted to - would like to run this patch once it is fixed Like yourself I attempted unnsuccessfully running the proposed fix from the SBS Blog post.

Dear all, we have finally managed to get the SharePoint back running. Unfortunately we had to revert to the latest backup of the virtual machine (SharePoint runs virtualized) from two weeks ago. We then were able to attach the current content database - now everything is OK again. This has been option 1 from MS support (after having tried lots of steps with psconfig all day long) - the second option would have been to back up the SQL-databases, completely uninstall WID and SharePoint and reinstall it. Then attach the databases again. I am a little unsure if that would have worked because we were not able to backup some tables when accessing via SQL Server Management Studio -we got the same error as described above (access blocked because signature is invalid). Because of that, we are even happier that the first option worked! Thank you all for your support!