Category: Troubleshooting

Java version on migRaven Update server

Replacing the existing Java installation with another / newer Java version Java will be on the migRaven Server is required for the neo4j database. Please proceed in this order. Updating the Java version without re-registering the Windows service leads to incorrect behavior. As a rule, the "aikuxGraph" service can no longer be started. - End the ...

Read more

Permanent link to this post: https://help.migraven.com/java-version-auf-migraven-server-updaten/

Consistency check of the migRaven Database

To check whether everything in the database is correct, the following commands can be executed: This is also explained in detail on the neo4j website. https://neo4j.com/docs/operations-manual/current/tools/consistency-checker/ The name of our database is = graph.db. If there are any errors in the TXT file, please make them available to our support at support@migraven.com. This is what the output looks like if ...

Read more

Permanent link to this post: https://help.migraven.com/konsistenz-check-der-migraven-datenbank/

Data retention log is not saved

In an earlier version of migRaven it was possible to set the path for the log recordings within the directory, which by default was \ ProgramData \migRaven\ archiveLog When updating to a newer version, this setting is not migrated accordingly. Since version 6.3.19351, a path for this has been expressly requested. If an update has been carried out, errors can occur ...

Read more

Permanent link to this post: https://help.migraven.com/data-retention-log-wird-nicht-gespeichert/

Task monitoring (admin)

Task Monitoring shows you active, scheduled, and past directory builds and archives.

Read more

Permanent link to this post: https://help.migraven.com/aufgabenueberwachung/

HTTP Error 403.14

If the browser shows the 403.14 error message when the Web client is invoked,you should look in the Windows features for the solution:

Read more

Permanent link to this post: https://help.migraven.com/http-error-403-14/

migraven database service start problem after Java update

The automatic update of Java has the problem that the database used can no longer find the correct Java version after the update and therefore cannot start. For this reason, the new Java version must be saved in the Configuration database. 1. 64bit version It is important for a Java update that you install a 64bit version again. ...

Read more

Permanent link to this post: https://help.migraven.com/java-131-problem-migraven-datenbank-startet-nicht-nach-update/