Hi, I have the message below starting the engines. Collabo

Hi sonamg

1. We should stop the respective engine(s), when transferring the kdbs.
2. The possible cause for the above problem is , the kdbs might have corrupted.(Earlier the engines were didn't shutdown properly)
3. When we got the issue like this, we can resolve by either of the following.
   • Rename the latest working kdb to next number appended in the series.(So the engine(s) will start pointing new one)
   • repair the kdb by running the repair script.(If you are in production environment it not recommend to do. Please raise a support case) Please go through this link for instructions . https://docs.appian.com/suite/help/17.2/Appian_Engine_Repair.html 

Old folder kdbs.

If all the engines are showing the FATAL status, that due to some other reason i.e., Some went wrong.(Start doing from the beginning with fresh installation)

If you are upgrading the your Appian, make sure you are following update guide and also you are using the same primary data source.

Suppose for example if you want to repair the  process execution engine kdbs, Please fine the below steps(Assume my Appian is in C:/ drive.)

1. Navigate to location where repair scripts available.
   • cd C:\appian\server\_scripts\tools
2. Repair the kdb file which is corrupted.(not working) .
   • repair C:\appian\server\process\exec\02\gw1\pe44.kdb
3. Navigate to the engine kdbs location.
   • cd C:\appian\server\process\exec\02\gw1\
4. Create new kdb file with the repaired kdb file.The new kdb file should be the highest number kdb file.(So the engine will start pointing the new kdb file)
   • copy pe44.kdb.repaired pe55.kdb