February 16, 2010 at 8:35 pm
I'm new to SSIS and am trying to create a simple package using BIDS for SQL Server 2008. I'm getting the following error when trying to execute the package (within in the debugger as well as from command line):
I've bolded the piece that I think is the most pertinent piece of the error....
SSIS package "Divisions.dtsx" starting.
Information: 0x4004300A at Division ETL dataflow, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Division ETL dataflow, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Division ETL dataflow, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Information: 0x40043006 at Division ETL dataflow, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Division ETL dataflow, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Division ETL dataflow, Read category table for divisions [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.
Error: 0xC004701A at Division ETL dataflow, SSIS.Pipeline: component "Read category table for divisions" (1) failed the pre-execute phase and returned error code 0xC0202009.
Information: 0x4004300B at Division ETL dataflow, SSIS.Pipeline: "component "Flat File Destination" (60)" wrote 0 rows.
Information: 0x40043009 at Division ETL dataflow, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Division ETL dataflow
Warning: 0x80019002 at Divisions: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Divisions.dtsx" finished: Failure.
I've basically got a control flow which has an OLE DB Source outputting to a flat file. I'm able to preview the results just fine when I edit the OLE DB Source piece, so I'm not quite sure what could be causing an issue.
I'm running BIDS on a 32 bit Windows 2008 Server. The OLE DB source is an Informix 9.4UC5 server and am using the driver provided by IBM.
Any help is appreciated.
Thanks,
Jared
February 17, 2010 at 3:43 am
Are you running from your client PC or or you remotely connecting to the PC?
Is the Account that you are using a Local Admin on the Server?
Are you running the SSIS Package interactively?
Have you tried breaking down the package to one step at a time?
Are you sure that you are using the correct provider?
Are you sure that you do not have any issues with 32/64 bit?
Are you creating an error log file and are you running in debug mode?
Have you tried altering the batch size and other options?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 17, 2010 at 10:50 am
Are you running from your client PC or or you remotely connecting to the PC? I'm RDP'ng into a Windows 2008 Server and launching BIDS through there. I'm using an OLE DB command to connect to a remote Informix IDS 9.40.UC5 database.
Is the Account that you are using a Local Admin on the Server? Yes.
Are you running the SSIS Package interactively? Interactively meaning running it through BIDS???
Have you tried breaking down the package to one step at a time? The package has only 2 steps. OLE DB command to grab a few columns from the Informix db and export to a flat file. It seems to be erroring out on the first step (OLE DB command).
Are you sure that you are using the correct provider? I'm pretty sure I'm using the right provider. I'm able to preview the results in BIDS when I edit the OLE DB step, but when I execute the package within BIDS I get the errors. I'm able to connect using ODBC, but it seems like BIDS will only use OLE DB. I'm not sure if it's something I don't have configured correctly in the package or something on the database I'm trying to pull from.
Are you sure that you do not have any issues with 32/64 bit? I don't think there are any. I have some other 64-bit SSIS 2005 packages developed by a third party that connect to the same database.
Are you creating an error log file and are you running in debug mode? I'm not creating an error log. I am running it through BIDS which I believe is in debug mode.
Have you tried altering the batch size and other options? I haven't really changed anything yet. The package should only return 4 rows. I'm trying to start out simple to get used to SSIS and make sure it's working before I get into the more complicated stuff.
Thanks.
February 17, 2010 at 11:04 am
Have you tried executing the SQL Command outside of the SSIS PAckage?
There are several logs that you can use and can be helpful.
I have experienced issues with mixing 32 bit & 64 bit.
You have to specify breakpoints and go into debug mode.
Why not just create a simple Wizard with the two tasks separated?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 17, 2010 at 11:07 am
This problem will occur when running in 64-bit mode whit the 32 bit Informix Client components installed.
Please verify installation.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 17, 2010 at 12:19 pm
I'm using the 32bit Informix drivers in a 32bit Windows 2008 Server. The Informix DB is also 32bit. Is there a setting for 64bit in SSIS that I need to change?
I can try a simple wizard, but even when I just have the OLE DB command as the only task I get the error.
February 17, 2010 at 7:21 pm
If I try to use the SSIS Import and Export Wizard I get the following error after I enter in the properties of my IBM Informix OLE DB Provider:
===================================
Cannot get the supported data types from the database connection "Provider=Ifxoledbc.2;Password=;Persist Security Info=True;User ID=user;Data Source=dbname@on_some_server". (SQL Server Import and Export Wizard)
===================================
EIX000: (-111) ISAM error: no record found. (Ifxoledbc)
------------------------------
Program Location:
at System.Data.OleDb.OleDbConnectionInternal.ProcessResults(OleDbHResult hr)
at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions)
at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions)
at System.Data.OleDb.OleDbMetaDataFactory.GetDataTypesTable(OleDbConnection connection)
at System.Data.OleDb.OleDbMetaDataFactory.PrepareCollection(String collectionName, String[] restrictions, DbConnection connection)
at System.Data.ProviderBase.DbMetaDataFactory.GetSchema(DbConnection connection, String collectionName, String[] restrictions)
at System.Data.ProviderBase.DbConnectionInternal.GetSchema(DbConnectionFactory factory, DbConnectionPoolGroup poolGroup, DbConnection outerConnection, String collectionName, String[] restrictions)
at System.Data.OleDb.OleDbConnection.GetSchema(String collectionName, String[] restrictionValues)
at System.Data.OleDb.OleDbConnection.GetSchema(String collectionName)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.LoadTypeData(DbConnection myDestConnection)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.CacheDataSourceInfo(IDbConnection myConnection)
I'm guessing this might be part of it...
February 17, 2010 at 7:51 pm
Can you check your local machine, to determine that both the client Server Component as well as the OLEDB Providers to determine that it is not a 32/64 bit issue?
Can you Goggle thru you code and capture the errors?
Refresh my memory. Are you running on 64 bit Server?
Are you using 32 bit Client SQL Server and/or 32 bit OLEDB Providers?
What is the version of the Sybase Client?
Can't you run from the client & server client components from a 32 bit machine to eliminate 32/64 bit compatibility issue?"
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply