Hello,
I have created an SSIS package to retrieve data from a Lotus Notes database using the NotesSQL 3.02g ODBC driver.
In SSIS design mode, I can connect to the Notes datasource using the following connection string without any validation errors.
uid=UserID;Dsn=LN_Costs;
I have tried other variations of the connection string including every possible connection string parameter available to the driver as follows.
server=Server_Name;uid=UserID;Dsn=DSN_Name;Driver={Lotus NotesSQL Driver (*.nsf)};database=costing/productcost.nsf;username=UserID;encryptpwd=encrypted_password;maxsubquery=20;maxstmtlen=4096;maxrels=20;maxvarcharlen=254;keeptempidx=1;maxlongvarcharlen=512;showimplicitflds=0;mapspecialchars=1;threadtimeout=60;
Using the above connection strings in SSIS design mode, the datasource test succeeds, and an sql select statement in a datasource reader returns the table structure with no error.
However, when I try to run the package, I receive the following error.
SSIS package "Sales Data Load.dtsx" starting.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Error: 0xC0047062 at Data Flow Task, DataReader Source 2 [408]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)
Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source 2" (408) failed validation and returned error code 0x80131937.
Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
SSIS package "Sales Data Load.dtsx" finished: Failure.
Furthermore, I have packages configured in SQL 2000 DTS to use the same system dsn without any errors.
Why doesn't this work in SQL 2005 SSIS
Thanks.
Runtime Connect Error to ODBC System DSN
Ghost of Sapper
I believe I have found the solution myself. Viewing the properties of the solution in SSIS, I found a debug option called Run64BitRuntime. This is set to True by default. Considering the Notes Driver is 32bit, apparently the runtime debugger could not find the System DSN using the Notes Driver.
After setting the Run64BitRuntime value to False, the package executes without error.
Thanks.
tezzanator
i'm gettting exactly the same problem connecting (or trying to) an RDB database on a mainframe using odbc.
Can you tell me WHERE you found that run64bitruntime flag, i havent been able to locate it.
thanks
ML
MaxVernon
Mary Lou, in case you haven't found it yet it is in the project properties within your project in SQL Server Business Intelligence Studio (Studio). Once you have your project open in Studio, there will be a menu for Project, click that and then choose Properties. That opens the Properties window and now within Configuration Properties are the Debugging properties click on that node and then you should see Run64BitRuntime within the Debug Options group.
Hope that helps.
BAR