Error Executing, SSIS Packages Coppied from another server

Hello All,

I am working on an application used to move packages (SSIS Packages) from one server to another.The packages are saved under MSDB folder.

Case: When the application is running on my system, i try to copy packages created from another server to my Server.I am using package protection level as "Server Storage". When i try to execute the coppied package from my system, it is giving me error.
An oledb error has occured, Error Code 0x80040E4D, An Oledb record is available, Source : Microsoft OLedb Provider for Sql Server", Description : "Login failed for sa".

Case : When the Package Coppier application is running on my system, i try to copy packages created on my server to my another Server.I use the same package protection level as "Server Storage". When i try to execute the copied package on destination server it is working fine without errors.

Please guide me on this issue, as soon as possible

Thanks And Regards
Subin

Make sure all the permissions are properly set on your server.

DId you read this (http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx)

ServerStorage. No encryption is added to the package. Instead the package’s contents are secured based on the database’s object access security. If the ServerStorage value is used, the package must be saved to SQL Server in the sysdtspackages90 table in the msdb database. It cannot be saved to the file system.

The SSIS package security model is also extensible. There is a Sensitive attribute in the XML schema of an SSIS package that controls access to the package’s properties. For example, if the Sensitive attribute is set to 1, when the user opens the package all sensitive data will be removed. Developers can incorporate this Sensitive attribute to get the same type of protection for their SSIS custom components.

If you are using the ServerStorage ProtectionLevel property, the method of controlling access to the packages saved in the database is by using SQL Server Database roles. By default, SQL Server 2005 provides the following roles for SSIS package management . You can find these by opening SQL Server Management Studio, then expanding the msdb database, Roles, Database Roles node:

?

db_dtsadmin. SSIS package administrator rights.

?

db_dtsltduser. Rights to execute only the SSIS packages the user has been given permission for.

?

db_dtsoperator. Operation rights to SSIS packages including the ability to run as well as backup and restore packages.

You can also create your own custom database roles for SSIS Package management. Add the appropriate users to those roles and then assign those roles to your own SSIS packages.

You can enable package roles using the SQL Server Management Studio by right-clicking a saved package and then selecting the Package Roles option on the shortcut menu as is shown in Figure 11

BTW, is there any reason for not using SSMS to import/export the packages (http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx)