The official blog for Windows Server Essentials and Small Business Server support and product group communications.
[Today’s post comes to us courtesy of Douglas Boyd and Damian Leibaschoff from Commercial Technical Support]
In the past few months we started seeing the recurrence of an old issue that was previously documented in:
832880: You cannot successfully install the intranet component or connect to http://companyweb in Windows Small Business Server 2003 http://support.microsoft.com/default.aspx?scid=kb;EN-US;832880
However, the scope of the SBS 2003 media affected by this issue has effectively changed. You now need to use SBS 2003 with SP1, SBS 2003 with SP2, or SBS 2003 R2 media to have a successful installation. Any older media will encounter the problem, no matter the version of SQMCFG.DLL present on CD 3.
This problem may occur if one of the following used to install the Intranet component:
Background Information:
When SBS 2003 originally released in 2003, an issue was discovered with the way WMSDE verified the validity of a SharePoint file. To work around the problem, a fix was created (KB832880) and a NEW release of SBS 2003 shipped that included updated files on CD 3. However, this would only circumvent the problem until late 2009. A proper resolution to this issue was not available until Service Pack 4 was released for the SharePoint WMSDE instance (KB909544).
Symptoms:
The following error is generated when the installation tries to create the configuration database in WMSDE.
Metadata manifest 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin\sqmsto.dll' does not exist or has invalid signature. (Error code: 2779).
To identify if you have the affected media, look for the existence of a folder named IE6 present on the CD 3 under \SBS\CLIENTAPPS. If you have the folder, then the CD is older than SP1 and you will experience the problem. If your CD 3 does NOT have the \SBS\CLIENTAPPS\IE6 folder, then it is an SP1 or greater CD. If that is the case, you will also have a CD 4 that contains the following folder structure:
02/23/2005 01:37 PM 2,238 autorun.ico 02/23/2005 01:37 PM 52 autorun.inf 04/05/2007 10:34 AM <DIR> MSDE_SP4 04/05/2007 10:34 AM <DIR> SBS 04/05/2007 10:34 AM <DIR> WMSDE_SP4
Resolution:
In order to resolve this issue, perform the following steps:
We have a working WSS 2.0 site, exept that we cannot login to it on the SBS2003 itself (login from workkstations is fine). Having approved 909544 in WSUS, however, doesn't seem to offer it up to the SBS. Is there a URL from where this update can be downloaded manually?
@Steve
Hi,
If your CompanyWeb is working fine, then you most likely have long ago installed 909544. The issue you are seeing is described here:
http://blogs.technet.com/sbs/archive/2009/04/17/authentication-issues-accessing-companyweb-from-the-server-itself-after-963027.aspx
And the update you want is 961143.
As a reference, you can get to any update by going to
http://catalog.update.microsoft.com
Regards,
SBS Bloggers
I seem to be having this problem on a install of SBS 2003 for a client. They had the older SBS media (dated Nov. 2003) and I got the Sharepoint error @ install. The rub is this customer didn't want to buy any new software and SBS wouldn't install on their new hardware. I had to rip the i386 folder off a version of SBS 2003 R2 we had and slipstream it into their media to get it to install. Then I applied the official SBS SP1 to the server.
I noticed in the SP1 docs that 832880 is listed as being part of SP1. Will this affect the procedure list above since 909544 is supposed to be installed first? If so, is there a work around?
Thanks.