error in download json from api - System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'

May 24, 2020, 3:23 am

≫ Next: SSIS 2019, MSOLEDBSQL, Thread safe? Connection issue

≪ Previous: Config file in ssis - similar to web.config in web application or app.config in wpf

Hi All,

i'm trying to get data from rest api with token with "script component" in ssis.

when the code is reaching the part of return client.DownloadString(downloadURL) it fails

and return the error: System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'

this is what i'm getting in the script component: runtime error:

at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at System.Net.WebClient.DownloadString(String address)
at ScriptMain.DownloadJson(String downloadURL) in c:\Users\320049665\AppData\Local\Temp\Vsta\624378d242724fcc9e5bf1dbf2294601\main.cs:line 26
at ScriptMain.PreExecute() in c:\Users\320049665\AppData\Local\Temp\Vsta\624378d242724fcc9e5bf1dbf2294601\main.cs:line 17
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.PreExecute()

this is the code:

using System;
using System.Net;
using System.Collections.Generic;
using System.Web.Script.Serialization;

[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
{
string json;

public override void PreExecute()
{
base.PreExecute();
string url = "https://www.xxx?Authrization=Bearer eyJhbGciOiJIUzxxxv4_NP7wg";
json = DownloadJson(url);
}

}

public static string DownloadJson(string downloadURL)
{
using (WebClient client = new WebClient())
{
return client.DownloadString(downloadURL);
}
}

please help

↧

SSIS 2019, MSOLEDBSQL, Thread safe? Connection issue

May 12, 2020, 8:26 am

≫ Next: Strange event handler behaviour

≪ Previous: error in download json from api - System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'

Hi,
I have a "ETL framework" built in SSIS. It has been running fine for several year, but when trying to run it on SQL Server 2019 I´m getting into trouble.

Earlier I was using an OLE DB connection manager with the "SQL Server Native Client" (SQLNCLI11.1) provider.
Googling around I found that this one is deprecated and shouldn´t be used together with SQL Server 2019 so I changed to the new "Microsoft OLE DB Driver for SQL Server" (MSOLEDBSQL.1).
First I though that this solved my problem, but I still get random errors so let me explain the problem in depth.

I´ve spent a week now trying to figure out the cause.

I´ve create a small SSIS project from scratch just to be able to reproduce the problem.

The project consist of 2 packages:

"Sub Package" - Contains one "Execute SQL Task" (just runs simple SQL statement "SELECT 1") using an OLE DB Connection (Project Level Connection Manager).
This OLE DB Connection uses the OLE DB Provider "Microsoft OLE DB Driver for SQL Server" (MSOLEDBSQL.1).
The ConnectionString of the OLE DB Connection is set through an Expression. In this test package the Expression is "hardcoded" as:
"Data Source=my_server_name;Initial Catalog=FrameWorkETL;Provider=MSOLEDBSQL.1;Integrated Security=SSPI;Auto Translate=False;"

"Main Package" - Contain 2 For Loop containers running in parallell. Each loop runs for 1000 laps and each lap it runs an Execute Package Task with "Sub Package".

I´m running the "Main Package" under SQL Server Agent.

Sometimes the package runs fine, but many times I randomly get different error messages.

Example error 1:

Package:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Driver for SQL Server"
Hresult: 0x80004005 Description: "Invalid connection string attribute".

Example error 2:

Package:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server"
Hresult: 0x80040E4D Description: "Invalid authorization specification".

Example Error 3:

Package:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E73.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components"
Hresult: 0x80040E73 Description: "Format of the initialization string does not conform to the OLE DB specification.".

It is olso common that the package fails with "Unexpected Termination". Then it looks like this in the Event Viewer:

Faulting application name: ISServerExec.exe, version: 15.0.2000.5, time stamp: 0x5d8a8258
Faulting module name: ntdll.dll, version: 10.0.17763.292, time stamp: 0x7ded7809
Exception code: 0xc0000374
Fault offset: 0x00000000000faf49
Faulting process id: 0x1a18
Faulting application start time: 0x01d62865c4ae326b
Faulting application path: C:\Program Files\Microsoft SQL Server\150\DTS\Binn\ISServerExec.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5348cd22-fdea-46aa-a908-5848856a5e53
Faulting package full name:
Faulting package-relative application ID:

Looking in the SSIS internal log table [internal].[event_message_context] I can see that the Connectionstring sometimes get corrupt.
It gets corrupt in different ways which might explain why I get different error messages.

Example of corrupt connectionstring from log table:
Data Source=my_server_name;Initial Catalog=FrameWorkETL;Provider=MSOLEDBSQL.1; (missing the last part of the string).
Data Source=my_server_name;Initial Catalog=FrameWorkETL;Provider= (also missing some part of the string).
Data Source=my_server_name;Initial Catalog=FrameWorkETL;Provider=MSOLEDBSQL.1;Integrated Security=SSPI;Auto Translate=False;MSOLEDBSQL.1;Integrated Security=SSPI;Auto Translate=False; (extra parts added last in the string)

I´ve only been able to reproduce the problem under the following circumstances:

The Connection Manager uses the OLE DB Provider "Microsoft OLE DB Driver for SQL Server" (MSOLEDBSQL.1) - Might be the same problem with SQLNCLI11.1 provider. The package runs fine if I use for example an ADO.Net Connection Manager with SqlClient Data Provider.
The Connectionstring of the Connection Manager is set through an Expression. - The package runs fine if the connectionstring is not set through an Expression.
There are "tasks" running in parallel trying to initialize a database connection. - The package runs fine if the "Main Package" only has one for loop. = No connections are initialized in parallell.
The package runs on a SQL Server 2019 machine. - The Package runs fine on for example a SQL Server 2017 (even if the connection manager connects to a SQL Server 2019 database).

My environment:
VM with Windows Server 2019 standard
SQL Server 2019 (15.0.4033.1) CU4 (latest CU).
MSOLEDB Provider version 18.3 (latest)

Any help appreciated.

Regards
Stefan

↧

Strange event handler behaviour

May 24, 2020, 7:22 am

≫ Next: How to extract all Database Objects from SSIS Packages 2014?

≪ Previous: SSIS 2019, MSOLEDBSQL, Thread safe? Connection issue

Given the following scenario:

Why does the PARENT PACKAGE report the error from the FAILURE TASK and exit with an error?

↧

How to extract all Database Objects from SSIS Packages 2014?

May 20, 2020, 7:13 pm

≫ Next: why bitmap index in DWH

≪ Previous: Strange event handler behaviour

Hi All,

I am looking for options to extract Database Objects (Source Query or table/sp/view, Destination Query or table/sp/view, any lookup table, any Execute SQL Task query) from SSIS Packages 2014.

This is need to prepare data dictionary or create Extraction flow.

Would like to know has anyone tried this..? any free or paid tool in market to extract Database Objects from SSIS packages...?

Thanks Shiven:) If Answer is Helpful, Please Vote

↧

why bitmap index in DWH

May 25, 2020, 2:51 am

≫ Next: SSIS Setup failed unknown error 0x80131500 0x80131500 and VS 2019

≪ Previous: How to extract all Database Objects from SSIS Packages 2014?

I have seen bitmap index as preferred choice in data warehousing environment. I wanted to know reasons for that. As per my own experience, one reason is bit map index are compressed and hence confined in less index space. When we have large number of FK indexes then this index space matters. Bit map index will enable faster search and hence reduced response time in such cases. I wanted to hear other reason for same from experts.
As per my own research(below URL), bitmap works well for low cardinality columns , however DWH may not necessarily have low cardinality column.

↧

SSIS Setup failed unknown error 0x80131500 0x80131500 and VS 2019

March 4, 2020, 10:02 am

≫ Next: How to get multiple csv / excel files from secured webpage and load into different tables

≪ Previous: why bitmap index in DWH

Because I did see only an empty ssis toolboxI tried to reinstall SSIS Version 3.4 and I got an error and following protokol:

[0A70:1AA8][2020-03-04T18:45:56]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: .\Downloads\Microsoft.DataTools.IntegrationServices.exe, cmdline: ''
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ProductVersionVar' to value '15.0.2000.71'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ReleaseVersion' to value '3.4'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'LicenseTermsUrl' to value 'https://go.microsoft.com/fwlink/?LinkID=853828&clcid='
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'PreviewStatementUrl' to value

../ some lines I had to delete because of size / ..

[27A0:0C4C][2020-03-04T18:47:31]i301: Applying execute package: SSAS_AMO2016, action: Repair, path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\payload\SQL_AS_AMO2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 47
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 24, Overall progress: 48
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 37, Overall progress: 49
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 63, Overall progress: 51
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 76, Overall progress: 52
[0A70:1AA8][2020-03-04T18:47:32]i000: MainViewModel.OnPackageActionProgress: Percent completed: 89, Overall progress: 53
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server 2016 Analysis Management Objects (id: SSAS_AMO2016)
[0A70:1AA8][2020-03-04T18:47:40]i319: Applied execute package: SSAS_AMO2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:40]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {97A881AD-5134-4CD2-A6A8-371C83E5622B}, package: SSAS_AMO2016
[27A0:0C4C][2020-03-04T18:47:40]i323: Registering package dependency provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, version: 13.1.4561.14, package: SSAS_OLEDB2016
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[27A0:0C4C][2020-03-04T18:47:40]i301: Applying execute package: SSAS_OLEDB2016, action: Repair, path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\payload\SQL_AS_OLEDB2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 55
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 28, Overall progress: 56
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 41, Overall progress: 57
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 54, Overall progress: 58
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 67, Overall progress: 59
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 80, Overall progress: 60
[0A70:1AA8][2020-03-04T18:47:42]i000: MainViewModel.OnPackageActionProgress: Percent completed: 95, Overall progress: 61
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[0A70:1AA8][2020-03-04T18:47:45]i319: Applied execute package: SSAS_OLEDB2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:45]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, package: SSAS_OLEDB2016
[27A0:0C4C][2020-03-04T18:47:45]i323: Registering package dependency provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, version: 14.0.3002.563, package: SSDTISSingleton140
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[27A0:0C4C][2020-03-04T18:47:45]i301: Applying execute package: SSDTISSingleton140, action: Repair, path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\payload\SSDTISSingleton140.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 62
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 63
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 64
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 48, Overall progress: 65
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 66
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 73, Overall progress: 67
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 84, Overall progress: 68
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageActionProgress: Percent completed: 98, Overall progress: 69
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[0A70:1AA8][2020-03-04T18:47:46]i319: Applied execute package: SSDTISSingleton140, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:46]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, package: SSDTISSingleton140
[27A0:0C4C][2020-03-04T18:47:46]i323: Registering package dependency provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, version: 15.0.2000.71, package: SSDTISSingleton
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[27A0:0C4C][2020-03-04T18:47:46]i301: Applying execute package: SSDTISSingleton, action: Repair, path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\payload\SSDTISSingleton.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 70
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 71
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 72
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 56, Overall progress: 73
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 74
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 75, Overall progress: 75
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 88, Overall progress: 76
[0A70:1AA8][2020-03-04T18:47:51]i000: BootstrapperEngineDataModel.OnExecutePackageComplete: Package requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: SSDTISSingleton, result: 0x0, restart: Required
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, package: SSDTISSingleton
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsixPreInstall, version: 1.0.0.0, package: ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsixPreInstall, action: Install, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 80
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 84
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsix, version: 1.0.0.0, package: ISVsix
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsix, action: Install, path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe" /q /admin /instanceIds:"33f63265" /logFile:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_11_ISVsix.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 88
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Process returned error: 0x80131500
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to configure per-machine EXE package.
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied execute package: ISVsix, result: 0x80131500, restart: None
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsix, package: ISVsix
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsix, from path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\
[27A0:0C4C][2020-03-04T18:48:10]i326: Removed dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 92
[27A0:0C4C][2020-03-04T18:48:10]i301: Applying rollback package: ISVsixPreInstall, action: Uninstall, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log" /u'
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied rollback package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsixPreInstall, from path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton, from path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton140, from path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_OLEDB2016, from path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2016, from path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2014, from path: C:\ProgramData\Package Cache\{76CBDC35-0752-4B5A-83E8-49A741BD42BC}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2012, from path: C:\ProgramData\Package Cache\{53086A62-13F3-4FC5-AA41-211FD74340B3}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2016, from path: C:\ProgramData\Package Cache\{1F86F7A6-BCC6-49C4-8033-785993FA6331}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2014, from path: C:\ProgramData\Package Cache\{07001141-C74D-47ED-B03D-892C7EF00E3D}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2012, from path: C:\ProgramData\Package Cache\{DB97C76B-9116-42C5-8814-0041856EB9E6}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: VCRedist2010, from path: C:\ProgramData\Package Cache\28C54491BE70C38C97849C3D8CFBFDD0D3C515CB\
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[0A70:1AA8][2020-03-04T18:48:10]i000: BootstrapperEngineDataModel.OnApplyComplete: Bundle requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2594.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: last modified at 03.03.2020 15:54:53, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2f54.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: last modified at 03.03.2020 15:57:04, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]e000: MainViewModel.OnBundleAction: Bundle action failed: Unknown error (0x80131500) (0x80131500)
[0A70:1AA8][2020-03-04T18:48:10]i399: Apply complete, result: 0x80131500, restart: Required, ba requested restart: No
[0A70:0C04][2020-03-04T18:48:17]i000: MainViewModel.OpenUrl: Opening url: .\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556.log

Somebody can help?

regards

Olaf

olaf870

↧

How to get multiple csv / excel files from secured webpage and load into different tables

May 25, 2020, 6:55 am

≫ Next: Object reference not set to an instance of an object.

≪ Previous: SSIS Setup failed unknown error 0x80131500 0x80131500 and VS 2019

Hello everyone,

My requirement is to get files from webpage using SSIS script task / any other transformation but without using third party / new download transformation.

Using username and password only I can log into that particular webpage and weekly basis files will be loaded

Files no's may vary sometimes.

Example week1 , we may get File1 , File2, File3. ( all the files contains different columns) but in Week2 i may get File1, File2 ..

so i want to write script task to get all the files from webpage uing user name and password and then finaly wants to load into existing different SQL tables. (old data truncate and new data load)

Note : in webpage i will get files with these names only (file1 , file2 , file3, file4, file5, file6)

Thanks in advance.

GVRSPK VENI

↧

Object reference not set to an instance of an object.

May 25, 2020, 1:09 pm

≫ Next: SSIS support from Microsoft

≪ Previous: How to get multiple csv / excel files from secured webpage and load into different tables

[Convert GS to JSON [29]] Error: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Convert GS to JSON" (29) failed with error code 0x80004003 while processing input "Input 0" (39). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

I am doing .net code in ssis script component, i already tried many steps but i dont know why , please help me

This is my script component code public override void Input0_ProcessInputRow(Input0Buffer Row)

{

while (Row.NextRow())
{

if (Row.SlugType.Trim().ToLower() == "lg")
{

if (Row.EarlySc != "" && Row.EarlySc != null && Row.EarlySc.Trim().Length > 7)
{
//MessageBox.Show(Row.EarlySc);
EarlyList.Add(Math.Round(Convert.ToDecimal(Row.EarlySc.Substring(0, 7)) * 100, 2));
}
else
{
if (Row.EarlySc != "" && Row.EarlySc != null && Row.EarlySc.Trim().Length > 0)
{
EarlyList.Add(Math.Round(Convert.ToDecimal(Row.EarlySc) * 100, 2));
}
else
{
EarlyList.Add(0);
}
}

if (Row.LateSc != "" && Row.LateSc != null && Row.LateSc.Trim().Length > 7)
{
DelayedList.Add(Math.Round(Convert.ToDecimal(Row.LateS.Substring(0, 7)) * 100, 2));
}
else
{
if (Row.LateSc != "" && Row.LateSch != null && Row.LateScheduledcumulative.Trim().Length > 0)
{
DelayedList.Add(Math.Round(Convert.ToDecimal(Row.LateSc) * 100, 2));
}
else
{
DelayedList.Add(0);
}
}

if (Row.Actualcu != "" && Row.Actualcu != null && Row.Actualcu.Trim().Length > 7)
{
ActualList.Add(Math.Round(Convert.ToDecimal(Row.Actualcu.Substring(0, 7)) * 100, 2));
}
else
{
if (Row.Actualcu != "" && Row.Actualcu != null && Row.Actualcu.Trim().Length > 0)
{
ActualList.Add(Math.Round(Convert.ToDecimal(Row.Actualcu) * 100, 2));
}
else
{
if (x.Count > 1)
{
if (x[x.Count - 1] == 0)
{
ActualList.Add(0);
}
}
else
{
x.Add(0);
}
}
}
if (Row.y!= "" && Row.y!= null && Row.y.Trim().Length > 0)
{
if (Row.y.Trim().Length > 7)
{
z= Math.Round(Convert.ToDecimal(Row.x.Trim().Substring(0, 7)) * 100, 2);
}
else
{
z= Math.Round(Convert.ToDecimal(Row.x.Trim()) * 100, 2);
}
}

if (Row.ww!= "" && Row.ww!= null && Row.ww.Trim().Length > 0)
{
if (Row.ww.Trim().Length > 7)
{
q= Math.Round(Convert.ToDecimal(Row.ww.Trim().Substring(0, 7)) * 100, 2);
}
else
{
q= Math.Round(Convert.ToDecimal(Row.ww.Trim()) * 100, 2);
}
}

if (Row.aa!= "" && Row.aa!= null && Row.aa.Trim().Length > 0)
{
if (Row.aa.Trim().Length > 7)
{
zz= Math.Round(Convert.ToDecimal(Row.aa.Trim().Substring(0, 7)) * 100, 2);
}
else
{
VarLate = Math.Round(Convert.ToDecimal(Row.LateVariancecumulative.Trim()) * 100, 2);
}
}

}

dataDateList.Add(Row.DataDate);

}

↧

SSIS support from Microsoft

May 25, 2020, 11:27 pm

≫ Next: db2 driver azure and laptop differences

≪ Previous: Object reference not set to an instance of an object.

Hi,

I came (might me rumor also) to know that Microsoft is going to stop the support and phasing out SSRS service in near future in MS SQL server. We were planing to develop SSRS reports for our product that we are building currently and will be available till decade for my customers.

Can anybody let me know if the news is true then by when SSRS will be available and can we use for our product?

Regards,

Navanit

↧

db2 driver azure and laptop differences

May 21, 2020, 1:33 pm

≫ Next: SSRS support by MS

≪ Previous: SSIS support from Microsoft

Hi,

Difficult problem here. New to db2. Just looking for places to start. I installed a v 11.x db2 driver on my laptop, using vs 2015 enterprise and ssis ssdt 14.x . i was able to login to the db2 server with both ssis and the native db2 tools if I overrode the port number to say 20000. No one else in my group needs to override the port number to 20000. Then I ran the job on azure with a completely different db2 driver and I still have to override my port number to get it to work and no one else in my group does. I will grant that the db2 driver I have could have a different configuration than the people I work with but why would that carry over to a an azure server with just one db2 client install? Can't promote this package forward in the azure sdlc chain if my db2 server reference has to be custom.

↧

SSRS support by MS

May 26, 2020, 4:17 am

≫ Next: expression vs expression and constraint

≪ Previous: db2 driver azure and laptop differences

Hi,

Can anybody let me know if the news is true then by when SSRS will be available and can we use for our product?

Regards,

Navanit

↧

expression vs expression and constraint

May 26, 2020, 6:40 am

≫ Next: Error running dtexec /f from command line after including set parameters

≪ Previous: SSRS support by MS

HI,

I have the process to check if the file is exists before continue with the other process. I am not sure which one should I pick and what is the different between two.

Thanks

↧

Error running dtexec /f from command line after including set parameters

May 26, 2020, 10:45 am

≫ Next: SSIS Project file Issues

≪ Previous: expression vs expression and constraint

HI,

I have a package with project level parameters. I have managed to run it from the SSIS Integration Service Catalog and it works, I actually need to use the command prompt, test it and if it works convert it to a bat file and use it to run it as I would have to add it to the task scheduler.

Anyway, this is my command, where am I making mistake, since this is a project level variable, how do I change my command accordingly

DTExec.exe /f "C:\Users\gdmal\source\repos\SSISTutorial\SSISTutorial\Package.dtsx" /SET \Package.Variables[Project::ServerName].Properties[Value];"DESKTOP-6TI366J" /SET \Package.Variables[Project::DatabaseName].Properties[Value];"sourcedb"

I am getting the below error

Started:  1:40:16 AM
Error: 2020-05-27 01:40:16.85
   Code: 0xC00470A6
   Source: Package
   Description: The variable "$Project::DatabaseName" was not found in the Variables collection. The variable might not exist in the correct scope.
End Error
Error: 2020-05-27 01:40:16.85
   Code: 0xC0047098
   Source: Package
   Description: Attempt to parse the expression "@[$Project::DatabaseName]" failed and returned error code 0xC00470A6. The expression cannot be parsed. It might contain invalid elements or it might not be well-formed. There may also be an out-of-memory error.
End Error
Error: 2020-05-27 01:40:16.85
   Code: 0xC0017003
   Source: Package
   Description: The expression "@[$Project::DatabaseName]" on property "\Package.Connections[localhost.sourcedb].Properties[InitialCatalog]" cannot be evaluated. Modify the expression to be valid.
End Error
Error: 2020-05-27 01:40:16.85
   Code: 0xC00470A6
   Source: Package
   Description: The variable "$Project::ServerName" was not found in the Variables collection. The variable might not exist in the correct scope.
End Error
Error: 2020-05-27 01:40:16.85
   Code: 0xC0047098
   Source: Package
   Description: Attempt to parse the expression "@[$Project::ServerName]" failed and returned error code 0xC00470A6. The expression cannot be parsed. It might contain invalid elements or it might not be well-formed. There may also be an out-of-memory error.
End Error
Error: 2020-05-27 01:40:16.85
   Code: 0xC0017003
   Source: Package
   Description: The expression "@[$Project::ServerName]" on property "\Package.Connections[localhost.sourcedb].Properties[ServerName]" cannot be evaluated. Modify the expression to be valid.
End Error
Warning: 2020-05-27 01:40:16.85
   Code: 0x80012017
   Source: Package
   Description: The package path referenced an object that cannot be found: "\Package.Variables[Project::ServerName].Properties[Value]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning
DTExec: Could not set \Package.Variables[Project::ServerName].Properties[Value] value to DESKTOP-6TI366J.
Started:  1:40:16 AM
Finished: 1:40:16 AM
Elapsed:  0.157 seconds

↧

SSIS Project file Issues

May 26, 2020, 9:30 pm

≫ Next: ODBC source performance issue

≪ Previous: Error running dtexec /f from command line after including set parameters

Hi Everyone,

Can you please suggest in the below situation with SSIS .Proj file ?

I have added a new SSIS project to my solution. dtproj file is generating the different versions of analysis services data bases files every time . Below code is changing to different versions as SSIS_ProjName 2.database and then SSIS_ProjName 3.database etc. If I try to update it from source XML code this is generating next number for the name.

<Name>SSIS_ProjName.database</Name>

<FullPath>SSIS_ProjName.database</FullPath>

</Database>

This is generating as below and in the source folder and generating the different versions of Analysis Services Data Base files like SSIS_ProjName 1, SSIS_ProjName 2, … SSIS_ProjName 7 etc. in the source code.

<Database>
<Name>SSIS_ProjName 7.database</Name>
<FullPath>SSIS_ProjName 7.database</FullPath>
</Database>

Thanks In advance.

↧

ODBC source performance issue

May 26, 2020, 11:17 pm

≫ Next: Distribution List in Send Mail SSIS task is omitted?

≪ Previous: SSIS Project file Issues

Hi All,

i am getting crores data from ODBC connectivity (ODBC source) to OLE DB destination (MS SQL Server).

But automatically "ODBC source" enforced row by row fetch method. this task taking lots and lots of time.

how to get and load data from odbc to sql server?

GVRSPK VENI

↧

Distribution List in Send Mail SSIS task is omitted?

May 27, 2020, 4:04 am

≫ Next: SSIS Package - ADO.net Destination with ODBC connection - Input columns not keeping mapping

≪ Previous: ODBC source performance issue

hi,

it is weird. The PostExecute event for the task is done but nobody receives the email.

Defining individually all the recipients, works perfectly.

primary Integration Services on client: 15.0.2000.94

build Sql server: 12.0.6372.1

SMTP: in this case we are not using the smpt.office365.com but <mycompany.com>.mail.protection.outlook.com

is it more related to 365 or SSIS?

↧

SSIS Package - ADO.net Destination with ODBC connection - Input columns not keeping mapping

May 27, 2020, 4:13 am

≫ Next: SSIS scheduled job fails

≪ Previous: Distribution List in Send Mail SSIS task is omitted?

Hello,

I have an SSIS package that was originally built for SQL Server but I have had to rebuilt this for MySQL as the end destination due to budget constraints. I have multiple data flow tasks that load csv files into MySQL. The file name is a variable the issue I am finding is that whenever I load up the SSIS package the input columns are blank for each of the ado.net destination elements I am using the ODBC add on which enable the data to load into the MySQL DB but it doesn't remain resolved as the columns loose their mapping information.

So every time I save the mappings it works fine but each time I load the package it shows the errors as above and ignore all input columns.

I would greatly appreciated any advice on this issue as this won't work as an ongoing overnight ETL to load in data.

Thanks,

David

↧

SSIS scheduled job fails

May 16, 2020, 9:03 am

≫ Next: Inserting data from SQL server to MYSQL

≪ Previous: SSIS Package - ADO.net Destination with ODBC connection - Input columns not keeping mapping

Hi,

I am running an SSIS scheduled job on an SQL Server 2012(SP3 11.0.6260.1) instance. This job is running on-premise and the target is Dynamics 365. Starting from schedule the job always fail with an "Unexpected empty response". If i start the job manually it runs just fine. I use the same account as the proxy starting the job.

Error message:

"Copy CRM Data:Error: KingswaySoft.IntegrationToolkit.DynamicsCrm.WebAPI.WebApiServiceException: Unexpected empty response received from the resource URL: https://xyz.crm4.dynamics.com/api/data/v8.0/RetrieveVersion ---> System.Exception: Unexpected empty response received from the resource URL: https://xyx.crm4.dynamics.com/api/data/v8.0/RetrieveVersion
at tzt.bcf(Uri mb, String& mc, String& md)
at tzt.bce()
at tzt.bcb()
at uhk.iyn(String bdc, String bdd)
at uhk.rlq.osq()
at tzh.pfx[bz](Func`1 iq, Func`2 ir, Int32 is, PipelineComponent it)
--- End of inner exception stack trace ---
at tzh.pfx[bz](Func`1 iq, Func`2 ir, Int32 is, PipelineComponent it)
at uhk.iyk(String bcx, String bcy, String bcz)
at uhk.iyd(String bcs, String bct, String bcu, HttpStatusCode& bcv)
at uhk.iyi()
at uhn.tjs()
at uhn.pye(String bir)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at uhn.pxm(String bge)
at uhj..ctor(uhn bbr, uaa bbs)
at uhn.tjk(uaa hgj)
at KingswaySoft.IntegrationToolkit.DynamicsCrm.CrmSourceComponent.PreExecute()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper100 wrapper)"

Anyone have clue what can be the problem?

Best regards
Frode M

↧

Inserting data from SQL server to MYSQL

March 16, 2013, 12:21 am

≫ Next: ForEachLoop Wildcard filename

≪ Previous: SSIS scheduled job fails

Hello Friends

I need to INPUT some values from SQL SERVER to MYSQL using SSIS.

I have follow these

http://blogs.msdn.com/b/mattm/archive/2009/01/07/writing-to-a-mysql-database-from-ssis.aspx

but getting error;

[ADO NET Destination [43]] Error: An exception has occurred during data insertion, the message returned from the provider is: ERROR [42000] [MySQL][ODBC 5.1 Driver][mysqld-5.1.57-log]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"phone_number", "filter_phone_group_id") VALUES ('755514', 'EXISTING')' at line 1

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "ADO NET Destination" (43) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (46). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

Please help

↧

ForEachLoop Wildcard filename

May 27, 2020, 3:58 pm

≫ Next: How to generate a SSIS package by VS to load data from DB2 and output a CSV file?

≪ Previous: Inserting data from SQL server to MYSQL

Hi All,

I have a requirement where I'm getting flat file from customer inside FTP folder such as:

1. Terminal_ABCD_20200527.txt

2. Terminal_BCD_20200527.txt

3. Terminal_CD_20200527.txt

4. Terminal_D_20200527.txt

5. Terminal_12345_20200527.txt

6. Terminal_1234_20200527.txt

7. Terminal_123_20200527.txt

I have to loop through FTP folder and process File 1,2,3 from 1st SSIS package to populate into 1st table

Then process File 4,5 from 2nd SSIS package to populate into 2nd table

then process File 6,7 from 3rd SSIS package to populate into 3rd table.

I tried using Foreachloop container. Used filename as variable with value Terminal_*.txt but it picks up all the files although it fails for the rest of the files because of destination table column mappings.

How can I achieve this so that I can run all SSIS packages together and picking the right files for right tables?

↧