Post Deployment - Running Pkg With Set Values !!VOID

I was wondering if someone could provide me with a bit info on how to Set Values in the dtexecui?

I have a package that does a T-SQL SELECT query with a @.var, and that @.var needs to be set at runtime, in the Agent Job....

Thanks in advance.

Nevermind, having a slllllowwww moment this morning, need more coffee:)
In case others would like to know:

\Package.Variables[User::VAR_NAME].Properties[Value] : VAR_VALUE|||I've submitted a DCR to get a GUI interface as part of dtexecui that allows you to generate these property pathswithout typing them in yourself. It shouldn't be hard seeing as the same thing already exists in SSIS Designer.
In the meantime, the way to generate these property paths is using the XML configuration file wizard within SSIS Designer.

I'm sure you know this Jason :)

-Jamie|||Is it Feedback. Got a reference I can vote on? Drives me round the twist too.|||

DarrenSQLIS wrote:

Is it Feedback. Got a reference I can vote on? Drives me round the twist too.

Nah. I did it thru betaplace!

Post Deployment - Running Pkg With Set Values

I was wondering if someone could provide me with a bit info on how to Set Values in the dtexecui?

I have a package that does a T-SQL SELECT query with a @.var, and that @.var needs to be set at runtime, in the Agent Job....

Thanks in advance.

Nevermind, having a slllllowwww moment this morning, need more coffee:)
In case others would like to know:

\Package.Variables[User::VAR_NAME].Properties[Value] : VAR_VALUE|||I've submitted a DCR to get a GUI interface as part of dtexecui that allows you to generate these property pathswithout typing them in yourself. It shouldn't be hard seeing as the same thing already exists in SSIS Designer.
In the meantime, the way to generate these property paths is using the XML configuration file wizard within SSIS Designer.

I'm sure you know this Jason :)

-Jamie|||Is it Feedback. Got a reference I can vote on? Drives me round the twist too.|||

DarrenSQLIS wrote:

Is it Feedback. Got a reference I can vote on? Drives me round the twist too.

Nah. I did it thru betaplace!

possible setup.exe exit codes?

As part of our application deployment we have wrapped and automated the SQL Server Express install by launching the setup.exe with our parameters and waiting around for the process to exit.

I had been checking for a Exit Code != 0 to detect errors returned by setup.exe but this does not appear to be foolproof. Several customers' deployments have returned non-zero exit codes, but SQL Express seems to be successfully installed.

I have not found a reference of possible codes returned and their meaning that I could use to fine tune our checking. Does one exist? Or am I going about this the wrong way and should just check for the existence of our instance after setup is complete?

thank you for any input.

I *think* the only other success error code you need to code around is error code 3010, which signifies success, but a reboot is necessary.

Here is a list of other possible Windows Installer error codes:

http://msdn2.microsoft.com/en-us/library/aa368542.aspx

Thanks,
Sam Lester (MSFT)