Installation & Upgrade

When I try to install the software that I downloaded from the website, I am getting an error stating "Another version of this product is already installed. Installation of this version cannot be continue." What should I do? 

This should only happen when your previous installation is an old version. If you receive this error, you must uninstall the previous version before installing the new version. To do so, use "Add/Remove Programs" or "Programs and Feature" on the Control Panel and select "SSIS Integration Toolkit for Microsoft Dynamics CRM" to remove it. 

Licensing

Do I need a trial license to evaluate the software? 

You do not need to acquire a license if you only want to test out the software functionality within your development tools (SSDT-BI, BIDS - Business Intelligence Development Studio, or Visual Studio). After installation, the software will operate under the free developer license by default. With the developer license, you can create and develop data flows within your development tools, including executing test loads without requiring a commercial license. 

If you want to evaluate whether the software functions properly outside of your development tools (SSDT-BI, BIDS, or Visual Studio), you can acquire a trial license using the License Manager program which is installed along with the software. After you have acquired a trial license, you will be able to run SSIS packages on a scheduled basis, or from any other Windows process such as command line or even CRM plugins. The trial software will operate fully-functional for the trial period, which is generally 14 days. When the trial period expires, the software will revert back to the free developer license. 

What are the limitations of the free developer license? 

The free developer license is fully-functional within your development tools (SSDT-BI, BIDS, or Visual Studio). The only limitation is the inability to run the software outside your development tools.

What's the difference between subscription license and perpetual license? 

There is no functionality difference between a subscription license and a perpetual license. However, with a subscription license, your capability to run our software outside your development tools (such as running SSIS packages on a scheduled basis) is limited to your subscription period. After your subscription period expires, the software will revert back to the free developer license mode if it is not renewed. With a perpetual license, you can run the designated version of our software within or outside the development tools (SSDT-BI, BIDS, or Visual Studio) for as long as you want.

Development

How do I upgrade the software? What precautions should I take?

We always recommend keeping our software up-to-date. There are new features and enhancements along with bug fixes that are implemented into our products every release. In order to upgrade a licensed system to the latest software release, you need to make sure that you have up-to-date software maintenance for that particular license, which you can find out by checking the Maintenance Expiry Date after launching the KingswaySoft License Manager program. You need to make sure that your maintenance date is greater than the release date of a particular version that you want to upgrade to. In case that your software maintenance has expired, you can reach out to us for a renewal quote, we will be happy to assist you. Note that software maintenance is only applicable to perpetual licenses, not subscription licenses, as software maintenance is always included in subscription license, in which case you can upgrade to any version as long as your subscription has not expired. For the free developer license, you have the same freedom to upgrade, but we typically recommend you stay with that same version that you use for your production environment to maintain the maximum compatibility when you deploy SSIS packages.

Once you have confirmed you have an up-to-date maintenance that qualifies you for the upgrade, then you can proceed with the upgrade process. Best practices would be to uninstall the old version before installing the new version (our software does support in-place upgrade without having to uninstall first, but there are cases the in-place upgrade doesn't clean up the old version properly). We usually try to maintain maximum backward compatibility so your packages will continue to work after the upgrade. However, you will want to pay attention to any Breaking Changes that may have been introduced between versions, in which case you may need to make changes to your SSIS packages to work with the new version that you are upgrading to. It is highly possible that those Breaking Changes (if any at all) may not even affect you, in which case you do not need to do anything with your packages to have them work with the newer version.

We generally recommend you try out our new release in a DEV or test environment before implementing the new version in your production environment.

Information on any Breaking Changes can be found on our Change Log page. Some of those changes can be addressed by simply refreshing the component, while the others may require some additional efforts.

  • Example 1 : Our v7.1 release introduced an SSIS metadata change to the entity type code fields in the CRM destination component when SOAP 2007 / 2006 service endpoint is used. This particular breaking change can be taken care of by clicking the “Refresh CRM Metadata” button in the component (only those CRM4 or CRM3 destination components) as suggested in the change log page.
  • Example 2 : Our v5.0 release introduced significant metadata changes - especially around the Destination Component's Error Output. When upgrading from a prior-v5.0 release to this release (or any newer version), you will notice that the only output of the destination component (the Error Output) in the prior-v5.0 release is split into 2 outputs - the Error Output and Default Output. The Error Output no longer contains successful records, and there is no ID column anymore (which has been moved to the Default Output under the name - CrmRecordId). You need to make the necessary changes to your SSIS packages accordingly to work with those SSIS metadata changes.
Our CRM/AX/NAV server has been moved to a different server. How would I handle this within my package? 

In the case that your CRM/AX/NAV server has been moved to a different server, you would go through your SSIS project and re-configure your Connection Manager(s) by pointing to the new server(s). 

Deployment

After I finished developing my SSIS packages, I deployed them to my server environment. When I tried to run the packages on the server, I ran into the following error, what should I do to fix this problem?The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails. 

There could be many reasons for this problem. One that typically causes this problem is the difference between your development and server environments. For example, if you have a 64-bit system for your SSIS server, but you have a 32-bit system for your development environment, it is possible to run into this error. Make sure you are running the same bit of operating system on the two environments.

When I try to execute my SSIS packages as a SQL Agent job, I am getting the following error message. Why so? What should I do to fix this problem?Failed to decrypt protected XML node "Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

This is related to the package protection level setting used when the SSIS package is saved. By default, a SSIS package is stored using EncryptSensitiveWithUserKey option. This means that any sensitive data (such as Password in our case) is stored using the SSIS package author's user key. When a SSIS package is executed by SQL Agent job engine, the package will be loaded using a user account that might be different from the package's original author, who would have a different user key. Therefore the encrypted sensitive data cannot be properly decrypted. To address this issue, configure your SSIS job by entering the password with SQL Server Management Studio (SSMS). Alternatively, you can use the following options:

  • Change the package's ProtectionLevel setting from EncryptSensitiveWithUserKey to EncryptSensitiveWithPassword and provide a PackagePassword. In the SQL agent job's SSIS package execution step, navigate to Command Line page to enter the package password when prompted.
  • The best practice is to use SSIS Package Configuration wizard to create a .config file for your deployment by parameterizing your connection manager (leaving the ProtectionLevel as the default EncryptSensitiveWithUserKey). You would also have to manually add Password and ProxyPassword parts to your ConnectionString if you use these for your connection manager.
When I attempt to deploy an SSIS package or when executing an SSIS Package on SQL Server Management Studio for SQL Server 2014, I receive the following error message 'Unexpected Termination' (or System.AccessViolationException).

When using SQL Server 2014, a cumulative update is required (cumulative update 2 or later, or any recent service packs). The following is the list for the download links.