mikes1p
Tue Aug 26 15:19:03 CDT 2008
Thanks! That was useful but we started getting different errors after
updating the reports\web.config. Turns out we had to upgrade to .Net 3.5 as
some of the aspx pages were written to use it.
Mike
"Per Jakobsen" wrote:
> Hi Mike
>
> Put a web.config with following in your reports directory:
> <?xml version="1.0"?>
> <configuration>
> <system.web>
> <compilation debug="true"/>
> <authentication mode="Windows"/>
> <httpHandlers>
> <clear />
> <add verb="*" path="*.aspx"
> type="System.Web.UI.PageHandlerFactory,
> System.Web, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a" />
> </httpHandlers>
>
> <httpModules>
> <add name="Session"
> type="System.Web.SessionState.SessionStateModule"/>
> </httpModules>
>
> <trust level="Full" originUrl="" />
> </system.web>
> </configuration>
>
> On Fri, 22 Aug 2008 15:19:00 -0700, mikes1p <mikes1p@discussions.microsoft.com> wrote:
>
> >We have just started running WSS3.0 for our Intranet (
http://intranet).
> >We have several reports written with .NET (aspx pages) that are located on a
> >different IIS server
> >We need to have the URL's for the aspx pages to be
http://intranet/reports
> >
> >These pages are not going to be elements within Sharepoint, we just want to
> >use the Sharepoint server as a web server hosting the aspx files. So far we
> >cannot get it to work because the webconfig of the Sharepoint server takes
> >precedence and the aspx pages needs different settings.
> >
> >How do we get IIS/Sharepoint to exclude a folder? WSS 2.0 had a method to
> >exclude a folder/path. WSS 3.0 does not have the same
> >
> >Thanks
> >Mike
> --
> BR
>
> Per Jakobsen
> Blog:
http://www.theblackknightsings.com
>