Microsoft Sql Server 2008 Error 7399
Contents |
19, 201022 Share 0 0 When setting up linked server to third-party Databases, it is recommended to run the third-party provider in out-of-process mode, because when the provider
Microsoft Sql Server Error 7399 Linked Server
is run in-process (within the same process as SQL Server), then any microsoft sql server error 7399 invalid authorization specification issues with the provider can affect SQL Server process which could also result in crashing SQL server.
sql server error 7399 access denied To how to set a provider to run out-of-process, uncheck "Allow In Process" property of the provider: There are certain permissions that have to be set onMsg 7399 Level 16 State 1 Line 1 Access Denied
MSDAINITIALIZE to be able to initialize the provider out-of-process and run linked server queries successfully locally and remotely.
MSDAINITIALIZE is a COM class that is provided by OLE DB. This class can parse OLE DB connection strings and load/initialize the provider based on property values in the connection string. MSDAINITILIAZE is initiated by users connected to SQL Server.Error 7399 Linked Server Oracle
If windows authentication is used to connect to SQL Server, then the provider is initialized under the logged in user account. If the logged in user is a SQL login, then provider is initialized under SQL Server service account. Based on the type of login used, permissions on MSDAINITIALIZE have to be provided accordingly.
When these permissions are not set for the logged in users, we get Access Denied errors as below: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. Access denied. Msg 7301, Level 16, State 2, Line 1 Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)". Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) An exception has occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The OLEDB Provider "MSDAORA" for linked server(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My sql server startup account Forums Answered by: Problems with OraOLEDB.Oracle SQL Server > SQL
Cannot Initialize The Data Source Object Of Ole Db Provider Oraoledb.oracle For Linked Server 7303
Server Data Access Question 0 Sign in to vote Good day everyone.... I have installed msg 7330, level 16, state 2, line 1 the OraOLEDB.Oracle Provider on 3 different servers, and have made a link server on all three. On two of the machines, I am successful https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ in retrieving data from the Oracle database. But, on the third machine, I receive this error: Server: Msg 7399, Level 16, State 1, Line 1The OLE DB provider "OraOLEDB.Oracle" for linked server "employee_prod" reported an error. The provider did not give any information about the error.Server: Msg 7303, https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a1a8dcbc-027c-4794-b13a-8bd4d7d4d682/problems-with-oraoledboracle?forum=sqldataaccess Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod". On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it. I have also uninstalled/installed serveral times. All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition. Does anyone have any suggestions? Wednesday, June 07, 2006 12:34 PM Reply | Quote Answers 12 Sign in to vote Found the solution.... "Allow inprocess" has to be checked in the provider options. Wednesday, June 07, 2006 12:58 PM Reply | Quote All replies 12 Sign
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/5198381/linking-server-in-sql-server-2008-r2 of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: sql server Sign up Linking Server in SQL Server 2008 R2 up vote 9 down vote favorite Can anyone guide me around to linking a server to another in SQL Server 2008 R2? I am getting the following error when trying to do so in Management Studio. The linked server has been created but failed a connection test. Do you want to keep the linked microsoft sql server server? ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The OLE DB provider "SQLNCLI" for linked server "CDSPM1" reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "CDSPM1". OLE DB provider "SQLNCLI" for linked server "CDSPM1" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399) sql-server sql-server-2008 linked-server share|improve this question edited Feb 7 '13 at 0:55 abatishchev 57.1k56215354 asked Mar 4 '11 at 19:33 Jeff 2285923 3 What's wrong with a screen shot? –Oded♦ Mar 4 '11 at 19:35 Is the login and password valid for the linked server? –jim31415 Mar 4 '11 at 20:23 add a comment| 6 Answers 6 active oldest votes up vote 7 down vote accepted Seems like Authentication problem. Test by creating the linked Server using "Server Type" as "Sql Server". Then go into "Security" and set your user mapping. As a test, create a SQL login on the remote system and specify that on the "Be made using this security context" Be sure that you can PING the "