InstantForum.NET v4.1.4SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 22 Mar 2010 06:44:39 GMT20http://www.sqlservercentral.com/Forums/Topic813684-145-1.aspxthe issue is sorted. On one data base trusworty was set to on and on another data base it was set automatically to off when data base was restored from live. so when user was impersonated, the error came. this is very strange.We altered the data base and set trustworty on.cheersSiddarthFri, 06 Nov 2009 04:15:52 GMTRookee DBAhttp://www.sqlservercentral.com/Forums/Topic813684-145-1.aspxwe use "some-sa" account for logging on to db server in connection string in asp.net web application.cheersWed, 04 Nov 2009 10:57:00 GMTRookee DBAhttp://www.sqlservercentral.com/Forums/Topic813684-145-1.aspxAm I reading your post correctly? You are using the sa account to access your database from a web server?Wed, 04 Nov 2009 10:30:54 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic813684-145-1.aspxIn proc, current loggin is impersonated to "somedb-admin" to access objects in other db. So when the procs are called from asp.net, one proc tries to access objects from another data base by impersonation from "sa" to "somedb-admin" and we get this error. The server principal "somedb-admin" is not able to access the database "CAA" under the current security context.Recently db was restored from live to test and data base ids were also corrected. we have also executed EXEC sp_change_users_login 'Report'; to know orphan users, but nothing was returned.cheersSiddarthWed, 04 Nov 2009 09:39:29 GMTRookee DBA