Microsoft KB Archive/924429
Article ID: 924429
Article Last Modified on 11/20/2007
- Microsoft Content Management Server 2002 Service Pack 2
Microsoft has released security bulletin MS07-018. The security bulletin contains all the relevant information about the security update for Microsoft Content Management Server 2002 Service Pack 2 (SP2). This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites, depending on whether you are a home user or an IT professional:
- Home users:
- IT professionals:
This security update is available for the following language versions of Content Management Server 2002 SP2:
Issues that this security update fixes
In addition to the issues that are described in the security bulletin, this security update fixes the issues that are described in the following Microsoft Knowledge Base articles:
887574 FIX: You may receive the "OutOfMemoryException" error message when you perform a Site Deployment Import preview in Content Management Server 2002
912356 FIX: The Web server may stop responding when you try to generate a channel path by using the MCMS API in Content Management Server 2002
913072 FIX: The import may fail when you try to import certain SDO package files in MCMS 2002 Service Pack 1a
913400 FIX: You receive an error message when you try to use SQL authentication mode in the Database Configuration Application (DCA) after you install Content Management Server 2002 Service Pack 2
913401 FIX: If you try to perform a site deployment export operation to SQL Server 2005, the export operation fails in Content Management Server 2002 Service Pack 2
913554 FIX: You can no longer delete a hyperlink by clearing the Hyperlink Address field after you install Content Management Server 2002 Service Pack 2
913706 FIX: The attachment is stored as an unmanaged link when the file name contains a letter that has a grave accent in MCMS 2002 Service Pack 2 and in MCMS 2002 Service Pack 1a
914195 FIX: The MCMS Template Explorer disappears from Visual Studio .NET 2003 after you install Microsoft Content Management Server 2002 Service Pack 2
914782 FIX: A postback does not work when you use Mozilla Firefox or Netscape Navigator in Content Management Server 2002 Service Pack 2
916114 Description of Content Management Server 2002 post-Service Pack 2 hotfix package: August 3, 2006
917509 Description of Content Management Server 2002 post-Service Pack 2 hotfix package: March 30, 2006
919841 FIX: An incorrect version of the Nrdhtml.dll file is installed after you apply the Content Management Server 2002 hotfix that is described in KB article 913706
921300 FIX: You may not see parts of a Web site after you import an .sdo file that contains updates to connected postings in MCMS 2002 Service Pack 2
921930 FIX: Error message when you render a placeholder in edit mode and when you change the focus from an Internet Explorer browser window to any other open window in MCMS 2002: "Object Expected"
923755 Description of the Content Management Server 2002 post-Service Pack 2 hotfix package: August 8, 2006
927508 Error message when you use a custom application for Web site deployment in Content Management Server 2002: "Memory could not be read/written at address"
If you install this security update manually, you must restart the computer.
Note If this security update is installed from one of the following sources, you do not have to restart the computer:
- Microsoft Update
- Microsoft Office Update
A problem has been found with the security update. This problem affects deployments in which you used a custom installation path to install Content Management Server 2002. The security update overwrites the registry values for the custom installation location by using the default installation paths for Content Management Server 2002 files.
The following is an example of an affected scenario:
Content Management Server 2002 is installed together with the following:
- Service Pack 2
- The latest software update (MS07-018)
Additionally, Content Management Server 2002 files are installed in a nondefault path.
When you deploy a site from a remote computer, you receive the following message:
Site Manager will not start. When a user tries to start Site Manager on the server on which Content Management Server 2002 is installed, the user receives the following error:
The Database Configuration Application will not start. If a Content Management Server administrator tries to run the Database Configuration Application after the update is installed, the application will not run at all.
Images on Content Management Server pages are missing. When you locate a Content Management Server page that contains images, a red "X" appears instead of each image.
Incorrect information is reported in the event logs for Content Management Server.
To work around these symptoms, view the values in the following registry keys to see whether the path has been changed to the standard installation path for Content Management Server.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Note The standard installation path for Content Management Server is as follows:
C:\Program Files\Microsoft Content Management Server
If the server part of Content Management Server only is installed:
HKEY_LOCAL_MACHINE\SOFTWARE\NCompass\Resolution Content Server\dir
HKEY_LOCAL_MACHINE\SOFTWARE\NCompass\Resolution Content Server\Database Manager\PhysicalExecPrefix
HKEY_LOCAL_MACHINE\SOFTWARE\NCompass\Resolution Content Server\Database Manager\PhysicalReadPrefix
Only computers that have the Client installed will have the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\NCompass\NCompass Resolution Client\Dir
Only computers that have the Site Stager installed will have the following registry keys:
All the paths that you see in these keys should be changed to the path in which the Content Management Server files have been installed. For example, do the following if the Content Management Server files are installed in
- Click Start, click Run, type regedit, and then click OK.
- Expand HKEY_LOCAL_MACHINE, and then expand SOFTWARE.
- Click the NCompass registry node.
- In the right-side pane, double-click the REG_SZ value that is named CmsInstallLocation.
- Replace C:\Program Files\Microsoft Content Management Server by using the custom installation path.
Note In this example, the placeholder
C:\CMSInstall represents the installation location. However, the installation location may be different.
- Repeat this procedure for each key that is identified earlier in this section.
Additional query words: cms2002 cms2k2 update security_patch security_update security bug flaw vulnerability malicious attacker exploit registry unauthenticated buffer overrun overflow specially-formed scope specially-crafted denial of service dos content management server office security patch performance reliability update download 2002 fix
Keywords: kbbug kbfix kbsecvulnerability kbqfe kbsecurity kbpubtypekc kbexpertisebeginner kbcontentmgtserv2002presp3fix KB924429