« previous next »
Pages: [1]   Go Down

Author Topic: deploy seems to work, but machine is not in agents-group!  (Read 4643 times)

0 Members and 1 Guest are viewing this topic.

avalon

  • Guest
deploy seems to work, but machine is not in agents-group!
« on: July 07, 2006, 08:10:37 AM »
hi there,

i´ve installed adnm on our bussiness network and the deployment seems to work on my testmachine. also, a restart is performed automatically. but this machine (and another one too) is not listed in the group with installed agents. it seems that adnm does not see the installed agent. avast tray icon is active and i can start the client-avast...

here ist the remote install log of this machine:


-------------schnipp----------------

07/07/06 07:59:54:   rinstInstall begin
07/07/06 07:59:54:   Init 50 60 C:\WINDOWS\TEMP\asw1B.tmp C:\Programme\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw1A.tmp 0
07/07/06 07:59:56:   Store
07/07/06 07:59:56:   Domains: *,
07/07/06 07:59:56:   Init KANZLEI\VIRTUAL
07/07/06 07:59:56:   VIRTUAL: GetAccount
07/07/06 07:59:56:   VIRTUAL: CallBack 201
07/07/06 07:59:56:   StartThread
07/07/06 07:59:56:   Loop
07/07/06 07:59:56:   SpawnThreads
07/07/06 07:59:56:   VIRTUAL: StartSetup
07/07/06 07:59:56:   VIRTUAL: CallBack 202
07/07/06 07:59:57:   VIRTUAL: CallBack 203
07/07/06 07:59:58:   VIRTUAL: File \\VIRTUAL\C$\~AVINSTL\aswResp.dat not created
07/07/06 08:00:00:   VIRTUAL: Copying setif_av_net-236.vpu
07/07/06 08:00:00:   VIRTUAL: Copying setup_av_net-236.vpu
07/07/06 08:00:01:   VIRTUAL: Copying av_net_agent-92.vpu
07/07/06 08:00:02:   VIRTUAL: Copying av_net_cmn-2d.vpu
07/07/06 08:00:02:   VIRTUAL: Copying av_net_dll407-30.vpu
07/07/06 08:00:04:   VIRTUAL: Copying av_pro_dll407-79.vpu
07/07/06 08:00:06:   VIRTUAL: Copying av_pro_hlp407-15c.vpu
07/07/06 08:00:06:   VIRTUAL: Copying av_pro_skins-13.vpu
07/07/06 08:00:07:   VIRTUAL: Copying av_srv_core-230.vpu
07/07/06 08:00:11:   VIRTUAL: Copying av_srv_dll-10f.vpu
07/07/06 08:00:12:   VIRTUAL: Copying avscan-243.vpu
07/07/06 08:00:13:   VIRTUAL: Copying winsys-1.vpu
07/07/06 08:00:14:   VIRTUAL: Copying winsysgui-1.vpu
07/07/06 08:00:15:   VIRTUAL: Copying vps-62700.vpu
07/07/06 08:00:20:   VIRTUAL: Copying vpsm-62702.vpu
07/07/06 08:00:20:   VIRTUAL: Copying news405-32.vpu
07/07/06 08:00:20:   VIRTUAL: Copying news409-31.vpu
07/07/06 08:00:20:   VIRTUAL: Copying part-prg_av_net-236.vpu
07/07/06 08:00:20:   VIRTUAL: Copying part-vps-62702.vpu
07/07/06 08:00:20:   VIRTUAL: Copying part-news-4a.vpu
07/07/06 08:00:20:   VIRTUAL: Copying part-setup_av_net-236.vpu
07/07/06 08:00:20:   VIRTUAL: Copying prod-av_net.vpu
07/07/06 08:00:21:   VIRTUAL: Copying jollyroger.vpu
07/07/06 08:00:21:   VIRTUAL: Copying servers.def
07/07/06 08:00:21:   VIRTUAL: CallBack 204
07/07/06 08:00:21:   VIRTUAL: CallBack 205
07/07/06 08:00:56:   VIRTUAL: ReadProgress
07/07/06 08:00:56:   VIRTUAL: CallBack 210
07/07/06 08:00:56:   VIRTUAL: RemoveProgress
07/07/06 08:00:56:   VIRTUAL: Folder \\VIRTUAL\C$\~AVINSTL not removed: 145
07/07/06 08:00:56:   VIRTUAL: CloseConnection
07/07/06 08:00:56:   TerminateAll
07/07/06 08:00:56:   rinstInstall end 0

-------------schnipp----------------


please assist. thnx

cu
thomas
« Last Edit: July 07, 2006, 10:06:35 AM by avalon »
Logged

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: deploy seems to work, but machine is not in agents-group!
« Reply #1 on: July 10, 2006, 08:40:48 AM »
Please post the contents of the files error.log and warning.log (from the <avast>\data\log directory) from the workstation in question...

BTW was the AMS address in the installation package correctly specified?

Thanks
Vlk
Logged
If at first you don't succeed, then skydiving's not for you.

avalon

  • Guest
Re: deploy seems to work, but machine is not in agents-group!
« Reply #2 on: July 11, 2006, 08:48:10 AM »
hi vlk,

Quote from: Vlk on July 10, 2006, 08:40:48 AM
Please post the contents of the files error.log and warning.log (from the <avast>\data\log directory) from the workstation in question...

here they are:

------error.log-------

14.06.2006   10:41:10   1150274470   SYSTEM   2300   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
14.06.2006   10:41:16   1150274476   SYSTEM   2300   avast! Antivirus service is not running, computer is not protected! 
14.06.2006   10:41:17   1150274477   SYSTEM   2300   Unable to start avast! Antivirus service, error 0000041D has occured 
14.06.2006   10:41:19   1150274479   SYSTEM   2300   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 
14.06.2006   10:43:20   1150274600   SYSTEM   1784   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
14.06.2006   10:43:31   1150274611   SYSTEM   1784   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 

------shortened, because it is allways the same error message...--------

03.07.2006   16:53:08   1151938388   SYSTEM   1736   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
03.07.2006   16:53:18   1151938398   SYSTEM   1736   ODBC function SQLConfigDataSource() failed. Error description: Komponente wurde in der Registrierung nicht gefunden. 
04.07.2006   14:24:22   1152015862   SYSTEM   1728   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
04.07.2006   14:24:34   1152015874   SYSTEM   1728   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 
04.07.2006   14:25:20   1152015920   SYSTEM   1728   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
04.07.2006   14:25:30   1152015930   SYSTEM   1728   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 
04.07.2006   14:27:27   1152016047   SYSTEM   1728   Third server conn attempt (last good: 0.0.0.0:16111) failed. (error 00002741). 
04.07.2006   14:27:36   1152016056   SYSTEM   1728   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred. 

---------error.log end---------------

---------warning.log-----------------

14.06.2006   10:41:19   1150274479   SYSTEM   2300   CClient::PopupThread - GetConnection failed! 
14.06.2006   10:58:49   1150275529   SYSTEM   1784   CClient::PopupThread - GetConnection failed! 
14.06.2006   15:05:38   1150290338   SYSTEM   1768   CClient::PopupThread - GetConnection failed! 
23.06.2006   11:21:03   1151054463   SYSTEM   1752   CClient::PopupThread - GetConnection failed! 
27.06.2006   14:37:37   1151411857   SYSTEM   1744   CClient::PopupThread - GetConnection failed! 
04.07.2006   14:49:17   1152017357   SYSTEM   1728   CClient::PopupThread - GetConnection failed! 
05.07.2006   10:00:36   1152086436   SYSTEM   1724   CClient::PopupThread - GetConnection failed! 
06.07.2006   15:25:47   1152192347   SYSTEM   1732   CClient::PopupThread - GetConnection failed! 
07.07.2006   08:01:43   1152252103   SYSTEM   1736   CClient::PopupThread - GetConnection failed! 
07.07.2006   11:44:52   1152265492   SYSTEM   1760   CClient::PopupThread - GetConnection failed! 
07.07.2006   14:40:41   1152276041   SYSTEM   1776   CClient::PopupThread - GetConnection failed! 
11.07.2006   08:19:23   1152598763   SYSTEM   1740   CClient::PopupThread - GetConnection failed! 

------------warning.log end--------------

warning.log shortened, because this system only accepts messages with 10.000 bytes. the system# varies, i tried to make all the different ones visible, so i shortened the log for 1 entry per system#. 1736 is the most one in the log.

Quote
BTW was the AMS address in the installation package correctly specified?

yes, it is correct.

cu
thomas
Logged

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: deploy seems to work, but machine is not in agents-group!
« Reply #3 on: July 11, 2006, 08:54:19 AM »
1. Is the avast netclient version that latest one? (i.e. 4.7.566). The ODBC-related messages are a bit strange because starting with v4.7, avast doesn't use ODBC anymore.

2. It seems that the client, for some reason, does not know the address of the management server. Could you please have a look in the file <avast>\data\avast4.ini - is there a line ServerAddress= , and if so, what is the value?

3. To change the name of the AMS, you can use the aswChAms.exe command-line tool located in the avast folder. Just do

        aswChAms.exe AMSName

and that should do the trick.


Thanks
Vlk
Logged
If at first you don't succeed, then skydiving's not for you.
Pages: [1]   Go Up
« previous next »