db execute permission denied..

[Not Me]

Hi there,

I've just switched over an app from one iis server to another.. the sql
server db remains in the same place. Windows authentication was, and
is being used.. with the IIS server running under the same account
(same domain etc.) - I've probably got some of that wrong but the gist
is it all should be the same!

However I'm getting permission denied errors.. any ideas?

Looking at Request.LogonUserIdentity.Name - I'm given the exact
username I want to authorise the db against... does this mean that the
IIS server is definately set up correctly?

can there be any other issues that might affect this?

cheers,
Chris

 

[Not Me]

I've just switched over an app from one iis server to another.. the sql
server db remains in the same place. Windows authentication was, and
is being used.. with the IIS server running under the same account
(same domain etc.) - I've probably got some of that wrong but the gist
is it all should be the same!

However I'm getting permission denied errors.. any ideas?

Looking at Request.LogonUserIdentity.Name - I'm given the exact
username I want to authorise the db against... does this mean that the
IIS server is definately set up correctly?

I've set up a simple page which displays
request.logonuseridentity.name, and also the result of a simple 'select
suser_sname' query. The results return different logins - why is this
the case? the login returned from the database seems a bit arbitrary...
(not random, but I've no idea why it picked that account.)

I appreciate any help you can give,
Chris

 

[Not Me]

I've just switched over an app from one iis server to another.. the sql
server db remains in the same place. Windows authentication was, and
is being used.. with the IIS server running under the same account
(same domain etc.) - I've probably got some of that wrong but the gist
is it all should be the same!

However I'm getting permission denied errors.. any ideas?

Looking at Request.LogonUserIdentity.Name - I'm given the exact
username I want to authorise the db against... does this mean that the
IIS server is definately set up correctly?

OK seems fixed now.. I needed to add identity impersonate=true in the
web.config.. not sure why this wasn't required on the old server, or
where the random logon appeared from/why I was allowed to use their
credentials.... but it seems ok now!