RE: Reporting - Page cannot be displayed error
- From: Sai Wong [MSFT] <saiwong@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 May 2005 09:22:12 -0700
It could be many different things :
Since you are on Windows 2003, check if the ASP ISAPI extension is enabled
Check if Session state is enabled (see below)
Launch Internet Services Manager
go to your Reporting Point directory and
choose 'Properties'
Press 'Configuration' button which will bring up new
property pages
Choose the 'App Options' tab.
There should be a checkbox to enable Session state. Make
sure this is enabled
If the above don't help then try the following. Run notepad.exe and copy the
following text and save the file as test.asp in your reporting point folder
<HTML>
<TITLE>Some test page</TITLE>
<BODY>
<% Response.Write "Hello Mum" %>
</BODY>
</HTML>
Does this simple asp page run ?
If not move the file to inetpub\wwwroot and try again. Does the simple asp
run ?
Sai
This posting is provided "AS IS" with no warranties, and confers no rights.
"jbourdet23" wrote:
> I installed SMS sp1 on my member server 2003 sp1 and all my clients are
> discovered. I'm in the processes of puching out the clients and I'm trying to
> learn so of the cool features of SMS - ex. Reporting
>
> When I go under reporting i choose a report I want to run and run it then my
> browser pops up to display the page but it says "page cannot be displayed". I
> get the same error if I just try to view the root Report.asp page. I have IIS
> install installed and running with whatever default setting. I didnt run the
> lockdown tool.
>
> Any ideas?
> Thanks
> Jason
.
- References:
- Reporting - Page cannot be displayed error
- From: jbourdet23
- Reporting - Page cannot be displayed error
- Prev by Date: Re: Components not Installed
- Next by Date: Any know issues with the Enhanced System Discovery?
- Previous by thread: Reporting - Page cannot be displayed error
- Next by thread: Re: Reporting - Page cannot be displayed error
- Index(es):