About this task
The Service is not running
Applies to
All Versions and Systems
Procedure
Check the Log files and the System performance for overutilization.
...
Folder Path
| Code Block | ||||
|---|---|---|---|---|
C:\Program FilesProgramData\SVA\BVQ\bvq-core\bvq-server\bin C:\Program Files\SVA\BVQ\bvq-core\bvq-server\logs C:\Program Files\SVA\BVQ\bvq-core\bvq-scanner-localmongodb\logs C:\UsersProgramData\SVA.DKarch\AppData\Roaming\SVA\BVQ\bvq-guiserver\logs | ||||
| Expand | ||||
| ||||
| Panel | ||||
|
In many cases, the memory provisioning has to be adjusted.
| Expand | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Panel | ||||
|---|---|---|---|---|
| ||||
Please reinstall the BVQ scanner with a higher value for Java max heap size, depending on the current size and on the available memory. |
Reinstall BVQ with the correct version.
Start the installer as administrator
...
| title | expand... |
|---|
...
| borderColor | black |
|---|---|
| borderStyle | solid |
...
Work through the wizard until you find the specific page, in this case Web server and enlarge the Java max heap size
...
If Services shut down to to not enough memory,
you can always use your BVQ° install file to adjust the memory values provided to the services.
After a service restart due to an update, the MongoDB service starts first, followed by the Server service attempting to connect to the running MongoDB instance.
If your Server service shuts down a few seconds after each start, it may be due to incorrect credentials. You can find the relevant entry in the MongoDB log:
| Code Block |
|---|
"error":"AuthenticationFailed: SCRAM authentication failed, storedKey mismatch" |