SSIS Newbie - Deployment Utility Help

[fuzzyocelot]

Hi everyone!

I’m trying to figure out how to deploy an SSIS package to our dev server (Windows Server 2003 SP2; SQL 2005 SP2).

I created a basic SSIS package on my computer. Then I created a deployment utility in BIDS. I made sure I changed the CreateDeploymentUtility option to True and rebuilt the solution.

I’m not sure what to do next. The path on my computer for the deployment is:

C:\Projects\HRIS\TestFileTransfer\TestFileTransfer\bin\Deployment\

I want to deploy the package to a remote server. Do I need the same folder set up on the server? Our database files are on the D drive on the server and I’d like to put the package files there as well. Maybe I’m just not understanding this part of the deployment because I’m feeling lost right now.

Could someone please shed some light on this for me? I’ve searched the Web and this site, but haven’t found much that helps.

Thanks!

 

[MDXer]

copy all files from the deployment directory to the server you want to deply them to and then execute the manifest file. THis will start with allowing you to chose file system or MSDB deployment.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[fuzzyocelot]

Thanks for the info! I did just that. Upon executing the manifest file, I chose to deploy to MSDB. I also specified for it to validate the package after the installation and to use Windows Authentication.

The validation fails due to a login failure on the OLE DB task within the package. I've been trying a bunch of different things from within the package but it keeps failing. I've tried changing the package security protection level to DontSaveSensitive to EncryptSensitiveWithPassword. I can't use the levels that specify WithUserKey because I'm using LoginA for the package and I'm deploying the package logged into the server as LoginB. I also have the Save Password checkbox selected within the connection manager for the OLE DB connection.

It seems no matter what I do, I get the same error. I know the login works because I've used it before. I also just double-checked and the login still works. I've had this problem before but it's been so long I can't remember how to fix it. :-/

 

[MDXer]

You may need to add dynamic configurations to set you ole db connection info.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[fuzzyocelot]

I got it to work! Here’s what I had to do…

I changed the package protection level to EncryptAllWithPassword and set a password. Then I made sure I was deploying to my Production configuration where the Run64BitRuntime is set to False and my Deployment Utility settings are correct (CreateDeploymentUtility=True). Then I rebuilt the package, copied the deployment files to the server, ran the manifest file, unchecked verify after installation, and accepted the defaults for the rest. I then ran it from Management Studio on the server and it worked! I must have been doing something screwy in the first place because now it works!

Thank you for your help!