Problem on SBS2003

Avast Business Avast Distributed Network Manager
1

After I have installed Avast Management Console and Management Server on my SBS2003, the service “avast! Management Server” don’t start.

I use MSDE and the service MSSQL$AVAST is running

If I try to start the service, after a few second the service was stopped with these two errors in the Event Viewer:

Event Type: Error
Event Source: avast!
Event Category: Client
Event ID: 90
Date: 07/07/2004
Time: 14.50.47
User: SBS\administrator
Computer: SBS2003
Description:
While binding ClientsListen socket WinSock error 0x0000271D has occurred.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 07/07/2004
Time: 14.59.28
User: N/A
Computer: SBS2003
Description:
The avast! Management Server service terminated with the following error:
%%2147426319

any help??

2

Please try running

netstat -a

Is there anyone listening on port 6001 or 6002 on your machine? :slight_smile:

Thanks
Vlk

3

Active Connections

…
TCP sbs2003:6001 sbs2003.sbs.local:0 LISTENING
TCP sbs2003:6002 sbs2003.sbs.local:0 LISTENING
TCP sbs2003:6004 sbs2003.sbs.local:0 LISTENING
…

This is the result of netstat -a

4

Please try TcpView to find out which program is listening on these ports…

5

Thanks, now I have the 6001 and 6002 port free and the service start

6

BTW who was allocating the ports?

Thanks
Vlk

7

Exchange 2003 in particular

Microsoft Exchange Information Store and Microsoft Exchange Information Attendant

See Microsoft KB 833401

8

I have the exact same problem on a sbs 2003 server, installed adnm with msd sql but management server wont start, i have used tcpview to confirm that store and map are using port 6001 and 6002 on the server, and read the kb article suggested.

Now my question is: what excately did you do to free the ports? - Im afraid that exchange will stop working if i tamper with the ports. Or am I missing something vital?

9

We’ve changed the port numbers that the ADNM server will use to prevent this particular collision with Exchange. The change will become effective in the upcoming program update - hopefully due next week.

Thanks
Vlk

10

Sounds good, in the meantime, is there anyway for me to change adnm’s port config, or do i have to wait for the update?

  • btw. thanks for the quick response.
11

Just a lillte inquiry :wink:

This famed update that will move the ports, so they no longer collide with exchange, any news as to when it will be availble?

Thanks
Thomas

12

We now have a beta build that solves a number of issues and adds a couple of new features. Among other things, it solves the conflict with MS Exchange installed on the same server.

If you’re interested, it can be downloaded here:

Thanks
Vlk

13

Thank you it works great for me now - I’m now on to deploying to clients :slight_smile:
Thanks again

Steen