Sunday, September 23, 2012 5:06 AM
When I try moving some packages from one server to another some of the packages stop workiing I got an Error Package... at the asp.net
The packages are running from asp.net application and there are params for the database connection string and the file connection string that the package is using to update the database.
The packages are saved as files ".dtsx" when I open the package with the Bids and connect the file that I'm trying to upload now I got error MetaData
I want to know how the same file that works at the production server not working I try it at the new server with the same ssis Package that was copied from the production server (I got package error at the asp.net page) and when I open the package by BIDS and connect to it the file that I want to upload I got Metadata Error
some packages was needing to add for them IMEX=1 to let them works and update the meta data but with the change of IMEX I'm now need to do changes to the file where it holds numeric values like [120 ILS] To 120
So I want to know what all the checking that I have to do when moving exists package from one server to another to keep it working without to do any changing to the package or the files
Like check the production Registry....?
Thanks you in advance
Sunday, September 23, 2012 10:55 AMCheck whether the configuration data is setup correctly i.e. any environment variables/ xml configuration from the production server should exist on the new server. Ensure that you are using an input excel with similar structure to the one used on production. Ensure that the production and new server have the same version of sql and service packs. Ensure you have access to all the network file shares.
- Marked As Answer by Eileen ZhaoMicrosoft Contingent Staff, Moderator Friday, September 28, 2012 8:34 AM