Microsoft Sql Server Error 7399 Msdasql
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MSDASQL Linked Server error SQL Server > SQL Server Express Question 0 Sign in to vote Hi microsoft sql server error 7399 linked server all, I have created a System DSN to a MYOB database file. microsoft sql server error 7399 invalid authorization specification I have SQL 2000 and 2005 Express editions installed on the same machine. I am logged in to PC as Local sql server error 7399 access denied Admin. I am also logged into 2005 Express using 'sa' to avoid any security problems. Creating a New Linked Server using SQL 2000 works fine using the System DSN I created, however,
Msg 7399 Level 16 State 1 Line 1 Access Denied
If I use exactly the same settings (Microsoft OLE DB Provider for ODBC) I get an error message. "The OLE Provider "MSDASQL" for linked server "sname" reported an error. The provider did not give an information about the error." "Cannot initilize the data source object of OLE DB Provider "MSDASQL" for Linked Server "name". (Microsoft SQL Server, Error: 7399)" I have installed SL 2005 Express SP2. error 7399 linked server oracle As another test I created a data source using the same System DSN in Excel. It worked fine and queries the MYOB database file. Any ideas to assist me?? Thanks. Alan Monday, January 07, 2008 9:56 AM Reply | Quote Answers 0 Sign in to vote HI Refer the below link, this may help you. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=614402&SiteID=1 Monday, January 07, 2008 11:40 AM Reply | Quote Moderator All replies 0 Sign in to vote HI Refer the below link, this may help you. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=614402&SiteID=1 Monday, January 07, 2008 11:40 AM Reply | Quote Moderator 0 Sign in to vote Thank you Vidhya. I re-installed SQL 2005 Express SP2 and created another Instance (just in case). Create a New Linked Server and no errors. Thanks again. Alan Monday, January 07, 2008 9:30 PM Reply | Quote 0 Sign in to vote Hi Al_civilSorry to bother you with this and I know it has been a while but I am facing trouble trying to create a linked server to a MYOB database from SQL Server 2005. How did you do it? What are the correct values for the parameters?Thanks in adavance, any help would be appreciat
19, 201022 Share 0 0 When setting up linked server to third-party Databases, it is recommended to cannot initialize the data source object of ole db provider "sqlncli11" for linked server run the third-party provider in out-of-process mode, because when the provider
Sql Server Startup Account
is run in-process (within the same process as SQL Server), then any issues with the
Cannot Obtain The Required Interface Iid_idbschemarowset
provider can affect SQL Server process which could also result in crashing SQL server.
To how to set a provider to run out-of-process, uncheck https://social.msdn.microsoft.com/Forums/sqlserver/en-US/6cb98544-5fec-4885-9d42-13009aa47332/msdasql-linked-server-error?forum=sqlexpress "Allow In Process" property of the provider: There are certain permissions that have to be set on 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. https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ 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. 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") fDatabase (CMDB)LoginCancel changesDiscard all changes?NoYesClose MessagesTroubleshooting Linked Server18973 viewsNumber:KB0538992 Troubleshooting linked server ProblemThis article guides you through the process of troubleshooting linked server issues. It provides steps to help eliminate common causes for your problems by verifying that the https://hi.service-now.com/kb_view.do?sysparm_article=KB0538992 configuration of your networking is correct. SymptomsSymptoms https://hi.service-now.com/kb_view.do?sysparm_article=KB0546265 may include: Some properties are not editable during configuration. There are error messages received when running queries. The queries against the linked server timeout. The user cannot create a linked server. The sql server user cannot query the linked server. The connector timed out when trying to run a scheduled job. ResolutionDetermine whether any of the troubleshooting steps below are true for the environment. The steps provide links to articles that help eliminate possible causes sql server error and take corrective action as necessary. Verify that MS SQL Server Management Studio is running as an administrator. For more information, see this Microsoft article. When testing the connection, it works properly, but when running queries, this error message is received:Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSDASQL" for linked server " SERVICENOW" reported an error. Access denied.Msg 7350, Level 16, State 2, Line 1Cannot get the column information from OLE DB provider "MSDASQL" for linked server "SERVICENOW" Microsoft Data Access Components (MDAC) may not be working properly. For more information, see thisMicrosoft article. When running queries against the linked server, this error message is received:OLE DB provider "MSDASQL" for linked server "SERVICENOW" returned message "[Dat
Database (CMDB)LoginCancel changesDiscard all changes?NoYesClose MessagesResolving Microsoft SQL Linked Server Access Errors with ODBC Driver3713 viewsNumber:KB0546265 Resolving Linked Server AccessErrors with ODBC Driver Problem When using the ODBC Driver with Microsoft SQL Linked Server, theODBC Driver is unable to access the application logs or file cache. SymptomsWhen using the ODBC Driver with a Microsoft SQL Linked Server, one of these errors appears: Cannot obtain the required interface("IID_IDBSchemaRowset") from OLE DB provider "MSDASQL" for linked server"SERVICENOW". (Microsoft SQL Server, Error: 7301) Cannot obtain the required interface(“IID_IDBCreateCommand") from OLEDBprovider "MSDASQL" for linked server"SERVICENOW". (Microsoft SQL Server, Error: 7301) Cannot create an instance of OLE DB provider "MSDASQL" for linked server "SERVICENOW". (Microsoft SQL Server, Error: 7302) Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "SERVICENOW". OLE DB provider "MSDASQL" for linked server "SERVICENOW" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK Client]Failed to create the Core Service component.". (Microsoft SQL Server, Error: 7303) The OLE DB provider "IBMDADB2.DB2COPY1" for linked server "