Post New Web Links

Excel Data Source SSIS AcquireConnection failed 0x80004005 unspecified error

Posted By: Posted Date: September 02, 2010 Points: 0 Category :Sql Server

Nuances of using Excel data sources with SSIS Your Development Machine Setup Needs Jet Drivers, available along with the default Office install so if you have Excel working fine locally, this is enough. Installing the "Office Data Connectivity Components" (download file name AccessDatabaseEngine.exe) as well as having Office installed corrupts the Jet Driver stack so that SSIS in VS 2008 cannot create the object to read the XLS file. You will see the title error "Unspecified Error" and "80004005" code. Resolution: Uninstall the Jet Engine pack on your development XP machine if you have Office. It will be listed as something like "Microsoft Access Database Engine (2010)". Run Office 200x setup with the Repair option and reboot. Try configuring the task in SSIS and it should be able to read the Sheet names again and columns. Live Server (32-bit and 64-bit) Deploying your SSIS package to a server without Office 200x means it will not have the Jet Engine drivers to read XLS, XLSX files. You must install the 32-bit Office Data Connectivity Components - Jet Drivers mentioned above found here (http://www.microsoft.com/downloads/details.aspx?familyid=7554f536-8c28-4598-9b72-ef94e038c891&displaylang=en). There are no 64-bit drivers; therefore regardless of 32 or 64-bit live environments, this step is the same. You shoul

View Complete Post

More Related Resource Links

SSIS: Error in the package when the data in the flat file source is modified

Hi All,

I have a package which loads data from a flat file source to an OLEDB destination, which is executed successfully and data is loaded perfectly.

But later when the data in the flat file source is modified i.e. if an extra column gets added to the text file, the package is throwing an error because it is unable to detect the extra added column.

How can i avoid this error??? I need my package to execute successfully ignoring the changes(added columns) happened in the flat file source.

Please provide me wth your suggestions and solutions....

Thanks in Advance!!

Initialization of the data source failed in Excel 2007 from As 2008R2

Environment: Win server 2003 , Office2007, SQL Server2003, PowerPivot for Excel

All the user do have access to connect the cube. am the admin user and i get the same error message.

"Initialization of the data source failed. Check the database or contact your database administrator. Make sure the external database is avaliable, and then try to operation again.

I have tried deleteing the data source and creating a new one.

Can any one help with this there are other fourms on this but i can't see a answer for it.

dog

SSIS excel data source numeric values returned as null

Hello everyone, long time no see!, I have a problem and was hoping someone can help me:
I'm using SSIS 2005 Enterprise edition,ÃÂ I'm creating a package that reads an excel (xls)ÃÂ file using the "excel source" component, and it dumps the data into an OLEDB destination (a sql server).
When I drag the excel source component andÃÂ create the excel connection to my file the component automatically reads the columns and their datatypes.

The problem is that I have a column which has numeric data and the package uploads as NULL every number that starts with a zero. (note: in excel this columnÃÂ is formatted as "text", despite it has only numbers, because it's the only way excel maintains the left sided zeros).
So I checked the data types by right clicking the excel source component -> show advanced editor and my surprise is that this column's data type is detected as double-precision float, and it doesn't let me change it.

I tried the answer posted here: http://devselekta.blogspot.com/2007/09/ssis-excel-data-source-values-returned.htmlÃÂ but it only works when the first row of data hasÃÂ a numberÃÂ beginning with zero on this column.
Someone knows how to get the data imported correctly? Thanks in advance.

Odin_Dark

Unit Testing Error - The unit test adapter failed to connect to the data source or to read the data

I'm using VSTS 2K8 and I've set up a Unit Test Project. In it, I have a test class with a method that does a simple assertion. I'm using an Excel 2007 spreadsheet as my data source.

My test method looks like this:

[DataSource("System.Data.Odbc", "Dsn=Excel Files;dbq=|DataDirectory|\\MyTestData.xlsx;defaultdir=C:\\TestData;driverid=1046;maxbuffersize=2048;pagetimeout=5", "Sheet1", DataAccessMethod.Sequential)] [DeploymentItem("MyTestData.xlsx")] [TestMethod()] public void State_Value_Is_Set() &nbs

`MDW Disk Usage for Database Report Error - A data source has not been supplied for the data source D`

  Hello,
On the MDW Disk Usage Collection Set report, I get the following error when I click on a database hyperlink.
A data source has not been supplied for the data source DS_TraceEvents
SQL profiler shows the following SQL statements are executed (I've replaced the database name with databaseX)
1. exec sp_executesql N'SELECT
dtb.name AS [Name]
FROM
master.sys.databases AS dtb
WHERE
(dtb.name=@_msparam_0)',N'@_msparam_0 nvarchar(4000)',@_msparam_0=N'databaseX'
this returns zero rows as databaseX does not exist on my MDW central server, but is a database on a target server (i.e. one that is being monitored and uploaded into the MDW central server).
2. USE [datatbaseX]
this produces the following error:
Msg 911, Level 16, State 1, Line 1
Database 'databaseX' does not exist. Make sure that the name is entered correctly.
why is the report looking for the database on my server?
thanks
Jag
Environment: MDW (Management Data Warehouse) on SQL 2008 R2

`Data Source View Gives incorrect Error--Different Data Type`

  Hi,
I'm creating a report model (2008 R2).  I am trying to create a relationship between two tables.  One FKs to another--same name and type (tinyint) columns.  But the Data Source View editor doesn't allow this, giving the message "...source
 and destination column have different data types".  But the columns are the same types.  I ahd this once before  acouple of years ago and don't remember how I got around it.
Does anyong have ideas?

`ssis sql 2000 image to 2008 varbinary Failed to retrieve long data for column`

  Hi,
I have a task that to migrate the image type column from sql 2000 to varbinary type in sql 2008.
The source column having 3812353 max datalength size for the column. The package always failed with following error message.
[OLE DB Source [13177]] Error: Failed to retrieve long data for column "attch_file_content_t".
[OLE DB Source [13177]] Error: There was an error with output column "attch_file_content_t" (13209) on output "OLE DB Source Output" (13187). The column status returned was: "DBSTATUS_UNAVAILABLE".
[OLE DB Source [13177]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "output column "attch_file_content_t" (13209)" failed because error code 0xC0209071 occurred, and the error row disposition on "output column
 "attch_file_content_t" (13209)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.
Meng Chew

`SQL ServerDestination error - Unable to prepare the SSIS bulk insert for data insertion.`

  Having searched the forum, this one clearly has form... However beyond assisting those who have fallen at the first hurdle (i.e. forgetting/not knowing that they cannot execute the package remotely to the instance of SQL Server into which they are inserting), the issues raised by others have not been addressed. Thus I am bringing nothing newÃÂ to the table hereÃÂ - just providing an executive summary of problems which others have run into, written about, but not received answers for.
ÃÂ 
First the complete error:
Description: Unable to prepare the SSIS bulk insert for data insertion.ÃÂ  End ErrorÃÂ  Error: 2008-01-15 04:55:27.58ÃÂ ÃÂ ÃÂ ÃÂ  Code: 0xC004701AÃÂ ÃÂ ÃÂ ÃÂ  Source:ÃÂ <xxx> DTS.PipelineÃÂ ÃÂ ÃÂ ÃÂ  Description: component "<xxx> failed the pre-execute phase and returned error code 0xC0202071.ÃÂ  End ErrorÃÂ  DTExec: The package execution returned DTSER_FAILURE (1).ÃÂ  Started:ÃÂ  4:53:34 AMÃÂ  Finished: 5:00:00 AMÃÂ  Elapsed:ÃÂ  385.384 seconds.ÃÂ  The package execution failed.ÃÂ  The step failed.
ÃÂ 
Important points


It mostly works - It produces no error more than 9 times out of 10.

It fails on random dataflows - My package has several dataflows, (mostly) executing concurrently. Where the error occurs it does not do so on the same dataflow each time: on one run it'll fail on dataflow AÃÂ whilst B,C,D and E succeed, then A-E will all succeed (and continue doing so for the nextÃÂ ten runs thereafter), and

`Need an example of error in OLE DB Source component when source is Excel file.`

  I want an example of error (not truncation) in individual row or individual cell that can occur in OLE DB Source component when source is Excel file.
I'm trying out Error Output of data task component.  I have already tried out Error Output of OLE DB Destination component.

`I need to create a script in SSIS which creates a data source that connects to an Access database.`

  I need to create a script in SSIS which creates a data source that connects to an Access database.


The Access database file name needs to be set as a variable as it will change from month to month.

I have no idea what I am doing can anybody give me some tips? Mr Shaw


Categories:

ASP.Net	Windows Application	.NET Framework	C#	VB.Net	ADO.Net
Sql Server	SharePoint	Silverlight	Others	All