Exception in Task: ExecutePackage->Unhandled exception: System.ArgumentException: Keyword not supported: 'driver'.
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:\git\code\SSISDBExecute\SSISDB.vb:line 51

Exception in Task: ExecutePackage->Unhandled exception: System.ArgumentException: Keyword not supported: 'driver'.
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:\git\code\SSISDBExecute\SSISDB.vb:line 51

What version are you using? Please send screenshots of your connection settings to support@visualcron.com

---

Currently using version 9.3.5

We got this problem figured out now we have encountered a new problem.
We are trying to have VisualCron run our SSISDB package and we are now getting this error:

Exception in Task: Begin package execution log
Package:Validation has started.
Data Flow Task:Validation has started.
Data Flow Task:Information: Validation phase is beginning.

Data Flow Task:Validation is complete.
Package:Validation is complete.
Data Flow Task:Start, 6:49:35 AM.
Data Flow Task:Validation has started.
Data Flow Task:Information: Validation phase is beginning.

Data Flow Task:Validation is complete.
Data Flow Task:Information: Prepare for Execute phase is beginning.

Data Flow Task:Information: Pre-Execute phase is beginning.

Data Flow Task:Information: The processing of file "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv" has started.

Data Flow Task:Warning: Access is denied.

Data Flow Task:Error: Cannot open the datafile "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv".

Data Flow Task:Error: Flat File Source failed the pre-execute phase and returned error code 0xC020200E.

Data Flow Task:Information: Post Execute phase is beginning.

Data Flow Task:Information: The processing of file "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv" has ended.

Data Flow Task:Information: "OLE DB Destination" wrote 0 rows.

Data Flow Task:Information: Cleanup phase is beginning.

Data Flow Task:The task, 'Data Flow Task', failed.
Data Flow Task:Finished, 6:49:36 AM, Elapsed time: 00:00:00.297.
Package:Start, 6:49:35 AM.
Package:Warning: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) 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.

Package:Finished, 6:49:36 AM, Elapsed time: 00:00:00.454.
End package execution log

We got this problem figured out now we have encountered a new problem.
We are trying to have VisualCron run our SSISDB package and we are now getting this error:

Exception in Task: Begin package execution log
Package:Validation has started.
Data Flow Task:Validation has started.
Data Flow Task:Information: Validation phase is beginning.

Data Flow Task:Validation is complete.
Package:Validation is complete.
Data Flow Task:Start, 6:49:35 AM.
Data Flow Task:Validation has started.
Data Flow Task:Information: Validation phase is beginning.

Data Flow Task:Validation is complete.
Data Flow Task:Information: Prepare for Execute phase is beginning.

Data Flow Task:Information: Pre-Execute phase is beginning.

Data Flow Task:Information: The processing of file "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv" has started.

Data Flow Task:Warning: Access is denied.

Data Flow Task:Error: Cannot open the datafile "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv".

Data Flow Task:Error: Flat File Source failed the pre-execute phase and returned error code 0xC020200E.

Data Flow Task:Information: Post Execute phase is beginning.

Data Flow Task:Information: The processing of file "\\files\Apps\Seradex\Import\Ascentis\Duratech_Seradex.csv" has ended.

Data Flow Task:Information: "OLE DB Destination" wrote 0 rows.

Data Flow Task:Information: Cleanup phase is beginning.

Data Flow Task:The task, 'Data Flow Task', failed.
Data Flow Task:Finished, 6:49:36 AM, Elapsed time: 00:00:00.297.
Package:Start, 6:49:35 AM.
Package:Warning: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) 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.

Package:Finished, 6:49:36 AM, Elapsed time: 00:00:00.454.
End package execution log

That looks like a permission issue. Make sure you are using credentials/have correct permissions set

---

i have the EXACT same error on a flat file source, but have confirmed the VC credentials i am using has access to the folder and the file:

Load Current ETID File:Information: Prepare for Execute phase is beginning.

Load Current ETID File:Information: Pre-Execute phase is beginning.

ETID import 20221005:Finished, 3:13:48 PM, Elapsed time: 00:00:01.641.
Load Current ETID File:Information: The processing of file "\\xxx-srv1\main\xxxxx\xxxx\xxxxx\xxxxxx\xxxx\source files\GLOBAL_COMBINED_BillingCycleExport.txt" has started.

Load Current ETID File:Warning: Access is denied.

Load Current ETID File:Error: Cannot open the datafile "\\xxx-srv1\main\xxxxx\xxxx\xxxxx\xxxxxx\xxxx\source files\GLOBAL_COMBINED_BillingCycleExport.txt".

Load Current ETID File:Error: Current Cycle File failed the pre-execute phase and returned error code 0xC020200E.

Hi

We had the same problem when we set this up several years ago. The problem is that I don't remember the solution:)

1) Try adding bulkadmin server role to the user connecting to sql server. I don't remember if this is actually needed for SSIS, but I can see we have this role added

2) We also had a 'double hop' issue: https://techcommunity.mi...and-kerberos/ba-p/317304 
This took a long time to figure out, so you may want to talk to your network admin or DBA to see if this is relevant to your case.

3) The third possibility I see floating out there, is that the user actually executing the job isn't the user you think:
https://social.technet.m...m=sqlintegrationservices 

Thomas

I will def look at these options. Thank you!

we never found a solution other than installing VC on the server where the SSIS package would run then simply call that job from the server we wanted to control the job variables like the schedule, triggers, email, etc

on the server where the package was called we used a domain user to make the connection to the sql instance (load profile and local login)

I cannot tell you what the permissions are on the sql instance or the package individually but you could certainly try to set the permissions very high then work backwards once you see it run one time

I will def look at these options. Thank you!

Let us know if you still have issues with this. I recommend Joey S suggestion here as well.