Cannot Initialize The Data Source Object Of Ole Db Provider Msdasql
- Cannot Initialize The Data Source Object Of Ole Db Provider Msdasql For Linked Server Mysql
- Cannot Initialize The Data Source Object Of Ole Db Provider Msdasql For Linked Server Error 7399
Hi, Some of the users report the following error message while using the openquery:Msg 7399, Level 16, State 1, Line 1The OLE DB provider 'MSDASQL' for linked server 'remoteserver' reported an error. The provider reported an unexpected catastrophic failure.Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider 'MSDASQL' for linked server 'remoteserver'.I dont think we have a problem with the connecter since other users can fetch data using openquery.Could anyone help me on this?Many thanks,sqlstar.
- Dec 16, 2013 Cannot initialize the data source object of OLE DB provider 'MSDASQL' for linked server 'Server' since we removed the use of the Synonyms. Thursday, December 12, 2013 1:11 PM Reply.
- 'OLE DB provider 'MSDASQL' for linked server 'SpiceWorksLink' returned data that does not match expected data length for column 'MSDASQL.summary'. The (maximum) expected data length is 100, while the returned data length is' you can use SQLites substr command to have SQLite truncate the data before shipping it to MS SQL.
The provider reported an unexpected catastrophic failure. Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider 'MSDASQL' for linked server 'remoteserver'.
Cannot Initialize The Data Source Object Of Ole Db Provider Msdasql For Linked Server Mysql
I'm trying to establish a linked server from SQL Server 2008 R2 to an Access database. The Access database is not password protected. As I have seen in other posts , this is usually due to the current user not having access to the Temp folder inside the NetworkService folder. Since we are running this in Windows Server 2008, the directory structure is quite different than what most are eluding to. I have allowed access to every temp folder in the 'root:Documents and Settings' directory, and to no avail.This is the procedure I am using to add the linked server: EXEC spaddlinkedserver@server = N'OSAccess',@provider = N'Microsoft.ACE.OLEDB.12.0',@srvproduct = N',@datasrc = N'C:RTBDataDataOS.mdb';GOIt creates the linked server with no problem, but I am not able to view the tables/views of the database. Likewise, my ASP.NET application cannot access it either.I have tried both ACE and JET(64-bit)(by installing the Data Connectivity Components for Office), and they both do not work.
I have also tried configuring the ACE provider with 'Dynamic Parameter' and 'Allow InProcess' to true.Additionally, I tried upping the memory usage by the MSSQLSERVER services by adding '-g512;' in front of 'startup parameters' string in SQL configuration manager to rule out memory issues.If anyone could shed some light on this that would be fantastic! Thanks!UPDATE: I logged into SQL using the sa account, and I was able to view the linked server.
Cannot Initialize The Data Source Object Of Ole Db Provider Msdasql For Linked Server Error 7399
My current user account has full permissions in SQL server, so I am unsure of what the difference is between the accounts. Maybe I gave permissions to the wrong Temp folder, in which the sa account (being built-in) has access to. If someone could point me in the right direction here, that would be great, and I think it would also help a lot of other people.