Prev: App pool being disabled
Next: IIS and delimiter in "Request.Form" values ... ASP NET
From: Anton Khozov on 20 Aug 2010 00:13
Hello, All

I have this problem too with iis7.5, but not with iis7.0.
I found solution next solution:
I removed Request.AddHeader "CONTENT-LENGTH" command from rptserver.asp and now crystal viewer displays data.

> On Tuesday, March 16, 2010 6:54 PM Andrew Steel wrote:

> Hi All,
>
> I have had a bit of a hunt around at it seems a few people have come across
> this problem but have not found a solution yet.
>
> The Crystal Reports Viewer activex component will correctly display a report
> when hosted on IIS7 (32 or 64bit and also IIS6 etc). However it will not
> display the report correctly when hosted on IIS7.5 (64 bit) - the report
> template shows up but the actual content frames just display 'loading'. You
> can export the report and see that the data is all there - it just will not
> display. (We are using Crystal XI developer edition though I believe this
> same issue affects all versions).
>
> So there is a difference somewhere - but where is the question (I have not
> seen any errors in the log files but I am yet to enable more detailed logging
> to delve deeper). I have played around with the application pool settings
> (changed the identity to network service, changed to an admin account to rule
> out permissions problems etc) with no luck. Comparing 64bit IIS7 on 2008 next
> to 64bit II7.5 on 2008 R2, I tried to rule out any configuration differences
> (hence the app pool identity changes/testing) but still no luck.
>
> Has anyone come up with a solution for this?
>
> Cheers


>> On Thursday, March 18, 2010 11:18 PM Gina Bourret wrote:

>> I have been working all day on this same problem and have found nothing on the
>> web. This is the first that helps me realize it is a compatabiltiy issue
>> with 7.5 and Crystal XI. Hope for help soon.
>>
>> "Andrew Steel" wrote:


>>> On Friday, April 16, 2010 11:33 AM Jim Ortiz wrote:

>>> I have been looking into this too. I have not found much else either. I have
>>> verified that the report object is created and populated correctly, just the
>>> viewer is not working. At this point, I am considering exporting the report
>>> to PDF, and then displaying the PDF in the browser instead of using the
>>> Viewer at all. I'd lose the ability for the end user to export the report to
>>> Excel/Word/Etc though.


>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>> Changing WCF Service Implementation at Runtime
>>> http://www.eggheadcafe.com/tutorials/aspnet/d9263dcc-f7ed-42f3-bc96-321461be3306/changing-wcf-service-implementation-at-runtime.aspx
 | 
Pages: 1
Prev: App pool being disabled
Next: IIS and delimiter in "Request.Form" values ... ASP NET