Database Error 15406 At Opc
Contents |
on SQL ServerWhere is this place located?All Places SAP on SQL Server 1 Reply Latest reply: May 31, 2011 9:13 AM by Clas Hortien Database error 4860 / 911 at OPC Basti D. May 31, 2011 8:42 AM Currently Being Moderated cannot open database requested by the login. the login failed. login failed for user Hi experts,we get the following error messages each monday morning:Database error 4860 at OPC> cannot open database requested by the login c# [Microsoft][SQL Server Native Client 10.0][SQL Server]Cann> bulk load. The file "C:\Program Files\Microsoft SQL> Server\MSSQL10.MSSQLSERVER\MSSQL\CCMS_CHECK_DB_HIST_2011.txt> does not exist.Database error 4860Database error 911
Cannot Open Database Requested By The Login. The Login Failed. Clientconnectionid
at OPC> [Microsoft][SQL Server Native Client 10.0][SQL> Server]Database 'mssqlsystemresource' does not exist. Make> sure that the name is entered correctly.Database error 911We found this error messages on two independent ECC 6.0 systems which both
Cannot Open Database Requested By The Login The Login Failed Windows Authentication
run MS SQL Server since activating early watch reports. At this time data for the early watch report is collected, maybe this is the trigger for this error. But I think that the real cause for this error is located somewhere in the database configuration.By the way there is no shortdump or any additional information in the EWA report.Any ideas or hints? Thank you in advance. 7222Views Re: Database cannot open database requested by the login visual studio error 4860 / 911 at OPC Clas Hortien May 31, 2011 9:13 AM (in response to Basti D.) Currently Being Moderated Hi,i assume, that the early watch report wants to read the file CCMS_CHECK_DB_HIST_2011.txt. This is the log of a database check job, which you can schedule in db13. If you do not have this job scheduled, the file will not exist. You can ignore the error, but if you want to fix it, just schedule the DB check job (at least one time) or just create a textfile at this path with this name. Btw, you should run a DB check anyway from time to time to ensure the physical consistency of your database. Recommened is a run every week.The mssqlsystemresource database is a hidden system database, which cannot be accessed directly. I assume that the report scan through all databases (select * from sys.databases) and tries to get more information about this databases then. The error is not severe and can be ignored. If you want to have it fixed, open an OSS message for the EWA tool.Best regards Clas Alert Moderator Like (0) Actions Login to follow, like, comment, share and bookmark content. Login Register Follow SCNJive Software Version: 5.0.6.2 , revision: 201308121150.54f5b14.release_5_0_6_2
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company
Cannot Open Database Requested By The Login Entity Framework
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs java.sql.sqlexception cannot open database requested by the login. the login failed Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, sql server error 4060 cannot open database just like you, helping each other. Join them; it only takes a minute: Sign up SQL SERVER changing security contex inside of stored procedure up vote 2 down vote favorite Inside of some stored procedure I have https://scn.sap.com/thread/1965053 to change security context to more powerful login. I tried something like this: USE ProjectsDB EXECUTE AS login = 'sa' --SOME OPERATIONS REVERT; but I get the following error message: Msg 15406, Level 16, State 1, Line 3 Cannot execute as the server principal because the principal "sa" does not exist, this type of principal cannot be impersonated, or you do not have permission. The 'sa' login exist with all needed permissions. What may http://stackoverflow.com/questions/7400707/sql-server-changing-security-contex-inside-of-stored-procedure be the problem? Ilan. sql-server sql-server-2005 sql-server-2008 stored-procedures share|improve this question asked Sep 13 '11 at 10:54 Ilan 3542617 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted You need to have the "IMPERSONATE" permission to do this. Check out the GRANT IMPERSONATE statement. Besides that I believe the best way to do this (instead of bumping up the permission level to SA) in sql server is: Create a certificate Sign the stored procedure with the certificate Remove the private key from the certificate Create a user from the certificate Grant the required rights to the user Optional if you need "Server wide rights": Export the certificate to disk Import the certificate in the master database Create a login from the certificate Grant the appropriate rights to the login More optional if you need "cross database rights" import the certificate in the database where you want to grant permissions create a user from the certificate. grant the correct rights to the user SQL Server will chain all the users/login permissions together through the certificates and when you execute the signed procedure it will use the permissions of the users linked to the certificate. share|improve this answer edited Sep 13 '11 at 12:07 answered Sep 13 '11 at 11:57 Filip De Vos 7,8402250 @
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Grant https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ae1c199e-9408-493d-aea4-a5646adc051f/grant-access-to-a-procedure-executing-as-sa-login?forum=sqlsecurity access to a procedure (executing as sa login) SQL Server > SQL Server Security Question 0 Sign in to vote Hi, I am a db owner on the database, and when i try to execute the procedure, i get the below error.When i checked in to procedure i found the command (Execute cannot open as login = 'sa' and revert)How can i execute the procedure with out any below issues.Being a db owner can i impersonate sa account and what will be the command for this. Msg 15406, Level 16, State 1, Procedure SP_GetLogical_data, Line 91 Cannot execute as the server principal because the principal "sa" cannot open database does not exist, this type of principal cannot be impersonated, or you do not have permission. ThanksNaga Monday, August 10, 2009 3:36 PM Reply | Quote Answers 0 Sign in to vote Hi, Based on the error message, it indicates that the SQL Server login that you wish to impersonate doesn’t grant you access to do the impersonation. To grant someone rights to impersonate the SQL Server login, you could use the GRANT statement. You also need to specify the SQL Server login to which the permission is being granted in the GRANT statement. The following example grants IMPERSONATE permission on the SQL Server login WanidaBenshoof to a SQL Server login created from the Windows user AdvWorks\YoonM.USE master;GRANT IMPERSONATE ON LOGIN::WanidaBenshoof to [AdvWorks\YoonM];GOIf there are any more questions, please let me know.Thanks.***Xiao Min Tan***Microsoft Online Community*** Marked as answer by Xiao-Min Tan – MSFTModerator Tuesday, August 18, 2009 9:59 AM Unmarked as answer by