- Remove From My Forums
-
Question
-
Good morning,
I created a linked server to
access sql server 2008.At first everything worked properly,
now returns the error 7303.I have already shared the folder with all
of the database permits users full control
of sql server users , users of
the system, etc..Does anyone know how can you fix?
I found a solution on the Internet,
says to create an Admin user
on the machine, and as a path
to a temporary folder on your
hard disk different from the profile, by entering
the required permissions to SQL Server, but not
seems to work after a while let us start, however,
to return the error 7303.i found if i drop linked server , restart pc and reacreate it , it work , but when i restard pc all return error 7303.
SQL Version : 10.0.2573
Thanking you in advance,
GR
Answers
-
Hi ,
I fix the issue by myself.
I Change the SQL Server’s service Log On to «Local System account» AND
I Provide full access to Windows 7 folder C:WindowsServiceProfilesLocalServiceAppDataLocalTemp
to USERS who starts SQL SERVER ANd SQL AGENT (in my case localservice and netowrk service) and to SQLSERVER$… user type
In SQL Server under Provider Microsoft.Jet.OLEDB.4.0 i Disabled «Allow inprocess «
Thank’s 4 all ,
Giuseppe R.
Update : Before do all I update SQL Server to SP3
-
Marked as answer by
Monday, November 7, 2011 2:37 PM
-
Edited by
Giuseppe Regina — BG
Monday, November 7, 2011 3:04 PM
missing a part
-
Marked as answer by
- Remove From My Forums
-
Question
-
I am getting below error when i tried to create linked server to MySQL. Tried all the methods provided in the forums but no result.
Can anyone please provide the solution for this. IT would be great help for me.
cannot initialize the data source object of OLE DB provider «MSDASQL» fro linked server «MYSQL»,
OLE DB provider «MSDASQL» for linked server «MYSQL» returned message «[MYSQL][ODBC 5.3(a) Driver] Unknown MySQL server host ‘xxxx'(34)’. (Microsoft SQL Server Error : 7303)Thanks
Naga
Answers
-
What port is running in myssql ?
mysql> SHOW GLOBAL VARIABLES LIKE ‘PORT’;
The SQL Server linked server was created by using following statement :
EXEC master.dbo.sp_addlinkedserver @server = N'TESTMYSQL1', @srvproduct=N'MYSQL', @provider= N'MSDASQL', @provstr=N'DRIVER={DataDirect 7.0 MySQL Wire Protocol}; Hostname=10.xx.xx.xx; PORT=5807; DATABASE=test; LogonID=xxxx; PASSWORD=xxxx;'the MySQL database is listening on Port
3307 what over you should change in link serverResolution Add the port number MySQL is listening on to the connection string like :
@provstr=N’DRIVER={DataDirect 7.0 MySQL Wire Protocol}; Hostname=10.30.21.94; PORT=3307; DATABASE=test; LogonID=test01; PASSWORD=test01;’
Check and confirm.
Refereence link is following
https://knowledgebase.progress.com/articles/Article/Error-occurs-connecting-to-MySQL-using-the-Connect-for-ODBC-MySQL-driver-in-SQL-Server-Linked-Server
https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx
-
Proposed as answer by
Tuesday, January 16, 2018 5:30 PM
-
Marked as answer by
manisubbu
Monday, January 29, 2018 7:07 PM
-
Proposed as answer by
-
Glad to hear that solution work for you.Please mark answer so it helpful to others.
https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx
-
Marked as answer by
manisubbu
Monday, January 29, 2018 7:06 PM
-
Marked as answer by
-
Hi AV111,
It worked for me. successfully created linked server and able to access the MySQL server.
Thanks a lot !!!
Thanks
Naga
Hi Naga,
Since you have solved your issue, please help to mark AV111’s reply as answer, I think his solution has solved your problem. Further more, it is also beneficial to other community members who come across same problems.
Best Regards,
Will
MSDN Community Support
Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
MSDN Support, feel free to contact MSDNFSF@microsoft.com.-
Marked as answer by
manisubbu
Monday, January 29, 2018 7:07 PM
-
Marked as answer by
I am going around in crop circles, trying to set up a linked server (from SQL Server 2016 to MySQL).
Here is the basic procedure that I used: Create a Linked Server to MySQL from SQL Server. Upon clicking OK to create the new linked server, I received the following SSMS 2016 spasm, Error #7303:
The linked server has been created but failed a connection test. Do you want to keep the linked server?
Additional information:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MYSQL".
OLE DB provider "MSDASQL" for linked server "MYSQL" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)

I tried variations that included a Provider String and Catalog (same error):

I have tried the latest MySQL ODBC ANSI/Unicode drivers (5.03.07.00), set up via System DSNs in both the 32- and 64-bit versions of the ODBC Data Source Administrator.
Now, I suspect that something screwy is going on with MS SQL Server and/or its OLE-DB Provider (MSDASQL), because:
-
All tests of the System DSNs within the ODBC Data Source
Administrator are successful. -
Crippled Access 2016 is able to link (via the aforementioned Unicode System
DSN) to MySQL just fine, with minimal effort, listing all databases
and tables.
What is the magic that SQL Server 2016 needs to make the linked-server dialog not result in the above error?
- Remove From My Forums
-
Question
-
I am having difficulty creating a linked server to and Access 2003 database on my SQL 2005 server.
Whenever I create a linked server through the either the “New Linked Server” tool in the SQL Management Studio or using the sp_addlinkedserver method, receive and error indicating “Cannot initialize the data source object of the OLE
DB provider…(Microsoft SQL Server Error: 7303)”.
Although my ultimate goal is to link to a secure Access 2003 database file, the current MDB file I am trying to link to is “unsecured”.
I have already verified that the SQL Service account has read and write access to the folder containing the MDB file as well as the temp directories on the SQL server (suggestions from other forums).
Is there any SQL Server configuration that I need to modify in order to use the Jet 4.0 linked server provider (Microsoft.Jet.OLEDB.4.0)?
Answers
-
For Microsoft.ACE.OLEDB.12.0 I managed to solve the problem by checking:
— Nested queries
— Allow inprocessin Microsoft.ACE.OLEDB.12.0 -> Properties.
-
Marked as answer by
Tuesday, November 30, 2010 4:37 PM
-
Marked as answer by
- Remove From My Forums
-
Question
-
I am having difficulty creating a linked server to and Access 2003 database on my SQL 2005 server.
Whenever I create a linked server through the either the “New Linked Server” tool in the SQL Management Studio or using the sp_addlinkedserver method, receive and error indicating “Cannot initialize the data source object of the OLE
DB provider…(Microsoft SQL Server Error: 7303)”.
Although my ultimate goal is to link to a secure Access 2003 database file, the current MDB file I am trying to link to is “unsecured”.
I have already verified that the SQL Service account has read and write access to the folder containing the MDB file as well as the temp directories on the SQL server (suggestions from other forums).
Is there any SQL Server configuration that I need to modify in order to use the Jet 4.0 linked server provider (Microsoft.Jet.OLEDB.4.0)?
Answers
-
For Microsoft.ACE.OLEDB.12.0 I managed to solve the problem by checking:
— Nested queries
— Allow inprocessin Microsoft.ACE.OLEDB.12.0 -> Properties.
-
Marked as answer by
Tuesday, November 30, 2010 4:37 PM
-
Marked as answer by
Troubleshooting SQL Server
Troubleshooting
Error 7303
Severity Level 16
Message Text
Could not initialize data source object of OLE DB provider '%ls'. %ls
Explanation
This error message indicates that the OLE DB data source object could not be initialized.
Action
This error message can occur because of one of these problems.
| Problem | Resolution |
|---|---|
| One of the initialization parameters specified in sp_addlinkedserver (data_source, location, provider_string, or catalog) is incorrect for this provider. | Verify that these parameters defined for the linked server, specified by executing sp_addlinkedserver, are correct for the given provider. Check the provider’s documentation for the appropriate values for these parameters. |
| Login and password sent to the provider is invalid. | Verify that there is a valid login and password configured for the linked server and the current SQL Server login through sp_addlinkedsrvlogin. |
See Also
Distributed Queries
Errors 7000 — 7999
sp_addlinkedserver
sp_addlinkedsrvlogin
Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41
Cannot initialize the data source object of OLE DB provider «Microsoft.Jet.OLEDB.4.0» for linked server «TestLinkServer».
OLE DB provider «Microsoft.Jet.OLEDB.4.0» for linked server « TestLinkServer» returned message «Cannot open database ». It may not be a database that your application recognizes, or the file may be corrupt.».
After reading my linked server’s article in SQL Server 2005 at
http://www.sqlhub.com/2009/03/linked-server-in-sql-server-2005-from.html
http://www.sqlhub.com/2009/03/linked-server-is-not-configured-for.html
One of my subordinate wanted to use it in one of our small application. He started using the same code I gave in one of my above article about Linked Server but he was facing above described error. He tried everything and every possible solution from internet but didn’t find his luck. Finally he told me to look at the error and try to solve it. At the very first glance I found problem with his OLE DB adapter. He was using the MDB file which has been developed in ACCESS 97 but there was ACCESS 2007 in our SQL’s development server. As MDB was old, he was using “Microsoft.Jet.OLEDB.4.0” but he should use » Microsoft.ACE.OLEDB.12.0” as our development server has ACCESS 2007 and it doesn’t understand old provider.
Reference: Ritesh Shah
http://www.sqlhub.com
Note: Microsoft Books online is a default reference of all articles but examples and explanations prepared by Ritesh Shah, founder of http://www.SQLHub.com