Pragmatic Works

Greetings,

I was trying out the demo version of the DTSxChange tool.  I selected 5 DTS packages of varying complexity from one of our staging servers and walked through the wizard to convert them to SSIS packages.  All 5 encountered errors during the conversion process and gave me the following error.  "[ERROR] Object reference not set to an instance of an object."  For my dev environment I am running Virtual Server 2003 R2.  I have visual studio 2005 and all the SQL Server client tools installed.  I saved the log file.   

Thanks,

Carl 

/*********************************************/
Migration Report [ Date: 11/27/2007 11:48:23 AM]
/*********************************************/

FC_ImportCancellationsUpdate_LPS_V1.0.0
 [5] Variable(s) Found
 [2] Connection(s) Found
 [10] Task(s) Found
 Preparing for Package Migration
  Applied Dynamic Connecton Rule.
  New Configuration file [FC_ImportCancellationsUpdate_LPS_V1 0 0.dtsConfig] will be generated at [C:\Converted_To_SSIS]. You can copy [FC_ImportCancellationsUpdate_LPS_V1 0 0.dtsConfig] manually on the SSIS Server where migrated package will be stored for future execution. Config File Path On SSIS Server is [C:\SSIS\Config]
 [ERROR] Object reference not set to an instance of an object.
----------------------------------------------------

ImportCancellationsUpdate_LIS
  Variable(s) Found
 [3] Connection(s) Found
 [14] Task(s) Found
 Preparing for Package Migration
  Applied Dynamic Connecton Rule.
  New Configuration file [ImportCancellationsUpdate_LIS.dtsConfig] will be generated at [C:\Converted_To_SSIS]. You can copy [ImportCancellationsUpdate_LIS.dtsConfig] manually on the SSIS Server where migrated package will be stored for future execution. Config File Path On SSIS Server is [C:\SSIS\Config]
 [ERROR] Object reference not set to an instance of an object.
----------------------------------------------------

RPTDTS_LOLB_Aging_Transfer
  Variable(s) Found
 [2] Connection(s) Found
 [4] Task(s) Found
 Preparing for Package Migration
  Applied Dynamic Connecton Rule.
  New Configuration file [RPTDTS_LOLB_Aging_Transfer.dtsConfig] will be generated at [C:\Converted_To_SSIS]. You can copy [RPTDTS_LOLB_Aging_Transfer.dtsConfig] manually on the SSIS Server where migrated package will be stored for future execution. Config File Path On SSIS Server is [C:\SSIS\Config]
 [ERROR] Object reference not set to an instance of an object.
----------------------------------------------------

STARLoanNumberChangev1.0.1
 [10] Variable(s) Found
  Connection(s) Found
 [19] Task(s) Found
 Preparing for Package Migration
  Applied Dynamic Connecton Rule.
  New Configuration file [STARLoanNumberChangev1 0 1.dtsConfig] will be generated at [C:\Converted_To_SSIS]. You can copy [STARLoanNumberChangev1 0 1.dtsConfig] manually on the SSIS Server where migrated package will be stored for future execution. Config File Path On SSIS Server is [C:\SSIS\Config]
 [ERROR] Object reference not set to an instance of an object.
----------------------------------------------------

STARLoanNumberChangev1.0.2
 [10] Variable(s) Found
  Connection(s) Found
 [20] Task(s) Found
 Preparing for Package Migration
  Applied Dynamic Connecton Rule.
  New Configuration file [STARLoanNumberChangev1 0 2.dtsConfig] will be generated at [C:\Converted_To_SSIS]. You can copy [STARLoanNumberChangev1 0 2.dtsConfig] manually on the SSIS Server where migrated package will be stored for future execution. Config File Path On SSIS Server is [C:\SSIS\Config]
 [ERROR] Object reference not set to an instance of an object.
----------------------------------------------------

/*********************************************/
Validation Report [ Date: 11/27/2007 11:48:23 AM]
/*********************************************/

FC_ImportCancellationsUpdate_LPS_V1.0.0
----------------------------------------------------

ImportCancellationsUpdate_LIS
----------------------------------------------------

RPTDTS_LOLB_Aging_Transfer
----------------------------------------------------

STARLoanNumberChangev1.0.1
----------------------------------------------------

STARLoanNumberChangev1.0.2
----------------------------------------------------

Correction:  I meant to say that I was running Virtual Server 2005 R2...  which runs windows server 2003... as my dev environment.

Thanks,

Carl

Hi Carl, this is Darren and I'm part of the dev team on the product. Can you give me a little more detail on your environment? Do you have the tool installed on your local box with only the client tools installed? If this is the case, you will need to install the tool on a SQL Server box with Integration Services installed due to the fact that the tool uses the SSIS object model. We couldn't package the SSIS object model with the tool because unfortunately, Microsoft's licensing restrictions do not allow for the SSIS object model to be redistributed. So if you are running the tool on a box that doesn't contain SSIS, you may get this error. 

Hi Darren,

Yep, I installed the tool in my dev environent.  My host OS is Windows XP.  I'm running Virtual Server 2005 R2 which runs Windows Server 2003 as the OS.  I have a SQL Server 2000 instance and a SQL Server 2005 instance installed with SSIS installed.  As well as Visual Studio 2005, Visual Studio .Net 2003, and Biztalk Server 2004.  I also have the .Net 2.0 framework installed. 

Thanks,

Carl  

Hi Carl, could you please confirm this is running on a 32 bit OS? I also sent you a personal email and if you didn't receive it, please email support@pragmaticworks.com and we'll work individually to make sure you get this working like a champ. 

Greetings,

Yep, the SSIS package output folder path is a valid path.  Its just a local folder on the C drive of my dev box and I'm sure the app has full control to that folder.  I unchecked the box next to "Dynamic Connections Using Configuration File", ran the wizard, it completed the migration, and created the SSIS package files.  I did get about 20 validation errors though.  After looking at those error messages it looks like some of the DTS packages I was trying to convert had connections to files that did not exist in our UAT environment.  One of the DTS packages that I selected for conversion is one that I already had converted to SSIS myself.  It will be interesting to see what the tool does as compared to what I did. 

Thanks for the help. 

Carl