Error 400 invalid directory when opening reports

[Former Member]

Description of Problem or Question:

When attempting to pull up a report from Java InfoView, I get an http Status 400 error.

Product\Version\Service Pack\Fixpack (if applicable):

Crystal Reports Server 2008 (latest one, just downloaded last week).

Relevant Environment Information (OS & version, java or .net & version, DB & version):

I installed the Crystal Reports Server 2008 onto a just built Windows Server 2008 R2 64bit system. Nothing else is installed.

I read through the documentation and installed the prerequisistes.

I did a default install of the server (didn't make any changes), I believe this installs MySQL locally and Apache and tomcat. All ports are the default.

Nothing else but windows and updates are installed.

Sporadic or Consistent (if applicable):

Consistent

What has already been tried (where have you searched for a solution to your question/problem):

Searched forums and internet (google). Could not login to KB area.

Steps to Reproduce (if applicable):

I installed crystal Reports 2008 on a client.

Created a report.

I used the publishing wizard to upload to the server.

Login to Java InfoView comes up, attempt to launch a report file (the one I just published or examples doesn't matter) I get the following error:

HTTP Status 400 - Invalid path /CrystalReports/view was requested

type Status report

message Invalid path /CrystalReports/view was requested

description The request sent by the client was syntactically incorrect (invalid path /CrystalReports/view was requested)

Apache Tomcate/5.5.20

Can anyone lend a hand? It would be greatly appreciated. Is it a 64bit and Apache Tomcat problem. I have ran across another software package that put in a 32 bit tomcat executable and I had issues and so had to change the executable out for the 64bit version.

Thanks!

[Former Member]

I wish I had an update, as you can see nothing was posted here for assistance. Here are some of my notes on this issues.

1. I was able to reproduce it in firefox, IE 8 and chrome (so it was not just an IE9 issue).

2. I started from scratch, not even using a windows VM template like I did on my original install. Choose default EVERYTHING for windows. Updated windows (maybe this is causing the issue), followed their install docs again to the letter. Same thing.

3. I attempted several clients and browser versions (XP SP2, XP SP3, Windows 7) didn't make a difference either.

4. Jumped back several java versions, didn't make a difference either

essentially this tanked SAP for our environment. Since I couldn't get a functional demo up, and no help we moved to a competitor. FYI, SAP has no pre-sales support, so I couldn't call them for assistance.

I don't mind a company not having pre-sales support staff, but then you better well make sure the install docs and stuff better be correct and up to date so people can set it up and see if it fits their needs. In this case they failed on both fronts, and lost a a good 10-15 thousand dollars that we gave to another company.

I guess when you make millions what's a few thousand? Obviously they don't care.

[joshua_kuhn]

I was able to find 3 other instances where the same error was logged with SAP support. Twice, a redeploy of the war files resolved the issue. In the 3rd scenario, only IE9 was a problem and when using IE8 in compatibility mode, viewing worked. In this last scenario viewing with Firefox also worked which isn't consistent to what you witnessed, so we can probably throw this out as a possibility.

This morning, I tested a new install of CRS2008 v1 on Win2003 64-bit and everything seemed fine. I tested viewing the sample reports with both the java viewer and regular default html viewer. In both cases the crystal report documents viewed. I didn't have access to a Win2008 64-bit server, otherwise i would have used that for a better comparison. The issue might occur from either a mismatched jvm on the windows client or something on the Tomcat side. Both the jvm and Tomcat should be 32-bit versions, since the rest of CRS is 32-bit.

A few things to consider:

- Did the error happen for all crystal report documents? I have to assume so. But make sure you at least test the sample reports.

- Does the same issue happen within the CMC as well?

- Try downloading a browser debugger to see how far the request is going (http://www.fiddler2.com/fiddler2/) is one option.

- compare these urls in fiddler to the /tomcat55/webapps directory and make sure the files exist.

- Try viewing it in InfoView on the server console as well.

- Try redeploying the webapps within tomcat as a last resort. Doing so seemed to resolve two other similar scenarios.

Below is the beginning of my output from fiddler when requesting to view the report. since this is what a working view request will look like, comparing it to yours might shed some light on the source of the problem.

-

---

http://lm-xi33x64:8080/CrystalReports/view.do?bypassLatestInstance=true&cafWebSesInit=true&appKind=I...

http://lm-xi33x64:8080/CrystalReports/js/callback.js

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/crviewer/images/style.css

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/crviewer/crv.js

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/dhtmllib/images/skin_standard/wait01.g...

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/dhtmllib/images/skin_standard/dialogti...

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/dhtmllib/images/skin_standard/dialogel...

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/dhtmllib/images/transp.gif

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/allStrings_en.js

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/processindicator.js

http://lm-xi33x64:8080/CrystalReports/crystalreportviewers/js/dhtmllib/empty.html

Edited by: Joshua Kuhn on Sep 14, 2011 10:35 PM

[Former Member]

I still have no definitive proof of anything, but I have the impression that it is due to an incoompatibility issue with IE version 9. The support department here will investigate the matter and try to get some answers.

[Former Member]

Any news on this. I have the same issue.

Matt

[Former Member]

Anyone find a workaround or resolution? We are experiencing the same issue with IE9.