Thanks for the help,
so in other words, i should run the web-application like
this:
http://myComputer/myFolder/myApplication.aspx
right?
Thanks.
[color=blue]
>-----Original Message-----
>You need to edit the Web.config file as suggested,[/color]
<customErrors[color=blue]
>mode="Off"/>, or run the web app on the server. Then[/color]
you'll see the detailed[color=blue]
>error description.
>
>--
>Carsten Thomsen
>Enterprise Development with Visual Studio .NET, UML, and[/color]
MSF[color=blue]
>
http://www.apress.com/book/bookDisplay.html?bID=105
>"Artmic" <ads@dhal.com> wrote in message
>news:05c801c34740$15082440$a301280a@phx.gbl...[color=green]
>> Hello can anyone help me with a MS-SQL2000 install
>> and .Net + windows2000 advance server.
>>
>> I installed everything, and everything works fine on[/color][/color]
its[color=blue][color=green]
>> own. But when i try to run my ASP.NET application it
>> gives me a very basic error message, and i can not[/color][/color]
figure[color=blue][color=green]
>> out what is wrong with the application, i have included
>> the error message below.
>>
>> The problem is that it is not specific enough to track
>> down the problem, although i'm pretty sure it is MS-SQL
>> Server specific since i can access parts of my
>> application that do not connect to the MS-SQL server,
>>
>> Please help !!! :( At least so i can figure out how i
>> can get some detailed debug messages out of the error
>> page...
>>
>>
>> Server Error in '/MyApplication' Application.
>> -------------------------------------------------------[/color][/color]
---[color=blue][color=green]
>> Runtime Error
>> Description: An application error occurred on the[/color][/color]
server.[color=blue][color=green]
>> 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[/color][/color]
create[color=blue][color=green]
>> 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>
>>
>>
>> Notes: The current error page you are seeing can be
>> replaced by a custom error page by modifying
>> the "defaultRedirect" attribute of the application's
>> <customErrors> configuration tag to point to a custom
>> error page URL.
>>
>>
>> <!-- Web.Config Configuration File -->
>>
>> <configuration>
>> <system.web>
>> <customErrors mode="RemoteOnly"
>> defaultRedirect="mycustompage.htm"/>
>> </system.web>
>> </configuration>
>>
>>
>> .
>>
>>[/color]
>
>
>.
>[/color]
