Upgrading your TimeXtender software should be fast and easy. On rare occasions, problems may occur as the result of an upgrade. This article discusses the three most common issues, and how to resolve them.
Cannot open one or more projects
Sometimes after upgrading, trying to open a project will result in an "out of bounds index/array" error, or an "object not set to instance of an object" error. This problem can be alarming, but it is not as serious as it may first appear.
This issue is usually due to a hidden problem in the repository database. Often, these problems are invisible to the end user, and are only revealed by the changes the upgrade process makes to the repository database. These issues are often caused by multiple people working on the same project at the same time without the proper use of work items.
To resolve this problem, submit a ticket and create a backup (.bak) of your repository database. We recommend compressing the .bak file, if possible. If the file is less than 20MB in size, you can submit it with your ticket. If it is larger than that, TimeXtender support will provide you with an FTP upload link.
If you need to continue immediately continue development work, you can restore the auto-backup created by the upgrade process to quickly regain access to your project while we resolve the issues with your repository.
Cannot deploy or execute SSIS packages
Inability to deploy or execute SSIS packages is an extremely common problem that many people encounter after upgrading. The reason this occurs is that for many security setups, you must run the application as an administrator. This setting does not transfer from old versions of the software to new ones, as they are considered different programs from the operating system's point of view.
The best way to deal with this is right-click on your program shortcut and select Properties, choose the Compatibility tab, click Change settings for all users, and check Run this program as an administrator.
Restart the program from the updated shortcut, and you should be able to deploy and execute SSIS packages with no problems.
Circular reference errors
In older versions of the TimeXtender software, circular reference detection wouldn't work properly in some circumstances. This allowed careless users to make bad circular references; it also allowed careful users to make functioning circular references.
In newer versions, circular reference detection works properly, and will not allow you to deploy any object that contain such a reference. This means that certain objects may not deploy properly after upgrading.
Exactly how to handle this problem depends largely on the nature of the circular reference. If you get this error, the first thing to do is determine whether or not your circular reference actually works. For instance, mutual lookups between two tables will never behave as expected, because both tables will be stuck waiting for the other to load.
If the reference does work, you will need to develop a fix. A common valid, although somewhat risky circular reference is to create a view of a raw table, then do a lookup from that view back into the same table. This self-reference will work, provided that none of the join or condition fields have a transformation on them that's relevant to the lookup process. However, if you have a parameterized view, this table will no longer deploy after an upgrade.
There are a number of solutions in this particular case - the easiest one is to replace the parameterized code in the view with the translated code, which can be viewed by selecting the translation button. After that, delete the parameters from the view, and the circular reference error will no longer occur. This technique does mean you will no longer get the benefits of parameterized code, but it is a quick and easy way to resolve this issue.