Got more questions? Find advice on: SQL | XML | Regular Expressions | Windows
in Search
Welcome to AspAdvice Sign in | Join | Help

Crystal .NET Blog

Sample codes, tips, random rantings on Crystal Reports, Crystal Enterprise etc...

ASP.NET images appear as a red "X"

Lately I've seen a lot of questions posted stating that when and ASP.NET app is deployed to the webserver that the report icons appear as red “X”s. The BusObj support site lists two KB articles to help you resolve this.
 
In summary, there are two things happening. The first is that you are using Forms Authentication and you don't have permission to view the file crystalimagehandler.aspx. You have to modify the web config file to make this accessible. The second reason is that the app was deployed manually and not using with the merge modules. The files were not deployed correctly and you have to either move the files to the GAC or copy them to the same virtual directory as crystalimagehandler.aspx.
 
The KB articles are here:
 
 
 
A third problem I've seen, although I can't find any KB articles on it, is that the virtual directory that stores the images never gets created. As mentioned before, this can happen during a manual installation. To fix this you need to create a folder within the Inetpub/wwwroot folder called 'CrystalReportWebFormViewer2'. Copy from the development machine the file in the Viewers folder (and its subfolders). This is found in the Crystal Reports folder of the MS.NET Program Files installation location. After creating the folder and copying the image files over, make it an IIS application by right-clicking on it and selecting Properties. Then click the Create button. Now you ASP.NET application will be able to use the virtual directory to display the images on the report.
 
 
Hope this helps,
 
Brian Bischof
 
 
Sponsor
Published Monday, September 27, 2004 3:18 PM by crystal

Comments

 

crystal said:

Thanks! This post helped resolve the problem I was having.
July 9, 2005 9:56 PM
 

crystal said:

Thanks for the pointers.

The problems still occured for me, then I realised the problem was that my VS install was placing the app on a different port. So I created a new virtual folder named crystalreportwebformviewer2 on the same port pointing at the same path as the existing default web site virtual folder, and now everything works fine.
July 28, 2005 6:43 AM
Anonymous comments are disabled