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

I am not able to Poll an application nor create a new app

I get this error anytime to poll/test/or create.... any ideas....

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Find more posts tagged with

Accepted answers

familyofcrowes

Wow... sorry, been so busy I missed all this..... Kate did fix it....

Here is Kates update:

They have 3 pollers; APM is primarly used on the 3rd poller although it's installed on all 3.

My first thought was Job Engine which I replaced on all 3 pollers, but no luck.

Noticed that the APM Poller was throwing errors saying it couldn't connect to the business layer host of the primary poller. He said that they'd recently had to rebuild the primary, but hadn't touched the other 2. Tried re-running config wizard, no errors but didn't fix it.

Verified I can telnet to 17777 on primary.

Repaired core & npm on APM poller; now it works! Repaired other poller ...

All comments

familyofcrowes

Error is:

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

martin.susil

Did you try to restart Orion Services?

If you are connecting to Additional Website (not primary Orion), then make sure that time is set correctly (synchronized) on all Orion machines.

There might be some additional information about the error in these log files

c:\Documents and Settings\All Users\Application Data\SolarWinds\Logs\Orion\OrionWeb.log

c:\Documents and Settings\All Users\Application Data\SolarWinds\Logs\APM\APM.BusinessLayer.log

You can try to reproduce the issue and then see what messages will show up in these logs.

If you won't be able to figure out the cause of the error yourself, please open a support ticket.

familyofcrowes

Thanks for the ideas. Restarted all services on all servers and still have the same issue. I have a ticket open and a Go To setup in 30 minutes so I'm sure Kate will figure it out.

Thanks!!!

aLTeReGo

If you or Kate were able to find a solution please post it here so the entire community can benefit. Thanks!

FormerMember

did we get a solution for this guys? can you post the solution from tech support?

familyofcrowes

Wow... sorry, been so busy I missed all this..... Kate did fix it....

Here is Kates update:

They have 3 pollers; APM is primarly used on the 3rd poller although it's installed on all 3.

My first thought was Job Engine which I replaced on all 3 pollers, but no luck.

Verified I can telnet to 17777 on primary.

Repaired core & npm on APM poller; now it works! Repaired other poller ...

FormerMember

aww thanks mate.... i can not even get to the bit of IPSLA where i have to select the node, so the only way i could even consider getting this implemented would be to run the repair on all nodes, and that would no doubt mean restarting all servciesm which will in turn re-trigger everything that is in alert, nd with multiple customrs on there it is just not feasable...

this product is very frustrating some times :-( we have 8 additional pollrs, and an additional website.... total nightmare

aLTeReGo

If you're using the Advanced Alert Manager then alert emails should not be re-sent unless the condition of the monitored object has changed.

mdriskell

Just wanted to state that I had similar problems with the faulted state error on 3 pollers today after migrating the primary to a new server....Repairing core & SAM on all 3 corrected my issues as well.