Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ent Manager & Ops Man

Status
Not open for further replies.

12345kevin

Vendor
Feb 15, 2006
125
GB
We are getting a problem where at least once a week the server requires a reboot as the customer is unable to login to Ent manager. We upgrade to the latest software approx 2 months ago and still have the same problem.

This is the customers own server, and they say it never peaks much above 10% usage and they are happy with it etc etc.

Any pointers would be useful, we're currently waiting on Mitel support, but I don't hold much hope !
 
I had an issue where autodiscovery was trying to discover sets within a Class B network (65533 hosts) this caused the memory usage to expand until the server became unusable.

I would disable autodiscovery on your site and see if the problem goes away.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Are you using XP or Server o/s? XP will usually only allows 2 concurrent connections and I have seen XP do this exact thing.

30 years and it's still true.....NO GOOD DEED GOES UNPUNISHED!
 
The server is running 2003 Server edition, with all latest updates I believe.
 
What else is running on the server? There's a few backup and a/v clients out there that mess with the EMan/OpsMan services and could be causing this. Does the issue occur on the same days/at the same times? What do the server Application Logs tell you is going on when the problem occurs?
 
I had this exact same problem, even had a ticket open on it. The latest vers of EM seems to have solved it.
 
Hi
There was an issue with RMI that would cause the virtual memory to be used up and needed the server to be rebooted to clear this and allow ent/ops to work again

This is now fixed so if you run on rel 4 + you should be ok
 
Be careful when upgrading to release 4 if you are running a firewall, they changed the RMI port assignments to overcome the problem, but you need to make sure the new port assignments are allowed by your firewall first, or you'll have to mess around in the config files to change them back to the 3.x ports. A lesson I learned the hard way.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top