Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SolarWinds Agent Fails to Start after Scheduled Windows Server Reboot/Reboot after Windows Patching

Hi SolarWinds Community.

I have an ongoing issue where SolarWinds agents are failing to startup after scheduled restarts of our Windows servers/reboots following Windows server patching.

We have adjusted all SolarWinds agent services start-up types from Automatic to Automatic(Delayed), and added a registry key HKLM:\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout with a DWORD value of 60000 (60 seconds) to extend the Windows default timeout from 30 seconds to 60 seconds, on the servers with a SW agent.

The agent start-up failures 'seem' to have reduced after these changes, but have not completely resolved the issue and this is still occurring on some servers.

I have collected and attached the diagnostics of the main polling engine and a few of the servers which have had this issue recently in a support call to SolarWinds Support. But, alas, I am off to a bad start with support suggesting steps that I have mentioned already that I have taken in the support call description (it is hit and miss as some of us know).

Has anyone who has experienced this issue been able to permanently resolved/implement a permanent workaround? I found this thread where @dsimpkins and AlterEgo were experiencing the same problem, but it does not seem to have had any resolution.

Regarding suggestion, I would prefer not to create an alerting template that runs a script that starts any agents that experience this issue, and would prefer to make the necessary configurations to resolve this issue on a SolarWinds or Windows server level.

Thanks community,

--t.m-k

Find more posts tagged with

Accepted answers

All comments

admin_nsn

Hi t.m-k

Even though I do not have a complete fix for this issue, I'm first of all relieved to not be the only one experiencing this issue.

What I've done is, I've created a simple script running scheduled every hour from Jenkins that will detect issues with "broken" agents. Then move the agent to another polling engine. This seems to fix the issue pretty often. If that doesn't work, it'll try to restart the agent service remotely from Orion.

If none of the above works, we're forced to re-install the agent in order to re-establish monitoring.

t.m-k

Thank you admin_nsn, that is something that can be done of course but does not fix the underlying issue.

--t.m-k

zennifer

I am suspect of the .Net Framework. I don't use that many agents. SolarWinds agents rely on the .NET framework. If the update included changes to the .NET framework, it might require a restart for the agent to function properly. In any case, since you are both experiencing the same issue, I would open a support case. This needs to be properly identified, there may be a bug in the code that can be addressed with a patch.