July 27, 2015 at 3:44 am
I have an SSIS solution deployed to the SSISDB catalog. It has a number of project parameters which I have setup an environment to provide values to. I then created a SQL Agent job step to run the solution making use of the environment. When a colleague goes to look at the job step they get an error stating there is no value for a parameter, go to the configurations tab and the link to the environment is not there. They then put it in and I get the error.
So I assume the environment configuration in the SQL Agent Job step is linked to a user? If so how do we get around the above scenario?
Thanks
July 27, 2015 at 5:28 am
mandy-570563 (7/27/2015)
I have an SSIS solution deployed to the SSISDB catalog. It has a number of project parameters which I have setup an environment to provide values to. I then created a SQL Agent job step to run the solution making use of the environment. When a colleague goes to look at the job step they get an error stating there is no value for a parameter, go to the configurations tab and the link to the environment is not there. They then put it in and I get the error.So I assume the environment configuration in the SQL Agent Job step is linked to a user? If so how do we get around the above scenario?
Thanks
There is no such link, as far as I know. Can you provide the full text of the error you are seeing?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 27, 2015 at 5:29 am
Are you logged in using Windows Authentication, by the way?
SSISDB-related activities generally work better if you are.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 27, 2015 at 6:50 am
The error states:
The parameter "TargetServer" is configured to use an environment variable, but no environment has been selected. Check the "Environment" checkbox and sepcify the environment to use or specify a literal value for the parameter.
You can then open the job step and re-tick the environment box.
I am creating the environment and link via a post deploy script. I have checked all parameters have a variable and all are linked properly.
Yes we use windows authentication.
Thanks
July 27, 2015 at 7:08 am
I am creating the environment and link via a post deploy script. I have checked all parameters have a variable and all are linked properly.
This may be your problem. There are quite a few references to take care of and the structure of SSISDB is a little complex.
If you take this out of your post-dep script, does the problem go away?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 28, 2015 at 8:10 am
I have recreated the environment manually and the same issues is occurring.
July 28, 2015 at 8:28 am
On further investigation and digging the ENVREFERENCE value changes when my colleague creates the link?
July 28, 2015 at 8:43 am
mandy-570563 (7/28/2015)
On further investigation and digging the ENVREFERENCE value changes when my colleague creates the link?
The link between an environment and a project should be created only once. Why do you think it is necessary to do it over and over again?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply