1) Runtime Error:-

Description:
An application error occurred on the server. The current custom error settings for this application prevent the details of
the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running
on the local server machine.

Details:
To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors>
tag within a "web.config" configuration file located in the root directory of the current web application. This
<customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

You need a web.config file. Although there is more to this file, if it does not exist create the file in the top directory and paste in the code and test the page locally.

Simon

Hi,
Thanks for the reply.Earlier when I debugged the Asp.Net Application "Cannot connect to Localhost " was occuring.In the Config file we had mentioned Provider=MSOLAP . Here , error was occuring . i.e "OLAP Server error".We changed this to Provider=MSOLAP.3 and the error is not occuring .


Any way Thank You Very much for the reply.




Regards
Ajith S Kulgod

There are a number of set-up issues.

Is IIS loaded?
Which version are you running IIS6 or IIS7?
Has the local web site set-up?
Are you using Visual Web Developer?

Simon

Iam using IISv5.And also i have created the web setup.

Ajith,

You can also put on you page:

<%@ Page Language="VB" debug="true"%>

Not that at times the messages make any sense but it you have made a error it all becomes too apparent.

Microsoft Visual Web Developer 2008 is free to download and there is definitely error correction embedded. If you are running IIS 5 it is unlikely to be Vista, IIS6 is a definite improvement as you can set-up multiple instances of web sites.

Simon