Problem on SBS2003

[nsi]

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??

[Vlk]

Please try running

netstat -a

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

Thanks
Vlk

[nsi]

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

[Vlk]

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

[nsi]

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

[Vlk]

BTW who was allocating the ports?

Thanks
Vlk

[nsi]

Exchange 2003 in particular

Microsoft Exchange Information Store and Microsoft Exchange Information Attendant

See Microsoft KB 833401

[GhostDream]

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?

[Vlk]

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

[GhostDream]

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.

[GhostDream]

Just a lillte inquiry ;-)

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

[Vlk]

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:

- version with MSDE http://download1.avast.com/files/beta/setup_adnm.exe
- version without MSDE http://download1.avast.com/files/beta/setup_adnm_no_msde.exe


Thanks
Vlk

[mini]

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

Steen