en:troubleshootingmigration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:troubleshootingmigration [2020/01/30 16:08] – created Martin Machyniaken:troubleshootingmigration [2021/02/16 15:04] (current) Pavel Machyniak
Line 13: Line 13:
 </WRAP> </WRAP>
  
-When a problem occurs, you can examine the migration log file for any errors. You can find it in //%ProgramData%\TatraMed Software\T3C\Service\log\migrator.log//You can try to fix the problem manually or delete the entry. The following is a description of the updated data in the //Service// folder: +The data for the update itself, depending on the version, can be found in the following folders: 
-  * //job// folder contains downloaded studies+  * Since version 12, the //%ProgramData%\TatraMed Software\T3C\Service// folder 
 +  * Before version 12, the installation folder of //T3C Service// (the default folder is //%ProgramFiles(x86)%\TatraMed Software\T3C\Service//
 + 
 +When a problem occurs, you can examine the migration log file for any errors. The log file is //logs\migrator.log// or //log\migrator.log// 
 +The following is a description of the data in the //Service// folder by version
 +  * The //job// or //study// folder contains studies
     * if there is a problem with one particular study, we recommend deleting the specific subfolder     * if there is a problem with one particular study, we recommend deleting the specific subfolder
     * alternatively, you can delete the entire folder     * alternatively, you can delete the entire folder
-  * //robot// folder contains a database with records of currently running automated tasks. You can delete it, some tasks may not be completed and will need to be repeated 
-  * File //messages.db// - message database. You can delete it, you lose old messages. 
-  * File //rm.db// - database with study transfer records. You can delete it, you lose history. 
-  * File //notifications.db// - Database with notification settings. You can delete it. 
-  * File //users.db// - database with user settings. You can delete it. 
  
-Once the problem is fixed, you need to run the installer again to update the records. Other errors may occur, so the process needs to be repeated.+  * The //robot// folder - contains a database with records of currently running automated tasks. You can delete it, some tasks may not be completed and will need to be repeated. 
 +  * The //messages.db// file or the //message// folder - message database. You can delete it, you lose old messages. 
 +  * The //rm.db// file or the //record// folder  - database with study transfer records. You can delete it, you lose history. 
 +  * The //notifications.db// or //conf\notification.db// file - database with notification settings. You can delete it. 
 +  * The //users.db// or //conf\user.db// file - database with user settings. You can delete it. 
 + 
 +Once the problem is fixed, you need to run the installer again to migrate the records. Other errors may occur, so the process needs to be repeated.
  
 <WRAP round important 90%> <WRAP round important 90%>
  • en/troubleshootingmigration.txt
  • Last modified: 2021/02/16 15:04
  • by Pavel Machyniak