The server principal '%%' is not able to access the database '%%' under the current security context

• Leeland

  SSCrazy Eights

  Points: 8959

  More actions

  November 8, 2010 at 11:32 am

  #228678

  I have a very odd situation. I have a SQL 2005 standard SP3 server. The server houses several application databases which all interact in some fashion.

  The server was upgraded in June from SQL 2000 and have had a single issue. All of the sudden one of the applications (An Access 97) application starts failing with the stated error listed above.

  It would error for some people in a reproducible fashion...others...sporadic...

  The security is set up something like this for the application to function correctly.

  DB1 ------> DB2 ------> DB3

  ------> DB4

  So users get access via a role to DB1 and DB2

  Cross database ownership chaining was enabled on the server (server wide vs. individual DB setting).

  Users do not have direct access to DB3 and DB4.

  Based on logic of what is being done, the process starts in DB1 then flows over to DB2 to update records...and then based on logic specific calls can go to DB3 or DB4 or both DB3 and DB4.

  Several procedures were 'ALTERED' to include new logic and a new table column that were called by the application.

  SO...of course when these error messages started popping up for end users it immediately was something the database group did or changed...

  Nothing on the SQL server has changed and I am at a loss as to why this is happening.

  The current 'resolution' has been granting public access to DB3 and DB4 which apparently stops the error.

  Can anyone please explain why this would work? The procedures don't have public execute access...

  I thought that the Cross database ownership chaining facilitated this kind of process (where DB1 login calls procedure in DB2 which in-turn calls procedures in DB3 where the login has 0 rights)

  Thanks in advance,

  Lee