TracePro crash at startup

Question

Synopsis

Solution

"The possible causes of the problem differ if TracePro has run successfully on this PC for a period of time and then it failed vs a failure the first time TracePro was launched.

IF TRACEPRO HAS RUN SUCCESSFULLY ON THIS PC IN THE PAST

Here are a couple of likely explanations/resolutions to this problem:

1- Each time TracePro is exited, there is an initialization file named TraceProXX.ini (XX is the TracePro Release) that is saved with information that is useful to carry over to the next launch of TracePro (e.g. - license info, recent files opened, etc). On rare occasions, this file can become corrupted. TracePro will function without this file, but it will not have memory of the license information. Please locate TracePro.ini on your PC:

C:\Users\ <username>\AppData\Roaming\Lambda Research Corporation\TracePro

To determine if it is causing the crash, rename the file to TracePro_temp.ini. Once that is done, please try launching TracePro again. When prompted, enter the license information and see if TracePro runs successfully.

If TracePro runs successfully, delete the corrupted TraceProXX_temp.ini. A new TraceProXX.ini will be saved each time you exit TracePro. Please note the inconvenience that some of your personal TracePro preferences may be lost, but there is nothing saved in the ini file that would ever impact a ray trace result. If TracePro still crashes, delete any new TracePro.ini file that might have been created, then rename TracePro_temp.ini back to TracePro.ini, as this file was not the cause of the problem.

2- The TracePro Properties Database file, TracePro.db, can on rare occasions become corrupted. TracePro will not function without a Properties database file, and this file contains all the custom properties you have created in TracePro. Please locate TracePro.db on your PC:

C:\Users\ <username>\AppData\Roaming\Lambda Research Corporation\TracePro

To determine if it is causing the crash, rename the file to TracePro_temp.db. Once that is done, please try launching TracePro again. When prompted, click Yes to have a factory fresh TracePro.db file copied to the specified directory.

If TracePro runs successfully, please send us TracePro_temp.db and we will try to repair the file to salvage any properties you have created in TracePro in the past.

If TracePro still crashes, delete the new TracePro.db file that was created, then rename TracePro_temp.db back to TracePro.db, as this file was not the cause of the problem.

If the suggestions above do not resolve the problem, please write to us at support@lambdares.com and we'll work with you until the problem is resolved.