Skip to Content
0

Install and use CRViewer when NOT in Default Web Site on IIS

Feb 13, 2017 at 02:09 PM

30

avatar image

I have to create an asp.net app that loads reports. runs great when in "default web site" and on c: drive. However, this is not likely to be the case for some installations. How do I get Crystal installed on a drive that is NOT c: especially when that drive DOES NOT EXIST. How do I get the crystal viewer to work when it is in say Site 2 or Site 3?

Example...

DeFault Web Site : 80 d:\websites\

Site 2 :8080 e:\websites2

Site 3 :8088 f:\websites3

Site 4: 8090 g:\websites4

etc. you get the point

ALL sites have the aspnet_client folder but only default gets the crviewer etc under it and NOTHING is allowed to go there if it is there.

So the app runs like this....

site2/app it has a Vdir which points to the aspnet_client folder in its site. from what I can tell, this "should" work.

Viable solutions DO NOT include copying crystalreportviewer13 folder etc under each site, that is ridiculous, and won't get updated when new builds of cr are put on the server without manual intervention. that is a hack, I want to do this CORRECTLY.

Has ANYONE got this working correctly?

Fiddler shows 401 unauthorized even with EVERYONE FULL and the APPPOOL FULL,

I am out if ideas. surely in this world of everything web...someone has to have done this elegantly.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers