SQL Server Parameter Issue In Job
I  have a SQL job that runs the exact same package three times with different configuration values connecting to different servers. On the third time the package runs I get the error

Environment reference Id: NULL. Description: The parameter 'Client' does not exist or you do not have sufficient permissions. Source: .Net SqlClient Data Provider Started: 3:16:03 PM Finished: 3:16:03 PM Elapsed: 0.203 seconds. The package execution failed. The step failed.

This error happens in less than one second and I don't have a parameter Client in my SSIS package, job configuration parameter or in the configuration of the Integration Services Catalog.

Has anyone seen this error? What I am primarily wanting to hear is suggestions on where else to look for this parameter?

February 13th, 2015 12:49am

What is different between the runs?

I think you run using the SQL  Agent where the jobs are not running synchronously and therefore potentially experience a lock on the Config

Free Windows Admin Tool Kit Click here and download it now
February 13th, 2015 4:00am

It is one job.  There are three steps in the job that each sequentially run the same code base but point to a different SQL Server database as their source.
February 13th, 2015 10:49am

Hi Mr Murff,

According to your description, when you run SSIS package with SQL agent job, you got the error message: The parameter 'Client' does not exist or you do not have sufficient permissions.

To troubleshoot the problem, please refer to the following steps:

  1. The issue may occur because of incorrect connection string such as incorrect server name. Please make sure you specified the XML Configuration file when executing the package or configuring the job step.
  2. You may referenced the parameter in other objects, you may removed the parameter from the package, but it is still referenced in the job. You can simply delete the job step that run the package and re-add the step.
  3. The account does not have required permissions to access the Server or execute the package. You may have to assign appropriate permissions to the account.

If you have any more questions, please feel free to ask.

Thanks,
Wendy Fu

Free Windows Admin Tool Kit Click here and download it now
February 16th, 2015 6:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics