J
jacques.steward
I have an application that kicks off a long process on the database
server with a separate thread and then forwards the user to another
page which monitors the progress of this process by reading a table
that is being updated by the long process. On my development machine
it works fine but when I try to deploy the app to a server the long
process is blocked from database access. Apparently when the new
thread is created it either does not get or loses its credentials. On
my dev machine it is not a problem because it simply reverts back to my
credentials but on the server it reverts back to the default IIS user.
How can I work around this?
server with a separate thread and then forwards the user to another
page which monitors the progress of this process by reading a table
that is being updated by the long process. On my development machine
it works fine but when I try to deploy the app to a server the long
process is blocked from database access. Apparently when the new
thread is created it either does not get or loses its credentials. On
my dev machine it is not a problem because it simply reverts back to my
credentials but on the server it reverts back to the default IIS user.
How can I work around this?