How to solve the SSIS deployment issue :(

#**111**

Hi Todd,
thanks for the info.

Finally i do observe the gap and let me share out the experience

.

i have lock all my package with password. So, in order to run the SSIS
package at Job Agent, we need to ensure the CommandLine tab has to switch to
edit the command line manually. <the setting will capture on system although
next round u view again and is not selected at the manual radio button>

After with the just one manual radio selection, the package run successfully
on the job agent.

daniel.

"Todd C" wrote:

Quote:

Daniel:
You are very welcome. I also posted another blog concerning Passwords that
you may be interested in:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

I, too, have had packages run OK from SSIS server instance (right-click and
select "Execute Package"), but they fail when they are scheduled to run from
within SQL Server Agent.

The most I can tell you about this is to make sure that the Service Account
that runs SQL Agent has all the permissions it needs on all the resources
(things like integrated security on Database loginsn, file permissions on the
folders, etc).

Good Luck.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

"Daniel" wrote:

Hi Todd,

Now i m able to execute from the integration service server. But i m facing
another issue in executing the job in SQL Agent. The history log only show
the steps was invoke from who and fail. It does not show detail of why fail.

I tried changing the command line if i have encryption on the package - also
fail.

Any ideas on this?

Daniel.

"Daniel" wrote:

Bravo! I will definitely read thru the blog and give it a try. Thanks for ur
passion in sharing ur knowledge.

Daniel.

"Todd C" wrote:

In the design environment (BIDS) you can assign various values to a package
property called "ProtectionLevel". The defaul is "Save Sensetive With User
Key". One of the options there is "Save Sensetive With Password" but that
requires that you re-supply the password every time you save the package, and
that you know the password when you deploy or run it. (I know, just what you
needed, MORE PASSWORDS!).

You could work long and hard to design all your packages to save the
Connection String passwords INSIDE the package, but what if it changes? You
must then edit and re-deploy all your packages.

Enter SSIS's new functionality: Configurations

I *just* finished this blog and it might help you out:

http://toddchitt.wordpress.com/2008/06/27/ssis_configs/

HTH
------
Todd C

#**112**

Hi Todd,
thanks for the info.

Finally i do observe the gap and let me share out the experience

.

i have lock all my package with password. So, in order to run the SSIS
package at Job Agent, we need to ensure the CommandLine tab has to switch to
edit the command line manually. <the setting will capture on system although
next round u view again and is not selected at the manual radio button>

After with the just one manual radio selection, the package run successfully
on the job agent.

daniel.

"Todd C" wrote:

Quote:

Daniel:
You are very welcome. I also posted another blog concerning Passwords that
you may be interested in:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

I, too, have had packages run OK from SSIS server instance (right-click and
select "Execute Package"), but they fail when they are scheduled to run from
within SQL Server Agent.

The most I can tell you about this is to make sure that the Service Account
that runs SQL Agent has all the permissions it needs on all the resources
(things like integrated security on Database loginsn, file permissions on the
folders, etc).

Good Luck.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

"Daniel" wrote:

Hi Todd,

Now i m able to execute from the integration service server. But i m facing
another issue in executing the job in SQL Agent. The history log only show
the steps was invoke from who and fail. It does not show detail of why fail.

I tried changing the command line if i have encryption on the package - also
fail.

Any ideas on this?

Daniel.

"Daniel" wrote:

Bravo! I will definitely read thru the blog and give it a try. Thanks for ur
passion in sharing ur knowledge.

Daniel.

"Todd C" wrote:

In the design environment (BIDS) you can assign various values to a package
property called "ProtectionLevel". The defaul is "Save Sensetive With User
Key". One of the options there is "Save Sensetive With Password" but that
requires that you re-supply the password every time you save the package, and
that you know the password when you deploy or run it. (I know, just what you
needed, MORE PASSWORDS!).

You could work long and hard to design all your packages to save the
Connection String passwords INSIDE the package, but what if it changes? You
must then edit and re-deploy all your packages.

Enter SSIS's new functionality: Configurations

I *just* finished this blog and it might help you out:

http://toddchitt.wordpress.com/2008/06/27/ssis_configs/

HTH
------
Todd C

#**113**

Hi Todd,
thanks for the info.

Finally i do observe the gap and let me share out the experience

.

i have lock all my package with password. So, in order to run the SSIS
package at Job Agent, we need to ensure the CommandLine tab has to switch to
edit the command line manually. <the setting will capture on system although
next round u view again and is not selected at the manual radio button>

After with the just one manual radio selection, the package run successfully
on the job agent.

daniel.

"Todd C" wrote:

Quote:

Daniel:
You are very welcome. I also posted another blog concerning Passwords that
you may be interested in:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

I, too, have had packages run OK from SSIS server instance (right-click and
select "Execute Package"), but they fail when they are scheduled to run from
within SQL Server Agent.

The most I can tell you about this is to make sure that the Service Account
that runs SQL Agent has all the permissions it needs on all the resources
(things like integrated security on Database loginsn, file permissions on the
folders, etc).

Good Luck.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

"Daniel" wrote:

Hi Todd,

Now i m able to execute from the integration service server. But i m facing
another issue in executing the job in SQL Agent. The history log only show
the steps was invoke from who and fail. It does not show detail of why fail.

I tried changing the command line if i have encryption on the package - also
fail.

Any ideas on this?

Daniel.

"Daniel" wrote:

Bravo! I will definitely read thru the blog and give it a try. Thanks for ur
passion in sharing ur knowledge.

Daniel.

"Todd C" wrote:

In the design environment (BIDS) you can assign various values to a package
property called "ProtectionLevel". The defaul is "Save Sensetive With User
Key". One of the options there is "Save Sensetive With Password" but that
requires that you re-supply the password every time you save the package, and
that you know the password when you deploy or run it. (I know, just what you
needed, MORE PASSWORDS!).

You could work long and hard to design all your packages to save the
Connection String passwords INSIDE the package, but what if it changes? You
must then edit and re-deploy all your packages.

Enter SSIS's new functionality: Configurations

I *just* finished this blog and it might help you out:

http://toddchitt.wordpress.com/2008/06/27/ssis_configs/

HTH
------
Todd C

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

How to solve the SSIS deployment issue :(

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

RE: How to solve the SSIS deployment issue :( - 07-10-2008 , 10:43 AM

RE: How to solve the SSIS deployment issue :( - 07-10-2008 , 10:43 AM

RE: How to solve the SSIS deployment issue :( - 07-10-2008 , 10:43 AM