Error 15274 Sql Server
Contents |
42000] (Error 15274) ★★★★★★★★★★★★★★★ Deepak BiswalMarch 2, 20108 0 0 0 Problem: Having a SQL Agent Job, which executes a Stored ssrs access to the remote server is denied because the current security context is not trusted. prcedure to connect to a remote SQL server via linked server enable trustworthy database property and extract/manupulate the data. The SP runs successfully in SSMS but get failed, if run through an agent error 15274 sql server 2008 Job. NOTE: A Windows a/c is used here to connect to remote server and the a/c is having dbo permission in both source and remote server databases. Both the
Local Server Login To Remote Server Login Mappings
servers are on same domain. Resolution: Step -1: a. Make sure that the a/c used in linked server/Job having necessary permissions on both source and remote server databases.b. Remove the run as "Login a/c" for the Job step c. Remove the Login a/c, if it definedunder "Local Server Login to Remote Server Login Mappings"to impersonate.d. In Linked Server properties, linked servers cannot be used under impersonation without a mapping for the impersonated login. Choose "Be made using the Login's current security context",if the a/c having permissions on remote server and isused to run the SQL Agent Service else choose "Be made using this security context" and define the Remote Login and password.
Tags job fails Comments (8) Cancel reply Name * Email * Website Chris says: July 29, 2011 at 12:24 pm +1 for the accurate resolution on this one. Many thanks! Reply Ian says: July 26, 2012 at 4:05 pm This was a HUGE HELP!! Thank you!! Worked for me…perfect directions!! Reply m says: March 27, 2013 at 3:45 pm what is 'a/c'? in the phrase 'NOTE: A Windows a/c'? Account credentials? authentication something? Reply mike_plichta@ipsd.org says: September 25, 2013 at 3:11 pm There is a known bug with saved windows credentials accessing a remote server. You have to authenticate with SQL credentails 1. Right click the SQL instance of the remote server in your Management Studio and go to Properties 2. On the security tab, click "SQL Server and Windows Authentication mode 3. Reup Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Administering » Problems querying a linked server from a SQL... 11 access to the remote server is denied because no login-mapping exists posts,Page 1 of 212»» Problems querying a linked server from a SQL Agent job Rate
Sp_addlinkedsrvlogin
Topic Display Mode Topic Options Author Message binary lumberjackbinary lumberjack Posted Thursday, October 2, 2008 10:09 AM Grasshopper Group: General Forum Members
The Server Principal Is Not Able To Access The Database Under The Current Security Context
Last Login: Thursday, May 19, 2011 7:23 AM Points: 16, Visits: 37 First of all, where are the SQL Server 2008 forums?So here's my setup. I created a linked server to a db2 database. I have a user https://blogs.msdn.microsoft.com/deepakbi/2010/03/02/job-fails-on-linked-server-access-to-the-remote-server-is-denied-because-the-current-security-context-is-not-trusted-sqlstate-42000-error-15274/ on the db2 database called cbsdba, so I created the same user on my sql server with the same password so I could use a local login for my linked server connection. It works as expected, as the cbsdba user I can use openquery to hit my db2 database just fine. Then I put my query into an agent job, change the step to be "run as" the cbsdba user, and it fails with the following:Executed http://www.sqlservercentral.com/Forums/Topic579778-146-1.aspx as user: cbsdba. Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274). The step failed.So I'm guessing this has something to do with the context that the agent job is running under. The job step is owned by cbsdba user, but the whole job is owned by sa. So, I changed the whole job to be owned by cbsdba and now I get this:Executed as user: cbsdba. The OLE DB provider "IBMDADB2" for linked server "crmdev" reported an error. Authentication failed. [SQLSTATE 42000] (Error 7399) Cannot initialize the data source object of OLE DB provider "IBMDADB2" for linked server "crmdev". [SQLSTATE 42000] (Error 7303) OLE DB provider "IBMDADB2" for linked server "crmdev" returned message " SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ". [SQLSTATE 01000] (Error 7412). The step failed.Which makes no sense to me, because if anything, making the whole job be owned by cbsdba should help. But now it's acting like the cbsdba user can't authenticate across, but I created the linked server login with "locallogin = 'cbsdba'", so as I understand it the linked server should try to sign in to the DB2 system with my sql server cbsdba user credentials (which match what db2 has). I thought I understood this because it works from Manag
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen