On Main Server

Error message

This database has transaction info and needs a journal file to start.


Resolution

The database has been initialized to run with journaling enabled, but you are trying to run with no journal file specified or it cannot locate the journal file. The following possible alternative fixes can be tried in this order: 

  1. Browse to and select the selected database's journal file in the Journal file: field. This will likely resolve the error.
    OR
  2. If you have decided to run without journaling or have taken a copy of the database for test and are getting this error with the test database, you will need to remove journaling. If, at a later date, you want to run a mirror server against the main server, you have to use the database manager to restart journaling by creating a new one

Error message

Journal ahead of database.


Resolution

The journal file and the database are out of sync. You may be running an old version of the database against a newer version of the journal file. This can happen if you reload a backup of the database. The following possible alternative fixes can be tried in this order: 

  1. You are running the wrong database or the wrong journal file. Please check and change one or the other or both.
    OR
  2. Remove journaling and create a new journal file. If you are running mirror servers, their caches may now be invalid and they need to be reset.

Error message

Database transaction does not exist in journal.


Resolution

The journal file and the database are not compatible. The journal file does not contain information about the last transaction done in this database. This can happen if the journal file is "older" than the database. The following possible alternative fixes can be tried in this order:

  1. You are running the wrong database or the wrong journal file. Please check and change one or the other or both.
    OR
  2. Remove journaling and create a new journal file. If you are running mirror servers, their caches may now be invalid and they need to be reset.

Error message

Last transaction info not found i db.


Resolution

The journal file and the database are not compatible. The journal file does not contain information about the last transaction done in this database.  The swjournal file is specified and exists, but there is no transaction information in the database. The following possible alternative fixes can be tried in this order:

  1. You are running the wrong database or the wrong journal file. Please check and change one or the other or both.
    OR
  2. Remove journaling and create a new journal file. If you are running mirror servers, their caches may now be invalid and they need to be reset. 

On Mirror Server

Error message

User does not exist or invalid password. 


Resolution

You need to specify the correct password for the "system" account to enable the mirror server to connect to the main server.


Error message

Db transaction does not exist in journal.


Resolution

The mirror server cache and the main server database with journaling are not in sync. This cannot happen during normal operations. It can happen if you restart the main server against an older backup database. The most common error is trying to connect to the wrong main server. The following possible alternative fixes can be tried in this order:

  1. Verify that you are trying to login to the correct main server, i.e., that the host and IP address are correct.
    OR
  2. Restart with new cache file.

Error message

Error - Could not verify transaction, Journaling not enabled.


Resolution

You are trying to start a mirror server against a main server that has not been prepared for mirroring. Restart the main after enabling journaling.


Error message

Mirror login refused: journaling is not enabled


Resolution

The following possible alternative fixes can be tried in this order: 

  1. Verify that you are logging in to the correct main server. 
  2. If you want to run with a mirror server against this main server, you need to enable journaling.

Error message

Incomplete transaction info in db


Resolution

The journal file and the database are not compatible. The journal file does not contain info about the last transaction done on the selected database. This can happen if the journal file is "older" than the database. The following possible alternative fixes can be tried in this order: 

  1. Verify that you are logging in to the correct main server and/or have the correct journal file selected.
    OR
  2. Remove journaling and create a new journal file.

Error message

Users are getting "Error communicating with server. Connection to server is terminated."


Resolution

The mirror server cannot connect to the main server. Investigate if the main server is down. It will need to be restarted and then the mirror server(s) will need to be restarted.


In DatabaseManager

Error message

Cannot create cache file if journaling has not been enabled.


Resolution

The database is not set up for journaling. Before you can create a cache file, you must first enable journaling.


In Test Environment

Error message

Unexpected crash: Journal ahead of database.


Resolution

If you have taken a copy of the production database and production database journal for use in a test environment, most likely the journal will be ahead of the database copy. You do not need to have journaling enabled in your test environment. Simply remove journaling for the database copy that you have in your test environment.