Hi there,

I've looked all over the community and none of the possible solutions fixed my problems. Can someone help me look into it?

In the SSIS job history the error message is not helpful. The error message is just unexpected termination. In the event viewer I see that it is categorized as a windows error reporting. There are mdmp files attached to the error, but I'm not able to open it and I'm afraid that even if I do, I won't be able to debug it.

I know that mdmp file is more for windows support, is there anywhere I can send my mdmp files related to my error so that I can find out the root cause of my error and fix it. 

The ssis job succeeds 20% of the time, but 80% of the time it would fail. Not sure why.

Thanks,

Ron

Greetings, I have a package that has a variable @supportemail. I create a config file named "support_emails.dtsconfig" including the @supportemail variables value to overide when I run via agent job with prod support email addresses. This is the"1st" file added in the configurations of the agent job. I add a second config file, that contains address of our email server and other data, it does not contain the @supportemail variable. These 1st 2 config files are my common configurations that apply across all packages, so I have 1 version of these used by all packages. Then I add a 3rd config file that has the specifics for each individual package, and if I want to override the @supportemail variable to say send an error situation to a vendor or someone other than the normal prod support, I add that @supportemail to my 3rd config file and attempt to override the setting from the 1st config file, but it is not working as expected. How does SSIS apply these config files as I this is how I understand this is working.

My environment is running on SQL 2014 standard, running the packages from the file system as was done in 2008. Screenshot of the config files for the job in question below;

Hello, is there going to be an end of life to the old file system way of doing things with SSIS? and having the SSISDB  catalog the only way to use SSIS?

thank you!

Hi everyone,

I am working on a project that requires that export data from SQL Server database into files and then send these excel files as an attachment in email using SSIS.

The package will create 3 different excel files from different tables and then the files will be sent to the same recipients in the email.

Please assist!

me

Hi guys,

Is it possible to have a dropdown option for package parameter in SSIS with a string data type. I need this because I will like the users to always enter the correct value for the parameter. The result behind this is because I have a conditional variable in the SSIS that will need the input value from this parameter, thus if the wrong value is entered the variable will not work as expected.

me

Hello,

I have a problem with Windows Integrated security in a package connection.
Running DTEXEC locally  is working
Running the same from another server returns error "Anonymous logon denied".
After trial and discussions I decided to open a paying ticket with Microsoft to help me solve it.
A workaround is to use only SQL Logins and no Windows integrated security, at least for all connections going outside of the server where ssis is stored.
I have no insurance, no contract.
All engineers i engaged in this were unable to fix it. I am sure it will take the MSFT person just a few minutes to fix this.

How can I open this ticket?

Thanks,

Philippe

Thanks/Regards, Philippe Cand

So we replaced one of our SQL Server from 2014 to 2019.

For development, we have VS 2017 with SSDT and found out that with a SSIS project, we don't have an option to choose the Deployment Target Version to SQL Server 2019. On the drop down, only options are 2012,2014,2016 and 2017.

How to add 2019 as an option?

TIA

HI All,

I am new to this forum.

I have a requirement where i need to copy tables from the source SQL database and migrate it to Sql Server 2014.
I have achieved this task using Transfer SQL Server Object Task.
But now i got additional requirement to get the row count from source and the destination table.

how can i achieve this task?

Please let me know if you need more details.

Hi all, 

I am trying to get the SSIS package deployment history (not the SSIS project project deployment). Through SSISDB.internal.packages I got five rows with a project_version_lsn field, so I guess they are connected to a project deployment as the numbers of that field match with the "Project LSN" of project versions (right click an SSIS Project-> Versions)

And old post pointed to table [msdb].[dbo].[sysssispackages], which my rows are not relevant to my question.

Does anyone figure out where to find this information (If available)?

Hi There,

I am trying to automate SSIS package execution using Windows Task scheduler and batch file(Since I don't have permissions to use SQL server agent).

In the SSIS package I am using two connections, one for Source server connection and other for target server.

In the batch file I am using below code:

When I run the batch file, I am getting the error "the runtime connection manager with the id cannot be found" for both the connections. Please let me know what I am missing here.

Thanks

Manju

I am trying to just test a connection to a database. I have a label in a form named "lblBDconnection" and if the connection works it displays "Connected to Database". I cannot seem to connect to the data. I know the path is correct.

Here is the code:

using System;
using System.Data.OleDb;
using System.Windows.Forms;

namespace DBconnectionTest
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }

        private void Form1_Load(object sender, EventArgs e)
        {
            try
            {
                OleDbConnection dbConnection = new OleDbConnection();
                dbConnection.ConnectionString = @"‪Provider=Microsoft.ACE.OLEDB.16.0;Data Source=‪C:\temp\Users_DBs_Eqpmnt.accdb;Persist Security Info=False;";
                dbConnection.Open();
                lblBDconnection.Text = "Connected to Database";
                dbConnection.Close();
            }
            catch (Exception exp)
            {
                string er = exp.ToString();
                MessageBox.Show("Error" + er);
                tbError01.Text = er;
            }
        }
    }
}

My project target platform is "Any CPU" and "prefer 32-bit" is unchecked.

I am using MS Access from office 365.

I used the textbox just to copy the exception information.

Any help would be appropriated.

Thanks!

I restored our SSISDB from 2014 to 2019. However, we could not deploy packages getting the error below:

It looks like a schema issue and the proposed workaround worked when I tested this. Problem is, if you have a lot of packages, redeployment is something you would not want to do. Anyone have any tips or a different take on this?

TIA

TITLE: SQL Server Integration Services
------------------------------

The required components for the 64-bit edition of Integration Services cannot be found.  Run SQL Server Setup to install the required components.
A .NET Framework error occurred during execution of user-defined routine or aggregate "deploy_project_internal": 
System.Data.SqlClient.SqlException: The required components for the 64-bit edition of Integration Services cannot be found.  Run SQL Server Setup to install the required components.
System.Data.SqlClient.SqlException: 
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnectionSmi.EventSink.DispatchMessages(Boolean ignoreNonFatalMessages)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQuerySmi(Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteToPipe(SmiContext pipeContext)
   at Microsoft.SqlServer.Server.SqlPipe.ExecuteAndSend(SqlCommand command)
   at Microsoft.SqlServer.IntegrationServices.Server.ServerConnectionControl.RaiseError(SysMessageId messageId, SysMessageSeverity severity, Object[] args)
   at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.GetDtsPath(Int16 use32bitOn64, String& path)
   at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.GetISServerExecPath(Int16 use32bitOn64, String& path)
   at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal(SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName)
. (Microsoft SQL Server, Error: 27222)

Hi,   Background: all executions on my win 10 laptop work great, both oledb and ado.net.   on a win 12/ ms sql 2014 server and an azure partition, the oledb tasks work great as ssis jobs.   For a teradata ado.net task it runs on my client but I get a "could not create a managed connection" on both our server environment and our azure partition.  I work in a big company and they tend to upgrade the teradata driver on laptops before the server editions catch up.  I know this makes a difference for c# binaries but it's hard for me to believe it would make a difference for ssis, where would ssis demand a certain teradata client version?  Some suggest a Run64bitruntime tweak to fix this.   When i look in the dtsx file after I switch Run64bitruntime, I see no reference to it in the xml.  In dtsconfig I don't see Run64bitruntime as a property that can be placed in the runtime dtsconfig file.

I have a simple SSIS job.  Map a drive, import a .CSV file from that drive to a SQL table, unmap the drive.  (I find that flat files do not accept UNC paths - this is on SQL Server 2008).  This runs as expected within Visual Studio, but reports that it cannot open the text file when scheduled in SQL Agent.  The SQL Agent job is set to be execute by a proxy which has the necessary permissions (the same as the ID  used when running from Visual Studio.

(1) Run from design environment - works

(2) Execute job stored in SQL Agent 'Jobs' - fails

(3) Execute job stored in MSDB, Integration Services - works

It looks like a permission issue, but I can't find it.  I'm accessing the network via VPN - could that be a factor?

I've been creating many SSIS packages lately using VS2013 Ultimate w/ Update 4.  On several occasions, I have built packages and have them working then come back later and re-open the package in the designer and all I get is a solid white designer.  The first times this happened it was because I had eliminated one of the tables that it sourced from.  I was able to pick through the XML and remove it then it opened again where I could make the needed changes.  However, I now have two packages with the same problem and no idea why they will not open.  Even if the source was changed or removed, I would still expect to be able to open the package and be warned that something has changed and be given an opportunity to correct it.  The only fix I have now is to start over on these packages.  That represents many hours of work.  I'm really starting to doubt that SSIS is the best tool for the job.  If anyone has a solution that will let me view the designer again, you'll be my hero.

Thanks!

Ian

Ian

Hi, below is a basic proposal for a new SSIS package (not mine). I am relatively new to SSIS and in the learning so far I have really enjoyed what SSIS has to offer. So for me the below concept will work but just feels like way to many SQL tasks.

Are there any really good SSIS tasks that would effectively do the same or similar or better job to anything listed below?

Custom Data Loader Design

There will need to be the following:

• Several objects in the data warehouse:
  • A configuration table that holds details of the child packages to be run
  • An event logging table
  • An error logging table
  • A load logging table
• One SQL Agent job per loader:
  • This will call the logging SSIS package (parent) and pass an identifier for the loader SSIS package (child) as a package parameter to the parent package.
• One logging SSIS Package that can be used for all loaders:
  • Retrieves the details of the child package (and, potentially, other details) from the configuration table using the package parameter passed in (SQL Task)
  • Creates the event log record (SQL Task)
  • Creates the load log record (SQL Task)
  • Calls the child SSIS package (SQL Task)
  • Logs any record counts in the load log returned by the child package and completes the load log record (SQL Task)
  • Enters any errors returned from the child package in the error log (SQL Task)
  • Completes the event log record (SQL Task)
• One data flow SSIS package per loader:
  • Perform any pre-load tasks that are needed and are applicable to more than one of the data flows, e.g. retrieving the last run date for the loader (SQL Task)
  • One sequence container per table to be loaded:
    • Retrieve any values that are required before execution of the data flow and are specific to this data flow, e.g. retrieving the maximum ID value from the target table (SQL Task)
    • A truncate statement to clear down the staging table (SQL Task)
    • A Data flow task to transfer the source data into a staging table which captures the number of records transferred and any errors generated
    • A SQL command to truncate the model table if this is a bulk loader (SQL Task)
    • A SQL command to transfer the data from the staging table to the model table which captures the number of records inserted/updated and any errors generated.
    • Update the parent variables with numbers of records and errors (script task)

I have created Backup Maintenance Plans for full, differential, and transaction logs.

I notice that the rest run without a hitch. The differential file is created, but get the following error:

Executed as user: MyDomain\dba_Acct. Started:  10:51:08 PM  Finished: 10:51:13 PM  Elapsed:  4.625 seconds.  The package execution failed.  The step failed.

The event log says the same.

When I set the maxerrorcount to 1 I get the following message:

Message
Executed as user: MyDomain\dba_Acct. ...  Version 11.0.5058.0 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  11:02:06 PM  Error: 2020-07-06 23:02:06.42     Code: 0xC0010018    Source: {1FD37D2C-E1A5-4BD9-98EB-9998742FED98}      Description: Failed to load task "{1FD37D2C-E1A5-4BD9-98EB-9998742FED98}", type "". The contact information for this task is "Maintenance Plan Reporting Task; Microsoft Corporation; Microsoft SQL Server v9; ? 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1".  End Error  Progress: 2020-07-06 23:02:06.55     Source: {9D1D47D8-A2C2-485A-8FC3-82888DF62128}     Executing query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:06.58     Source: Maintenance Cleanup Task 1      Executing query "EXECUTE master.dbo.xp_delete_file 0,N'\\MyBKServer\...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:06.69     Source: Back Up Database (Differential)      Executing query "EXECUTE master.dbo.xp_create_subdir N'\\MyBKServer\...".: 20% complete  End Progress  Progress: 2020-07-06 23:02:06.69     Source: Back Up Database (Differential)      Executing query "EXECUTE master.dbo.xp_create_subdir N'\\MyBKServer\...".: 40% complete  End Progress  Progress: 2020-07-06 23:02:06.69     Source: Back Up Database (Differential)      Executing query "EXECUTE master.dbo.xp_create_subdir N'\\MyBKServer\...".: 60% complete  End Progress  Progress: 2020-07-06 23:02:06.69     Source: Back Up Database (Differential)      Executing query "EXECUTE master.dbo.xp_create_subdir N'\\MyBKServer\...".: 80% complete  End Progress  Progress: 2020-07-06 23:02:06.70     Source: Back Up Database (Differential)      Executing query "EXECUTE master.dbo.xp_create_subdir N'\\MyBKServer\...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:07.24     Source: Back Up Database (Differential)      Executing query "BACKUP DATABASE [model] TO  DISK = N'\\MyBKServer\k...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:08.03    Source: Back Up Database (Differential)      Executing query "BACKUP DATABASE [msdb] TO  DISK = N'\\MyBKServer\k$...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:08.44     Source: Back Up Database (Differential)      Executing query "BACKUP DATABASE [ReportServer$DBINSTANCE] TO  DISK...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:08.78     Source: Back Up Database (Differential)      Executing query "BACKUP DATABASE [ReportServer$DBINSTANCETempDB] TO...".: 100% complete  End Progress  Progress: 2020-07-06 23:02:19.07     Source: Back Up Database (Differential)     Executing query "BACKUP DATABASE [MyDB] TO  DISK = N'\\MyBKServer\...".: 100% complete  End Progress  Error: 2020-07-06 23:02:19.07     Code: 0xC0010026     Source: {1FD37D2C-E1A5-4BD9-98EB-9998742FED98}     Description: The task has failed to load. The contact information for this task is "Maintenance Plan Reporting Task; Microsoft Corporation; Microsoft SQL Server v9; ? 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1".  End Error  Error: 2020-07-06 23:02:19.07     Code: 0xC0024107     Source: {1FD37D2C-E1A5-4BD9-98EB-9998742FED98}      Description: There were errors during task validation.  End Error  Warning: 2020-07-06 23:02:19.07     Code: 0x80019002     Source: OnPostExecute      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.  End Warning  Warning: 2020-07-06 23:02:19.07     Code: 0x80019002     Source: Backup      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succe...  The package execution fa...  The step failed.

When I run sp_readerrorlog I get the following:

Database differential changes were backed up. Database: MyDB, creation date(time): 2016/03/15(16:07:04), pages dumped: 36908, first LSN: 3940:500656:237, last LSN: 3940:501192:1, full backup LSN: 3940:480544:286, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\MyBKServer\diff\backup_2020_07_06_230206_6942975.diff'}). This is an informational message. No user action is required.
BACKUP DATABASE WITH DIFFERENTIAL successfully processed 36794 pages in 9.986 seconds (28.785 MB/sec).

I have an SQL server running on 11.0.5058.0