Agent error - can't communicate with ePO server 1

[cottonpants]

Howdy. About a week ago, coincidentally after rebooting my ePO server, a considerable number of my agents have not been able to update their properties on the ePO server.

They are still managing to stay updated with DATs etc, however in the agent<>.log I get this error:
20040401101317 e InetMgr Failed to connect to server . Check the agent log for more details.
20040401101317 e Agent Agent failed to communicate with ePO Server
20040401101317 i Agent Agent communication session closed
20040401101317 I Agent Retry reached ASCI...Retry will stop now..
20040401101317 I Agent Agent communication failed, result=-2147467259
20040401101317 i Agent Agent will connect to the ePO Server in 2 minutes and 14 seconds.


Anyone have any idea what a 2147467259 error is?

 

[JimmyZ1]

What does the other log say? DNS possibly?

Last cube on the left, next to the backdoor...

 

[P3dr0]

I already have this error number, but it's was a credentials problem to connect to a repository

Have you tried to ping the ePo Server from the client ?
Did you use the epo agent generate by the ePo server itself ?

 

[cottonpants]

Pings work fine - I think the problem may be due to our proxy server. I've noticed that there are lots of Framework Service entries in our proxy logs and they are all from the affected agents.

So... how to determine if the agents are using Internet explorer settings or not. According to epo they should be (it is configured to bybass proxy for local addresses). I am thinking that for some reason these agents are not bypassing.

I haven't been able to find and reg entries or ini files on the agent where this is set.

Is there a way to re-install the agent (with the correct properties) without doing an uninstall first?

 

[jfp23]

framepkg /forceinstall /install=agent is the command to run a force install manually

 

[nosrevlah]

I am experiencing the same problem. My temporary fix is to stop the EPO server service on the server and restart it. This seems to correct it for a few days and then it does it again. It would be nice to find out the solution for this........

 

[cottonpants]

Success! - I have found that just sending the agent install again to the affected agents through my ePO Server has solved my problem (after changing the Agent policy back to use Internet Explorer settings!).

The trick was to find a way to send the re-install ONLY to those affected. I managed that by doing a directory search for agents that hadn't reported back since that day. I was able to sort those results and then select and perform an Agent Install.

Everything seems to be hunky dory - for now...

 

[bfralia]

There seems to be a problem with ePO 3.0.1 and Windows 2K pro clients. There is a GUID associated with each client that seems to get forgotten.

The most consistent way I've found to resolve this is to do a forced uninstall of the agent:

frminst /forceuninstall

that removes rather than disables the agent.

then reinstall:

framepkg.exe /install=agent /siteinfo=path\sitelist.xml

It most often starts working right away.