BIDS 2008 R2 freezes on large SSIS package when attempting to browse local variable

Hi,
When I set a break point on a control component within a large package and then attempt to watch local variables BIDS freezes. I then have to end BIDS using Task Manager.
So whilst debugging I view local variables the following way; -
When I try and expand the following variables tree BIDs freezes. The Task Manager on my desktop reports that my desktop where I am running BIDs is 80% idle.
Any help would be greatly appreciated.
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Hi Arthur,
Yes ... but if I am going to try and persuade my client to buy me a new laptop or upgrade my existing laptop to enable me to run BIDs against their servers I need to be more specific.
My current laptop has; -
Windows 7 Professional 64 Bit,
8 GB RAM,
Intel (R) Core (TM) i7-3630QM CPU @2.40Ghz
A Solid state drive with 80Gb free space.
To be honest it's the best laptop a client has ever loaned me. However the SSIS package which triggers the freeze is particularly large in terms of number of variables and size of control flow.
Whilst the freeze occurs as mentioned above the
Windows Task Manager reports; -
System Idle Process is set to 90+%
Memory usage set to 3.6Gb
Resource Monitor reports disk activity at virtually 0.
I wonder if there is an internal cap on resources within BIDs?
Any further help would be greatly appreciated.
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Similar Messages

Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

Hello,
I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
0 The package executed successfully.
1 The package failed.
3 The package was canceled by the user.
4 The utility was unable to locate the requested package. The package could not be found.
5 The utility was unable to load the requested package. The package could not be loaded.
6 The utility encountered an internal error of syntactic or semantic errors in the command line.
Details:
I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
Here I receives error code 1.
Can anyone help me to resolve this issue please?
Thanks in advance!
CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
@strPackage nvarchar(100)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
DECLARE @cmd VARCHAR(8000)
DECLARE @Result int
DECLARE @Environment VARCHAR(100)
SELECT @Environment = Waarde
FROM Sys_Settings
WHERE Optie = 'Omgeving'
--print @Environment
SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
SET @cmd = 'dtexec /SQL ' + @strPackage + ' /SERVER "w2250\NGSQLSERVER" /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
--print @cmd
EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
--print @Result
END

It has something to do with the security.
E.g. cmdshell is not enabled or the caller has not rights over the package.
There could be a syntax error, too.
I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
sp_start_job <job name>
Arthur
MyBlog
Twitter

Schedule SSIS packages as job in SQL Server Agent errors

Hi, I am using SQL Server 2008 R2 and created few SSIS packages and schedule them using SQL Server Agent and every time I try to schedule packages via SQL Server Agent my jobs keep failing. I am using domain/ione as the owner and when I invoke the job on
ServerA let's say and the job gets executed by domain/ServerA$ and fails as it does not have enough privileges. How do I fix this issue firstly without the proxy and why is the job being executed by domain/ServerA$ when the owner & user who invokes
it is domain/ione?
Thanks in advance............
Ione

Hi Ione,
The owner of any SQL jobs should be SA or any other non-expiring account
If you do not want the proxy used, then add the needed priveleges.
The owner of the job is one, the SSIS step gets executed by the account the Agent is running under.
Arthur
MyBlog
Twitter

SSIS packages to update dimensions

We are having a technical problem with dimension members refreshing after an insert of a new member into the mbr table through an SSIS package
When a new record is inserted into the mbr table, using a sql insert statement and a full process of the application occurs, that member is viewable in Current view BPC Excel after the dimension members are refreshed. However, the new member is not viewable on the Current View of BPC Web, until an individual process of the dimension occurs via BPC Administration (i.e. not a full process of the application).
Do you now of a way to process dimensions rather than applications from ssis tasks
and do you know what SQL layer process is required to get the web POV updated

Wrong forum. Refer thread - SAP Business Planning and Consolidation Topics (BPC)

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

SSIS PACKAGE MIGRATION FROM 2005 to 2008 - Script task/component errors

HI All,
We have to migrate ssis packages (about 300) from ssis 2005 to 2008 .
1. I understand that the major concern is regarding the script component/tasks.
I searched a lot about this and also consulted with many friends , all of them are aware of this issue but not able to provide what could be the issues and the solution.
Can some one help me with the common script issues that can happen during migration and the solution for the same.
2. I do have one more question.
As per my understanding given in the below link
http://blogs.msdn.com/b/mattm/archive/2008/03/21/package-upgrade-wizard.aspx
there is this part which says ...
Once the packages have been chosen, the next page asks you to pick the output location. This can be:
Same as the source location
File System
SSIS Service (Package Store)
SQL Server
Does this mean I can deploy in sql server directly on fly while upgrading ?
Any help highly appreciated .
Regards
Praveen..

Hi Praveen,
Question 1: The error may occur if there are duplicate input columns in the Script Task/Component or the current user cannot access the C:\Windows\Temp directory. Except for the link provided by SanBhaumik, you can also refer to the following
threads:
http://www.sqlservercentral.com/Forums/Topic811208-148-1.aspx
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5c11eb57-59d6-4f81-bfdc-13bd6489a0ac/sql-server-2008-ssis-package-script-component-error?forum=sqlintegrationservices
Question 2: We can directly save the package to the File System, SSIS Package Store, or SQL Server by selecting the proper destination during the package upgrade. However, this operation is not equal to the package install operation identically.
For example, if we have enabled package configurations for a package, the package configurations won’t be upgraded or installed during the package upgrade.
Regards,
Mike Yin
TechNet Community Support

SSIS package runs from BIDS and by Executing package, but failing with Job

I have SQL Serve 2012 SSIS. I have problems to run from SQL Server Agent Job.
Steps runs SSIS package without configuration file. Package Run64BitRuntime is False in BIDS.
Package is runned by SQL Server Agent Service Account.
Server does not have Office 2010/2013 installed. Should it be installed?
ERROR1:
Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered.
If the 64-bit driver is not installed<c/> run the package in 32-bit mode.
ERROR2: (here SSIS package is trying to import XML source, but cannot file file)
Description: An error occurred with the following error message: "Could not find file 'D:\Integration\Metadata\'.".
Kenny_I

Hi Kenny,
It seems like you are using Excel as source file right? If yes, then please follow below steps:
Edit the job step and Check the option: Use 32 bit run time. Below is the screenshot for the same.
Please let me know for any questions.
Thanks, Madhu

SSIS package Corrupted - Connection element is not found - Visual Studio 2008

Some body help me...
last week my senior give me a SSIS package, but when I open in visual studio 2008 there is pop up like this.
TITLE: Microsoft Visual Studio
There were errors while the package was being loaded.
The package might be corrupted.
See the Error List for details.
BUTTONS:
OK
and this is the description of
Error   1   Error loading KIBB_INVC_IS.02.dtsx: The connection "{A9C72380-F326-44BF-A7CB-B8C7E9103F01}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
    C:\Users\CYH\Documents\Visual Studio 2008\Projects\IS\IS\KIBB_INVC_IS.02.dtsx   1   1
Error   10   Validation error. SheetValue Insertion Error Log Execute SQL Task: Connection manager "{A9C72380-F326-44BF-A7CB-B8C7E9103F01}" does not exist.     KIBB_INVC_IS.02.dtsx   0
0
Error   11   Validation error. SheetValue Insertion Error Log : There were errors during task validation.     KIBB_INVC_IS.02.dtsx   0   0
Error   12   Validation error. Data Flow Task: SCB_IB_IDS 05: The connection "{A9C72380-F326-44BF-A7CB-B8C7E9103F01}" is not found. This error is thrown by Connections collection when the specific connection element
is not found.     KIBB_INVC_IS.02.dtsx   0   0
if some body know this problem, please help me to resolve my problem :(

It is due to a connection manager being deleted.
Oftentimes fixable by introducing it back. Sometimes the package even runs successfully even w/o it.
But if you can create a new package anew.
Arthur My Blog

Getting error after enabling the Transaction in SSIS package in Windows Server 2008 R2 Standard machine

Hi,
I created a package with "Execute SQL Task and Data Flow Task". I am able to execute successfully in my server having
"Windows Server 2008 R2 Standard" Operating System.
But after enabling the Transaction in my SSIS Package I am not able to execute it. It is giving error. The same package is running in my local machine with Transaction enabled on
Windows 7 Operation System.
The error which I got in my server after enabling the Transaction is
"The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D025
"The partner transaction manager has disabled its support for remote/network transactions.". End Error "
I search with this error message in google and found some solutions in the following links
http://social.msdn.microsoft.com/Forums/en-US/7172223f-acbe-4472-8cdf-feec80fd2e64/the-partner-transaction-manager-has-disabled-its-support-for-remotenetwork-transactions
http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx
http://support.microsoft.com/kb/817064
But none of the above solution is not working. Kindly help me to resolve this issue.
Thanks in Advance.
Sridhar

Hi Sridhar,
Please compare the DTS settings on the Windows 7 computer and the Windows Server 2008 R2 computer and make sure they are identical. Make sure the “Allow Inbound” and “Allow Outbound” options are check, and pay attention to the authentication mode as
well.
Besides, make sure both Distributed Transaction Coordinator (TCP-In) and Distributed Transaction Coordinator (TCP-Out) rules in Firewall are enabled.
If the issue persists and there are any security/anti-virus software, temporarily disable the security/anti-virus software and check the issue again.
Regards,
Mike Yin
TechNet Community Support

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
There are four steps in the package deployment process:
    The first optional step is optional and involves creating package
configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
    The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy
    The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
    The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

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."<sup>1</sup>
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

Run sql 2008 ssis package into sql server 2012 machine

Hello,
I have created a ssis package in sql server 2008 and use a job to execute it pointing to databaseA. works fine.
Then, I place that package into a sql server 2012 machine and use a job to execute it in the same database, databaseA.
The error I get is something like:
can not use the old version in the new version machine.
Is this really the case or am I doing something wrong please?

Hi Arkiboys,
Arthur is right that the error occurs because the SSIS 2008 package cannot be upgraded to SSIS 2012 package. When the SSIS 2008 package is called by SSIS 2012 dtexec utility tool, the package will be upgraded temporarily and the changes won’t be saved. Since
your current SSIS 2008 package cannot be upgraded automatically, you can create the package from scratch in SSDT installed by SQL Server 2010. Another option isto open the SSIS 2008 package in SSDT or add the package to a SSIS 2012 project, then the upgrade
will be performed automatically. Then, you can check the error message during the upgrade, which may help you to find the tasks/components that cause the upgrade failure. In this way, you can remove the tasks/components in question from the SSIS 2008 package
and then upgrade the package, and then add the tasks/components in question in SSDT 2010.
Regards,
Mike Yin
If you have any feedback on our support, please click
here.
Mike Yin
TechNet Community Support

Error in SSIS Package in SQL Server 2008 R2

Dear All,
I am getting below error in SSIS Package.
[OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The statement has been terminated.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >,
>= or when the subquery is used as an expression.".
The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
Pld guide me cause of the issue
-- Kind Regards Sandeep

Dear All,
I am getting below error in SSIS Package.
[OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The statement has been terminated.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when
the subquery is used as an expression.".
The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
Pld guide me cause of the issue
-- Kind Regards Sandeep
Query should return only one value. Instead it is returning more than one value. Check the query result in ssms.
Thanks.
- please mark correct answers

How do I get SQL Agent to perform an FTP connection through a SSIS package?

I have created a number of SSIS packages that I am running through SQL Agent in various jobs. I have set up a Credential / Proxy for the job steps and for the most part everything runs no problem. The issue I have is with the step where I make
a connection to a FTP server and download files. In BIDS the step works fine but in SQL Agent the step times out. I presume that it has to do with the account that it is being run under but that is what I thought the Credential / Proxy was supposed
to handle (as it does for all the other steps). I am running on SQL Server 2008 R2. I have created a test job that has only one step which is to connect to the FTP server and download some text files. I have tried utilizing package configuration
files and have tried various ProtectionLevels to no avail.
Anyone have any thoughts or direction for me to take? Will continue to research and will post if I resolve this.
Thanks, Andrew

On the dev environment the ProtectionLevel is set to EncryptSensitiveWithUserKey and that is what I tried first on the prod server. Subsequently I also tried utilizing a package config file (with ProtectionLevel then of DontSaveSensitive) and have
also tried working with the ServerStorage.
For deployment I copied the relevant dtsx files to a solution on the prod server. I verified that the packages all had tested connections in the Connection Manager. I have run all the packages in the BIDS on the prod server and they all worked.
I have created a test package from scratch on the prod server to test the ftp connection. This test package runs from BIDS fine. I have set the SQL Agent file to access through the file system (no luck) and have saved the package to the SSIS Packages
and had the job step access from there (no luck either).

Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

Hi,
We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
SQL Server Data Tools and SQL Server Database Engine reside on the same server.
We tried the following:
Disabling TCP Chimney Offload
Installed Windows Server 2008 SP1
Splitting our SSIS code into multiple steps so it is not all one large continuous operation
The error occurs during a BulkDataLoad task.
Other options we are investigating with the engineering team (out-sourced, so delayed responses):
Firewall configurations (everything is local, so this should not make a difference)
Disabling the anti-virus scanner
Are there other things we can try?
Any insight is greatly appreciated.
Thanks!

Hi HenryKwan,
Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
Set "RetainSameConnection" Property to FALSE on the all the connection managers.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

BIDS 2008 R2 freezes on large SSIS package when attempting to browse local variable

Similar Messages

Maybe you are looking for