SSIS 2012 job hangs dataflow task

hi all,
i have 2 data flow tasks in a package that run based on parameters.
the package is being run as a sql agent job using catalog execution model.
the job sometimes hangs without reason. also, when i looked at the target sql tables, only few rows have been loaded into the 2 target tables and stopped when the job hanged,
the data flow tasks loads data from source into a target sql table.please advice on why the job hangs, are there issues with the catalog model of ssis 2012 that is causing this?

Perhaps this info (scripts) somehow shed light on the problem
http://sqlblog.com/blogs/davide_mauri/archive/2014/07/23/ssisdb-analysis-script-on-gist.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Similar Messages

Is it a bug - SSIS 2012 ReadOnlyVariables in Script Task doesn't work

It's very weird when I use the ReadOnlyVariables in SSIS 2012 Script Task, it doesn't work at all!!! And I never notice this change before, but everything in 2008 R2 is fine! Is it a bug in SSIS 2012 ?
All the variables I set them to "ReadOnlyVariables"
In scripts - I assigned some values from system variables.
String PackageName = Dts.Variables["System::PackageName"].Value.ToString();
DateTime CurrentDate = (DateTime)Dts.Variables["System::StartTime"].Value;
// User Defined Variables
Dts.Variables["User::PV_CURRENT_DATE"].Value = CurrentDate;
Dts.Variables["User::PV_YEAR"].Value = CurrentDate.Year;
Dts.Variables["User::PV_MONTH"].Value = CurrentDate.Month;
Dts.Variables["User::PV_DAY"].Value = CurrentDate.Day;
Dts.Variables["User::PV_PACKAGE_NAME"].Value = PackageName;
Execute the package, it works !
The only thing I can make it as SSIS 2008 R2 does is to change the ReadOnly for each variables.
Then you will get the error.
Why do we need this feature here but not to use the ReadOnlyVariables in script task ?
Please vote if it's helpful and mark it as an answer!

I can reproduce it as well. Feels like a bug...
Locking the variable for read in code has the same effect:
public void Main()
// Lock variable for read
Dts.VariableDispenser.LockForRead("User::myStringVariable");
// Create a variables 'container' to store variables
Variables vars = null;
// Add variable from the VariableDispenser to the variables 'container'
Dts.VariableDispenser.GetVariables(ref vars);
// Now try giving it a new name
vars["User::myStringVariable"].Value = "new value";
// Release the locks
vars.Unlock();
Dts.TaskResult = (int)ScriptResults.Success;
For reference:
https://connect.microsoft.com/SQLServer/Feedback/Details/991697
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

Ssis job hangs

i am using ssis 2012 jobs hang randomly,
today, when i ran the profiler, i found the below, please please guide on how to prevent hangs
exec sp_executesql N'
        --Preparing to access the Catalog object
        DECLARE @t_catalogs TABLE (
        Name sysname COLLATE SQL_Latin1_General_CP1_CI_AS,
        EncryptionAlgorithm nvarchar(256) COLLATE SQL_Latin1_General_CP1_CI_AS,
        SchemaVersion int,
        SchemaBuild nvarchar(256) COLLATE SQL_Latin1_General_CP1_CI_AS,
        OperationLogRetentionTime int,
        MaxProjectVersions int,
        OperationCleanupEnabled bit,
        VersionCleanupEnabled bit,
        ServerLoggingLevel int,
        OperationLogNumberOfRecords int,
        VersionLogNumberOfRecords int)
        IF DB_ID(''SSISDB'') IS NOT NULL
        BEGIN
        INSERT INTO @t_catalogs VALUES(
        ''SSISDB'',
        (SELECT [property_value] FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''ENCRYPTION_ALGORITHM''),
        (SELECT CAST([property_value] AS INT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''SCHEMA_VERSION''),
        (SELECT [property_value] FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''SCHEMA_BUILD''),
        (SELECT CAST([property_value] AS INT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''RETENTION_WINDOW''),
        (SELECT CAST([property_value] AS INT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''MAX_PROJECT_VERSIONS''),
        (SELECT CAST([property_value] AS BIT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''OPERATION_CLEANUP_ENABLED''),
        (SELECT CAST([property_value] AS BIT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''VERSION_CLEANUP_ENABLED''),
        (SELECT CAST([property_value] AS INT) FROM [SSISDB].[catalog].[catalog_properties] WHERE [property_name] = N''SERVER_LOGGING_LEVEL''),
        (SELECT COUNT(operation_id) FROM [SSISDB].[catalog].[operations]),
        (SELECT COUNT(object_id) FROM [SSISDB].[catalog].[object_versions])
        END
SELECT
''IntegrationServices[@Name='' + quotename(CAST(SERVERPROPERTY(N''Servername'') AS sysname),'''''''') + '']'' + ''/Catalog[@Name='' + '''''''' + REPLACE((SELECT Name from @t_catalogs), '''''''', '''''''''''') + '''''''' + '']'' +
''/CatalogFolder[@Name='' + '''''''' + REPLACE(folders.[name], '''''''', '''''''''''') + '''''''' + '']'' + ''/ProjectInfo[@Name='' + '''''''' + REPLACE(projects.[name], '''''''', '''''''''''') + '''''''' + '']'' + ''/EnvironmentReference[@Name=''
+ quotename(refs.[environment_name],'''''''') + '' and @EnvironmentFolderName='' + quotename(ISNULL(refs.[environment_folder_name], ''.''),'''''''') + '']'' AS [Urn],
refs.[reference_id] AS [ReferenceId],
refs.[project_id] AS [ProjectId],
refs.[reference_type] AS [ReferenceType],
ISNULL(refs.[environment_folder_name], ''.'') AS [EnvironmentFolderName],
refs.[environment_name] AS [Name],
refs.[validation_status] AS [ValidationStatus],
CAST (refs.[last_validation_time] AS datetime) AS [LastValidationTime]
FROM
[SSISDB].[catalog].[folders] AS folders
INNER JOIN [SSISDB].[catalog].[projects] AS projects ON projects.[folder_id]=folders.[folder_id]
INNER JOIN [SSISDB].[catalog].[environment_references] AS refs ON refs.[project_id]=projects.[project_id]
WHERE
(projects.[name]=@_msparam_0)and((folders.[name]=@_msparam_1)and(((SELECT Name from @t_catalogs)=@_msparam_2)and((CAST(SERVERPROPERTY(N''Servername'') AS sysname)=@_msparam_3))))',N'@_msparam_0 nvarchar(4000),@_msparam_1 nvarchar(4000),@_msparam_2 nvarchar(4000),@_msparam_3
nvarchar(4000)',@_msparam_0=N'Staging,@_msparam_1=N'Staging',@_msparam_2=N'SSISDB',@_msparam_3=servername

this is useless
Nobody would be able to repro using what you provided.
But I suspect some locking / blocking does occurs.
Suggestion: apply any missing service packs, and I typically hear this being reported on a box literally brought to its knees by the amount of tasks vs. resources available. Put Perf Counters to use and you will most likely find out that the machine is starved
on CPU and RAM thus the intermittent job hangs.
Arthur My Blog

Ssis 2012 configuration package wizard is hanging

Hi,
I am trying to edit the dtsconfig package xml file in SSIS 2012 VS envoirnemnt and the wizard is hanging up for minutes until I need to close VS.
Has anyone experienced this problem and what can be done to solve other than editing the XML file directly.

Hi danisroyi2 and Mike Yin Pactera
I am also experiencing this issue.
Edit an existing package configuration and click next.
It hangs on the loading properties form until you eventually (I have waited for over half an hour) have
to kill the process in task manager.
thanks

HELP: SSIS 2012 - Execute SQL Task with resultset to populate user variables produces DBNull error

I am experiencing an unexplainable behavior with the Execute SQL Task control in SSIS 2012. The following is a description of how to simulate
the issue I will attempt to describe:
1. Create a package and add two variables User::varTest1 and User::varTest2 both of String type with default value of "Select GetDate()"
for each, have shown this to not matter as the same behavior occurs when using a fixed string value or empty string value.
2. Add a new Execute SQL Task to the control flow.
3. Configure an OLE DB connection.
4. Set SQLSourceType = "Direct Input"
5. Set the ResultSet property of the task to "Single Row"
6. In the ResultSet tab add two results as follows:
Result Name: returnvalue1, Variable Name: User::varTest1
Result Name: returnvalue2, Variable Name: User::varTest2
7. Set an expression for the SqlStatementSource property with a string value of "Select 'Test' returnvalue1, 'Testing' returnvalue2'"
The idea is that the source would be dynamically set in order to run a t-sql statement which would have dynamic values for database name
or object that would be created at runtime and then executed to set the user variable values from its resultset. Instead what occurs is that a DBNull error occurs.
I am not sure if anyone else has experienced this behavior performing similiar actions with the Execute SQL Task or not. Any help would be
appreciated. The exact message is as follows:
[Execute SQL Task] Error: An error occurred while assigning a value to variable "varRestoreScript": "The type of the value
(DBNull) being assigned to variable "User::varRestoreScript" differs from the current variable type (String). Variables may not change type during execution. Variable types are strict, except for variables of type Object.
User::varRestoreScript is the first return value. And even with the a dummy select the same result occurs. I have narrowed the issue down
to the T-SQL Statement structure itself.
The following works just fine within the execute sql task control as long as no resultset is configured for return:
"Declare @dynamicSQL nvarchar(max)
Select @dynamicSQL = name
From sys.databases
Where name = 'master'
Select atest_var1=@dynamicSQL, atest_var2='static'"
I have tried various iterations of the script above with no success. However, if I use the following derivative of it the task completes
successfully and variables are set as expected. This will not work for my scenario however as I need to dynamically build a string spanning multiple resultsets to build one of the variable values.
"Select atest_var1=name, atest_var2='static'
From sys.databases
Where name = 'master'
I have a sample package which can reproduce this issue using the above code. You can get to that through the post on www.sqlservercentral.com/Forums/Topic1582670-364-1.aspx
Scott

Arthur, the query when executed doesn't return a null value for the @dynamicSQL variable. It returns "master" as a string value. Even the following fails which implements that suggestion:
Declare @dynamicSQL as nvarchar(max)
Select @dynamicSQL = name
From master.sys.databases
Where name = 'master' -- (or any other DB name)
I believe I have found the cause of the issue. It is datatype and size related. The above script will properly set the variables in the resultset as long as you don't use nvarchar(max) or varchar(max). This makes the maximum data size for
a String variable 4000 characters whether unicode or non-unicode typed.

Byte input to Webservice Task in SSIS 2012

Hi,
I have just created a new project in SSIS 2012 and I am using a webservice task in a package.
I imported the WSDL file and I have several inputs to set to use it properly.
I put variables on the 4 first inputs that are strings with success but I have a problem with the last one.
The last one is called xmlData and is in "byte" type and I can not set it correctly.
In the XSD file I have this definition: <xsd:element
minOccurs="0" name="xmlData" nillable="true" type="xsd:base64Binary"
/>
It is supposed to contain a XML file that I have to encode in base64 and then fill the xmlData with the binary value.
To encode my XML file to base64 I use a C# task but I do not know how to declare the value and how to set it.
I do it this way:
FileStream myStream = new FileStream(@"H:\myXML.XML", FileMode.Open, FileAccess.Read);
BinaryReader reader = new BinaryReader(myStream);
byte[] fichierXML = new byte[reader.BaseStream.Length];
for (int i = 0; i < reader.BaseStream.Length; i++)
fichierXML[i] = reader.ReadByte();
reader.Close();
myStream.Close();
string xmlAsString = EncodeBytesAsBase64(fichierXML);
MessageBox.Show(xmlAsString);
// Conversion de la String en byte[]
byte[] xmlData = System.Text.Encoding.UTF8.GetBytes(xmlAsString);
Dts.Variables["User::monXmlData"].Value = xmlData;
My variable User::monXmlData is an Object and there is no problem in execution.
The C# script runs well and the webservice task too but I always get an error response for the webservice saying that my xmlData field is not correct.
I think that my base64 encoding is correct because when I copy the result in my messagebox and paste in base64 decode on a free web decoder I get my original XML text.
Is there someone who can help me please?

Thanks to all that took some time to read me.
I have finally found the solution.
The Base64 encoding is not necessary. It is automatically done by the webservice when the request is sent.
The important thing to remember is that when you have to send a "byte[]" variable, you have to use a "Object" variable as an imput for the webservice.

XML Task in SSIS 2012

Hi All,
I need help on one requirement in SSIS 2012, Please let me know for any suggestions or solution.
I have two XML files having different structure, I have to manipulate data by applying XSLT and creating single output xml. (Which needs to pass these 2 Xml files and 1 xslt to SSIS task)
In SSIS we have in-built XMLTask which will take XSLT operation of 1 xml and 1 xslt to deliver new output xml, Is there any way to pass 2 xml files and 1 xslt to get new output xml?
Thanks for any help

Hi visakh,
i have tried as you said.but still i am not able to load multiple Xml files.
I'm having a problem using the Foreach Loop container that contains an XML Task followed by a data flow task. When I run my package in the debugger,
the XML Task fails with the following errors: [XML Task] Error: An error occurred with the following error message: "Data at the root level is invalid. Line 1, position 1.". [XML Task] Error: Property "New Source" has no source Xml Text; Xml Text is either
invalid, null or empty string.
The Foreach Loop container is a file enumerator. The XML Task validates XML files using an XSD file. The XML Task SourceType is a XSLTand the Source has the variable set by the Foreach Loop (index 0). I have an XML file which I know is valid. For some reason,
the XML Task Source is not referencing the variable, set by the Foreach loop.
If I use a file connection to the existing XML file, instead of using the variable, the XML Task validates the file successfully. I believe there might be a bug in the XML Task when a variable is specified. If I disable the task and let my data flow task run,
it has no problem importing each XML file, in the directory, using an XML Source that uses the Foreach loop variable for the Source. My data flow completes correctly.
Thanks

Stored procedure fails when run from SSIS DataFlow task

I'hv a stored procedure (with dynamis SQL), taking colums names as parameters to run and returns dynamic columns in output. E.g. if I pass @ipselect = '*' it will returns all columns in output, when I pass @ipselect = 'column1, column2, column3'
,it will returns 3 columns in output.
Now I have SSIS package. I've Data Flow task in foreach loop container and it is taking parameter from client table. e.g
clientid       column name
1                        *
2                columns1,columns2,column3
3               columns1,columns2,column3,columns4,columns5,column6
4                       *
Foreach container loop through each client id and set ipselect parameter with
column name and that value is being passed to @ipselect stored procedure in Dataflow task. When there is @ipselect = '*' it runs fine ,returns all columns and write to destination. But when there is ipselect = 'columns1,columns2,column3',
it fails with below error:
[OLE DB Source [1]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E55.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E55 Description: "Column does not exist.".
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput().
The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Any suggestion or solution would be really helpful.
Thanks!!

Hi Kevin,
Just an addition. To create SSIS package programmatically, please refer to the document:
http://msdn.microsoft.com/en-us/library/ms345167.aspx
To implement dynamic column mapping through SSIS Script Component, please refer to:
http://wikiprogrammer.wordpress.com/2011/04/08/dynamic-column-mapping-in-ssis-part-1/
http://blog.quasarinc.com/ssis/best-solution-to-load-dynamically-change-csv-file-in-ssis-etl-package/
Regards,
Mike Yin
TechNet Community Support

SSIS 2012 Script Task Debugging not working (VSTA Popup but no script displayed in IDE)

Hi,
I am trying to debug 2012 SSIS Package but for some reason its not working. Basically when I run package (64bit mode) it pop up Script IDE but never brings up Script (see below). Usually when debugging of script starts it should break execution at the code.
Anybody experienced this issue with SSIS 2012 ?
Thanks,
Nayan
Visit My Blog (Home of BI Articles)

Hi,
I am trying to debug 2012 SSIS Package but for some reason its not working. Basically when I run package (64bit mode) it pop up Script IDE but never brings up Script (see below). Usually when debugging of script starts it should break execution at the code.
Anyone has clue whats going on here?
Thanks,
Nayan
My Blog |
Convert DTS to SSIS |
Document SSIS |
SSIS Tasks |
Real-time SSIS Monitoring

CDC SSIS 2012 ,CDC TASK,CDC Source,CDC Splitter

Hi,
I tried CDC in SSIS 2012 yesterday I was unable to run the hole process sucessfully
http://www.mattmasson.com/index.php/2011/12/cdc-in-ssis-for-sql-server-2012-2/?utm_source=rss&utm_medium=rss&utm_campaign=cdc-in-ssis-for-sql-server-2012-2--------------------------------------------------------------------------------
did any one tried this process
Sri.Tummala

sorry my sql server agent is turned off i have to turn it on
after turning it on i trie dto run the package it gave following errors in data flow
[CDC Source [2]] Error: "Value ILUPDATE/CE/0x00078CD5000023D20001/IR/0x00078CD5000023590002//TS/2012-05-24T14:12:15.0476569/ of CDC state User::CDC_State is not well structured. Structure must be - logicalName(required)/[CS/<cs-lsn>/](optional)[CE/<ce-lsn>/](optional)[IR<ir-start>/<ir-end>/](optional)/[TS/timestamp/](optional)[ER/<error-message>/](optional).".
[CDC Source [2]] Error: System.Exception: Value ILUPDATE/CE/0x00078CD5000023D20001/IR/0x00078CD5000023590002//TS/2012-05-24T14:12:15.0476569/ of CDC state User::CDC_State is not well structured. Structure must be - logicalName(required)/[CS/<cs-lsn>/](optional)[CE/<ce-lsn>/](optional)[IR<ir-start>/<ir-end>/](optional)/[TS/timestamp/](optional)[ER/<error-message>/](optional).
at Attunity.SqlServer.CDCSrc.CdcSourceComponent.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on CDC Source returned error code 0x80131500. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Sri.Tummala

SSIS 2012 package runs under SSDT but fails with permission error from SSMS

I have a simple package that pulls data from a text file located on a Windows file server that runs successfully from SSDT on my client.
However, when deployed and running the package via SSMS from the client, the package fails with a permission error, with the error stating that the data file could not be opened.
I have done some investigation and have seen some info that states that a package run from SSMS runs under the account on which you are logged on to the machine, which I would have thought is correct. This is therefore the same account when running from
SSDT (which works) and I can see from the SSIS Report that the 'Caller' is stated as my account, so if this is the case why isin't the package working.
I've also seen an MSDN forum answer which stated the opposite that the package when run from the IS Catalog in SSMS doesn't run under the account on which the client is logged on with, which is the opposite of the above, but doesn't indicate which account
it is using.
So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?
If it is the account on which you are logged onto the client running SSMS, why is it not working when the account has the necessary permissions (as provent when running from SSDT) ?

I am aware it's using my account and not one of the service. There's nothing in the posts above which suggests I'm using the service account. I don't know why people keep assuming that I'm running the package from a job. I've never stated that in any of
the posts I'm running the package from a job. It's been made quite clear I'm running the package from the IS Catalog on SSMS:
"This is simply selecting a package from the IS Catalog, right-clicking and selecting Execute package.", as per the Nov 18 post, and in the original post "....So what account is being used to run SSIS 2012 packages from the IS catalog from
within SSMS".
Just to be clear, the package is NOT being run from a job. It's using the Execute package option when selecting the package within SSMS from the IS Catalog and it's running under the account on which I am logged on to my client.
Please read carefully. I was just answering your question "So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?" and stating that you where right and that it uses your account to run the package
when you execute a package manually from the Catalog and that you can prove that by logging the system variable.
A good suggestion about using a share in the task to map the drive and I will try this. I would find it strange that SSMS requires this mapping whereas SSDT does not though.
Ok let us know your findings. If it doesn't work you can also test it with a password and username:
net use f: \\financial\public yourpassword /user:username
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

How to deploy and execute SSIS 2012 packages when only SSDT is installed

Hi, I am facing a weird situation where we did an upgrade for visual studio to vs 2102 on all the dev machines and as part of that moved to SSDT from BIDS but all the database is still SQL Server 2008 R2. Now I have a few SSIS 2012 packages which I cannot
schedule & run because DTEXEC.exe is not compatible and I get all sorts of version & “Package Load error 0xC0010014 in CPackage::LoadFromXML” error even though I set it up in 32-bit mode and was trying to save it to msdb. I knew I will not be
able to schedule this as a job in SQL Server Agent but even saving the package does not work.
Thanks in advance............
Ione

I doubt 2012 ssis packages are backwards compatible with 2008r2. 2008r2 doesn't know anything about the project deployment model and i'm sure there's new tasks and connectors in 2012 so the package deployment model ssis packages won't work either.
You will need a sql 2012 integration services service installed and running somewhere. You need this to execute your 2012 packages
Jakub @ Adelaide, Australia Blog

SSIS 2012 Scheduled SSIS package fail to start – Execution timed out

Hi
I am currently running into an issue that seem to have a live Connect issue raised for it. The following is the link to the connect issue https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution
There is also a blog post that explains this issue in more detail, however the solution
it provides does not work all the time and I am very reluctant to create custom stored procedures in the SSISDB. http://speaksql.wordpress.com/2013/06/27/ssis-2012-fail-to-start-execution-timed-out/
Just to give some more background. When scheduling 10 or more, in my case I scheduled 14, SQL Server Agent Jobs all executing a package in the SSIS Catalog and all kicking off on exactly the same time about 10% to 20% of these jobs fail stating one of the
following error messages:
The operation failed because the execution timed out. Source: .Net SqlClient Data Provider Started: 12:20:01 Finished: 12:20:07 Elapsed: 5.797 seconds. The package execution failed. The step failed.
Description: Transaction (Process ID 66) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Source: .Net SqlClient Data Provider Started: 14:06:48 Finished: 14:06:53
Elapsed: 4.719 seconds. The package execution failed. The step failed.
This timeout takes place both when using TSQL to start the package in the Job or when the step in the Job is set to start the package as an Integration Services Package.
Steps to recreate this:
1. Create one SSIS package that simply executes for around a minute. For example you can use an Execute SQL Task and simply execute the following TSQL "WAITFOR DELAY '00:01:00'"
2. Create 14 SQL Server Agent Jobs each executing the same package and schedule all of them to run at the same time.
3. Watch the execution of the jobs take place and note the failures. (This does not always happen and you might get one run in which everything executes without a problem. The next run might have 6 or 7 of the jobs fail.)
You can also create 14 different SSIS packages, one for each job, and the result is the same.
I am running on SQL 2012 SP1 CU4. Windows Server 2012 R2 patched to the lastest patch level.
This issue does not happen when the packages are deployed to the SSIS Package Store the way that it was done in SQL2008 and before. It only occurs when the SSIS packages are deployed to the SSIS Catalog.
Any help or feedback on this would be greatly appreciated.
Kind Regards,
Christo Olivier

Hi Tom
Thank you for the fast response. I went and increased the value by 1024KB instead of the initial
512KB. Unfortunately this seems to only alleviate the issue but does not stop it from occurring. It
is happening much less often now but still occurring intermittently.
Regards,
Christo

Background Job hangs!

Hello Friends,
I am encountering a problem with background jobs which has driven me crazy.
The background job hangs and when I try to debug it using the JDBG command the results are surprising.
When the program control reaches a particular PERFROM statement, then no matter what command I give (F5, F6 or if I double click on any of the variables) it hangs. When I press F5, it should atleast go in to the corresponding FORM, and hang during some processing or it should go into an infinite loop but this is not the case. The system hangs even when I press F5 on the PERFORM. The FORM routine exists in the program, so that possibility is ruled out.
Actually the job processes records of a custom table, this problem starts with a particular record and if I skip the processing of this record then it happens with almost all the records after this one. Also, this does not happen every time the job is run, but whenever it does, it starts with a particular record.
When the system hangs then even if I try to stop the transaction by right clicking on the task bar then it has no effect, the only way to close the session is by using the 'Windows task manager'.
I tried transaction SM50, but there were no changes on that screen for this particular session indicating that it has hanged.
Please let me know if you require any more information.
Thanks and Regards,
Haseeb.

Hi,
Debug it in Sm66.
kishore.

SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

Hi,
This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
So far I have installed
http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
2012 release.
Here is the detail of error message:
TITLE: Package Validation Error
Package Validation Error
ADDITIONAL INFORMATION:
Error at Data Flow Task [Excel Source [2]]: 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.
Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Task: There were errors during task validation.
Error at Package [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".
(Microsoft.DataTransformationServices.VsIntegration)
Here are my environment details:
SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
Services Project2\Integration Services Project2\Package.dtsx.
Does this kind of Shared drives have any impact to give this issue?
Thanks in advance!
Ketan
P.S.: I had look at this forum question -->
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

Hi Arthur,
Thanks for your response.
Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
1) Some times excel source files cannot be parsed by excel source connection manager.
2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage while destination mapping.
3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file. <-- For
this we tried IMEX setting also
4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
Do you think it is advisable to convert Excel into CSV or Flat file.
Thanks,
Ketan

SSIS 2012 job hangs dataflow task

Similar Messages

Maybe you are looking for