Automise Project failed with return code 9 (PROJECTLOADERROR)

Hi,

The Automise project failed with return code 9 (PROJECTLOADERROR) with the message below:
-------------------------------------------------------------------
Error Loading Project File : Unable to read log file: Unable to open table PRD_HUN_DIP_KONYMONITORING
NexusDB: : Table does not exist. Root table “PRD_HUN_DIP_KONYMONITORING” not found [$2728/10024]


Exit with return code: 9 (PROJECTLOADERROR)
--------------------------------------------------------------------
The project has just one action “Execute Program”, the program usually takes about  10-20 sec to run. The project runs every 30 minutes, it runs fine on the next iteration. 
We use Automise 4, Version: 4.0.0.166.

Any help appreciated!

Regards,
Ildar

Hi Ildar,

It appears the log file for the project has become corrupt. Delete the log4 file that corresponds to the project, and run the project again. The log file will be recreated.

Hi Jason,

Thanks!
The project scheduled to run every 30 min and it runs fine on the next iteration. The LOG4 file automatically recreates when it reaches the size of 2.25 MB.
Can I do anything else to fix this problem?

Regards,
Ildar

Great to hear the project is working again. Typically this is the only solution once the file has been corrupted. Another option is to turn off logging through the command line. From memory the “/S” option does this.

Hi,

We have the same issue with new Automise version: Exit with return code: 9 (PROJECTLOADERROR)
Error Loading Project File : Unable to create temporary log file: NexusDB: FBLogDatabase: INTERNAL: File could not be opened [C:\Users\XXX\AppData\Local\Temp\FBTE997.at5lck, error 32, The process cannot access the file because it is being used by another process] [$2405/9221]
Can be related this to Antivirus or backup programms?

Not being able to open the lock file suggests another instance of Automise has the project open already. An Automise project can only be opened by one instance of Automise at a time (the log file is a single user database, which uses a lock file to protect it).

BTW, it could be antivirus or backup programs but I would check for another instance first.