Who is this article for?

IT Administrators who encounter "Error 1067" when starting the Robot service.

IT Administrator permissions are required to resolve the issue.

When starting the Robot service, you might get the error message "Error 1067:  The process terminated unexpectedly".

This article explains why the error occurs and how to fix it.

1. Issue

Error 1067 is a generic Windows message indicating that a service failed to start, without specifying the cause.

The Windows Event Viewer System log will show a matching entry.

2. Solution

Since this is a generic error message, finding the underlying cause requires some additional work. The error causing the issue is normally logged in the Robot log file.

To access the log file:

1. Navigate to the file location.
   By default, this is C:\Program Files (x86)\Pentana\ServerRobot\[Pentana Instance]\ServerRobot.txt.
2. Open the file.
3. Scroll to the end of the file.
4. Find error messages logged at the time you tried to start the service.

The errors listed will determine what troubleshooting to do next.

If the file is missing, ,ake sure that the Windows account used by the Robot service has permission to write to the parent folder.  If it doesn't:

1. Grant the user permission to write to the folder (e.g. C:\Program Files (x86)\Pentana\ServerRobot\[Pentana Instance]).
2. Try starting the service again.
    You might find it works this time, as the Robot fails to start if it can't create its log file.
3. Check that you're looking in the correct folder. 
   The Robot log location is configurable, and might have been changed.