MSDASQL Problem...
May 2, 2007Hi,
I have some MSDASQL database files and I don't know this database at all.
Can I get from somewhere SQL standard for this database?
Greg.
--
ADVERTISEMENT
64-bit MSDASQL
May 6, 2008Hi,
I got the 64-Bit MSDASQL through the following link and install it on Windows xp 64-bit:
http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en
But
_bstr_t strConnect="Provider=MSDASQL;Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/test/test.mdb;";
// create Connection object
m_pConnection.CreateInstance("ADODB.Connection");
hr =m_pConnection->Open(strConnect,"","",NULL);
...
I always get the error "Data source name not found and no default driver specified". I'm sure the test.mdb file exists and the code works well on windows xp 32-bit but fails on Window xp 64-bit even I install the above package. Anybody can help me? Thanks!!
64 Bit MSDASQL.DLL
Feb 17, 2007Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!
View 30 Replies View RelatedMSDASQL Errors
Dec 18, 2002I am having this problem with using a linked server to another dB. I can read tables from the server, but cannot update the same tables (permissions are ok). I get the message
The requested operation could not be performed because the OLE DB provider 'MSDASQL' does not support the required transaction interface
Does anyone have an idea where I should start looking? What interface are they talking about? I am linking with a system DSN running the Connx 8.3 driver.
Any help would be extremely aprreciated.
Robert Crooks
Ivaco Rolling Mills
'MSDASQL' Headache
Aug 10, 2006Hello - hope this is in the right group:We have just started with linked servers and have successfully createda view on SQL Server linked to a Progress database. I can query thisview happily in Query Analyzer.I have created an ASP.NET application to display this view in adatagrid but I get the following error:System.Data.SqlClient.SqlException: OLE DB provider 'MSDASQL' reportedan error. at System.Data.SqlClient.SqlConnection.OnError(SqlExc eptionexception, Boolean breakConnection) atSystem.Data.SqlClient.SqlInternalConnection.OnErro r(SqlExceptionexception, Boolean breakConnection) atSystem.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObjectstateObj) at System.Data.SqlClient.TdsParser.Run(RunBehaviorrunBehavior, SqlCommand cmdHandler, SqlDataReader dataStream,BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)at System.Data.SqlClient.SqlDataReader.ConsumeMetaDat a() atSystem.Data.SqlClient.SqlDataReader.get_MetaData() atSystem.Data.SqlClient.SqlCommand.FinishExecuteRead er(SqlDataReader ds,RunBehavior runBehavior, String resetOptionsString) atSystem.Data.SqlClient.SqlCommand.RunExecuteReaderT ds(CommandBehaviorcmdBehavior, RunBehavior runBehavior, Boolean returnStream, Booleanasync) atSystem.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehaviorcmdBehavior, RunBehavior runBehavior, Boolean returnStream, Stringmethod, DbAsyncResult result) atSystem.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehaviorcmdBehavior, RunBehavior runBehavior, Boolean returnStream, Stringmethod) atSystem.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehaviorbehavior, String method) atSystem.Data.SqlClient.SqlCommand.ExecuteDbDataRead er(CommandBehaviorbehavior) atSystem.Data.Common.DbCommand.System.Data.IDbComman d.ExecuteReader(CommandBehaviorbehavior) at System.Data.Common.DbDataAdapter.FillInternal(Data Setdataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords,String srcTable, IDbCommand command, CommandBehavior behavior) atSystem.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32startRecord, Int32 maxRecords, String srcTable, IDbCommand command,CommandBehavior behavior) atSystem.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at...The code in my ASP.NET application looks fine and works on non-linkedviews on the same server. Do I need to add a command or change asetting on SQL Server?
View 2 Replies View Related64BIT MSDASQL
Nov 1, 2007Hi, is here someone who can send me new dll libary. Itīs very important. Thanks ALL
MSDASQL To NOTESSQL (odbc)
Jul 23, 2005Within an SQL Script is it possible to send a SQLDisconnectcommand? (server is MSDE)I have used sp_dropserver, sp_droplinkedsrvloginand do not get a SQLDisconnect.Each time I run the script a new nsql32.exe process loads up and theyaccumulate.use SalesGosp_dropserver 'M', 'Droplogins'goExec sp_addlinkedserver 'M', ' ', 'MSDASQL', NULL, NULL,'DRIVER=Lotus NotesSQL DRIVER(*.nsf);Database=C:eUROPEInstrument_Base.nsf;Ser ver=Local;UserName=XXXXXXXXXXXXX;EncryptPWD=XXXXXX X;'goselect * from M...MainForm where description= 'Described Here'Would like disconnect when this is done.......
View 2 Replies View RelatedHelp!! Need To Get The MSDASQL Provider In SQL 2005 EE 64 Bit
Aug 20, 2007
I understand that the MSDASQL.dll is not available in 64 bit (unless you are running 2008 beta 3). I also understand that you can setup 32 bit ODBC without issues (using ODBCAD32.exe in WOW directory). My issue is how does SQL 2005 64 bit see these ODBC links? What is everyone doing to get around this? I want to be able to use openquery. Any advice would be much appreciated.
Carlton
The OLE DB Provider MSDASQL Has Not Been Registered.
Feb 8, 2007I'm trying to set up replication on SQL Server 2005 (64-bit) and I am getting this error message when the replication kicks off.
'The OLE DB provider "MSDASQL" has not been registered.'
When I try and register the MSDASQL I get the folloing error message.
'LoadLibrary("c:program filesCommon FilesSystemole dbMSDASQL.dll") failed - the specified module could not be found.
'MSDASQL' Error On Linked Servers
Dec 16, 2003I've seen several posts on linking an AS/400 to a SQL 2000 server.
I have created the link, I can use DTS packages to get data to/from the AS/400 to the SQL Server. However, I cannot write any SQL statements against the AS/400. Here is a basic one that doesn't work...
Select * from openquery(jdedwardspy, 'Select * from mhscrp.f0006')
If you look quickly enough, you can see that it does return a row or so, but then that is replaced by this error...
[OLE/DB provider returned message: [IBM][Client Access Express ODBC Driver (32-bit)]Driver not capable.]
We're running Client Access V5R2, SQL Server 2000 SP3 and MDAC 2.7.1.
Any suggestions?
MSDASQL Linked Server Error
Jan 7, 2008Hi all,
I have created a System DSN to a MYOB database file. I have SQL 2000 and 2005 Express editions installed on the same machine. I am logged in to PC as Local 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, 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.
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
MSDASQL Error Requires SQL Service Restart
May 17, 2006I am having trouble with a linked server using MSDASQL. I'm connecting to a PostgreSQL database and pulling over data. This process has been working fine.
In trying to pull data from a different client database (same schema), I received an error that the MSDASQL couldn't read the column names.
The actual problem I want help on is that after this happens, I am no longer able to make valid connections to any of my Linked Servers using MSDASQL. The only way I can get my other linked servers to work again is to restart the SQL Service. Usually this is impossible for me to do because of the number of active users.
Two questions:
1) Is there another way to restart a more targeted service or sub-set to reset MSDASQL connections, and clear out my problem?
2) Any idea why I'm getting this error connecting to PostgreSQL on a large dataset when it worked fine for a small dataset using the same linked server? "The provider reported an unexpected catastrophic failure."
Any help is appreciated.
SQL Server 2005 DTS Conversion, Activex And MSDASQL
Mar 29, 2006Hi all
I am migrating some DTS2000 packages to SSIS via the migration wizard. However there is an activex script in each DTS that connects to an AS400 to retrieve record count for integrity checking. Under SQL server 2000 this worked fine but now it errors with "The OLE DB provider "MSADSQL" has not been registered" how do i get this to work i suspect its because this is a 32 bit dll and my new system is a 64bit sql server on windows 2003. The odbc driver for the as400 has been installed also. The script is as follows:
dim cn 'sql connection
dim rs 'sql recordset for the insertion of new as400 records
dim insertstr 'sql insert string
dim rs1 'sql recordset for the insertion of new as400 records
dim insertstr1 'sql insert string
set cn = createobject("ADODB.Connection")
set rs = createobject("ADODB.Recordset")
Function Main()
'set up connection for sql
cn.provider="sqloledb"
cn.commandtimeout = 3600 'timeout in seconds
cn.open %sqlserver05%, %user%, %password%
'populate temporary table in sql with recordset from as400 odbc
insertstr1 = "Insert into db.dbo.%table% select 'table name',a.* from openrowset ('MSDASQL','DRIVER={Client Access ODBC Driver (32-bit)};SYSTEM=%system name%;UID=%username%;PWD=%password%','SELECT count(*) from %table%') as a"
set rs1 = cn.execute (insertstr1)
'close all objects
cn.close
Main = DTSTaskExecResult_Success
End Function
Does anyone know how i change this to work under sql server 2005. i need to resolve this quickly in order to deliver a project on time. Many thanks
Chris
Catastrophic Failure, MSDASQL, Linked Servers And MySQL
Jun 21, 2007When executing a query which joins against a large resultset from a linked server, SQL Server reports the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "foo" reported an error. 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 "foo".
This is using SQL Server 2005 with SP2, and MyODBC version 3.51.16 (although previous versions also seem to have the same behavior).
Once the error occurs any subsequent query against the linked server (even something as simple as select top 3 * From foo...users) fails with the same error message. Queries using the OpenQuery syntax also fail with this error.
I've tried to determine if there are some error logs that might give me more insight into what's going on, but the above events don't seem to log to the ODBC trace logs. And I can't seem to figure out a way to trace the MSDASQL (i.e., oledb) events.
I initially thought there might be a problem with the MySQL myODBC driver, but the ODBC layer itself does not seem to have a problem. But the following steps indicate otherwise:
1. Create a new Linked Server to MySQL. Same error as above
2. Execute a query against the ODBC DSN directly, using a shell program. This works fine
I'm trying to clearly identify if the problem is with the MySQL driver or with the MSDASQL provider. It would appear that the latter is at fault, given the error message, and the lack of any ODBC logging.
Would anyone have any insights about what might be going on here, and if there is any possible resolution?
Intermittent Openquery Error ..The OLE DB Provider 'MSDASQL' Indicates That The Object Has No Columns..
Jul 20, 2005Help,I am running a pass through query to oracle from SQL server 2000 asfollows;select * from openquery(nbsp, 'select * from FND_FLEX_VALUES')I have run this query through both DTS and the query analyzer and getthe foloowing error;Server: Msg 7357, Level 16, State 2, Line 3Could not process object 'select * from FND_FLEX_VALUES'. The OLE DBprovider 'MSDASQL' indicates that the object has no columns.OLE DB error trace [Non-interface error: OLE DB provider unable toprocess object, since the object has no columnsProviderName='MSDASQL',Query=select * from FND_FLEX_VALUES'].The really strange thing is, I'll get this error the first time Iexecute the query but if I execute it immeadiatley after it will runfine.Any help would be most appreciated!Cheers
View 1 Replies View RelatedSQl 2005 Express - Linked Server - Access ADP - MSDASQL Error
Jan 8, 2008Hi everyone,
I'v finally managed to get a New Linked Server setup on SQL 2005 Express SP2 using the 'Microsoft OLE DB Provider for ODBC Drivers' MSDASQL. I have a Database setup on the SQL 2005 Express Database Engine which contains a query that OPENQUERY's the linked server. The query executes OK.
The problems in when I link an Access 2003 SP2 .adp file to the SQL 2005 Database Engine database. All objects, including the query containing the OPENQUERY (to the linked server) appear. However, when I run the same query within Access I get the following error:
"The OLE DB Provider for Linked Server "name" reported an error."
"The Provider reported an unexpected catastropic failure"
So the query works running within SQL 2005 Management Studio, but the same query doesn't work running within an Access 2003 SP2 ADP. I've closed down SQL 2005 Management Studio, but the same error is displayed.
I didn't know if the problem lies in Access 2003 SP2 or SQL 2005 Express SP2.
Any takers?? (I haven't logged this Thread in an Access forum)
Any assistance is appreciated.
Alan