Rant.... EOC 1.1 down

I really, really hate to rant but I have had a high priority ticket (98388) open since yesterday and received only 2 less than helpful emails from support which has not fixed my situation. I even emailed this morning requesting that they escalate it to URGENT as I have now been down for 22 hours.

My EOC application died for some unknown reason yesterday with the error "Error: There was no endpoint listening at net.tcp://localhost:17777/Solarwinds/InformationService/EOC that could accept the message. This is often caused by an incorrect address or SOAP action...."

My EOC site was clicking along and then this error....

I have verified that port 17777 was still accessible from all Orion's (in fact in the settings all Orion's still passed the connectivity test) and no other actions were done on the EOC server or database.

I have repaired all of the Solarwinds components as well as re-run the configuration wizard – several times. All services are up and running. When I try to run the Network Atlas against the EOC server I get the error “Server is not reachable”.

Any help from the community would be greatly appreciated as going on 24 hours of down time does not make me or Solarwinds look good to the eyes who pay the large renewal fees.

Find more posts tagged with

port_17777

no_endpoint

eoc_1.1

Accepted answers

FormerMember

Thought I would post the resolution so others can learn from my mistakes....

First - "NEVER TOUCH THE DATABASE DIRECTLY!!!!"

The problem was self generated when I had added a CP to my Orion last week and thought I gave it the wrong data type. I "fixed" the data type by going into the database and 'adjusting' the data type for the new CP. That fixed my problem and life was good - until I added more CP's this week. When I added new CP's to my Orion it then posted them to EOC which then picked up the fact that my CP I added last week did not match up to what the latest update from Orion was - hence I had 2 of the same CP's of different types trying to be pushed to EOC - and it didn't like it. I deleted the CP I added last week on the 2 Orion's in question and readded them and then cycled services and it fixed the problem.

Thanks to Zeid for taking the time to walk me through all of the many logs and such to identify the problem and getting it resolved. I will not flame support for their failure to solve the problem in a timely manner but Zeid saved the day!

All comments

derhally

I will take a look at your case.

FormerMember

Thought I would post the resolution so others can learn from my mistakes....

First - "NEVER TOUCH THE DATABASE DIRECTLY!!!!"

ElisabethZakes

I'm sorry you didn't have a good experience with support on this issue. We do try to respond as quickly as possible and to look at all factors that may be contributing to the problem in an attempt to find the best solution for you.

I'm glad Zeid was able to get you fixed up!

AndyMT

I had a similar issue but I did not modify my database directly as mentioned by a previous post. It has just been running stock since the upgrade from 1.0 to 1.1.

I had to restart each and every service one at a time till things started working.

I have no idea what is wrong but it is much less stable since the v1.1 upgrade with the Atlas component.

hcaballe

Can you share what Zeid did to resolve your issue? Looks like we are having similar issue.

FormerMember

Not sure exactly what your issue is with your EOC but ours had a big error on the web page. I could click on some of the links at the top but the main page would nto come up error free.

What I had to do was look at and comapre the CP's of each Orion that was connected. You could try to uncheck the Orion's one at a time and see if this helps. If you get a working page then you know basically were the conflict is. But like I said I am not sure if this is your issue or if it is service related.