See all of the top support solutions for our most common issues here
On 64-bit operating systems, some IIS-based Configuration Manager 2007 roles (Management Point, etc.) require 64-bit ASP.NET components to be registered. If we register 32 bit components instead of 64-bit (only one can be registered at the same time), these Configuration Manager roles may stop working.
Note: You can register these components based on this TechNet article: http://support.microsoft.com/kb/894435.
That means Configuration Manager 2007 requires 64-bit ASP.NET components to be activated.
However, if 32-bit SQL server is installed on the same server, when we try to install SQL Server Reporting Services (SSRS) from 32-bit SQL install media, we get a warning that SSRS will not work properly if 32-bit ASP.NET components are not registered. SSRS cannot be configured properly from its Reporting Services Configuration tool as it does not send the information properly to IIS. Only 64-bit SQL Server installation is able to work properly with 64-bit ASP.NET components, which are required for the previously mentioned Configuration Manager roles to function.
So what does all this mean? The bottom line is that if Configuration Manager roles requiring ASP.NET will be installed on the same machine as the Reporting Services Point, and the operating system is 64-bit, then we should also use 64-bit SQL server on the machine.
If you find yourself in a situation where you need to move to a 64-bit version of SQL Server, these options can help:
1. Replace 32-bit SQL Server installation with 64-bit version.
Install a separate SQL server and move the Configuration Manager database there temporarily. This way the Configuration Manager site will work until you reinstall 64-bit SQL on the Site server.
Remove 32-bit, and install 64-bit SQL server with SQL Server Reporting Services (SSRS), then move the ConfigMgr database back to Site server.
2. Move the site database to a different SQL server. Use an existing or install a new separate SQL server and move the Configuration Manager database there.
3. Use a remote SQL Server Reporting Services installation just for SQL Reporting Service Point role. Add this remote server as site system, and install only SQL Reporting Services Point ConfigMgr role on it.
Note that all methods require a separate SQL server (the first only temporary).
Hope this helps,
Imre Butsy | Senior Support Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
Thanks for such a good article!