[SqlException (0x80131904): User does not have permission to perform this action.]

Folks,

This is driving me nuts. I posted the other day on a related issue, which I belive turned out to be a file permission. I am trying to test my asp.net site under IIS before deploying it. I am now getting the above message which breaks on the opening page on opening a connection to the sql server database. I have permissions set on the database for MachineName\ASPNET and NT AUTHORITY\NETWORK SERVICE as Ken Tucker suggested. Still getting the message. This certainly looks like a sqlserver permission issue but I am at a loss as to how to grant IIS or the specific web app permission to access the database.

Any assistance is truely appreciated. I have spent way to many hours on this. If you don't have the answer but can suggest a resource where I can research it that would help also.

Thanks

What permissions have you set for the ASPNET user?

bullpit

|||ASPNET user has connect permission.|||

I asked because I had a similar situation and what I did was to go to SQL Server Enterprise Manager, navigate down to the database I was using, and then to its "users" tab, and for the ASPNET user, I right clicked and set the all the permissions to Insert, Update, Delete, Select and Execute. I dont know if you already done this or not. If not, you can give this a try.

Good luck,

bullpit

|||

Also, if you know your application is not going to do any inserts or updates to the database then I would suggest you try with minimal permissions (probably only Select). This will make your database less vulnerable.

good luck...

bullpit

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name on Linked Server

Hi Folks,
I'm having a strange situation here between 2 Linked MS SQL 2K servers.
One of the servers died recently and I rebuilt it.
All seems to be working fine, except that when I create views that access tables on the other (linked) server, I can not modify any data, because I get the [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name server.database.dbo.TableName error.
The View does work fine otherwise, ie displays the data in it, I just can't modify.
The Linked Servers are done with the sa user between these 2 servers.

Any ideas what could be causing this error?
Thanks!-- bump --
no one ideas on this?|||I'm also having problems with this - mine is in relation to a labeler printer, it is present in my ODBC and the test is successful. However, when I go to print I get the following error: [microsoft][ODBC SQL Server Driver][SQL SERVER] Invalid object name 'table name' ODBC -- call failed

I can't seem to see what the problem is as my project server works from this client.

[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied

Hi Folks,

Lets get this out of the way first - I KNOW NOTHING ABOUT SQL SERVER, MSDE or MDAC

Sorry I don't mean to shout but I really don't know anything at all so please make your answers as simple as possible.

I have an application (Webmarshall) that has a SQL database from which certain reports are run. Whenever I try to run the reports it asks me for database details.

According to the application it is using LANCELOT\WEBMARSHALL\Webmarshall as the database

As this is all happening on one server, I presume it is local and not remote.

When I am presented with the dialogue box for the reporting module it asks for a server and a database, I have tried the following :

Server: local Auth: Windows

Server: local Auth: SQL

Server lancelot (both authorisation methods)

Server: lancelot\webmarshall (both authorisation methods)

Server: \\lancelot\webmarshall (both authorisation methods)

Each time, I get the message

[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied

and I can't select a database.

Can someone help me please...its a long time since I went fishing in the dark (with no net) but thats how I feel right now!!!!

Thanks

In the SQL Server menu options on your Start menu, do you have Enterprise Manager? (you may not depending on which version of SQL Server you have and which installation options were selected, but if you do things will be simpler)

When you try to connect with SQL Auth, are you using a user name and password that are known to be correct? Windows Auth may not work simply because your Windows user may not have permission to connect.

|||

Hi Guys,

Thanks for the response, in the end I was so confused by it all that I got a (SQL experienced and very trusted) colleague to remote onto my server.

It turns out that it was MSDE, and that for some reason the connection details had all been lost during the upgrade process. We eventually found the user buried deep in the properties of the application, changed the password and now it all works OK

Perhaps I need to start learning more about SQL, and stop playing with exchange all day!!!!!!

Thanks again