SQL 6.5 - Execute permission denied error
-
Hello All!
I had an ASP based web-app connecting to a SQL 6.5 DB. The application was connecting as "sa". I went and changed it to a proper server login id. Yes, I made doubly sure that the login had the right permissions on the db in question. This new login "webaccess" is a member of public and has the "dbo" role. Now, I get errors from the ASP page which says
[Microsoft][ODBC SQL Server Driver][SQL Server]EXECUTE permission denied on
object SheetDates, database AusProjects, owner dbo
any help will be greatly appreciated
regards
Uday
-
I would double check the permissions on SheetDates. Once you get your problem resolved, I'd recommend that you put the login in a separate role and remove it from dbo. DBO is just a shade better than SA, still way too much access for your average app/user.
Andy
-
thanks Andy,
Like I mentioned already, I double checked perms for the server login "webaccess". Just FYI, this server login is used by several other web-based apps currently connecting to different dbs on the same 6.5 server. None of the other apps had a problem. This definitely has to be a bug of some sort, but still there has to be a solution.
more thoughts
regards
Uday
-
Can you connect from ISQL/W using this login and execute the stored procedure?
You might also run SQLTrace and see the exact call. Perhaps there is something you are not noticing from the ASP page.
Steve Jones
-
-
Hi Steve!
Yes, I tried connecting via ISQL/W using this login and it does work! This is pointing me straight to the ODBC driver that the ASP app uses....more thoughts?
regds
uday
quote:
Can you connect from ISQL/W using this login and execute the stored procedure?You might also run SQLTrace and see the exact call. Perhaps there is something you are not noticing from the ASP page.
Steve Jones
-
Strange. The isql/w call is the same as the ADO call?
Can you script an ASP page and enter the exact same call in both the page and isql/w and see what happens?
Can you run SQLTrace on this login and verify the calls are the same?
Sorry, I cam reaching a bit here. If it works in isql/w, then it should work through an ADO call.
Steve Jones
-
Double check the connect string and look to see how it's showing up in sp_who. If you get the string wrong, it can change back to a trusted connection.
Andy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply