After automatic installation of KB983444, when I open sharepoint services home page I Receive the message "Unable to connect to configuration database". In the event log there are a lot of errors with event Id 33002 and id 5583. It's an installation Of WSS3 With windows internal database.

Have you ran the SharePoint Products and Configuration Wizard, after the install?Regards, Aaron www.aaron-rendell.co.uk

I did experience more or less the same problem: the automatic installation tried to install the KB983444 but didn't succeed, so I forced it manually. I ran the SharePoint Products and Configuration Wizzard after the installation (including a restart) but it got stuck at the 9 of 10 tasks. Trying to resolve the problem I wondered why I had been suggested to install the KB983444 which is related to Windows SharePoint Services 3.0 while having MOSS on that server. The point is that I can't deinstall the KB983444 update, so I installed the KB979445 too , but again the SharePoint Products and Configuration Wizzard would get stuck at the same point. Martin

Same problem here. WSS 3.0 SP1 (using internal database) on a Windows 2003 Std SP2 server. KB983444 went on bundled in with a whole load of other updates this morning. While installing the updater seemed to get stuck on KB983444. Cancelled the update and on rebooting the server we got the 'Unable to connect to configuration database' and associated event log messages. Following the instructions in this thread : http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/8b3094a1-31ee-49d7-ab02-72ca0dc440a7 we tried to complete the Configuration Wizard using the psconfig command: psconfig -cmd upgrade -inplace b2b -wait -force This didn't work, so assuming that the update hadnt gone on correctly we downloaded and installed it manually from: http://www.microsoft.com/downloads/details.aspx?familyid=3841ceda-d0af-4e5e-8a1a-7dd954850783&displaylang=en The update went on ok, so we ran the Configuration Wizard again using the psconfig command above. This time it completed without errors and on reboot the site now *seems* ok (just seeing some weird formatting problems on our site which may or may not be related).

psconfig -cmd upgrade -inplace b2b -wait -force Solved my problem without reinstalling the update. Thanks a lot to everybody

I am still having problems with WSS 3.0 SP2 after this install and attemtping to manually force the upgrade My setup is the following - front end server with WSS 3.0 SP2 running - then I have a seperate SQL server running the SP DB"s on the the back end. When I attempt to complete the upgrade manually it fails on the 2nd step the the log file shows the following "Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: The certificate, asymmetric key, or private key file does not exist or has invalid format. Cannot create certificate from file sigconfigdb.cer Executing string: CREATE CERTIFICATE [MS_SchemaSigningCertificateEC1EFE979D60890D619A99F3E33C42C06F55B1BE] FROM FILE = 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\sql\sigconfigdb.cer' System.Data.SqlClient.SqlException: The certificate, asymmetric key, or private key file does not exist or has invalid format. Cannot create certificate from file sigconfigdb.cer Executing string: CREATE CERTIFICATE [MS_SchemaSigningCertificateEC1EFE979D60890D619A99F3E33C42C06F55B1BE] FROM FILE = 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\sql\sigconfigdb.cer' 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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SharePoint.Utilities.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout) at Microsoft.SharePoint.Administration.SPDatabase.ApplyWYukonSignatureFile(SqlSession session, String sqlSignaturePath) at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.ApplyWYukonSignature(String sqlSignaturePath) at Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence.PostUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.Initialize() at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()" Any assistance is appreicated.

We are having the same problem with our site but the previous mentioned fixed isnt working for us. The patch appears to have installed but it wont let us remove it and reinstall and we cant repair it. Any idea's? Thanks in advance for any help that can be provided.

Hi, Kindly check out this link for some help on this: http://prasanjitmandal.blogspot.com/2010/05/how-to-fix-central-administration.htmlBR, PM

Attempting to reprovision the Central Admin for WSS 3.0 failed - basically ran into the same problem when attempting to complete the Sharepoint Products and Technologies Config Wizard through the CMD prompt as part of the reprovision process - this failed with the following error "Performing configuration task 2 of 5 Initiating the upgrade sequence... Failed to initiate the upgrade sequence. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: The certificate, asymmetric key, or private key file does not exist or has invalid format. Cannot create certificate from file sigconfigdb.cer Executing string: CREATE CERTIFICATE [MS_SchemaSigningCertificateEC1EFE979D60890 D619A99F3E33C42C06F55B1BE] FROM FILE = 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\sql\sigconfigdb.cer'" The problem seems to be an issue with communication between our WSS server and oru SQL server - perhaps related to permissions. I have opened a ticket with Microsoft about this issue and am waiting to hear back. I suggest you use the 1-800-Microsoft number to contact them if you are still DOA with Sharepoint

Hi Charlie! My thanks for your post. It helped me with two of my sharepoint installations!

I am in deep trouble as well with KB983444. Its the only windows update that went in on top of WSS3 servicepack2 on my box. I have done psconfig, run the wizard but no avail. Please help.

hopefully microsoft can respond to this asap.

I have the same problem. None of the suggested fixes worked. I uninstalled and re-installed WSS 3.0, and we could get to our SP site again. But of course... KB983444 was installed again last night, and now the site is broken, again!!! WTF! I too am hoping Microsoft comes up with a better fix for this. In the mean time, it looks like I'm going to have to re-install WSS. I've turned off automatic updates. Should have done that a long time ago.

JohnB352, When uninstalling and reinstalling wss3.0, how do you deal with bringing back your sites/web application or any customization? I uses groupboard, added pages using sharepoint designer and modified a few templates. I do have backup using the central admin > backup and restore and i always do full backup. What is the easiest way to bring back my sites? I can setup another box with wss3 but how do i transfer database and configurations? Any guidance in this area is greatly appreciated.

JohnB352, When uninstalling and reinstalling wss3.0, how do you deal with bringing back your sites/web application or any customization? I uses groupboard, added pages using sharepoint designer and modified a few templates. I do have backup using the central admin > backup and restore and i always do full backup. What is the easiest way to bring back my sites? I can setup another box with wss3 but how do i transfer database and configurations? Any guidance in this area is greatly appreciated. I'm not sure I'm the best person to be giving advice on this. I'm fairly new to SP. But this is what I did - I just now did it for the 2nd time this week: - In IIS, remove the SP and CA site. - Uninstall SP, reboot server - Re-install SP - Run SP Wizard. I don't remember if this happened the first time I did this, but just now the wizard said it *failed*. But the site works. There are no problems with it. I did do a backup using CA. But I did not have to do a restore. Which was a total surprise to me. Hopefully someone with more experience will post here. And HOPEFULLY Microsoft will do something about this, like fix their *patch* so that it doesn't break SharePoint. Because I can't do updates on this server until they fix that.

Thanks JohnB352, I finally found the solution for my setup. I got WSS3sp2 with Groupboard 2007. KB983444 update went in last week and from then on I could not connect to central admin and all sites. The config wizard = failed on sequence 2, psconfig...-wait -force = failed on task 2. Working Solution: Uninstalled Groupboard > Run Configuration Wizard > Installed Groupboard Wasted 3 days and heaps of coffee. Let it be a lesson: backup daily and check all updates before installing. Thanks to all the techs who shared.

I have the same problem. After auto installing critical updates, SharePoint Services 3 running on SBS 2003, is complaining about event ID 33002 and id 5586 every five minutes. Running that SharePoint command mentioned by Ivo did not repair the issue for me. I called and created a Microsoft support ticket as the problem was caused by their updates and was told that I would receive no-charge support for this. Well, Microsoft messed up on this one. They marked my ticket as a home use ticket which was incorrect, and then closed my ticket with a reason of "unresolved"!! So this morning, two days later, I had to call back in and create a new ticket and the guy who took my call was so rude about the whole thing, didn't care that MS is causing downtime in my business, and offerred no help. So I am hoping now that I can get help in this forum rather than wait for Microsoft to help with the problem they caused. I have run the psconfig -cmd upgrade -inplace b2b -force command, but it fails on step 4 repeatedly. My events are saying that the "dbo.proc_getrunnableworkitems is blocked due to an invalid signature". Can anyone help please? James Nelson

I have run the psconfig -cmd upgrade -inplace b2b -force command, but it fails on step 4 repeatedly. My events are saying that the "dbo.proc_getrunnableworkitems is blocked due to an invalid signature". Can anyone help please? James Nelson That's dissappointing that Microsoft was of no help. I was hoping that they would come up with a fix that works for everyone. I litterly cannot run any Windows updates on the server I have, because of this. Whatever that "invalid signature" thing is, that is the crux of the problem here. After getting the KB983444 update installed, I now get a "invalid signature" error when I backup the site with CA. So it looks like I have a crippled SP installation. With no way to fix it. You could follow the steps that I posted. But make sure you have a backup first.

As of this morning Microsoft has passed my case from the Share Point support to the SQL team - hopefully they can figure this out - I will update once I speak with Microsoft

Thanks you so much everyone. I was at my wits end before I found this thread. I installed the update on Saturday as I had not heard any adverse things about it (should have done a more thorough search of the web). Where did you find that fix anyway? My standalone sharepoint 3 service didn't work with the first try of psconfig -cmd upgrade -inplace b2b but worked the second time with the -wait -force at the end. Not sure if I had to run it twice or if the last 2 switches had an effect. Thanks so much - How could Microsoft release this patch without thorough testing. My clients would have been furious if they'd had to wait any for Microsoft to come up with a fix.

Well I stand corrected. Ivo's last post convinced me to try again with this command. I was not using the -wait switch and when I did, it worked! All is well now. Thank you Ivo. James Nelson

I spent almost 2 hours on the phone with Microsoft this morning with this issue. When I ran psconfig -cmd upgrade -inplace b2b -wait -force it kept failing. Microsoft finally figured out that the user that I was logged in as did not have sufficient rights to apply the update 983444 which is what caused the initial problem, but it also prevented the fix to fail. I had to add the following to the user permission.... IIS_IUSRS , WSS_ADMIN_WPG , WSS_RESTRICTED_WPG , WSS_WPG Once I had proper permissions, the psconfig above successfully finished.

Hi everybody, We had the same problem since Friday 11/06 and finaly found the solution yesterday (15/06). 11/06 : update KB983444 didn't finished correctly and broke our Sharepoint sites. After many many attempts we finally solve the problem with this thread and others. - Re-install manually the KB983444 (http://www.microsoft.com/downloads/details.aspx?familyid=3841ceda-d0af-4e5e-8a1a-7dd954850783&displaylang=en ) - Reboot - command : psconfig -cmd upgrade -inplace b2b-wait -force : but failed in step 3 (so don't know if that help us to solve the problem) - command : stsadm -o upgrade -inplace - and Sharepoint works ! I hope that my response can help some of you, good cheer! Thanks for this thread. PS : Sorry for my English, I'm Fench ;-)

Clemg, When trying to reinstall manually it says that is already installed. Could you uninstalled it first? Thanks in advance.

For me the install of the KB983444 didin't work the 11/06 (error in the update.log for this KB), so I haven't uninstalled it because it was not in the Configuration Panel, Install/Uninstall Programs. Maybe you don't have exactly the same problem as mine ... try directly the MSDOS commands

Finally working! Final description in this alternative thread: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/78d0aa2b-ac22-4811-a553-6567463ab4c1?prof=required Fernando

Microsoft finally got our site back up and working yesterday - we had a couple problems that were causing the patch to install but the configu wizard to fail causing problems with connection to our content and admin DB's. We have WSS 3.0 front end on S2k3 R2 SP2 - with a SQL Server 2005 running the DB on a different physical box - we were getting invalid or non existant errors when trying to complete step 2 of the update looking for the file SIGCONFIGDB.CER - the Microsoft SQL team had me copy that CER and 2 others to the c:\program files\common files\microsoft shared\web server extensions\12\Template\SQL on our SQL server (had to manually create this path ) - once that was done the psconfig command passed the 2nd stage and quit on the 3rd stage - to get past this problem - we had to run the following 2 commands stsadm -o spsearch -farmserviceaccount [domain\username] -farmservicepassword [password of account for SP] once that completed we ran this stsadm -o spsearch -farmcontentaccessaccount [domain\usernam] -farmcontentaccesspassword [password for account for SP] then ran the command psconfig -cmd upgrade -inplace b2b-wait -force the wizard completed - Sharepoint is now working as it did before the patch - IT WAS A LONG WEEK TO GET HERE

May I ask, was that a freebie, since it was their update that created the problem? Our SP is still screwed up. It's running, but I no longer have CA and I can't install updates on this Server 2008 box, since it will hose SP again.

JohnB352 Yes this case was a freebie - I let them know right away that the problem started after I applied their patch - they made it a freebie right away and I never had to give them any information about billing. Call their pro support number 1-800-936-4900 - let them know you are a comany and that you are having SharePoint issues due to the patch, they will start the process of getting a case going.

The SharePoint team have posted this blog: http://blogs.msdn.com/b/sharepoint/archive/2010/06/22/installing-kb938444.aspx?CommentPosted=true#commentmessage (The KB number referenced within the post is incorrect, it should be KB983444. The Microsoft SBS blog references the correct KB)Regards, Aaron www.aaron-rendell.co.uk

I spent almost 2 hours on the phone with Microsoft this morning with this issue. When I ran psconfig -cmd upgrade -inplace b2b -wait -force it kept failing. Microsoft finally figured out that the user that I was logged in as did not have sufficient rights to apply the update 983444 which is what caused the initial problem, but it also prevented the fix to fail. I had to add the following to the user permission.... IIS_IUSRS , WSS_ADMIN_WPG , WSS_RESTRICTED_WPG , WSS_WPG Once I had proper permissions, the psconfig above successfully finished. Where did you set these permissions and what did you set them too? In IIS or in SQL Server or somewhere else? Ted

Ted, those are all security groups that you'll find in Windows Server itself (check out Server Manager or your Administrative group on Start). He's talking about ensuring that whichever account you're logged in with when running the update (an administrative-level account in one form or other) is added to each of those groups, if only temporarily. Note that the first one of the four is new with Server 2008/IIS7, so you won't find it in 2003.

Hi everybody, We had the same problem since Friday 11/06 and finaly found the solution yesterday (15/06). 11/06 : update KB983444 didn't finished correctly and broke our Sharepoint sites. After many many attempts we finally solve the problem with this thread and others. - Re-install manually the KB983444 (http://www.microsoft.com/downloads/details.aspx?familyid=3841ceda-d0af-4e5e-8a1a-7dd954850783&displaylang=en ) - Reboot - command : psconfig -cmd upgrade -inplace b2b-wait -force : but failed in step 3 (so don't know if that help us to solve the problem) - command : stsadm -o upgrade -inplace - and Sharepoint works ! I hope that my response can help some of you, good cheer! Thanks for this thread. PS : Sorry for my English, I'm Fench ;-) Recently run into the exact issue above and just want to say thanks, this has allowed me to get our Sharepoint site back online. Thanks for the input all.

Hi everybody, We had the same problem since Friday 11/06 and finaly found the solution yesterday (15/06). 11/06 : update KB983444 didn't finished correctly and broke our Sharepoint sites. After many many attempts we finally solve the problem with this thread and others. - Re-install manually the KB983444 (http://www.microsoft.com/downloads/details.aspx?familyid=3841ceda-d0af-4e5e-8a1a-7dd954850783&displaylang=en ) - Reboot - command : psconfig -cmd upgrade -inplace b2b-wait -force : but failed in step 3 (so don't know if that help us to solve the problem) - command : stsadm -o upgrade -inplace - and Sharepoint works ! I hope that my response can help some of you, good cheer! Thanks for this thread. PS : Sorry for my English, I'm Fench ;-) Recently run into the exact issue above and just want to say thanks, this has allowed me to get our Sharepoint site back online. Thanks for the input all. THANK YOU CLEMG ! this worked for me as well, had exact same issue at a client site - after running this update automatically the SBS 2008 Sharepoint services were KAKtus! My Steps to repair this issue 1) Sharepoint services not working - panic mode - LOL - search internet - eventually found this site, phew! 2) Downloaded KB983444 and installed manually 3) Reboot 4) run command in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN\psconfig -cmd upgrade -inplace b2b-wait -force 5) command took a long time around 20-25min to complete 6) all good, sharepoint services up and running, noticed intranet site missing the custom logo, but easily fixed.. Thanks again PS your English is waaaaaaaay better than my French!