Facebook
Twitter- Server operating system version
- Windows Server 2016
- Plesk version and microupdate number
- Plesk Obsidian 18.0.47
Hi,
I'm using Plesk Obsidian on Windows and System Health Monitor Service (C:\Program Files (x86)\Plesk\admin\bin\Parallels.MonitorSrv.exe)
crashes ALWAYS when it runs. There is error log in below but you 'll understand problem when I explain it.
I have two disks (C, D). My primary disk is C, and I use D for only backup purpose. I backup files to D Disk locally, then I upload them to Google Drive automatically. So Yes I have Google Drive application on machine. Google Drive applications creates a virtual disk (generally G:\). When system health monitor service try to read this disk it crashes. I tried many thing to solve it. I tried to change permissions, security settings on G disk, b ut I failed because it if a virtual disk and you cant change many thing on that drive.
There is crash log in below. As you can imagine, this logs are very old because It's impossible to start this service on my machine.
You just need to add a try-catch block for reading Disks (specially with G letter). I think it will solve this problem.
Logs from C:\Program Files (x86)\Plesk\admin\logs\HealthMonitoring20221025.log
Have a nice day
I'm using Plesk Obsidian on Windows and System Health Monitor Service (C:\Program Files (x86)\Plesk\admin\bin\Parallels.MonitorSrv.exe)
crashes ALWAYS when it runs. There is error log in below but you 'll understand problem when I explain it.
I have two disks (C, D). My primary disk is C, and I use D for only backup purpose. I backup files to D Disk locally, then I upload them to Google Drive automatically. So Yes I have Google Drive application on machine. Google Drive applications creates a virtual disk (generally G:\). When system health monitor service try to read this disk it crashes. I tried many thing to solve it. I tried to change permissions, security settings on G disk, b ut I failed because it if a virtual disk and you cant change many thing on that drive.
There is crash log in below. As you can imagine, this logs are very old because It's impossible to start this service on my machine.
You just need to add a try-catch block for reading Disks (specially with G letter). I think it will solve this problem.
Logs from C:\Program Files (x86)\Plesk\admin\logs\HealthMonitoring20221025.log
Have a nice day
