Re-establishing communication.

Avast Business Avast Distributed Network Manager
1

I’m having troubles with a W2K pro machine communicating with the console.

In the event log I’m getting:

Cannot connect ServerConnection socket, WinSock error 0x0000274C has occurred.

and

Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.

So I checked avast4.ini and found that Server and LastServer had the avastms instead of the proper ip address. I changed it to be the correct address and waited but it still didn’t show up as communicating in the computer catalog. I ran a discovery task still nothing. I’ve rebooted the machine and still the icon is greyed out. However there are no errors in any of the log files since I made the change. What am I missing and why shouldn’t have avast autodiscovered the AMS?

2

Can you ping/access the AMS from that machine?

3

Not only can I ping from the machine, it is my machine and I am running the remote console from it. ;D So it definitely has the connectivity to it.

4

So the Detect Servers button in the console Login dialog works?
Because it uses exactly the same algorithm as the NetClients…

5

Yes it does. I deleted the server out of the registry per our previous thread. Brought up the console and it was able to detect the AMS without a problem. So that makes today’s puzzler for you. ;D

6

I’ll send you some files with extra logging tomorrow.
I’m curious what is it this time… :-\ :slight_smile:

Good night (I know, not yet at your place but anyways)
Vlk

7

Any luck on this?

8

Please try updating to the latest version (released today). It’s labeled RC-2a. You can also update the AMS and/or console - it brings some enhancements as well (mostly the stuff we were talking about since the release of RC-2).

Thanks
Vlk

9

I’ve updated the console and client both to 2a but it still doesn’t talk.
Here’s the comm block of avast4.ini

[Communication]
ServerAddress=192.168.1.43
InformationPortAddress=6000
InformationTimeout=300
ClientsListenPortAddress=6011
SynchroTimeout=30
EmailChestFile_To=virus@asw.cz
ProblemEmail=support@avast.com
PopTimeout=600
PopTimeoutDiff=300
InstallGUID=cc4bdf02-2a1c-4ce2-8f66-03d5d5adc910
LastServerAddress=192.168.1.43
SMTPServer=smtp.xo.com
SMTPPort=25
SMTPUserName=
SMTPUserPassword=
SMTPFrom=avast@monetrics.com
CommScenario=PopOnly
MaximumSendSize=1024
[Common]

10

And nothing new in the Event log?
There should be at least something written in the NT event log, Antivirus category generated during the NetAgent service startup.

Thanks
Vlk

11

I found the problem. Netagent wasn’t starting at boot time. Though it is set to automatic it wasn’t starting. Now to figure out why it wasn’t starting.

12

And manual start of the service worked? :o

If it wasn’t starting at all, there’d have to be something in the Windows Event Log (from the Service Control Manager [SCM]). It’s more likely that the service actually started and then immediately stoped (crashed?) - that way the SCM wouldn’t notice. Or is there anything in the Event Log?

Thanks
Vlk

13

Yes a manual start worked.

I rebooted again after clearing the event logs and what I get is

The avast! Antivirus service hung on starting.

and a

The avast! NetAgent service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Timeout (30000 milliseconds) waiting for the avast! NetAgent service to connect.

Nothing in the avast logs though. And a manual start works fine.

as an error from the Service Control Manager

14

Any idea on what I should do to troubleshoot this?

15

This one will be really hard to debug. The problem is that if you start the service manually, it works.

That is, it must be some kind of timing issue… :frowning:

16

I am also having the same problem on the AMS with the management server. I get the following two errors in the event log:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 10/11/2004
Time: 11:35:56 AM
User: N/A
Computer: TESLA
Description:
Timeout (30000 milliseconds) waiting for the avast! Management Server service to connect.

and

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/11/2004
Time: 11:35:56 AM
User: N/A
Computer: TESLA
Description:
The avast! Management Server service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Yet a manual start will start it without a problem.

17

Even with the latest build I am still getting timeouts on the management service when it starts. Any idea on how to troubleshoot this?

18

I’ll create a logging version and will get back to you.

BTW sorry for the delay.