24 / 7 FAQ and Know How
In an earlier version of migRaven was it possible the path for the
To set log records within the directory. This was on by default \ Program Data \migRaven\ Archivelog
When updating to a newer version, this setting will not be migrated appropriately.
Since version 6.3.19351 a path is explicitly required.
So if an update has been made it may cause errors in the newer version come, ie. the log is not created.
Check if an appropriate folder is specified and set
If this is not the case.
Relevant for the data owner
The log files will continue under "ProgramData \migRaven\ archiveLog "and may not be accessible by the data owner.
Please configure a share on which also the account "Authenticated Users" has read rights, as these log files can be downloaded by the user via task monitoring.
Permanent link to this post: https://help.migraven.com/data-retention-log-wird-nicht-gespeichert/
The status of the archiving may be stuck at "Will be executed" and will not change anymore.
If this is the case, check if the anti-virus scanner has quarantined DataRetention.exe.
To be sure, it is recommended to put the whole folder MigRavenResourceScanServiceHost on the whitelist
Then restart the services.
Permanent link to this post: https://help.migraven.com/data-retention-wird-nicht-ausgefuehrt/
Permanent link to this post: https://help.migraven.com/auswahl-des-domain-controllers-fuer-den-ad-scan/
If a project is on -1, eg because saving was not completed correctly, it can be adjusted in the database.
(This query will set all projects to 0)
The query is:
match (u: Project) set u.status = '0' return u
Permanent link to this post: https://help.migraven.com/projektstatus-auf-0-setzen/
After the scan, the data is stored in the Neo4j database. Once this process is completed (saves to Db) the project should be set to 0 status, before that should migRaven under no circumstances be terminated.
Permanent link to this post: https://help.migraven.com/projekt-wird-nicht-angezeigt/
Each ResourceScanServiceHost exists under the label
Service 3 attributes:
excludedfolders excludedfiles s.excludedpaths
In order to exclude desired paths, folders or files from the scan, the respective values must be entered here. All projects that are scanned or rescanned after this change are subject to the filter.
Permanent link to this post: https://help.migraven.com/ordner-von-scan-ausschliessen/
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:
Permanent link to this post: https://help.migraven.com/http-error-403-14/
Depending on the configuration of migRaven, it is recommended to adjust the heap size in the database config, otherwise there could be difficulties with the saving process in the database.
Permanent link to this post: https://help.migraven.com/datenbank-heap-size-anpassen/
With Windows 10 exists since the Anniversary update
(Version 1607) the theoretical possibility to cancel the limit for the standard 260 character limit.
In the registry can be found below
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Filesystem a DWORD (32-bit) named LongPathsEnabled.
Under a standard installation this is with the value
0 deposited. Change this to 1 to activate the option.
Permanent link to this post: https://help.migraven.com/ueberlange-pfadnamen-unter-windows-10-windows-server-2016/
1. 64bit version
Important for a Java update is that you install an 64bit version again.
2. Path of the new Java version
If you have made an update to a new Java version and for that the migRaven Database services are stopped and restarted, the following error message is displayed:
Error2: The system can not find the system path to the new Java version
Open the cmd console with a user who has the rights to manage windows services.
Go to the database directory, by default: C: \ Program Files \migRavenDB \ bin
cd C: \ Program Files \migRavenDB \ bin in the console to call the directory.
Stop the database services in the services in the order before:
DB Service Host
Then enter in the cmd console:
neo4j uninstall service,
by neo4j install-service.
Restart the shutdown services and migRaven is ready for use again.
Permanent link to this post: https://help.migraven.com/java-131-problem/