If you have been denied access to msg 7399 on your computer, this guide will help you fix it.
| |
Search …
Last modified: Thursday 26 May 2011 Product: OLE DB Provider Benefit 
Title: Receive error: message 7399 “Access Denied” usingLearning a linked Microsoft SQL Server with advantage Description of the problem: When executing a query on Linked Advantage Server from MS SQL Server, an error similar to the one below is returned. Solution: Try switching to the Advantage OLE DB provider in the linked server configuration, right click, select Properties and set Allow Process. In Management Studio Express, go to Server Objects -> Linked Servers -> Providers -> OLE DB Provider Benefit (right click -> Properties or double click). Define “Allow Process” Was this helpful? |
Search …
Last modified:
Thursday May 26, 2011
Product:
OLE DB Provider Benefit
Title:
Retrieve Error: 7399 Access Denied message using linked Microsoft SQL Server with preference
Problem Description:
When executing a query on Linked Advantage from MS SQL Server, an error similar to the one below is returned.
======
Msg 7399, Level 16, State 1, Line 1
OLE DB provider “Advantage.OLEDB” for linked server “ADVANTAGE” reported an error. Access is denied.
Msg 7350, Level 16, State 2, Line 1
Unable to get column information for linkThe linked server “ADVANTAGE” from the OLE DB provider “Advantage.OLEDB”.
======
Solution:
Try switching to the Advantage OLE DB provider in the linked server configuration, right click, select Properties and set Allow Process.
In Management Studio Express, go to Server Objects -> Linked Servers -> Providers -> OLE DB Provider Benefit (right click -> Properties or double click).
Define “Allow Process”
Reason
Microsoft® SQL Server Connection Server may not have the necessary rights to use the OLE DB Provider interface.
SOLUTION / Rework
As mentioned earlier, I checked the service account and it was installed as NT Service MSSQLSERVER.
I changed this to Local System as shown below and restarted the service.
And then everything worked.
Did you notice this error and suggest a different solution? If so, please post in the comment box below to help others.
Link: Pinal Dave (https://blog.sqlauthority.com)
