You have a Windows 64-bit server and you must install the 32-bit version of SQL Server 2005 Reporting Services on this machine, which means that you must install Server 2008 64-Bit Asp Components. In this tip, I'll go through the steps you need to take for this installation.

I've seen customers who have Windows Server 2003 or 2008 64-bit machines but should install a 32-bit version of SQL Server 2005 Reporting Services. This requires installing a 32-bit version of ASP.NET 2.0 that runs on the top of IIS.

By default, IIS runs on 64-bit Windows 64. Microsoft recommends that the 64-bit operating system run on 64-bit operating systems on a 64-bit operating system, while some customers may need to re-use their existing licenses instead of buying a new product. When you try to install a Windows Server 64-bit SQL Server 2005 Reporting Services 32-bit, you will see the following error message

64-bit operating systems have always been a problem, you can find out how to enable nuisance asp components for server owners in server 2008 64-bit and how to solve them. Once the Persits or ASP Component has been installed, we need to do what we want to install;

  • A: Copy the .dll files inside the ASP component that you installed into the WindowsSysWOW64 directory.
  • Then - start> run> cmd in the window by running the command,
  • - regsvr32 C: WindowsSysWOW64AspUpload.dll
  • Then, - regsvr32 C: WindowsSysWOW64AspUpload.dll is running.
  • Again, we are going into the AspUpload folder and running the .reg file. Process completed.

When we restart our server, the asp component will now run smoothly. You can use these operations within other components.

CMD code window 
pops up 
regsvr32 C: WindowsSysWOW64AspUpload.dll 
regsvr32 C: WindowsSysWOW64AspJpeg.dll 

If it was not this way, 
enter IIS In the 
Applications Polls , Set Applications Polls enable 32 bit's true.

Configuring Windows Server 2003 64-bit to run IIS 6 on 32-bit

Installing SQL Server 2005 Reporting Services 32-bit on a Windows Server 2003 64-bit requires both configuring both ASP.NET 2.0 32-bit and IIS 6.0 to run both 32-bit web applications. In Windows Server 2003 Service Pack 1, IIS 6.0 can be enabled to run 32-bit applications on 64-bit Windows by using the Windows-Windows® 6464 (WoW64) compatibility layer. This enables the creation of 32-bit running processes within IIS as well as running ASP.NET 32-bit and other 32-bit web applications. The disadvantage of this is that after you configure IIS 6.0 to run on 32-bit, you cannot run other 64-bit web applications, making it a dedicated server for your 32-bit web applications.

To allow IIS 6.0 to run 32-bit web applications on a 64-bit Windows, go to the  % windir% \ Inetpub \ AdminScriptsdirectory and run the adsutil.vbs script with the following parameters.

cscript.exe adsutil.vbs set W3SVC / AppPools / Enable32BitAppOnWin64 .exe true c

This allows IIS 6.0 to run 32-bit web applications - these steps are  specified in this Microsoft TechNet article , which applies to 32-bit web applications, including ASP.NET  You can then install SQL Server 2005 Reporting Services 32-bit and install ASP.NET 2.0 as part of the .NET Framework installation. However, before you install SQL Server 2005 Reporting Services, you must manually install ASP.NET 2.0 32-bit in IIS 6.0 after you configure it to run 32-bit if the .NET Framework is already installed. Web applications, otherwise, you receive the same error in the screenshot above.

Navigate to the  Frame \ v2.0.50727 \% WINDIR% \ Microsoft.NET  folder (the .NET Framework 64-bit version will be in the  % WINDIR% \ Microsoft.NET \ Framework64 \  folder). Run aspnet _ regiis.exe on the command line utility.

aspnet_regiis -i

You can now continue to install SQL Server 205 Reporting Services 32-bit on IIS 6.0 running Windows Server 2003 64-bit.


Configuring Windows Server 2008 64-bit to run IIS 7 on 32-bit

If you have a Windows Server 2008 64 bit machine, there is more work to set up and configure IIS in 32-bit mode. SQL Server 2005 Reporting Services depends on IIS 6 or the previous metabase. So, even though you have IIS 7 already installed, you will still encounter a similar error in the following screenshot.

What's good about IIS 7 is that it supports IIS 6 backward compatibility through IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility. Installing both of these will also configure the IIS Default Application Pool to run 32-bit, similar to running the adsutil.vbs script for Windows Server 2003. To install these two options, you can add them to Role Role Services in IIS 7, configure them if they are already installed, or by using the Add Roles option under Server Manager. I have IIS 7 already installed, so I added the IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility options by using the Add Role Services option.

If for some reason this does not configure the Default Application Pool to run on 32-bit, you  can change the 32-bit Application  property of the application pool  by setting the Enable  property to  True . Reporting Services will be installed on the root website and will  default to the Default Application Pool  . The good thing is that you can run both 64-bit and 32-bit web applications on the same server by configuring the application pool separately.

After you install SQL Server 2005 Reporting Services, be sure to apply the latest service packs and cumulative updates.

Next steps

  • Check your SQL Server 2005 Reporting Services installation and make sure you have the appropriate media for the operating system platform. If not, you can always configure IIS to run in 32-bit mode.