In implementing SQL Server 2017, we found that there is some problem with the native MSSQL provider usedin VC. When we make a connection, the connection fails while using the native provider. Instead, we have to use the MSOLEDBSQL provider, which is an OLEDB provider. We are successful in getting the connection to make a connection to the database while setting of the connection and clicking the Test Connection button. Then, we use that connection definition to create a SSISDB task. While setting up the task, the Refresh buttons all fail giving the message "Keyword not supported "provider". (Note: The "provider" keyword is required in the connection string for the OLEDB providers since they are not native.) What this tells me is that although the connection is defined as OLEDB, the VC program is actually using the native provider to try to connect to the database server using the connection string that is properly formed with the provider keyword.

So, we worked around that, and set up the SSISDB execution by manually entering the proper values. BUT, even the execution seems to be using the native provider even though the connection is set to use the OLEDB provider as specified in the connection string. Here is the error output:



Is this a bug n the SSISDBExecute\SSISDB.vb code or is there a configuration that I missed somewhere?

Is this something that a developer can look into, please? We are stuck in our attempt to upgrade SQL SSISDB to v2017, and this should be a simple correction. Thanks.

We will look at this. Thanks

---

In implementing SQL Server 2017, we found that there is some problem with the native MSSQL provider usedin VC. When we make a connection, the connection fails while using the native provider. Instead, we have to use the MSOLEDBSQL provider, which is an OLEDB provider. We are successful in getting the connection to make a connection to the database while setting of the connection and clicking the Test Connection button. Then, we use that connection definition to create a SSISDB task. While setting up the task, the Refresh buttons all fail giving the message "Keyword not supported "provider". (Note: The "provider" keyword is required in the connection string for the OLEDB providers since they are not native.) What this tells me is that although the connection is defined as OLEDB, the VC program is actually using the native provider to try to connect to the database server using the connection string that is properly formed with the provider keyword.

So, we worked around that, and set up the SSISDB execution by manually entering the proper values. BUT, even the execution seems to be using the native provider even though the connection is set to use the OLEDB provider as specified in the connection string. Here is the error output:

ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 5459498)->ExecutePackage->Unhandled exception: System.ArgumentException: Keyword not supported: 'provider'.
at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey)
at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules)
at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous)
at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
at System.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at System.Data.SqlClient.SqlConnection..ctor(String connectionString, SqlCredential credential)
at SSISDBExecute.SSISDB.ExecutePackage(ProcessSSISDBTaskInfoClass task) in C:\sourcefiles\code\SSISDBExecute\SSISDB.vb:line 43

Is this a bug n the SSISDBExecute\SSISDB.vb code or is there a configuration that I missed somewhere?

By the way, what is the reason you want to use OLEDB instead of Native as Native is faster and has less dependencies?

---

The OLEDB provider is faster which is a nice benefit, but we are actually implementing it since the native provider is unable to connect in our environment. We think there is something more complicated about our security configuration that the native provider cannot handle. When we set up the connection in VC with the OLEDB provider, we CAN make the connection successfully to the database server while we cannot with the native provider.

The OLEDB provider is faster which is a nice benefit, but we are actually implementing it since the native provider is unable to connect in our environment. We think there is something more complicated about our security configuration that the native provider cannot handle. When we set up the connection in VC with the OLEDB provider, we CAN make the connection successfully to the database server while we cannot with the native provider.

I doubt that it is faster (you can search on OleDBConnection vs SQLConnection) but what error do you get with Native?

---

With the native provider, we get the following error:



Our database administrator tells us that with the native provider, VisualCRON is using TLS 1.0 or 1.1 (I am not sure which) but we are phasing out the older, less secure TLS versions in our environment. Thus, VisualCRON is unable to communicate to the new database server using the native provider. Thus, we found that MSOLEDBSQL provider CAN connect to the database server. That seemed to be our only option, but when executing the SSISDB package, VisualCRON seems to default to the native provider but still uses the connection string which has a "provider" keyword in it that the native provide finds objectionable.

😁 I just cheat and use PowerShell to call the process remote on the SQL Server from an AD ACL controlled share using whatever authentication has rights to run the SSIS processes on that DB ... makes for a highly compartmentalized processing if need be.
With the SSIS configured for Message / verbose the VisualCron Task Standard Out can be parsed .to provide great details that are easily used to report processing status .This can not be done easily remotely any other way that we know of.
PS looks like this in crude form - \\sql1\Transaction\DTSX\Dotit.ps1
dtexec '/SQL "\"\itoTodayPRD_VisualCronJobStatus\"" /SERVER CADEVSQL1 /CHECKPOINTING OFF /REPORTING EI /CONSOLELOG M '
No worries.
StdErr - is a real no help.
Std Out will look like this - watch for regex to get Info: Source: Message: DTExec: other stuff

JUNKBLAH1
...
Info: 2018-11-30 14:53:03.53
Code: 0x4004300B
Source: Data Flow Task 1 SSIS.Pipeline
Description: "Destination - MyVisualCronJobTable$" wrote 289 rows.
End Info
Log:
Message: The Destination - MyVisuaCronJobTable$ spent 15 milliseconds in ProcessInput.End Log
...
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 2:53:02 PM
Finished: 2:53:03 PM
Elapsed: 1.016 seconds

Has there been any action on this issue? We are still hoping to get the VisualCRON SSISDB feature working on our new SQL Server 2017 server. Thanks.

Steve,

Sorry to hi-jack you're thread but have you managed to get your SSISDB working with Files located within shares?

I setup Integration Catalog Services a while ago and can get VisualCron to connect to it perfectly fine however my basic test package that just deletes from a file share falls over with Access Denied, curious to know if you have come across this.

Can take this to a PM if you like.

Regards,

James

Has there been any action on this issue? We are still hoping to get the VisualCRON SSISDB feature working on our new SQL Server 2017 server. Thanks.

Update. We found that the SSISDB API does not support OLEDB. Only type SQLConnection which is direct.

---

Steve,

Sorry to hi-jack you're thread but have you managed to get your SSISDB working with Files located within shares?

I setup Integration Catalog Services a while ago and can get VisualCron to connect to it perfectly fine however my basic test package that just deletes from a file share falls over with Access Denied, curious to know if you have come across this.

Can take this to a PM if you like.

Regards,

James

What is the relation of the file to SQL server and VisualCron server - I mean, where is it resided?

---

The file is located in a File Share accessible by a UNC Path and accessible by "Everyone" VisualCron picks up the package from SSISDB correctly however when it runs it just falls over.

Log:

13:35:54: Server->Execute path: C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe
13:35:54: Server->Executing Task process
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->CreateService->Response channel created on address: /TaskProcess/299
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Requesting Task information
13:35:54: Server->Sending Task information
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Task information sent
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Task information received
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
13:35:54: Server->Task information sent
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Before execute
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.IntegrationServices, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.ConnectionInfo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.Folder->Fresh
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.ProjectName->Fresh SSIS
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.PackageName->SSISDB Test.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.ConnectionString->Data Source=fig-w2k16-sql;Initial Catalog=SSISDB;Integrated Security=True;Password=
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Diagnostics.STrace, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.SqlClrProvider, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.IntegrationServicesEnum, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.Catalog->SSISDB
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving catalogFolder (1 folder(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Catalog containing folder: Fresh
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving the project from catalogFolder (1 project(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Catalog folder containing project: Fresh SSIS
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving the package from project (4 package(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: Import OctoTelematics Response Files.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: Import TRAK Raw Data.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: PCL_By_Brand_V2.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: SSISDB Test.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package found, id: 66
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter count: 8
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Preparing value parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Looping through parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.Monthly_Agg_Report.csv 1.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.Monthly_Agg_Report.csv.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.InitialCatalog, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.Password, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.RetainSameConnection, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.ServerName, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.UserName, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Parameters set
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Looping through project parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Setting project parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Using the 32 bit runtime: True
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Environment reference count: 0
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Environment property not set - ignoring
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.IntegrationServices.Common.ObjectModel, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->executionId: 617
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->execution->Messages.Count: 0
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Waiting for completion
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Wait complete
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Error message log complete
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Execution status: Failed
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Package execution result: Failure
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Preparing Task log
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Sending result
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Result sent
13:36:00: Server->Executing Task process exited with exit code: 0
13:36:00: Server->Waiting for completion and result
13:36:00: Server->Task result received, success: False

It is this process that needs access: C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe

Only thing that affects this is the Credential you use to run the SSISDB Task. Make sure that A) you are using Load profile 😎 that you have not altered the Credential default setting "CreateProcessWithLogonW". You can see this if you enable Extended debuggin in Server settings and then edit the Credential.

The file is located in a File Share accessible by a UNC Path and accessible by "Everyone" VisualCron picks up the package from SSISDB correctly however when it runs it just falls over.

Log:

13:35:54: Server->Execute path: C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe
13:35:54: Server->Executing Task process
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->CreateService->Response channel created on address: /TaskProcess/299
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Requesting Task information
13:35:54: Server->Sending Task information
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Task information sent
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Task information received
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
13:35:54: Server->Task information sent
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Before execute
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.IntegrationServices, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.ConnectionInfo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.Folder->Fresh
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.ProjectName->Fresh SSIS
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.PackageName->SSISDB Test.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.ConnectionString->Data Source=fig-w2k16-sql;Initial Catalog=SSISDB;Integrated Security=True;Password=
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Diagnostics.STrace, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.SqlClrProvider, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.Management.IntegrationServicesEnum, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->task.Catalog->SSISDB
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving catalogFolder (1 folder(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Catalog containing folder: Fresh
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving the project from catalogFolder (1 project(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Catalog folder containing project: Fresh SSIS
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Retrieving the package from project (4 package(s))
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: Import OctoTelematics Response Files.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: Import TRAK Raw Data.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: PCL_By_Brand_V2.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Project containing package: SSISDB Test.dtsx
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package found, id: 66
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter count: 8
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Preparing value parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Looping through parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.Monthly_Agg_Report.csv 1.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.Monthly_Agg_Report.csv.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.ConnectionString, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.InitialCatalog, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.Password, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.RetainSameConnection, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.ServerName, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Package parameter: CM.fig-w2k16-sql.FreshSystems.UserName, value type: Literal, object type: 30
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Parameters set
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Looping through project parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Setting project parameters
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Using the 32 bit runtime: True
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Environment reference count: 0
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Environment property not set - ignoring
13:35:54: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Assembly loaded: Microsoft.SqlServer.IntegrationServices.Common.ObjectModel, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->executionId: 617
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->execution->Messages.Count: 0
13:35:55: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Waiting for completion
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Wait complete
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->ExecutePackage->Error message log complete
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Execution status: Failed
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Package execution result: Failure
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Preparing Task log
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Sending result
13:35:58: ExecuteProcess("C:\Program Files (x86)\VisualCron\\MSSQLSSISDB\SSISDBExecute.exe" 299)->Result sent
13:36:00: Server->Executing Task process exited with exit code: 0
13:36:00: Server->Waiting for completion and result
13:36:00: Server->Task result received, success: False

---

Update. We found that the SSISDB API does not support OLEDB. Only type SQLConnection which is direct.

So will this be updated anytime soon or will the SQLConnection be updated to support TLS2? Thanks.

Update. We found that the SSISDB API does not support OLEDB. Only type SQLConnection which is direct.

So will this be updated anytime soon or will the SQLConnection be updated to support TLS2? Thanks.

How is this related to OLEDB? TLS2? We support TLS1.2 at the moment.

---

Perhaps we need some information how to activate TLS 1.2 support. When we set our SQL Server to support TLS 1.1, the native provider in VisualCRON works fine. But, when we switch the SQL Server to TLS 1.2, the native provider stops working, and only the OLEDB provider will make a connection, which is fine, but the OLEDB provider is not supported in SSISDB. Therefore, we are unable to run SSIS packages on the database server with TLS 1.2 implemented there.

This implies that there is something in our implementation of VisualCRON that needs to be activated for TLS 1.2 to be supported on the SSISDB controls. Can you advise?

Perhaps we need some information how to activate TLS 1.2 support. When we set our SQL Server to support TLS 1.1, the native provider in VisualCRON works fine. But, when we switch the SQL Server to TLS 1.2, the native provider stops working, and only the OLEDB provider will make a connection, which is fine, but the OLEDB provider is not supported in SSISDB. Therefore, we are unable to run SSIS packages on the database server with TLS 1.2 implemented there.

This implies that there is something in our implementation of VisualCRON that needs to be activated for TLS 1.2 to be supported on the SSISDB controls. Can you advise?

Hi,

we sent you an email yesterday. We are investigating this. Thanks

---