G
Guest
Hello, I have been taking a swing at learning how I can use Impersonation via
code and I am getting back an error code of 1314. By searching the internet,
I have come to believe that this error means the account it invalid.
If I use my ID and password, the code works fine, so I am guessing it is not
the code.
I requested this "special" account from the network folks and have been
using it for submitting batch Console applications from my server. The
account works fine for these type of operations. I know the account has
special restrictions, such as I am not able to actually logon on to the
account from the server location. I get an error message indicating the ID
is restricted from active logons.
Is it possible/probable for the "special" account that I have set up to be
good enough to schedule batch .Net applications to run on the server, but not
appropriate for running ASP.Net Impersonation? Why would it work for batch
jobs but not ASP.Net Impersonation?
code and I am getting back an error code of 1314. By searching the internet,
I have come to believe that this error means the account it invalid.
If I use my ID and password, the code works fine, so I am guessing it is not
the code.
I requested this "special" account from the network folks and have been
using it for submitting batch Console applications from my server. The
account works fine for these type of operations. I know the account has
special restrictions, such as I am not able to actually logon on to the
account from the server location. I get an error message indicating the ID
is restricted from active logons.
Is it possible/probable for the "special" account that I have set up to be
good enough to schedule batch .Net applications to run on the server, but not
appropriate for running ASP.Net Impersonation? Why would it work for batch
jobs but not ASP.Net Impersonation?