cancel
Showing results for 
Search instead for 
Did you mean: 

Is SAP Crystal Reports runtime engine for .NET Framework 4 supported in Windows Server 2000

Former Member
0 Kudos

Hi,

We need to install 'SAP Crystal Reports runtime engine for .NET Framework 4' in our production servers.

Server Details:

Windows 2000 SP4 - 32 bit server (x86).

Download Link:

http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_32bit_13_0_1.zip

Objective:

We have come up with a small utility to convert .rpt files (Created in Seagate Crystal Report 7.0) to .pdf. To do this conversion we require 'SAP Crystal Reports runtime engine for .NET Framework 4' as the supporting software. Our production server runs in Windows Server 2000 SP4 - 32 bit server (x86).

Searched in the site but I was not able to find the system requirements to install 'SAP Crystal Reports runtime engine for .NET Framework 4' and have the below queries.

Query:

1. Is it possible to install 'SAP Crystal Reports runtime engine for .NET Framework 4' in Windows Server 2000 SP4 - 32 bit server (x86).

2. Do we need any other supporting software to get 'SAP Crystal Reports runtime engine for .NET Framework 4' installed in Windows Server 2000.

3. After installation will there be any need to restart the server.

We need your help to get our queries addressed.

Thanks,

Gokul

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Gokul,

Crystal Reports for VS2010 is not supported on Windows 2000 Server. You can review the Supported Platform document for complete details. It might be possible to get the runtimes to work on Win2000, but no one is likely going to be able to offer any troubleshooting steps if you run into issues on that server.

Deploying the CR runtime files to a supported server should be all you need with regards to the Crystal Reports portion of your application.

Restarting the server shouldn't be necessary, but you may want to do an IIS Reset (Start > Run > iisreset) after completing your install.

A Best Practice would be to use a test server and test your deployment scenario to see if it works.

Sincerely,

Dan Kelleher

Answers (0)