Compartilhar via

2nd UPDATE: Installing Hotfix 948110 on SBS 2003 Servers

  • Artigo

We have received a few reports of hotfix 948110 causing issues with SharePoint (Companyweb) on SBS 2003.  At this time please hold off on installing this patch on your SBS 2003 server.  Installing this hotfix may prevent the SharePoint WMSDE instance from starting.  We are currently investigating the issue and will update this blog post as soon as possible. Update 1: If you have already installed this hotfix AND the MSSQL$SHAREPOINT service is not starting you can perform the following steps to fix this service.

  1. Rename C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTBinn to Binn.old
  2. Restore C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTBinn from a backup taken previous to installing hotfix 948110.  If you do not have a backup try using volume shadow copy.
  3. Start the MSSQL$SHAREPOINT service
  4. Test CompanyWeb

This should fix CompanyWeb.  If you go to Windows Update you will once again be offered update 948110, do not install this update for the time being.

Update 2:

We have determined that this issue only occurs on Small Business Server 2003 Server in which CompanyWeb was upgraded to SQL 2000 from WMSDE and was neverupdated to SQL SP4.  If your CompanyWeb site is still using WMSDE (the default) you can go ahead and apply this update.  If your CompanyWeb has been migrated to SQL 2005 this issue also does not apply to you and you can apply this update.  If you have been affected by this issue or you have updated to SQL 2000 please review this: https://blogs.technet.com/sbs/archive/2008/07/11/cannot-access-company-web-after-installing-948110.aspx.

Comments

  • Anonymous
    January 01, 2003
    Oh...you mean restore the entire server from a microsoft backup?

  • Anonymous
    January 01, 2003
    Oh, I didn't get an update that you responded.... Hrm..how do I restore my instance? My process IS in the broken state.  I used the workaround that is crossed out to get it back up. However, it appears that I'm the only one that can access the server now. :(

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    It has been reported that hotfix 948110 is causing problems with sharepoint - problems that will prevent the service from running (so your companyweb site will be down!) From the SBS blog: If you have already installed this hotfix AND the MSSQL$SHARE

  • Anonymous
    January 01, 2003
    The Official SBS Blog is reporting that Hotfix 948110 is causing issues on SBS2003 servers. Hold off

  • Anonymous
    January 01, 2003
    First of all, I'm a semi-noob when it comes to servers....Okay, it seems what I posted earlier, before I had an account, is not coming up on screen.   I wanted to know if there's any problem with me just using the workaround?  The multiple links finally end at where I need to re-install the update to SQL2000 from the original disks. Also, I thought I applied the SP4 but I guess not.  If I just do the workaround, can I then just apply the SP4?  (I'll need help in how to do that.)

  • Anonymous
    January 01, 2003
    Just installed security updates today, July 9, 2008 and lost internet connectivity on a desk and laptop. Used restore to regain connectivity succussfully. Whats going on with these very recent updates?  Also, with automatic updating, the updates reappear on prior restore points as well.  I won't install them again!

  • Anonymous
    January 01, 2003
    The Official SBS Blog : UPDATED: Hold Off on Installing Hotfix 948110 on SBS 2003 Servers: http://blogs

  • Anonymous
    January 01, 2003
    Rit, this hotfix should not affect IPSEC. Your issue was most likely caused by some data corruption.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Since I'm in China presently and my server is in NYC...I guess I'll try a full restore from microsoft backup from an earlier time. Sorry for the spammy messages, there's no way to remove or edit posts. :(

  • Anonymous
    January 01, 2003
    Hi tqc4869, If you indeed have upgraded to Full SQL 2000 STD, in theory you should be able to restore your instance to before the security update and then properly apply Service Pack 4 for SQL 2000 before attempting to install the security update again. You should confirm that your Edition value in the registry under HKLMSoftwareMicrosoftMicrosoft SQL ServerSharepointSetup reads "Standard Edition" at that point. The steps in the main post are designed for people to complete the process from the broken state and not have to re-apply the security update after it is completed. Regards, SBS Bloggers

  • Anonymous
    January 01, 2003
    PingBack from http://blog.sbs-rocks.com/2008/07/09/hold-off-on-installing-hotfix-948110-on-sbs-2003-servers/

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Arnel:  We have not had any reports of this issue effecting SharePoint 3.0 on SBS 2003 when SharePoint is installed using the side-by-side whitepaper.  Please call support to report your issue.

  • Anonymous
    January 01, 2003
    Anil:  I am not sure what blog you are refering to but there is no registry tweak that will fix this issue.

  • Anonymous
    January 01, 2003
    Jason, we cannot post the Binn files becasue there are many different versions depending upon what was installed on your server prior to installing the hotfix.  Please call support and we can help you recover or reinstall the SharePoint WMSDE instance.  

  • Anonymous
    January 01, 2003
    Uh, I'm the one who asked if there's a problem with only using the workaround.  Please respond here.

  • Anonymous
    July 09, 2008
    just got an update from internal blog that we should not uninstall the patch..wondering if we can tweak in registry rather than uninstalling.

  • Anonymous
    July 09, 2008
    The comment has been removed

  • Anonymous
    July 09, 2008
    So those of us with a 2003 server with Sharepoint 3.0 with no backup (Just built it a month ago and testing it out before adding it to our backups) are SOL?

  • Anonymous
    July 09, 2008
    Well your description is identical to my situation. Windows update finished at 3:05 am last night and my server log states. Database MICROSOFT##SSEE is running. All the services are running, I even restarted them. But get The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) 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: #50071: Unable to connect to the database STS_Config on GENSRVSP006MICROSOFT##SSEE.  Check the database connection information and make sure that the database server is running.. I'll try calling support.

  • Anonymous
    July 10, 2008
    I had the problem also.  It turned out that there are a few updates with number 948110 (e.g. an update on SQL Server SP4 ; an update on the Server 2003 OS ; ...). The strange thing was that some of them were installed and one of them was not. So, I pushed that one to install also and after that I was able to keep MSSQL$Sharepoint running, which made everything to work again.

  • Anonymous
    July 10, 2008
    So is there a way to uninstall it or fix it yet?  My sharepoint is down.

  • Anonymous
    July 10, 2008
    I don't have those Binn files, can you guys post them?

  • Anonymous
    July 10, 2008
    This hotfix seems to also be effecting IPSEC as well.  We were able to use http://support.microsoft.com/kb/912023/en-us, followed by a reboot, as a work around to get back up and running.

  • Anonymous
    July 14, 2008
    A client (who we look after) have a server with just SQL 2000 Desktop engine, and this fails (both automatically and manually) to install the security update. Any thought would be welcome.

  • Anonymous
    July 14, 2008
    Well Rit is not alone, and if it is data corruption then the updates are causing it. I work for an IT servies company and provide IT support to several small to medium companies and have seen the event logs for 2 SBS severs that went into Block mode immediately after rebooting from the MS update installs in the last week. I know of a third. Most of our customers are not set for automatic installs so I suspect I will see more as we manually install the updates this month. In the 3 cases that I know of another reboot from the console fixes it.

  • Anonymous
    July 18, 2008
    So, I'm a bit lost...The work around works... What's the problem of me not following: http://blogs.technet.com/sbs/archive/2008/07/11/cannot-access-company-web-after-installing-948110.aspx

  • Anonymous
    July 21, 2008
    Hi, We are based in france and we have  problem with the 948110. Since july 8th we don't have access to companyweb and also cannot do backup. so we want to know how to "Perform the upgrade again to SQL Server 2000." We try to do the update with the "technologie CD" provide by SBS and the system don't want to do a regretion how to do this. Thanks

  • Anonymous
    July 24, 2008
    Experiencing the same problem with company web. The before and after are the Desktop Engine. There was never an attempt to upgrade to a newer version of SQL. The update tried to install, but it never does. The update just keeps re-appearing. Any pointers are appreciated.

  • Anonymous
    July 28, 2008
    I gave up on trying to recover my companyweb and sharepoint and just got the server reinstalled. But... After all my atempts I can't get the sharepoint databases to work. I really need help.

  • Anonymous
    August 03, 2008
    I followed a recommendation that was given here http://blogs.technet.com/sbs/archive/2008/07/11/cannot-access-company-web-after-installing-948110.aspx in one of the commments Alberto recommend the free upgrade to sql2005express, this got the mycompany website back up.. hope it works for everyone. jr