- 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:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp
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
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?
Step 1 – Solve Microsoft Sql Server Error 7303
Is Microsoft Sql Server Error 7303 appearing? Would you like to safely and quickly eliminate Microsoft Sql Server which additionally can lead to a blue screen of death?
When you manually edit your Windows Registry trying to take away the invalid microsoft sql server error 7303 linked server oracle keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!
Troubleshooting microsoft sql server error 7303 oracle Windows XP, Vista, 7, 8 & 10
Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Microsoft Sql Server Error 7303 complications.
Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the 7303 error) likewise as any broken hyperlinks inside of your registry.
Issue with microsoft sql server 2008 error 7303
Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.
- https://social.msdn.microsoft.com/Forums/sqlserver/en-US/96ca13a3-a39e-4271-aa93-86e20067544f/linked-server-error-7303?forum=sqldataaccess
- http://stackoverflow.com/questions/27191909/linked-servers-sql2008-to-mysql-error-7303-data-source
- https://hi.service-now.com/kb_view.do?sysparm_article=KB0538992
- http://dba.stackexchange.com/questions/36687/cannot-initialize-the-data-source-object-of-ole-db-provider-microsoft-ace-oledb
Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.
Fixed: microsoft sql server error 7399
Symptoms of Microsoft Sql Server Error 7303
“Microsoft Sql Server Error 7303” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Microsoft Sql Server Error 7303 when running the exact same system.
“Microsoft Sql Server Error 7303” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.
Will cause of Microsoft Sql Server Error 7303
Corrupt obtain or incomplete set up of Windows Operating System software program.
Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).
Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.
Another method maliciously or mistakenly deleted Windows Operating System-related files.
Mistakes this sort of as “Microsoft Sql Server Error 7303” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.
Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the microsoft sql server error 7303 linked server oracle connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your microsoft sql server error 7303 oracle related registry entry.
Solution to your microsoft sql server error 7303 db2 problem
There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.
Additional Measures:
One. Conduct a Thorough Malware Scan
There’s a probability the Sql Microsoft 7303 Server Error error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Microsoft Sql Server Error 7303 is actually connected to some element of that malicious plan itself.
2. Clean microsoft sql server error 7303 excel Disk Cleanup
The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an 7303 error because of possible conflicts or from overloading your hard drive.
Once you clean up these types of files using Disk Cleanup it could not just remedy Microsoft Sql Server Error 7303, but could also create a dramatic change in the computer’s efficiency.
Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Microsoft Sql discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.
Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any 7303 error associated with your temporary files.
How Disk Cleanup can help microsoft sql server 2005 error 7303
1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.
How to repair error 7303 silverlight
3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.
Microsoft Sql
Manufacturer
Device
Operating System
Microsoft Sql Server Error 7303
4 out of
5
based on
49 ratings.
One of the blog reader sent me the below mail. I always find that using linked server have been of concern and trouble at a number of places. So when the mail landed – well I was not surprised that there was a problem. It is common and hence the resolution for the same is also common yet not discussed. So I thought this blog will bring the nuances that I thought was the resolution and which helped our blog reader.
Hi Pinal,
I have two SQL Server instances on same machine and I want to fetch data from each other. So I went ahead and created linked server. In SQL Server Management Studio, Server Objects > Right-click, Linked Servers, and then selected New linked server. I gave the remote server name as SQL16NODEBSQL2014 and “Server type” as SQL Server as shown below.
While saving I got error as below
TITLE: Microsoft SQL Server Management Studio
——————————
The linked server has been created but failed a connection test. Do you want to keep the linked server?
——————————
The OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014” reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014”.
OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014” returned message “Invalid authorization specification”. (Microsoft SQL Server, Error: 7399)
If I hit No, the linked server is not created. If I created Yes, linked server is created, but any query is failing with the same error.
What should I do?
Thanks,
<name hidden>
I asked to check and run
sp_testlinkedserver N'SQL16NODEBSQL2014'
and as expected, it failed with the same error.
OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014” returned message “Invalid authorization specification”.
Msg 7399, Level 16, State 1, Procedure sp_testlinkedserver, Line 1
The OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014” reported an error. Authentication failed.
Msg 7303, Level 16, State 1, Procedure sp_testlinkedserver, Line 1
Cannot initialize the data source object of OLE DB provider “SQLNCLI11” for linked server “SQL16NODEBSQL2014”.
The message “Invalid authorization specification” means that linked server settings to connect to the server are not correct. To fix that, we need to go back to linked server properties and go to “security” tab and choose the proper authentication method from last two.
If there is a SQL Login to be used, then we need to provide account and its password.
Here is the T-SQL command for 3rd option where @useself is set to true
USE [master] GO EXEC MASTER.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'SQL16NODEBSQL2014', @locallogin = NULL , @useself = N'True', @rmtuser = N'' GO
Here is the T-SQL command for 4th option where @useself is set to false so we need to provide @rmtuser and @rmtpassword
USE [master] GO EXEC MASTER.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'SQL16NODEBSQL2014', @locallogin = NULL , @useself = N'False', @rmtuser = N'sa', @rmtpassword = N'sa' GO
Hope this will helps and do let me know if you have ever got this error in your environments.
Reference: Pinal Dave (https://blog.sqlauthority.com)
Problem:
I use SQL Server 2008.
We have here a linked server, linking to a MySql Database.
But since today, when I click «test connection», it shows me this error:
( I can’t post images yet):
The test connection to the linked server failed.
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MANTIS".
OLE DB provider "MSDASQL" for linked server "MANTIS" returned message "[Microsoft][ODBC Driver
Manager] Data source name not found and no default driver specified". (Microsoft SQL Server,
Error: 7303)
What should I do?
It was working yesterday. I thought about «data sources ( ODBC)». Yes, There is no DataSources for MySql ( it doesn’t even show me the option to add a mySql odbc when I click ADD), but it was working yesterday !!
I didn’t find a reasonable solution from any post.