I have Windows XP SP2 clients running Ad-Aware SE Professional (build 1.06r1) with the Ad-Axis Client. I have had nothing but trouble getting these clients to successfully (and consistently) register with the Ad-Axis Server (Windows Server 2003 Standard). My client logs throw up errors like:

2006-05-04 10:56:08 [DEBUG] Exception caught during pinging the manager: 'Ice::ConnectionRefusedException' (10631765)
2006-05-04 10:56:11 [DEBUG] Exception caught during pinging the manager: 'Ice::ConnectionLostException' (10634937)

or

2006-05-03 17:22:43 [DEBUG] Exception caught during registration check: 'Ice::EndpointParseException' (673187)
2006-05-03 17:22:43 [ERROR] CAAClientI::timeout(): Invalid manager proxy. (673203)

Machines appear and then are removed from the server management console (they register, appear to be active, and then get red Xs over them later). Some machines are in there multiple times but not work. Some machines that appear in the console as active, have not had a definition file updated in months. All machines are running identical images with identical Ad-Aware installations. The client software is set to the same port as the server. There are no other Ad-Axis servers out there. The client service is running on all clients and is automated. Stopping and restarting the client service has not rectified the situation.

Any guidance your support staff might have would be greatly appreciated. My renewal date is up in a few months and if I still can't get this product working I'm going to have to look at something else. Thanks.

Tom Ferratt. There are some updates available for the enterprise edition which address certain issues in the software. Have you been in contact with the support team?

There was an update that support sent me last year - the file date is 5/19/05. Since then, all the support team has told me to do is shut off stuff that I don't have running and restart the service which was the first thing I tried.