debugging asp.net applications remotely - please help

[sean]

Hi There,

I have an asp .net application that I am trying to debug remotely,
unfortunatley I do not have access to the server itself. I have verified the
application is working on my local machine but on the remote server it is
not.
The application inserts rows into an ms access DB, do I need to give the
aspnet worker process explicit access to the ms access database? and how can
I make the server return error messages, the one below tells me nothing,
what file do I need to modify on the server in order to see the actual error
message?


Thanks in advance for you answer

Sean



Server Error in '/' Application.
----------------------------------------------------------------------------
----

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 -->

<configuratio n>
<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 "defaultRedirec t" attribute of the application's
<customErrors > configuration tag to point to a custom error page URL.

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

<configuratio n>
<system.web>
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
</system.web>
</configuration>

[Joe]

Re: debugging asp.net applications remotely - please help

Um, that page you've cut and pasted gives you the solution to your problem -
i.e. edit your web.config file in the root directory of your application.

Joe


"sean" <seanNOSPAM@sho psmart.com.au> wrote in message
news:eaVRgFsuDH A.1512@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hi There,
>
> I have an asp .net application that I am trying to debug remotely,
> unfortunatley I do not have access to the server itself. I have verified[/color]
the[color=blue]
> application is working on my local machine but on the remote server it is
> not.
> The application inserts rows into an ms access DB, do I need to give the
> aspnet worker process explicit access to the ms access database? and how[/color]
can[color=blue]
> I make the server return error messages, the one below tells me nothing,
> what file do I need to modify on the server in order to see the actual[/color]
error[color=blue]
> message?
>
>
> Thanks in advance for you answer
>
> Sean
>
>
>
> Server Error in '/' Application.
> --------------------------------------------------------------------------[/color]
--[color=blue]
> ----
>
> Runtime Error
> Description: An application error occurred on the server. The current[/color]
custom[color=blue]
> error settings for this application prevent the details of the application
> error from being viewed remotely (for security reasons). It could,[/color]
however,[color=blue]
> be viewed by browsers running on the local server machine.
>
> Details: To enable the details of this specific error message to be[/color]
viewable[color=blue]
> on remote machines, please create a <customErrors > tag within a[/color]
"web.config "[color=blue]
> 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 -->
>
> <configuratio n>
> <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 "defaultRedirec t" attribute of the[/color]
application's[color=blue]
> <customErrors > configuration tag to point to a custom error page URL.
>
> <!-- Web.Config Configuration File -->
>
> <configuratio n>
> <system.web>
> <customErrors mode="RemoteOnl y"[/color]
defaultRedirect ="mycustompage. htm"/>[color=blue]
> </system.web>
> </configuration>
>
>[/color]