|
|
Peke, please provide more details + debug/freeze logs. |
|
|
Updated Description, steps and sent logs offline. |
|
|
image_2021_09_13T02_04_48_667Z.png (12,536 bytes) |
|
|
This deadlock is actually the same regression as in 0018281 (introduced while fixing 0017895) |
|
|
Fixed in 2502 |
|
|
Verified 2502 |
|
|
Reopen, I got this error while testing MM service installation and service permissions. |
|
|
Unfortunately no log file is created as service was started under "Local Service" permission which DBGView do not log. image.png (6,696 bytes) |
|
|
Based on the crash log it was assertion that MM5 wasn't closed within 10 seconds (this can happen only with debug build). The reason was that MM5.DB couldn't be accessed during that time (most probably because you were testing the MM service at the same time that was accessing the same DB). It is quite uncommon situation because normally either MM5 runs as service or MM5 is running (not both at once) The issue for improving the error messaging re inaccessibility of MM5.DB is now tracked as 0019578 |
|
|
Verified 2819 0019578 is fully implemented so this one can be closed |
- Anonymous
