If no ASPNET user account, can I use Global.asax for application-level error trapping?
- From: "Doug" <spamworks@xxxxxxxxx>
- Date: 29 Jun 2006 11:59:14 -0700
Using Visual Studio 2005, SQL Server 2000, and ASP.NET/VB.NET for a Web
Application.
We have a System DSN using Windows NT authentication defined on the
development box to connect to the SQL Server (both SQL and IIS are on
the 192.168.1.2 server).
We have "Identity Impersonate=true", and "CustomErrors mode=On" and
"defaultRedirect="ErrorHandler.aspx" in web.config.
(Note: We are NOT using userName = "DOMAIN\user" password="password" in
"Identity Impersonate" section. We tried it and it didn't seem to make
a difference.)
The Problem: it ONLY works from the "Development Box" via the IDE.
If I hit the server (192.168.1.2) from the development box
(192.168.1.3) directly through
Internet Explorer, it will fail with the following error:
"Error [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]
Login failed for user '<machine-name>\ASPNET'"
Adding the ASPNET user account back into SQL Server on the Test Server
"fixes" the problem. However, for security reasons, we are not allowed
to have this account on the production server.
Removing the "Global.asax" file and republishing the web site "fixes"
the problem. But then we have no error handling other than a generic
redirect page (i.e., no ability to log/e-mail the errors).
There are other options for application-level error handling, but this
seemed to be the most straightforward. Can anyone offer any help with
this problem? Thanks.
(P.S. Sorry for the duplication. My old thread had a slightly dif't
subject line and I thought that this described the problem more
accurately and succinctly)
.
- Follow-Ups:
- Prev by Date: Re: Issue with public variables
- Next by Date: Re: How to specify the sort column?
- Previous by thread: Issue with public variables
- Next by thread: Re: If no ASPNET user account, can I use Global.asax for application-level error trapping?
- Index(es):
Relevant Pages
|
Loading
