Access Database

  • Thread starter Thread starter Jim Heavey
  • Start date Start date
J

Jim Heavey

I am trying to get my first application to run on a production server and
the application continues to fail, and I am pretty sure it is failing when
it attempts to connect to my database.

What option do I need to set in my web.config file such that it will tell
me where the application is failing if I am running it from the Web Server
(localhost)? Right now it is showing me the web config file

What option in the web.configure file do I need to set to force it to go to
a standard error page? Will it take this option even if I am running it
from the Localhost and what to see the line that it is failing on? In
looking at my web.config, it says I should use the following...
<customErrors
mode="RemoteOnly" />

But then how do I steer the system to a particular web page?
 
You might try trapping the error by wraping your database access in a
try..catch block. That way you can find any database excpetions.

As for the web.config, just set it to "Off" (must be first last upper case)
for more detailed messages on your development box.

You might aslo try enabling "trace" for your page so that it will dump out a
complete trace at the bottom of your web when you view it. Just make sure
you reset the custom errors and the trace option before posting to your
production machine.
 
Back
Top