2 of 2 people found this helpful
This looks like the user that runs the job has not enough rights to instantiate the OLEDB provider, that would be a problem that has to do with access rights on the machine.
Here is an example of using ProcMon to see what files are accessed by SQL server when running an OLEDB Provider "in-process" :
You need to make sure that the use the job is using has access to the file and can execute it.
To go further is the above does not work
We do have plenty of KB articles on this topic:
And to better understand It would be useful to see:
- your linked server configuration : General + Security
- Your provider options
Let us know how it goes
Thanks for your quick reply. We are able to resolve the issue by restarting SQL server agent.
I'll go through your steps and update it.