Jump to content

Pulseway agents not working anymore after Windows NET.Framework Patch


Recommended Posts

Posted

Hello all,

We have agents running over multiple rds environments.

Pulseway has patched Net.Framework

After this patch Pulseway dashboard is showing those systems as offline but they are up.

What ive tried:

  • Executing the PCMonitor.exe is not showing or doing anything
  • Reboot rds servers
  • Restarting service PCMonitorsrv.exe in services, is giving me this error: 'Windows could not start the Pulseway service on Local Computer / Error 1053: The service did not respond to the start or control request in a timely fashion.

Weird thing is, Pulseway dashboard is working on those systems, but the agent is not working.

Please help me out!

Regards,


Leroy

Posted

Hi Paul, & Mariale 

Thanks for the fast reply,

See attachment for the windows log: 

Screenshot2024-11-15at10_30_59.thumb.png.774ac5265cddfbf81fedaba3012410fd.png

After this i checked if the service was running, service wasnt running, when enabling the pulseway agent service i get this error:

 

Screenshot2024-11-15at10_34_44.png.9e27e9bdfc281712f5dc9d37ac0b83d0.png

Regards,

-Leroy 

 

Posted

The Pulseway service on workstations will not start and appears to be marked for deletion.  I was also unable to reinstall Pulseway agent and unable to uninstall the current Pulseway agent.  Any way to manually fix this?

  • Administrators
Posted

@KerryC for the crashes, did you see any "Application Error" error too? Can you please send us a screenshot of that event too?

If the service is marked for deletion it should be removed upon a reboot. Once it's removed, you can use installutil from the C:\Windows\Microsoft.NET\Framework64\v4.0.30319 folder to manually register the service:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil.exe "c:\program files\pulseway\pcmonitorsrv.exe"

-Paul

Posted

Hey @Paul I have been experiencing this bug too in the last week I lost access to multiple windows 11 systems. Is there any suggested fix for this issue yet as even reinstalling doesn't work to fix this issue. I have attached the event logs too.

 

Screenshot 2024-11-22 at 8.31.49 am.png

Screenshot 2024-11-22 at 8.32.33 am.png

Screenshot 2024-11-22 at 8.33.02 am.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...