On one of the agents, is your server listed as the server in the 'Server details' section of the EMSS Agent Control Panel?
You should be able to bring up the EMSS Agent Control panel by double-clicking the 'HEAT EMSS Agent Control Panel' icon in the system tray/notification area.
Yes, the server is listed there with it's FQDN, ports are also correct. When i have a look in the Event Log, there are lot's of Event ID 256 Error "TimeoutCallback". So i would assume the clients tries to reach the server, but it's not answering.
I doubt, i'll have to reinstall the whole EMSS Server...
Wanted to make Videos from that procedure anyway....
But anyhow. If you have other tipps, i'm happy to hear them. Just because I'll not be able to reinstall that stuff within the next couple of weeks (is just my playground)
Have you rebooted your webserver since you started experiencing this issue?
Yes, of course.
i had a look in the event log at the EMSS Server just a sec. ago, i can see several messages reporting some components are missing or corrupted. maybe this is the reason for this behavior? Or is it a consequence of something else?
LOL I figured, but had to ask.
It's interesting that this issue and the other issue re: Installation Manager happened at the same time. I can't wrap my head around how the DB server being unavailable would cause corrupt/missing components on your web/app server.
On the webserver, if you go to Help > Technical Support, what do you see listed for 'Last Agent Connected'?
Hugh, the field is empty... didn't expect that.
strange things are happening here... I also saw in the logs, that the Bitdefender Engine is not able to contact the update servers to retrieve updates. That's all quite strange...
I have to say, i'm not so familiar with the Lumension products, I'm an DSM Engineer. Tell me about a problem there and i can pray down all the architecture and possible failure causes, but with lumension i'm completely lost. OK, EMSS is not so difficult to install. Pretty much straight forward. But when there are errors...
Do you have the EMSS agent installed on the webserver?
If so, when was the last time it checked in?
No, i did not.
Anyhow. I think I'll trash the server and rebuild it from scratch. Will cost me about 1,5 h. It's probably quicker than finding a fix for this problem... Just have to find out, if there's an option to export configurations before i trash it
Before you start all over review 931 Testing Agent Communications - L.E.M.S.S. This should give us a good indication as to why the Agent is not communicating.
Also, if you review the lmhost-main.log located in C:\ProgramData\HEAT Software\EMSSAgent\logs\ folder, search for winhttp and the logs should document the error code.
sounds like a useful information. I'll definitely give it a try
I'll checked the lmhost-main.log, there is nothing with winhttp listed in there. But what i have seen is, after the installation the client tried to upload some kind of XML File to the management server using a POST XML command. But it get's an Error 404 Back from the Webserver.
So i assume somehow permissions on the Application server have been screwed up. Don't have any idea what happened, because i didn't touch the system for 2 month execept logging on and having a look at the stats some times...
Thanks for the help so far, but i don't want to put more time in investigation now. It's not a productive system, so i'll rebuild it from scratch.