SSIS Package fails when agent job uses alternate environment.

• david_h_edmonds

  Default port

  Points: 1430

  More actions

  January 8, 2019 at 8:22 am

  #376725

  Hi, I am using SQL Server 2012 and SSIS.
  I have an agent job running in my dev environment with no issues.
  I have parameterised the connection managers and now deployed the packages to my UAT environment. The package now fails when the job encounters a step that has an "execute TSQL task" as park of the package. The actual error text is :

  Merge:Error: Failed to lock variable "RunId" for read access with error 0xC0010001 "The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on a container during execution of the package, and the variable is not there. The variable name may have changed or the variable is not being created.".

  and

  Merge:Error: Failed to acquire connection "CTM_A8_Handoff". Connection may not be configured correctly or you may not have the right permissions on this connection.

  I have done some digging and found that this can be an issue when using multiple environments. Does anyone have any experience of this error and any suggestions for a solution please?

  Cheers

  Dave

• david_h_edmonds

  Default port

  Points: 1430

  More actions

  January 9, 2019 at 4:46 am

  #2018395

  Hello,
  After a load of googling, I have found the cause and the solution.

  Cause:
  https://social.msdn.microsoft.com/Forums/sqlserver/en-US/e3d1f733-ed60-41ec-87f3-cbbafb7d1656/ssis2012-runid-variable-quotfailed-to-lockquot-at-runtime-bombs-0xc0010001?forum=sqlintegrationservices

  Solution that worked for me was to open all packages that contained a:
   
  and replace those tasks with:
  

  This negated the issue of the runid being {00000000-0000-0000-0000-000000000000} and the job worked perfectly.

  Best Regards

  Dave