Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Issues after restoring a Configuration Manager 2007 site server from a 32-bit to 64-bit operating system

Issues after restoring a Configuration Manager 2007 site server from a 32-bit to 64-bit operating system

Summary

Microsoft supports the use of the Site Repair Wizard to restore a System Center Configuration Manager 2007 site server from a 32-bit Operating System to a 64-bit Operating System as noted in the article About the Site Repair Wizard (http://technet.microsoft.com/en-us/library/bb680393.aspx). However, there are two possible issues that may occur on a site server restored in this manner. These issues will only occur if the site server was originally installed to the default \Program Files\Microsoft Configuration Manager directory on the 32-bit Operating System.

↑ Back to the top

More Information

Issue 1: Hotfixes, Service Packs, R-releases fail to install.  Windows Installer (.MSI) based packages will redirect the TARGETDIR property from \Program Files\Microsoft Configuration Manager\ to \Program Files (x86)\Microsoft Configuration Manager\ on the 64-bit Operating System. As the site server is installed to \Program Files the patch or update will fail.
 
Resolution
Use the mklink command line tool to temporarily redirect the installation folder:
 
mklink /D "C:\Program Files (x86)\Microsoft Configuration Manager" "C:\Program Files\Microsoft Configuration Manager"
 
Once the symbolic link is created, the hotfix or update installation will run without error.  After the installation is complete, the link should be removed using rmdir:
 
rmdir "C:\Program Files (x86)\Microsoft Configuration Manager"
 
Issue 2: On System Center Configuration Manager 2007 R3 Site Servers with a Reporting Services Point installed, the Reporting Services node of the Administrator Console will fail to load. The following error can be seen in the adminui.log:

System.InvalidCastException\r\n[A]Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.CatalogItem[] cannot be cast to [B]Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.CatalogItem[]. Type A originates from 'Microsoft.ConfigurationManagement.Reporting, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\Program Files\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll'. Type B originates from 'Microsoft.ConfigurationManagement.Reporting, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'LoadFrom' at location 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll'.\r\n at Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.ReportingService2005.ListChildren(String Item, Boolean Recursive)
 
This occurs when R3 has been installed after using the Site Repair Wizard to move from a 32-bit to 64-bit Operating System, and after using the mklink resolution noted previously.
 
Resolution
Edit the registry to set the R3 Assembly Search Path value to C:\Program Files\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll in the following location:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\AdminUI\QueryProcessors\SRS\Assembly Path

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2667543
Revision : 1
Created on : 1/8/2017
Published on : 1/24/2012
Exists online : False
Views : 96