Deployment of package on other machine
I created a package with configurations. When I try to deploy it on my local machine it works fine. But when I copy the deployment folder to other machine and change the configuration in the config file and now try to execute the package it throws error.
Before executing the package I make required changes in the config file and then add this file in configuration tab and then execute it shows error.
May 23rd, 2011 3:11am
Hi AqS11,
Can you please post the error in the pakcage? You can get it from the log file or in the progress bar of the package in BIDS.
Happy to help! Thanks. Regards and good Wishes, Deepak.
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 3:14am
Agree with Deepak, what is error message exactly?http://www.rad.pasfu.com
May 23rd, 2011 3:58am
Hi,
It seems you might not be having required permissions on other machine where you have copied the deployment folder. Please recheck folder has got enough permissions to execute the package.
Hope this helps !!!
Regards,
Vaibhav
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 4:40am
TITLE: SSIS Execution Properties
------------------------------
Warning: 2011-05-23 16:53:18.10
Code: 0x80019316
Source: Package Format Migration Module
Description: The provider name for the connection manager "CYRAMEDDM\SQL2005.CyramedData" has been changed from "SQLNCLI.1" to "SQLNCLI10".
End Warning
Warning: 2011-05-23 16:53:18.13
Code: 0x80019316
Source: Package Format Migration Module
Description: The provider name for the connection manager "CYRAMEDDM\SQL2005.Mmt.Cyramed.SecurityDb" has been changed from "SQLNCLI.1" to "SQLNCLI10".
End Warning
Warning: 2011-05-23 16:53:18.26
Code: 0x80019316
Source: Package Format Migration Module
Description: The provider name for the connection manager "CYRAMEDDM\SQL2005.Mmt.Cyramed.WCF.ProductionDb" has been changed from "SQLNCLI.1" to "SQLNCLI10".
End Warning
Info: 2011-05-23 16:53:18.55
Code: 0x40016019
Source:
Description: The package format was migrated from version 2 to version 3. It must be saved to retain migration changes.
End Info
Warning: 2011-05-23 16:53:19.40
Code: 0x00000000
Source: Script Task Script Task
Description: Found SQL Server Integration Services 2005 Script Task "ScriptTask_f1580aadf12a4b35b66a4a966d0a4148" that requires migration!
End Warning
Info: 2011-05-23 16:53:26.33
Code: 0x4001601A
Source: Script Task Script Task
Description: The Script Task "ScriptTask_f1580aadf12a4b35b66a4a966d0a4148" has been migrated. The package must be saved to retain migration changes.
End Info
Warning: 2011-05-23 16:53:26.36
Code: 0x00000000
Source: Logging Logging
Description: Found SQL Server Integration Services 2005 Script Task "ScriptTask_d018c2215aa04aa1bb487030185ea273" that requires migration!
End Warning
Info: 2011-05-23 16:53:33.36
Code: 0x4001601A
Source: Logging Logging
Description: The Script Task "ScriptTask_d018c2215aa04aa1bb487030185ea273" has been migrated. The package must be saved to retain migration changes.
End Info
Info: 2011-05-23 16:53:33.37
Code: 0x40016041
Source: Package
Description: The package is attempting to configure from the XML file "C:\Documents and Settings\azims\Desktop\CyramedDataMigration\CyramedDataMigration\CyramedConfig.dtsConfig".
End Info
Warning: 2011-05-23 16:53:33.44
Code: 0x80012012
Source: Package
Description: The configuration file name "C:\Documents and Settings\azims\Desktop\CyramedDataMigration\CyramedDataMigration\CyramedConfig.dtsConfig" is not valid. Check the configuration file name.
End Warning
Warning: 2011-05-23 16:53:33.55
Code: 0x80012059
Source: Package
Description: Failed to load at least one of the configuration entries for the package. Check configuration entries for "Configuration 2" and previous warnings to see descriptions of which configuration failed.
End Warning
Warning: 2011-05-23 16:53:33.68
Code: 0x8001F300
Source: Package
Description: Succeeded in upgrading the package.
End Warning
DTExec: Could not import the configuration file C:\Users\azims\Desktop\Deployment\CyramedConfig.dtsConfig.
May 23rd, 2011 8:25am
Hi,
It seems your package is in SSIS 2005 which you are migrating to SQL Server 2008.
Before migrating the package disable the config file in SSIS 2005 package.Once package is migrated then you can again create new config file and attach to the package.
Just try out above things.Please let me know it works for you or not.
Thanks,
Vaibhav
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 4:37am