K
Ken
When I attempt to use any of the Membership class functions that access the
db, it is the mydomain/processidentity that attemps to log in to sql server,
and this fails
So it seems that the problem is the Membership class functions run under the
processidentity id, not the impersonated user id. Is there a way around this
(besides sql server granting login rights to mydomain/processidentity)?
db, it is the mydomain/processidentity that attemps to log in to sql server,
and this fails
So it seems that the problem is the Membership class functions run under the
processidentity id, not the impersonated user id. Is there a way around this
(besides sql server granting login rights to mydomain/processidentity)?