Author Topic: Beta-2 deploying to clients.  (Read 9446 times)

0 Members and 1 Guest are viewing this topic.

gprzybyl

  • Guest
Beta-2 deploying to clients.
« on: June 28, 2004, 05:43:52 PM »
  I created a workstation task to deploy to 2 clients, Both W2K Pro.
When I deployed it the task ran without a problem.  After both PC's rebooted I got missing dll errors.  One of the clients was missing aswmaisv.exe and aswdisp.exe the other was just missing aswdisp.exe .


Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Beta-2 deploying to clients.
« Reply #1 on: June 28, 2004, 06:37:32 PM »
Can you check the folder <management tools>\InstPkgs? What is the size of the folder?

Also, can you post the file <avast>\setup\setup.log from that machines?

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

gprzybyl

  • Guest
Re:Beta-2 deploying to clients.
« Reply #2 on: June 28, 2004, 08:05:07 PM »
  I unistalled beta-2 from both machines and then reinstalled it one at a time and now it works fine.  I'll mail you the setup.log file it is too large to post.   The instpkgs folder is 23.2 MB.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Beta-2 deploying to clients.
« Reply #3 on: June 28, 2004, 08:20:09 PM »
The log you sent comes from the successful attempt or the failed attempt (buggy install)?

So you're saying that it was a problem when the deployment task was set to run on more than one machine..?
If at first you don't succeed, then skydiving's not for you.

gprzybyl

  • Guest
Re:Beta-2 deploying to clients.
« Reply #4 on: June 28, 2004, 10:04:19 PM »

   I was hoping it was from both the successfull and the failure as there was an hour difference between what appears to be to installs.  I copied the file after the successfull install so unless the uninstall deleted it or the new install replaced it you would have both installs in the same file.

   It seems (at least to me) that the problem was caused by doing multiple installs at the same time.  I could be wrong how ever.  ;D

gprzybyl

  • Guest
Re:Beta-2 deploying to clients.
« Reply #5 on: June 28, 2004, 10:13:30 PM »

   Actually my previous guess is wrong.  I just tried installing to one W2K Advanced Server with the same results.  The install looked fine from ADNM however when I logged in I got the missing DLL problem.  Here is the error log from it.

6/28/2004   1:13:17 PM   1088442797   NT AUTHORITY\SYSTEM   744   avast! Antivirus service is not running, computer is not protected!  
6/28/2004   1:13:22 PM   1088442802   DAVINCI\Administrator   1464   During the parsing of C:\Program Files\Alwil Software\Avast4\Tasks.xml XML document, following error occurred: C.  


   I will send the setup.log failure as it is to big to post.  The subject will be Failed setup.log.





Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Beta-2 deploying to clients.
« Reply #6 on: June 28, 2004, 11:25:20 PM »
What DLL is reported as "missing", exactly?
I don't mean the EXEs that're using it, I mean the DLL itself (the missing file).

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

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Beta-2 deploying to clients.
« Reply #7 on: June 28, 2004, 11:26:45 PM »
Also, can you post the listing of the InstPkgs folder on the AMS?
Ideally a redirected DIR command output.

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

gprzybyl

  • Guest
Re:Beta-2 deploying to clients.
« Reply #8 on: June 29, 2004, 03:35:42 PM »
Here is the directory of instpkgs.

 Volume in drive C has no label.
 Volume Serial Number is 68B7-782F

 Directory of C:\PROGRA~1\ALWILS~1\MANAGE~1\INSTPKGS

06/28/2004  11:16a      <DIR>          .
06/28/2004  11:16a      <DIR>          ..
06/25/2004  07:25a             539,206 avscan-100.vpu
04/06/2004  10:57a             544,907 avscan-e1.vpu
04/21/2004  10:34a             546,216 avscan-ec.vpu
05/06/2004  08:43a             546,321 avscan-f1.vpu
06/13/2004  06:46a             549,468 avscan-fd.vpu
06/24/2004  11:30a             224,673 av_mgm_mirror-17.vpu
06/25/2004  07:25a             124,492 av_mgm_srv-6.vpu
04/16/2004  02:43a              19,971 av_net_agent-a.vpu
06/17/2004  07:14a              19,970 av_net_agent-d.vpu
06/17/2004  07:14a               1,859 av_net_cmn-6.vpu
09/09/2003  06:49a             519,211 av_pro_skins-9.vpu
04/21/2004  10:34a           1,903,318 av_srv_core-69.vpu
06/25/2004  12:54p           1,922,075 av_srv_core-9a.vpu
04/21/2004  07:35a             994,202 av_srv_dll-35.vpu
06/25/2004  07:25a           1,000,192 av_srv_dll-4f.vpu
04/21/2004  10:34a           2,020,862 av_srv_dll405-2f.vpu
06/14/2004  08:31a           1,922,534 av_srv_dll405-37.vpu
04/21/2004  10:34a           2,528,472 av_srv_dll409-48.vpu
06/23/2004  01:26p           2,479,567 av_srv_dll409-69.vpu
04/21/2004  07:35a             379,219 av_srv_e2k-3e.vpu
06/25/2004  07:25a             379,531 av_srv_e2k-50.vpu
04/21/2004  10:34a             183,929 av_srv_hlp405-43.vpu
06/10/2004  12:47p             183,981 av_srv_hlp405-4e.vpu
04/21/2004  10:34a             160,744 av_srv_hlp409-43.vpu
06/10/2004  12:47p             160,613 av_srv_hlp409-4e.vpu
04/20/2004  12:10p             219,820 av_srv_pxy-20.vpu
06/25/2004  07:25a             228,795 av_srv_pxy-24.vpu
06/28/2004  12:57p             241,664 Install.dll
03/28/2004  10:24a                  86 jollyroger.vpu
03/28/2004  10:24a                  10 jollyroger.vpu.stamp
04/27/2004  09:01a              10,711 news405-2d.vpu
04/27/2004  09:01a              10,248 news409-2c.vpu
04/27/2004  09:13a                 220 part-news-40.vpu
04/27/2004  09:13a                  10 part-news-40.vpu.stamp
06/25/2004  01:13p               1,683 part-prg_av_net-64.vpu
06/25/2004  01:13p                  10 part-prg_av_net-64.vpu.stamp
06/25/2004  01:13p                 237 part-setup_av_net-64.vpu
06/25/2004  01:13p                  10 part-setup_av_net-64.vpu.stamp
06/25/2004  08:33a                 385 part-vps-42601.vpu
06/25/2004  08:33a                  10 part-vps-42601.vpu.stamp
06/25/2004  01:13p                 430 prod-av_net.vpu
06/25/2004  01:13p                  10 prod-av_net.vpu.stamp
06/25/2004  06:40p               1,806 servers.def
06/25/2004  06:40p                  10 servers.def.stamp
06/25/2004  12:55p              41,250 setif_av_net-64.vpu
06/28/2004  09:10a           1,015,856 setup.exe
06/25/2004  12:58p             400,717 setup_av_net-64.vpu
06/22/2004  07:38a           1,416,540 vps-42600.vpu
06/25/2004  08:33a               3,014 vpsm-42601.vpu
05/22/2003  06:53a             331,169 winsys-0.vpu
05/22/2003  06:53a             638,498 winsysgui-0.vpu
              51 File(s)     24,418,732 bytes
               2 Dir(s)   5,041,250,304 bytes free

gprzybyl

  • Guest
Re:Beta-2 deploying to clients.
« Reply #9 on: June 29, 2004, 03:38:13 PM »

   I will go deploy avast on some "virgin" machines and see if I can get it to fail.  If so I will send the exact dll it is complaining about.  Unfortunately I didn't do a screen print or write it down so I don't remember the dll.