Tue, Oct 9 2007 11:59
bradley
Read the bulletins this month!
In the "How NOT to patch" at SMBnation I said that my goal is to look to reasons to wait on patching. Oh I'll still patch and place all security patches on a system, but I always scan Patch Tuesday's recap for reasons to delay patching.....
http://isc.sans.org/diary.html?storyid=3480
If you have a side by side install of Sharepoint on a SBS box (where you have both Sharepoint 2 and Sharepoint 3) BEFORE you deploy ANY patches ensure you have a backup. This patch is a one way patch in that it cannot be uninstalled.
So READ HERE How to Backup Windows SharePoint Services:
http://thorprojects.com/blog/articles/297.aspx
And BACK IT UP FIRST!
Description of the security update for Windows SharePoint Services 3.0: October 9, 2007:
http://support.microsoft.com/kb/934525/
Known issues
| • |
During the last two steps of the SharePoint Products and Technologies Configuration Wizard, you may receive the following error message:
Failed to start service SPSearchServiceInstance on this server after completing upgrade. Please start it manually. However, the SPSearchServiceInstance service was actually started after the SharePoint Products and Technologies Configuration Wizard finished. You can safely ignore this error message and the error message that is logged in the SharePoint Products and Technologies Configuration Wizard log file.
|
| • |
The Microsoft GroupBoard Workspace 2007 add-in template for Windows SharePoint Services 3.0 may cause the SharePoint Products and Technologies Configuration Wizard to fail during a build-to-build upgrade.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
|
| • |
When you run a gradual upgrade of a Windows SharePoint Services 2.0 site collection to a Windows SharePoint Services 3.0 site collection, the server may be brought down. You must allow the gradual upgrade to complete before you apply this security update.
|
| • |
You use quiet mode to install Windows SharePoint Services 3.0. If this security update is applied during the installation, the SharePoint Products and Technologies Configuration Wizard unexpectedly runs after the installer program has finished.
To resolve this issue, extract this security update to a folder on the computer. Then, copy the files to the Updates folder of the program's release version. After the extracted files are copied to that location, the folder is ready to be used to install the release version of the program that is updated to this security update level.
|
| • |
After you install this update on a computer that is running Microsoft Windows Small Business Server 2003, the Web sites may not restart within the time-out period. Therefore, you may be unable to access the Backup, CompanyWeb, Microsoft Server ActiveSync, Monitoring, Outlook Web Access, or Remote Web Workplace Web sites. To resolve this problem, use one of the following methods:
| • |
Open Internet Information Services (IIS) Manager, and start any Web sites that are stopped. |
| • |
Restart the computer. | |
| • |
If you run a virus scanning program during the installation of this security update, you may experience intermittent issues during the installation. To resolve these issues, turn off the virus scanning program before you apply this security update. |
| • |
You use host-named site collections in Windows SharePoint Services 3.0. If you have many host-named site collections in your deployment, you may experience severe performance issues while this security update is being applied. For example, this issue may occur when there are more than 50 host-named site collections in your deployment.
Microsoft is aware of this issue in which the installation and upgrade will take a long time to update the databases when you run the SharePoint Products and Technologies Configuration Wizard. If you have many host-named site collections in your deployment, we recommend that you do not apply this security update at this point.
Note If you do not use host-named site collections in Windows SharePoint Services 3.0, you can safely apply this security update.
|
| • |
Consider the following scenario. You unprovision a Windows SharePoint Services 3.0 search service database by using one of the following methods:
| • |
Method 1
You run the following command-line:
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\bin\STSADM.EXE" -O SPSEARCH -ACTION STOP -F |
| • |
Method 2
You use the Central Administration page to stop the "Windows SharePoint Help Search" service. To do this, follow these steps:
| 1. |
Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration. |
| 2. |
Click Operations, and then click Services on Server under Topology and Services. |
| 3. |
Click Stop to stop the Windows SharePoint Help Search service. | | You perform a basic installation of Windows SharePoint Services 3.0 that contains the unprovisioned search service database and this security update. When you run the SharePoint Products and Technologies Configuration Wizard in this scenario, the wizard is not completed successfully.
To determine whether you are experiencing this issue, open the latest PSConfig log that is saved in the following location:
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\Logs If you receive the following error message in the PSConfig log, you are experiencing this issue:
Exception: System.ArgumentException: The object with id SOME-RANDOM-GUID does not exist in the configuration store. The object may have been deleted by another operation.
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.DeleteObject(Guid id)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.DeleteObject(SPPersistedObject obj)
at Microsoft.SharePoint.Administration.SPPersistedObject.Delete()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.ProvisionDatabase()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() To work around this issue, follow these steps:
| 1. |
Do one of the following:
| • |
Delete the Windows SharePoint Services 3.0 search service database in the Windows SharePoint Services 3.0 SQL instance. The database name starts with "WSS_Search_" and ends with the server name. |
| • |
Reprovision the Windows SharePoint Services 3.0 search service database by specifying a nondefault Windows SharePoint Services 3.0 search service database. To do this, use one of the following methods:
| • |
Method 1
Run a command-line that resembles the following command-line:
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\bin\STSADM.EXE" -O SPSEARCH -ACTION START -DATABASENAME “DBNameExample" |
| • |
Method 2
| a. |
Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration. |
| b. |
Click Operations, and then click Services on Server under Topology and Services. |
| c. |
Verify that the Windows SharePoint Services Search service is stopped. If it is running, stop the service. |
| d. |
Click Windows SharePoint Services Search under Services. |
| e. |
Under the Search Database, change the database name to any name other than the default name, and then click OK. |
| f. |
On the Services on Server page, click Start to start the Windows SharePoint Services Search service. | | | |
| 2. |
Run the following command-line:
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\bin\ PSConfigUI.exe | |
| • |
The hotfixes for the following issues are included in this security update. However, if you install a Windows SharePoint Services 3.0 service pack after you install this security update, the following hotfixes are lost.
| • |
You rename a Windows SharePoint Services 3.0 site collection. If you add a new user to the site collection, the welcome e-mail message that is received by the new user contains the old site name.
|
| • |
You use the Application Definition Designer tool to import a database model that is included in the Business Data Catalog Definition Editor tool (BDC tool) of the software development kit (SDK) for Microsoft Office SharePoint Server 2007. After the database model is imported, the database connection string is blank.
|
| • |
When you run SPWriter.exe, the program closes unexpectedly with an error message in module Oleaut32.dll. This issue was resolved by a hotfix that moved the GetTimeZoneMoveParameters() function to the end of the Owssvr.dll file.
|
| • |
You migrate user accounts to a new site collection by using the Stsadmin.exe command-line tool. When the new site collection is crawled, you receive event errors 6482, 6875 and 6482 in the Application log. This issue may occur when the user's SID in Windows SharePoint Services 3.0 is invalid.
|
| • |
You use a custom template in a Windows SharePoint Services 3.0 site collection. If you create a new Web page, all the standard Web parts may not be available when you click Add a Web Part.
|
| • |
When you apply this security update, some third-party services may be incorrectly stopped. If this issue occurs after you apply this security update, you must restart the computer.
|
| • |
You connect to a Windows SharePoint Services 3.0 site collection. If the page contains a Calendar Web part that is set to Calendar view, the page may not load completely. This issue may occur if you do not have the permission to read the Calendar list.
| |
Back to the top
Prerequisites
There are no prerequisites to apply this security update.
Restart information
In certain circumstances, a restart of the computer may be required. If a restart is required, follow these steps:
| 1. |
Restart the computer. |
| 2. |
Run the "SharePoint Products and Technologies Configuration Wizard." |
| 3. |
Verify that all the SharePoint services are now running in the services console. |
| 4. |
Verify that all the Web sites are running in the Internet Information Services (IIS) Manager |
Filed under: Security
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")