CDC Issue in SSIS Package

Hi All,
We have created SSIS package using CDC(2012). But performance is very slow. How can we improve performance in the below senario's
Scenario A:
Source DB & CDC in SSIS in the same server:
When we run the CDC package in this scenario. We are able to extract 500K records in 50seconds.
Scenario B:
Source DB is in physical server 1 and CDC with SSIS in physical server 2:
When we run the CDC package in the scenario, 10,000 record extraction takes 15min. We have Primary Key in the table from where we extracting the records.
Please reply us how to solve the delay in data extraction using CDC in the Scenario B. We are using 2012.
Kindly provide us multiple options.
Thanks in Advance...

Hi All,
We have created SSIS package using CDC(2012). But performance is very slow. How can we improve performance in the below senario's. The issue in reading transaction log
When we run the CDC package in this scenario, 10,000 record extraction takes 15min. We have Primary Key in the table from where we extracting the records.
Issue : CDC source component is taking time to read data from transaction log file . Is there any way to track this ?
Our requirement is reading changed data e.g. 100,000 records in some seconds .
Kindly provide us multiple options.
Thanks in Advance...

Similar Messages

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

SSIS Package Caused ASYNC_NETWORK_IO Issues - Disable LargeSend Offload & JumboPackets NIC Settings

We actually have multiple SSIS packages connecting to multiple servers and in one case we experienced very high ASYNC_NETWORK_IO even though the package had been in place for a long time and never caused this previously. Subsequently we opened a case with
MS Techsupport and after investigating many different aspects, Network Monitor was used to examine the traffic between two of the servers, the one where the package resides and the server that experience high ASYNC_NETWORK_IO. The NIC settings on the two servers
were checked and it was discovered that the LargeSend Offload and Jumbo Packets settings were different on the two servers.
The recommendation from MS Techsupport is to disable these settings on both servers, though we will have to expand this to cover at least another 6 servers. To disable these settings is apparently not considered as best practice by MS but nor is enabling
them.
We are concerned about the effect changing these settings might have on other services, for instance batch jobs, web connections, .NET, etc., etc.
Has anyone else had to change their NIC settings in order to deal with a performance issue with SSIS packages, and are there any concerns which should be considered before proceeding with such changes?
N.B. It has been noticed that some NICs do not even have an option for Jumbo Packets in which case is that ignored by that NIC or is that defaulted to a value that cannot be changed?
TIA
Michael MacGregor, Senior SQL Server DBA

Hi Michael,
You may wanna look at the following links:
http://www.sqlservercentral.com/Forums/Topic1372136-364-1.aspx
http://www.techques.com/question/2-253763/SQL-Server-2005-ASYNC_NETWORK_IO-waits:-can-we-just-increase-network-buffer-size?-(How?)
Regards, Leo

Please help with this issue "To Run a SSIS Package outside of Server Data Tools You must install Drived Column of Integration sercvies of higher" From C# app

i have searched all over the google and here on MSDN(I have read all the threads related to my problem ) , i am new to SISS and doing my clg project ,
I have this package which loads data from dim tables to a fact table , my Package runs without any problem in BIDS (2012)
I have installed SQl Server integration services on SQL and service is also running in services.msc,
the problem comes when i execute my package using my C# application i am using MSDN Method to execute a SSIS package programmatically given here.
"http://msdn.microsoft.com/en-us/library/ms136090.aspx"
For loading my FactTable i have used a Derived columns and some lookups ,
Now if i don't use derived columns and looks ups and just use source and destination component then my package runs fine from my C# application but if i use derived columns or looks ups etc it gives the following error
"Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/SSIS.Pipeline: To Run a SSIS package outside of SQL Server Data Tools you must Install Derived Column of Integration services of higher"
I am searching and trying to resolve this issue from previous 2 days but without any luck please help or guide me what is solution to this problem ,,i will be very thankful
I have also found that integration services that are running on my system have version 10.0
but the BIDS have version Version 11.0.3402.0
IS this causing problem ? if yes then what i have to do ?

Hi BlaxButt,
The package is developed in SSDT installed by SQL Server 2012, so it is a SSIS 2012 package. However, the Integration Services you have installed is SQL Server 2008 R2 version. To run the package outside SSDT, you need SSIS 2012 installed. The reason why
the package runs fine with only Source and Destination components is that such a simple package can be executed by the DTExec utility installed by SQL Server 2012 Data base Engine or Client Tools (SQL Server Import and Export Wizard). To run a package that
uses other tasks/components outside SSDT/BIDS, the SSIS runtime is also required except the DTExec utility. To obtain the SSIS 2012 runtime, we have to install SSIS 2012 on the server where the package runs.
Reference:
http://stackoverflow.com/questions/19989099/getting-error-running-ssis-package-on-non-ssis-server
Regards,
Mike Yin
TechNet Community Support

Issue with Dataflow Task in SSIS Package

Hello Everyone,
I have recently created an SSIS package to Load data from Flat file to SQL Server Table, it was working fine. Now I have bought a new laptop and copied the projects into this new system and changed all the connection managers(Flat files) accordingly.
Problem is, when I previously ran the package(With File1) in old laptop and check the distinct count on a table it was perfect, but when I ran the same package with same File on New Laptop, the Distinct count gives me an issue with particular record.
Eg: Distinct Count with old laptop Run , 10,20,100
Distinct Count with old New Run , 10,20,100 , 100
There is a Space being generated for a particular record, when I run the package on new laptop with same File as old one.
Any suggestions on this, I could not exactly figured out the Issue.
Please Help.
Thanks
Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.

You need to tell the responders here how exactly to reproduce your issue and provide the file.
I do not know how the "distinct count" works.
Seems to me it appears to be a database issue not SSIS.
Arthur
MyBlog
Twitter
When I perform the above query on old laptop, this gives me a result set of
10
20
100
When I perform the Same query on New laptop, this gives me a result set of
10
20
100
'100 ' (No Quotes please see the spaces generated)
Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.
Can you give us an idea of tasks you're having after the file source?
Particulary see steps where you are doing some data manipulations.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page
I am using simple Flatfile source and oledb destination in here. this is causing issue, all the other tasks after this are loading perfectly except this.
Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.

SSIS package issue

I need to schedule job to run through a package.
for that i imported SSIS package by connecting Integration services after import done it showing there in MSDB.
Now i connected to SQL DB engine to see and schedule asa job for the imported package but i am not able to see the imported package in maintenance plans. so totally confused with this behavior of package.
I have alternate for schedule this package through new job steps so i done it and then when i run the job it getting error as "login failure for user", here the user is service account, so please help in this issue.
Thanks,
Janardhan

Hi Janardhan,
According to the error message that “login failure for user”, it seems that SQL Agent Service account does not have required privileges to access the data sources in your SSIS package. Please check if the service account has enough permissions.
Please note that to configure a user to execute Microsoft SQL Server Agent jobs, we should grant the user with the following SQL Server Agent fixed database roles in the msdb database:
SQLAgentUserRole, SQLAgentReaderRole, or SQLAgentOperatorRole. Just as SequelMate suggested, If the user is non-administrative user that want to run jobs to execute SSIS packages, they will need to have access to a proxy account that has the
required privileges and then run the SSIS package under this account. Please check the issue again.
Reference:
Configure a User to Create and Manage SQL Server Agent Jobs
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS package and sql agent issue

Hi guys, I don't know if is the perfect place but I've got a question about running SSIS package from the Job Agent. The problem that I am having this issue: Access Denied.
What I do is to put the package in a folder in my network where everyone is able to read and write. Of course if I double click the package it's works, bear in mind that the package write in the Database FORUM and I am the only one that has access to the
database. So if one of my colleague try it doesn't work. But, two questions:
1) SQL agent need to be configured as a normal user or automatically if you put a package in SQL Agent it can write everywhere?
2)Most important, in network terms should I ask to the administrator to set up NAMENETWORK\NAMESERVER$ in order to read/write from the table where the package is?

Sorry...resolved. I set up a proxy with my credentials and now it's running good.

Issue with creation of SSIS package - reading from XML

Good Morning,
having a slight difficulty here and more than this, am afraid solution is pretty straight forward. I am trying to read an XML-file and save the rows to a CSV file (late ron it should be sent to SQL-database).
Am having this input XML
<?xml version="1.0" encoding="utf-16"?>
<DataSet>
<xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="ROW">
<xs:complexType>
<xs:sequence>
<xs:element name="COLUMN" type="xs:short" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
<diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
<NewDataSet>
<ROW diffgr:id="ROW1" msdata:rowOrder="0">
<COLUMN>1</COLUMN>
</ROW>
<ROW diffgr:id="ROW2" msdata:rowOrder="1">
<COLUMN>2</COLUMN>
</ROW>
</NewDataSet>
</diffgr:diffgram>
</DataSet>
but when running the SSIS-package, I get this
no errors are shown, but also no rows are written/processed.
Why is nothing read here?

by the way, when I split the schema and the XML data, having those 2 files
data.xml
<?xml version="1.0" encoding="utf-8"?>
<NewDataSet>
<ROW >
<COLUMN>1</COLUMN>
</ROW>
<ROW >
<COLUMN>2</COLUMN>
</ROW>
</NewDataSet>
schema.xsd
<?xml version="1.0"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="NewDataSet">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" name="ROW">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="COLUMN" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
then result is fine

Assembly issue + SSIS package

Hi All,
We have added "DataWarehouseLibrary.dll" under C drive of our server, as we are usiing that assembly in our SSIS package Script Task Editor -->> Edit Script -->> Add Reference.
Now we are executing that package through an SSIS Agent Job, but we are getting below error:-
SLoad (SSIS package) encountered the following error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'DataWarehouseLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=959d9ef6c647261e' or one of its dependencies. The system cannot find the file specified.
File name: 'DataWarehouseLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=959d9ef6c647261e'
at SLoad.csproj.ScriptMain.Main()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
Any body can help me out.
What and where I'm doing wrong, to execute this package successfully.
Thanks
Kumar
KG, MCTS

OLD Server (which has same package running through the Job), has VS 2008 details as:-
Microsoft Visual Studion 2008
Version 9.0.30729.1 SP
Product Details as:-
Microsoft SQL Server Integration Services Designer
Version 10.0.4000.0 ((Katmai_PCU_Main).100916-1939 )
NEW Server (which is also same package running through the Job), has VS 2008 details as:-
Microsoft Visual Studion 2008
Version 9.0.30729.1 SP
Product Details as:-
Microsoft SQL Server Integration Services Designer
Version 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
Does this will make any difference?
Thanks
Kumar
KG, MCTS

Unicode and non-unicode string data types Issue with 2008 SSIS Package

Hi All,
I am converting a 2005 SSIS Package to 2008. I have a task which has SQL Server as the source and Oracle as the destination. I copy the data from a SQL server view with a field nvarchar(10) to a field of a oracle table varchar(10). The package executes fine
on my local when i use the data transformation task to convert to DT_STR. But when I deploy the dtsx file on the server and try to run from an SQL Job Agent it gives me the unicode and non-unicode string data types error for the field. I have checked the registry
settings and its the same in my local and the server. Tried both the data conversion task and Derived Column task but with no luck. Pls suggest me what changes are required in my package to run it from the SQL Agent Job.
Thanks.

What is Unicode and non Unicode data formats
Unicode :
A Unicode character takes more bytes to store the data in the database. As we all know, many global industries wants to increase their business worldwide and grow at the same time, they would want to widen their business by providing
services to the customers worldwide by supporting different languages like Chinese, Japanese, Korean and Arabic. Many websites these days are supporting international languages to do their business and to attract more and more customers and that makes life
easier for both the parties.
To store the customer data into the database the database must support a mechanism to store the international characters, storing these characters is not easy, and many database vendors have to revised their strategies and come
up with new mechanisms to support or to store these international characters in the database. Some of the big vendors like Oracle, Microsoft, IBM and other database vendors started providing the international character support so that the data can be stored
and retrieved accordingly to avoid any hiccups while doing business with the international customers.
The difference in storing character data between Unicode and non-Unicode depends on whether non-Unicode data is stored by using double-byte character sets. All non-East Asian languages and the Thai language store non-Unicode characters
in single bytes. Therefore, storing these languages as Unicode uses two times the space that is used specifying a non-Unicode code page. On the other hand, the non-Unicode code pages of many other Asian languages specify character storage in double-byte character
sets (DBCS). Therefore, for these languages, there is almost no difference in storage between non-Unicode and Unicode.
Encoding Formats:
Some of the common encoding formats for Unicode are UCS-2, UTF-8, UTF-16, UTF-32 have been made available by database vendors to their customers. For SQL Server 7.0 and higher versions Microsoft uses the encoding format UCS-2 to store the UTF-8 data. Under
this mechanism, all Unicode characters are stored by using 2 bytes.
Unicode data can be encoded in many different ways. UCS-2 and UTF-8 are two common ways to store bit patterns that represent Unicode characters. Microsoft Windows NT, SQL Server, Java, COM, and the SQL Server ODBC driver and OLEDB
provider all internally represent Unicode data as UCS-2.
The options for using SQL Server 7.0 or SQL Server 2000 as a backend server for an application that sends and receives Unicode data that is encoded as UTF-8 include:
For example, if your business is using a website supporting ASP pages, then this is what happens:
If your application uses Active Server Pages (ASP) and you are using Internet Information Server (IIS) 5.0 and Microsoft Windows 2000, you can add "<% Session.Codepage=65001 %>" to your server-side ASP script.
This instructs IIS to convert all dynamically generated strings (example: Response.Write) from UCS-2 to UTF-8 automatically before sending them to the client.
If you do not want to enable sessions, you can alternatively use the server-side directive "<%@ CodePage=65001 %>".
Any UTF-8 data sent from the client to the server via GET or POST is also converted to UCS-2 automatically. The Session.Codepage property is the recommended method to handle UTF-8 data within a web application. This Codepage
setting is not available on IIS 4.0 and Windows NT 4.0.
Sorting and other operations :
The effect of Unicode data on performance is complicated by a variety of factors that include the following:
1. The difference between Unicode sorting rules and non-Unicode sorting rules
2. The difference between sorting double-byte and single-byte characters
3. Code page conversion between client and server
Performing operations like >, <, ORDER BY are resource intensive and will be difficult to get correct results if the codepage conversion between client and server is not available.
Sorting lots of Unicode data can be slower than non-Unicode data, because the data is stored in double bytes. On the other hand, sorting Asian characters in Unicode is faster than sorting Asian DBCS data in a specific code page,
because DBCS data is actually a mixture of single-byte and double-byte widths, while Unicode characters are fixed-width.
Non-Unicode :
Non Unicode is exactly opposite to Unicode. Using non Unicode it is easy to store languages like ‘English’ but not other Asian languages that need more bits to store correctly otherwise truncation will occur.
Now, let’s see some of the advantages of not storing the data in Unicode format:
1. It takes less space to store the data in the database hence we will save lot of hard disk space.
2. Moving of database files from one server to other takes less time.
3. Backup and restore of the database makes huge impact and it is good for DBA’s that it takes less time
Non-Unicode vs. Unicode Data Types: Comparison Chart
The primary difference between unicode and non-Unicode data types is the ability of Unicode to easily handle the storage of foreign language characters which also requires more storage space.
Non-Unicode
Unicode
(char, varchar, text)
(nchar, nvarchar, ntext)
Stores data in fixed or variable length
Same as non-Unicode
char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks
nchar: same as char
varchar: stores actual value and does not pad with blanks
nvarchar: same as varchar
requires 1 byte of storage
requires 2 bytes of storage
char and varchar: can store up to 8000 characters
nchar and nvarchar: can store up to 4000 characters
Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple
encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."1
Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world.
All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred
from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.
https://irfansworld.wordpress.com/2011/01/25/what-is-unicode-and-non-unicode-data-formats/
Thanks Shiven:) If Answer is Helpful, Please Vote

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

Excel Connection Manager suddenly can no longer connect to Excel from SSIS package

During the last 3 months, I used 32 bit SSIS 2008 (v 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results (reports) to an excel spreadsheet. Each report is written to a different
tabbed sheet in the same spreadsheet. The package was working just fine until May 9 2013, when suddenly every single Data Flow task with an Excel Destination displayed error icons and raised the following
error message when opening the Advanced Editor:SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at <DataFlow task name>: SSIS
error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager <Excel connection Manager> failed with error code 0xC0202009. There may be error messages posted before this with more
information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)Originally the error message reported that the Error Code was "0x8000FFFF", but I can't seem
to reproduce that error code since. Now I am only getting the above error message.From the time I created the original package (when it worked fine) until now, I have been using the same computer, writing to a (32 bit) 2010 Excel file in
a local folder. The filename and location have not changed. The ConnectionString has not changed. The Connnection String I am using is Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion Results_dt01.xlsx;Extended Properties="EXCEL
12.0 XML;HDR=YES;". Now an attempt to create and test a NEW Connection Manager yields me this error. "Test connection failed because of an error in initializing provider. Unspecified error.",  whereas before I had
no problems creating a new connection manager.I checked a second SSIS package, which I also built during the past 3 months, which loads multiple sheets from multiple Excel files to a SQL Server 2008 database holding table. It uses the same
ACE OLE DB 12.0 connection to load the Excel speadsheets and this package continues to work fine on the same workstation.In desparation, wondering if the Microsoft ACE OLE DB 12.0 driver had become corrupt (even though the second package
was raising no errors), I did download and install the Microsoft ACE OLE DB 12.0 driver.  That did not solve my problems with the first package.I need to get this package running again ASAP as it is targeted for UAT testing in a
matter of days. Any help with this issue would be greatly appreciated!

I submitted this issue above and now I am having the same problem again. I am using the same local computer, the same operating system (WinXp v 5.1.2600 SP3 Build 2600) as originally described. I am working with the same SSIS package that
writes multiple query results (reports) to an excel spreadsheet. This package has been successfully executed multiple times, but now I am suddenly getting the same error as follows:
Error at 1ConversionContacts [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
Error at DFlow Write soft deleted duplicate claims to Excel sheet [Excel Destination - write duplicate claim nbrs that have been removed to Excel [61]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
The package will not run because of these multiple errors (multiple because it occurs on every single excel destination in the package).
I have Run64BitRuntime set to false on the project. I have triple checked that the excel file name (which I created and can access) exists with the correct name in the correct path, which is local on my machine. The file is the same file in the same
location as when the package worked. I am running the SSIS service under my own network login, as I was when the package worked. I have been consistently getting this same error whenever I change my network password without updating the password
in the SSIS service, but I have triple verified that the service is using my latest password. If I try to open and edit the Excel Destination in any DataFlow task I get the same error. I can successfully create a new Excel Connection Manager pointing
to the same excel file. However if I try to assign the newly created Excel Connection Manager in the data flow, I cannot activate the drop down to choose the Excel sheet without getting an 'Unspecified error' message. I then swapped out
the file with its template version, and ensured the name was updated as correct. I still get the same errors.
Oh, and the SSIS package is extracting data from a SQL Server 2008 database with an ADO.net Connection Manager using Windows authentication. I have no problems with the SQL Server connection, it has always worked and still does. It is only
the connection to excel output file which is locally stored on my machine.
Has anyone got any suggestions for me?

Issue with SSIS Custom Components - 64 bit SQL 2012

Hello All,
Our SSIS packages built on SQL 2008 R2 make use of some custom components. These custom components are installed as part of an MSI. The dll's are copied over to the Windows/assemble [GAC Folder] and also to the Program Files(x86)/SQL Server/110/DTS/* folder.
The installation does not copy the dll's to the 64 bit program files folder.
X:\Program Files\Microsoft SQL Server\110\DTS
These packages are executed via SQL Agent jobs on a 64 bit SQL server and there does not seem be any issue.
Now we are upgrading our servers to SQL 2012 and we have a new installer for the custom components as well. The new custom components use .NET Framework 4.0 and when installed the dll files get copied over to the Ms.NET 32 bit runtime GAC folder and also
to the SQL Server DTS Folder in x86. The upgraded packages work only when we set the runtime mode to 32 bit. The packages successfully executes within the 32 bit dtexec utility, but when we try to run the same package using a 64 bit dtexec utility the
process errors out with a component failed to load message. The package moves data between two SQL Server instances.
The custom components have always been built for 32 bit runtime. I can run a older package through the dtexec utility (from the 64 bit folder in program files) and it does work without any issues. After the upgrade the package will only execute on
a 32 bit utility. can someone help me understand this issue?
Regards, Dinesh

Thank you Arthur.
i think we got the answer as well, as the .NET framework 3.0 installer copied the files over to the C:\windows assembly the dtexec utility [32 bit/64 bit] was able to load the components.
Now with the new installer the files are copied to specific runtime gac folders as Arthur has mentioned. The 64 bit utility does not find the dlls in the GAC whereas the 32 bit version will find them.
Regards, Dinesh

How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

Hi ALl,
I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
. This package runs fine if i click the server connection properties type the password and save it.
Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying
"Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
Can someone please help me with any suggestions on how to do this?
I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
So, If someone can please throw any suggestions or ideas on this it would be great.
Thanks

You need to add password as a config item and set it from the file source or sql table
see this as an example
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Getting error while trying to upload the data in excel from SSIS package through sql agent job

We are getting below errors.
Error:
The Microsoft Jet database engine cannot open the file '\\serversdev\Documents\QC Files\Prod.xls'. It is already opened exclusively by another
user, or you need permission to view its data.
Please suggest ASAP
Regards,
Ramu
Ramu Gade

Hi Dikshan Gade,
According to your description, you want to upload data from excel to database, when you call ssis package through SQL Server Agent job, you got the error message.
To troubleshoot the problem, please refer to the following steps:
Validate that the account has permissions on the file and the folder.
Verify that the file and the data source name (DSN) are not marked as Exclusive.
Make sure SQL Server Agent Services service account has the permission to access the database.
We can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues. For more information about the issue, please refer to
the following KB article:
http://support.microsoft.com/kb/306269
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

CDC Issue in SSIS Package

Similar Messages

Maybe you are looking for