Try without integrated security and see if it still messes up. If so, it is
likely to be a security issue. The best method to go from there is to do two
things.
1. On SQL Server, turn on profiler and see the user that is hitting the
database when it fails.
2. In ASP.NET trace out (or write out if you do not use trace) the user it
thinks it is running under
If you find that the user is IUSR, you have your problem child identified.
Once you figure this out, you have a better means to determine where to go
next.
With apps that use forms auth, you can set the cookie name and allow users
hitting the same server (same domain?) to log in once and hit all apps. This
is more FYI, as it will not solve your problem directly.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Trapulo" <no**********@qui.it> wrote in message
news:ev**************@TK2MSFTNGP10.phx.gbl...
I've two copy af the same asp.net application. The application enter on
sql server, working with two separate databases (on the same sql server
instance, of course). The connection is made with integrated security, and
the server is a domain controller.
If I start only the first application (call the web site), all right.
If I start only the second application, all right.
If I start an application, and then call a page from the second, my second
application cannot enter the database. If I kill aspnet process, the
recall the same page, this second application works fine, but I have the previuos
error if now I try to enter the first application!
This is a very strange problem!
What can I do?
