Event ID 7022 and 7034 errors on system startup

After installing Avast Server Edition on a Windows 2003 Terminal Server each time after the system reboots I get Event ID 7022 (the Avast! Antivirus service hung on starting) and Event ID 7034 (the Avast! Antivirus service terminated unexpectedly). I have tried uninstalling/reinstalling with the same results. Any ideas what is going on here? The Windows 2003 OS is at SP1 and is a new install.

I’m also experiencing the same errors. Using Win2K3 SP1 with terminal services in application mode. Have tried reinstalling numerous times. Ideas?

well, we (I mean Willisd and I) managed to get this going, only after playing around with it for serveral hours trying out a few things.

FYI:

  • When we installed, it REFUSED to start using an account (administrator or even a custom created admin access equivilent). I had to switch it to logon locally and allow it to interact with the desktop in order to get it to function correctly.

  • There’s a good chance that the license data will be corrupted if the service fails to load or you don’t complete the steps after the reboot. This happened to me twice. I found if I chose the option not to restart, set the services to login locally with desktop interaction, then rebooted, the last steps came up fine and I was able to complete the install.

We have it running right now, and it seems to be working fine, but we’re off to a rocky start.

koverturf, feel free to contact myself if these instructions are not clear.

Willisd,

Thanks for the information. Our 2003 terminal server is also in application mode. I will try following your instructions this Friday and see if I can also get it running. I will let you know…
Thanks again…

Ken

I can confirm that there’s a problem in the current version of avast Server Edition if its service is configured to run under a non-LocalSystem account.

However, switching its log on settings to LocalSystem should do the trick, and shouldn’t have any other consequences.

Thanks
Vlk