You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that Windows 7 is already EOL but I have several pc with Windows 7 32bit that started to disconnect systematically after upgrade to MeshCentral 1.1.34.
The only log that I was able to find is this from agent:
[2024-11-29 03:25:15 PM] [A6FCA84280C769A8] ..\microstack\ILibParsers.c:2776 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00af59be / BaseAddr: 0x00b2807d / Delta: 206527]
same error is displayed if I try to re-install the agent
adding coreDumpEnabled=1 to .msh file provide no output
Windows 10 and linux installations seem to be not affected
EDIT:
after several tries I was able to get in the log this message Certificate loaded from DB was not signed by our root cert in the Cert Store
and google helped in try this change in .msh file nocertstore=1
with this modification agent start and connect ok.
downsides:
a. pc is duplicated in list as it seems that the nodeId changes.
b. need to be applied manually at new installations or update msh definition on server side
The text was updated successfully, but these errors were encountered:
I know that Windows 7 is already EOL but I have several pc with Windows 7 32bit that started to disconnect systematically after upgrade to MeshCentral 1.1.34.
The only log that I was able to find is this from agent:
[2024-11-29 03:25:15 PM] [A6FCA84280C769A8] ..\microstack\ILibParsers.c:2776 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00af59be / BaseAddr: 0x00b2807d / Delta: 206527]
same error is displayed if I try to re-install the agent
adding coreDumpEnabled=1 to .msh file provide no output
Windows 10 and linux installations seem to be not affected
EDIT:
after several tries I was able to get in the log this message
Certificate loaded from DB was not signed by our root cert in the Cert Store
and google helped in try this change in .msh file
nocertstore=1
with this modification agent start and connect ok.
downsides:
a. pc is duplicated in list as it seems that the nodeId changes.
b. need to be applied manually at new installations or update msh definition on server side
The text was updated successfully, but these errors were encountered: