Crystal Report on web server not displaying

[Former Member]

Hi

I posted a problem up earlier today and thought I had solved the problem. I am getting the same problem on our clients test enviroment now.

Dev environment: VS 2010 - CR for VS 2010 - Windows 7 - Various browsers

Client Test Environment: DotnetFX4.0 runtime - CR runtime 32bit - Windows Server 2003 - IE7 or Chrome

I have copied the aspnet_client folder and it's contents to the root folder that the web app lives in (and various other places to try and get it to work)

I have given 'Everone' access to the C:\Windows\Temp' folder - I can see crystal temp files created there.

I've tried installing Chrome but this gives the same problem.

I have overcome the log4net.dll/type initializer/report failed to load errors and now have the last hurdle.

The report simply is not there. The page appears in the browser, and I can see a button that I have placed there on the page. I am logging the progress through the code to a text file and it all seems fine. The report is simply not there.

When this happened on our test server here, putting the aspnet_client folder in the right place did the trick and it worked. I'm guessing that the problem is related to this, and that the CR viewer simply does not have access to it or something, or it's in the wrong place.

Can anyone shed any light on this. I'm on day 3 of getting Crystal working on servers and it's wearing me down....

Julian

[former_member183750 · Accepted solution]

See if an HTTP sniffing utility such as [Charles|http://xk72.com/] or [Fiddler|http://www.fiddlertool.com/fiddler/] will tell you where the process is looking for the viewer directory.

- Ludek

[saurabh_pathak · Accepted solution]

The symptoms that you have mentioned points me towards - bobj is undefined.

You can go thorough following:

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22994

- Saurabh

[Former Member · Accepted solution]

Hi,

I know this is an old post, but I am having a similar problem again.

Many thanks Ludek for your 'fiddler' utility idea. That solved my problem before. The files it was trying to access were in crystalreportviewers13 and it was looking for them in a folder with a very slightly different name.

Anyway, all has been fine for the past few months. We have recently updated the website. Something even stranger is happening. The reports all work fine for a while and then all of a sudden they stop working and we get a Report load failed exception occurring. We have three different reports that all stop working at once.

Report 1. Reads from a dataset in memory and also reads the .rpt file from disk using the Load(...) function

Report 2. Reads from a dataset in memory and reads the Crystal Report from memory as opposed to reading it from file

Report 3. This is a test report that just has a label on it

If I rename the folder that reports 1 & 2 are pointing to and repoint the folder in web.config (we are using asp.net 4.0) then it all starts working again for a few hours.

I can see the files in C:\Windows\Temp being created even on a failure, they report simply is not there (again). Fiddler doesn't show anything up this time when it's not working.

Any ideas would be most appreciated.

Many thanks

Julian

[Former Member · Accepted solution]

I have something similar except I get "The report filename was empty." When we restart IIS the problem goes away for a bit, but then comes back.

[Former Member · Accepted solution]

Hi Chris,

I posted this problem again, and got it sorted. Don't know if it will help you?

Have a look through the following post.

Julian

[Former Member]

Thanks guys, I think there's a couple of things there that I haven't tried yet.

Will let you know if I get things working!

Julian