Crystal Reports Page Cannot Be Found

We are in the midst of shifting web servers from a Windows 2000 Server to a Windows 2003 Server machine. I have a series of ASP pages for employee timesheet logging. All of that has been modified properly and is working. However, inside the virtual directory is a Crystal Reports file, TSReport.rpt. The 2000 server had a link to it that would open the report in the browser. On the 2003 machine, when I hit the report link I just get a "Page Cannot Be Found" error. The report is there and opens fine across the network. I'm sure there's an error somewhere in my IIS config, but I haven't the slightest idea where.

Anyone have any suggestions?

Thanks in advance!

Run Inetmgr and right click the web site virtual directory and click properties. your document tabs default document path should be verified and the path to your rpt verified in your asp pages. This ius a good place to start. ;)

Done and done. Still no luck. I copied a static HTML page into the directory with the report and it works fine. I copied the RPT file into the virtual directory's root, where ASP; HTML; and ASPX pages run fine, and when you try to open the RPT file in the browser, I still get the "Page Not Found" error. I've tried a couple of different RPT files and it's the same result. I'm pretty certain my problem lies either with Crystal Reports or the way I have IIS configured to handle RPT page requests.

Thanks for the reply though! Keep them coming!

Could it be something with dependancy files on the server for CR? Maybe the old server had CR dlls installed?

I suppose that's entirely possible, but both servers are running CR Developer Edition 8 installed from the same media. On the odd chance that something got missed during installation or overwritten by another program, I reinstalled CR 8 on the 2K3 server, but we're still getting the 404 Error.

Then it may be something with the paths in your virtual directories or ??? Im not that good at IIS. Maybe try creating a thread in the ASP forum. ;)

I think I have the resolution with the help of a co-worker.
Assuming you have Crystal Reports 8 already installed on the 2003 server.

1) Open a command prompt. Change directory to C:\Windows\System32.
Excecute the following command:
cscript iisext.vbs /AddFile "C:\Program Files\Seagate Software\WCS\wcsinsapi.dll" 1 CrystalReports 0 "Crystal Reports 8.0"

(for more information see http://support.microsoft.com/kb/328419/en-us)

2) Execute the following command:
cscript iisext.vbs /EnFile "C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"

(for more information see http://support.microsoft.com/kb/328360/en-us)

3) Open up the IIS Manager. Right-click on the computer name and select Properties. Click on the MIME Types button. Add the following extensions:

Extension___MIME Type
---------___----------
.rpt________application/octet-stream
.shtx_______application/octet-stream
.csp________application/octet-stream
.cri_________application/octet-stream
.cwr________application/octet-stream

(by default on 2000 all extensions assumed application/octet-stream, or executable)

4) Open the properties window for the application or web site that will be using Crystal Reports. Click on the configuration button. Add the following application extensions:

Extension__Executable
---------__----------
.rpt_______"C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"
.shtx______"C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"
.csp_______"C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"
.cri________"C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"
.cwr_______"C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"


It worked for me.

Anther way but more unsecure is to go into the Web Service Extensions under IIS and select All Unknown ISAPI Extensions. Once highlighted, press the "Allow" button. This also worked for me which proved that Crystal Reports will work.

Hope this helps -
Mike

Nice find! :thumb: