Login issue in Mgmt Console

  • I Created one user and i assingned that user to one database, My DB Server have some more DB also, if i trying to login in SQL Server 2008 Mgmt studio.

    The following Exception is throwing when i expand the database for every database.

    The server principal "sUser" is not able to access the database "OtherDB" under the current security context. (.Net SqlClient Data Provider)

    Note :It is populating the database when added the user to all other database by ddl deny roles.

    Expected behaviour:

    If i a user is created and assigned to some specific Database,When we login in Mgmt studio, it should display only the databases which is assigned to that user.

    Please suggest howe to achieve the above Behaviour.

  • Check to see that the user has 'connect' rights to the server and at least 'public' on the database in question.

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • User (suser) having connect permission to the DB and public n db owner of database(db1)

    Could you please tell me i have 10 databases on the server db1.....db10

    i have 1 user db1user user.

    i want db1 user should access only DB1. i have assigned the user as dbowner.... to my db1 database.

    After login to the mgmt studio it is logging into dbserver, when i try to expand the Database from server Explorer,it is throwing the above exception.

    but i can connect it from my application,but the problem is i am not able to open the database from management studio.

    if i assign the user to all db with deny option and public .. to my db1 database then i can able to wrok in the management studio.

  • Hey there,

    Is the user sUser a SQL account or AD account and if so is it a member of any groups which could be registered with SQL and conflicting?

    Regrading your app, can you be sure that the account being used to connect to SQL IS the sUser account? For example if you are connceting with local authentication (AD), this does not mean that there is not some underlying service (maybe on an app server) which isnt connecting to SQL with a different account.

    If in doubt try with a completely new account (either AD or SQL) and then set up basic rights and work backward from there. 😎

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • sUser is a SQL USer

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply