May 31, 2018 at 11:56 am
I've finally achieved success in importing a DBF file from a legacy app.
Using the FoxPro OleDB driver failed due to our 64-bit SQL instance failing to recognize the 32-bit FoxPro driver.
The DBF file is in a separate folder on the same drive as the data file of the SQL intstance databases.
Instead we went with a Linked Server based on the Office 12.0 Access OLE DB Provider. It's workng fine, interactively.
It will not run as a SQL job. Error is
"Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)."
SQL is 2014 Enterprise SP2.
I've tried changing the job owner, and the failing job step "Run as user", to the SQL Agent Account(s) - first NT SERVICE\SqlServerAgent, then a newly SERVERNAME\AgentAcct (which became obviously the agent startup account), and which was made SysAdmin and given Full Control to the folder containing the DBF.
How do I get the "remote server", i.e. the DBF file, to trust the current security context?
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
May 31, 2018 at 1:48 pm
Mike Hinds - Thursday, May 31, 2018 11:56 AMI've finally achieved success in importing a DBF file from a legacy app.
Using the FoxPro OleDB driver failed due to our 64-bit SQL instance failing to recognize the 32-bit FoxPro driver.
The DBF file is in a separate folder on the same drive as the data file of the SQL intstance databases.Instead we went with a Linked Server based on the Office 12.0 Access OLE DB Provider. It's workng fine, interactively.
It will not run as a SQL job. Error is
"Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)."SQL is 2014 Enterprise SP2.
I've tried changing the job owner, and the failing job step "Run as user", to the SQL Agent Account(s) - first NT SERVICE\SqlServerAgent, then a newly SERVERNAME\AgentAcct (which became obviously the agent startup account), and which was made SysAdmin and given Full Control to the folder containing the DBF.How do I get the "remote server", i.e. the DBF file, to trust the current security context?
What is the security settings for the linked server?
June 1, 2018 at 5:19 am
Sue_H - Thursday, May 31, 2018 1:48 PMMike Hinds - Thursday, May 31, 2018 11:56 AMI've finally achieved success in importing a DBF file from a legacy app.
Using the FoxPro OleDB driver failed due to our 64-bit SQL instance failing to recognize the 32-bit FoxPro driver.
The DBF file is in a separate folder on the same drive as the data file of the SQL intstance databases.Instead we went with a Linked Server based on the Office 12.0 Access OLE DB Provider. It's workng fine, interactively.
It will not run as a SQL job. Error is
"Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)."SQL is 2014 Enterprise SP2.
I've tried changing the job owner, and the failing job step "Run as user", to the SQL Agent Account(s) - first NT SERVICE\SqlServerAgent, then a newly SERVERNAME\AgentAcct (which became obviously the agent startup account), and which was made SysAdmin and given Full Control to the folder containing the DBF.How do I get the "remote server", i.e. the DBF file, to trust the current security context?
What is the security settings for the linked server?
On "Linked Server Properties", Security tab, there is only one mapping, and it is for NT SERVICE\MSSQLSERVER and Impersonate is checked. "Be made using the login's current security context" is selected in the lower half of the pane.
... and now the job has started working. I have no clue what the successful combination actually was.
:ermm:
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
June 1, 2018 at 11:33 am
Mike Hinds - Friday, June 1, 2018 5:19 AMSue_H - Thursday, May 31, 2018 1:48 PMMike Hinds - Thursday, May 31, 2018 11:56 AMI've finally achieved success in importing a DBF file from a legacy app.
Using the FoxPro OleDB driver failed due to our 64-bit SQL instance failing to recognize the 32-bit FoxPro driver.
The DBF file is in a separate folder on the same drive as the data file of the SQL intstance databases.Instead we went with a Linked Server based on the Office 12.0 Access OLE DB Provider. It's workng fine, interactively.
It will not run as a SQL job. Error is
"Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)."SQL is 2014 Enterprise SP2.
I've tried changing the job owner, and the failing job step "Run as user", to the SQL Agent Account(s) - first NT SERVICE\SqlServerAgent, then a newly SERVERNAME\AgentAcct (which became obviously the agent startup account), and which was made SysAdmin and given Full Control to the folder containing the DBF.How do I get the "remote server", i.e. the DBF file, to trust the current security context?
What is the security settings for the linked server?
On "Linked Server Properties", Security tab, there is only one mapping, and it is for NT SERVICE\MSSQLSERVER and Impersonate is checked. "Be made using the login's current security context" is selected in the lower half of the pane.
... and now the job has started working. I have no clue what the successful combination actually was.
:ermm:
Thanks for posting back - I guess that's better than broken. There just seems to have been more of these odd "and now it's working" kind of things. I've experienced a few of them and now I'm starting to wonder if some of it isn't SSMS as different things are broken in different versions. I use a few different versions due to the different issues. It is weird though.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply