Welcome to TechNet Blogs Sign in | Join | Help

The Official SBS Blog

The official blog for Small Business Server (SBS) support and product group communications.

News

  • Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of Microsoft. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
2nd UPDATE: Installing Hotfix 948110 on SBS 2003 Servers

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 Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Binn to Binn.old
  2. Restore C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Binn 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: http://blogs.technet.com/sbs/archive/2008/07/11/cannot-access-company-web-after-installing-948110.aspx.

Posted: Wednesday, July 09, 2008 12:50 PM by SBS Bloggers

Comments

anil said:

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

# July 9, 2008 3:30 PM

el cattivo said:

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!

# July 9, 2008 7:40 PM

Susan said:

ElCattivo, the issue you address is about the DNS patch.  Do you have Zone Alarm installed?  If so this is the reason why.

You need to reinstall them and to determine the root cause.

# July 9, 2008 7:46 PM

THE OFFICIAL BLOG OF THE SBS "DIVA" said:

The Official SBS Blog : UPDATED: Hold Off on Installing Hotfix 948110 on SBS 2003 Servers: http://blogs

# July 9, 2008 7:47 PM

Arnel said:

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?

# July 9, 2008 7:51 PM

SBS Bloggers said:

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.

# July 9, 2008 8:20 PM

SBS Bloggers said:

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

# July 9, 2008 8:22 PM

Arnel said:

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 GENSRVSP006\MICROSOFT##SSEE.  Check the database connection information and make sure that the database server is running..

I'll try calling support.

# July 9, 2008 8:56 PM

Mario De Witte said:

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.

# July 10, 2008 3:27 AM

Switch Systems Blog said:

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

# July 10, 2008 3:48 AM

Jason said:

So is there a way to uninstall it or fix it yet?  My sharepoint is down.

# July 10, 2008 9:06 AM

Nick Whittome - The Naked MVP said:

The Official SBS Blog is reporting that Hotfix 948110 is causing issues on SBS2003 servers. Hold off

# July 10, 2008 9:35 AM

Jason said:

I don't have those Binn files, can you guys post them?

# July 10, 2008 9:58 AM

Rit said:

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.

# July 10, 2008 10:58 AM

SBS Bloggers said:

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.  

# July 10, 2008 11:47 AM

SBS Bloggers said:

Rit, this hotfix should not affect IPSEC. Your issue was most likely caused by some data corruption.

# July 10, 2008 11:49 AM

Ian said:

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.

# July 14, 2008 5:22 AM

MikeMCSE said:

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.

# July 14, 2008 7:21 PM

TC said:

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

# July 18, 2008 12:51 AM

tqc4869 said:

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

# July 18, 2008 1:04 AM

tqc4869 said:

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.)

# July 18, 2008 1:18 AM

SBS Bloggers said:

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 HKLM\Software\Microsoft\Microsoft SQL Server\Sharepoint\Setup 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

# July 18, 2008 11:21 AM

tqc4869 said:

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. :(

# July 20, 2008 3:22 AM

tqc4869 said:

Oh...you mean restore the entire server from a microsoft backup?

# July 20, 2008 3:32 AM

tqc4869 said:

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. :(

# July 20, 2008 3:35 AM

tqc4869 said:

Okay, just an update.

I used Microsoft backup to roll back to an earlier system state and that worked.

Then I downloaded the sp4 and followed those instructions to update the components.  I had SP3 and SQL Windows Standard.

# July 20, 2008 6:43 AM

azerty said:

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

# July 21, 2008 3:52 AM

thejamie said:

I'm having my share of difficulty figuring out the right approach to the 948110.  First of all, I did experience the inability to get to the internet and log into my server.  If I remember correctly (not likely) I rebooted the server several times because I believed I had been hacked (gee, we can't log into the server)

I also believe that I read the part about reinstalling SP4 from the command line, which I did for all versions of SQL 2000 desktop (not sure if I upgraded to SQL Std or not... thought I did but to be sure, reran the SP).  Needless to say, it did not run at first and I discovered that I needed to remove something from the folder (the autoinst.inf if I recall correctly) and at that point, the reinstall went okay for all instances including the Sharepoint instance.

Once that happened, the login worked again.  Since that time, I have jumped through hoops trying to turn off the automatic update which tries, each day (14 times now) to install itself and fails each time.

Since all is working, it would seem the only faulty part now is to get the update to stop installing.  I tried the trick of stopping and restarting services (wauuptdt and bits and eventlog etc) reregistering the link libraries for the update, copying the old catroot2 in and then back after the second stop and finally restarting everything but this did not remove the update from the "I insist on installing" list.

Am I safe?  Or must I somehow figure out how to force the 948110?

# July 23, 2008 8:35 AM

Jorge said:

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.

# July 24, 2008 12:29 AM

António Lima said:

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.

# July 28, 2008 1:30 AM

deek said:

Hi,

Im trying to get my head round this problem

(& failing spectaculary)... Our company web is b0rked, all symptoms point to 948110.

Got the invalid schema on master db   error

Got the errorlog bit

2008-07-29 22:47:50.70 server    Microsoft SQL Server  2000 - 8.00.2050 (Intel X86)

Mar  7 2008 21:29:56

Copyright (c) 1988-2003 Microsoft Corporation

Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)

server is running sql 2005 workgroup edition.

but looking at errorlog,it says that it is running sql 2000

can company web be running on 2000 & other DBs on 2005?is this the same problem,

If I re-install 2005, will the problem be fixed?  

So many questions..

# July 30, 2008 6:40 AM

Jorge said:

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

# August 3, 2008 12:02 PM
New Comments to this post are disabled
Page view tracker