Connection timeout. A timeout occurred during execution which resulted in the job being canceled. HELP :(

Hi,

Has anyone come across this error on application templates before?

Connection timeout. A timeout occurred during execution which resulted in the job being canceled.

We have 8 polling engines and this is only happening on one of them. Some templates work fine on this polling engine as well, however A few were green yesterday and now have gone to unknown and are displaying this message.

I do keep tabs on all unknown templates and we do have very few that are actually unknown so I don't think its a stress issue, plus SAM polling is at less then 6%

I have seen similar known issues but none that seem to display this exact error message.

The node is up and I have tested the credentials which all come back as working.

Find more posts tagged with

sam

active directory

application templates

server and application monitor

Accepted answers

All comments

grantallenby

Anyone have any advice? Still get this. one minute the application is green, the next to goes known with this...

sum_giais

Did you happen to resolve this by any chance grantallenby? Seeing the same issue now. Wondering if it's self-inflicted though.

skipdog77

Which operator system are you seeing this under? We just began to observe this same behavior.

OS: Windows Server 2016.

jere557

I also have this problem..... any update? Monitoring an application on a Windows 2008 R2 Server.

grantallenby

Never actually got this resolved

jere557

We ended up opening a ticket with Support. Looks like Orion wasn't able to see the Counters from where they are stored on the Windows Servers we were monitoring. There's a couple command line commands to run to fix it, but since this was on our Domain Controllers we weren't able to do it in the time i was there. We had to wait for a change window, and i was only on site for the week. I'd recommend opening up a ticket with Solarwinds, and they should be able to get it resolved within minutes. Support guy says he sees a couple times a week, and fixing the issue "most times" does not involve a reboot on the target node.

sierra1011

Same issue here, maybe 1/3 of our DCs are showing unknown and the counters will test successfully individually, but testing all of them simultaneously causes the Performance Counters to time out (Windows Service Monitors and Windows Event Log Monitors work fine), usually most of them but frequently all. I'll open a ticket as suggested to do so by jere557 and in the meantime I'll try disabling some of the monitors I don't need right now.

beohmer

Yeah, having the same issue as well only specifically on the Security application template on one DC. Other monitors using the same method (RPC) with the same credentials to the same resource (Event Logs) on the same DC are working fine.

If anyone has specifics on how to resolve this without a reboot, that would be swell!

jlhartsock

We're seeing the same behavior on the AD template. Some work without any problems while other just randomly start displaying the mentioned error message. Following this thread while I wait on a response.

grantallenby

Unfortunately I never got a straight answer.

After many deleted templates and reboots ours worked and stayed stable. I would be interested thought if anyone knows outright what causes it and how to resolve.

beohmer

Reboot of the node in question was ultimately what fixed it for us. It's been a week now and the components that were giving us fits have been quiet.

jmvelasquez01

i just applied the template "Windows Server 2016 Services and Counters" to a few 2016 server and received same result "Connection timeout. A timeout occurred during execution which resulted in the job being canceled."

be interested on the fix was for this.

beohmer

Reboot took care of it for us. Been quiet for weeks...granted a non-reboot solution would be preferred!

petergwilson

Anyone got an answer to this. We've just replaced our domain controllers (2008 to 2012 - yes I know but I have no say in things). and are getting this. A fix without reboots would be nice as we can only reboot servers from 07:00 to 09:00 on Tuesday mornings (unless something breaks, then we can do what we like ).

grantallenby

Morning Peter,

Unfortunately I'm no longer with Comtact, but I'd get them to log you a ticket. James should be able to do it for you. Failing that try deleting the template all together and re adding it.

I'm guessing you have swap templates to the 2012 ones anyway? So the above might be pointless. You can also try installing the agent and seeing if polling the SAM Template through the agent fixes it. Its an easy download and is non intrusive so doesn't need a reboot to work.

Let us know how you get on.

Many Thanks,

Grant

amrita1690

Hi Folks,

Has anyone got solution for this ?

pushpendra

We had similar issue and by going through each post i figured out that it could be related to WMI services, so when I looked into the server services were in 'stopping' state, hence a reboot is required, I tried to restart the services via cmdlet I got the below error and service(wmi) simply will would not restart.

so *.bat file script might be required to do timely restart of the service to avoid such issues in future.

Thanks,

tjkru

I had this same issue. Found a solution that worked of me. I am using Server 2016 both on the Solarwinds nodes and the host that had the issue. This host was managed using an agent. Found the solution in the another Thwack post. I basically removed and re-added the failing SAM application from the specific node it was failing on. Yes I did lose the historical information for this monitor but in my case this was not an issue for this machine.

Text from Thwack post with solution:

Go through all of the currently assigned applications and remove any that are failing as down or unknown. If you don't want to remove them figure out why they are failing and resolve it. Failures and unknown components take much longer to process because the scheduler has to wait for the timeout before it finally gives up.

Link to solution: Success Center

ales.vrbas

Hello Everyone. I came across the same issue and non-restarting solution was to assign the node to another polling engine (if you have one).