I just took over a customer that is using Avast and I’m brand new to the coroporate side of avast!. The Management Server service fails to start. The error is:
Error 42000: 0xa410
Running the AMS Maintenance Utility, SQL Conn → Test Connection is successful, but the Check DB fails with:
AMS Database is not compatible (0x0000A410).
Going to check version of database of avast! on MS SQL Server “SERVER\Avast” , using user “sa”…
Cannot execute avsVersion(), error 0x80004005…
I just downloaded and installed the latest ADNM thinking that might resolve the problem but it did not.
I also tried changing the credential on the service. This did not help either.
All of the other avast! related services are running fine.
I’ve attached the logs from the management tool as well as the SQL log. As far as I can tell, this issue has been going on for months and there is no backup of the database. Is there any way to get this working and not lose any data? I’m at a total loss so any help would be greatly appreciated.
What data you want to prevent of loss? Data in ADNM has no value, when ADNM did not start for ages… (maybe from beginning?
Data in avast.mdf has no value for you, it is not necessary prevent of loss. You will get it back after first run of server task (Finding computers) The only data which has value for me is my own dynamic groups definitions. It is one of main reasons to make weekly database backup from my point of view.
Please write more detailed info about your infrastructure… ADNM is running on W2k3 as is shown at log, but database is running MSDE or full server?
I recommend clean server from ADNM, check registry and file system for rest of ADNM. I’ am not sure, if AVAST uninstaller (aswcleaner) has option for ADNM, but try to look. And after it, try brand new ADNM installation. And I preferr using SQL 2005 Expres instead of MSDE. For mirror service I used strong account, member of Domain admins, but it is not necessary. It is rest of my first steps with earlier version of ADNM and problems with ISA proxy, some years ago. (Management service is under local system account)
Sorry for the delay in responding. I’ve been out of the office all of last week.
Thanks for letting me know that. As I said, I am new to ADNM and wasn’t sure what I would loss.
Please write more detailed info about your infrastructure... ADNM is running on W2k3 as is shown at log, but database is running MSDE or full server?
MSDE
I recommend clean server from ADNM, check registry and file system for rest of ADNM. I' am not sure, if AVAST uninstaller (aswcleaner) has option for ADNM, but try to look. And after it, try brand new ADNM installation.
Couldn’t I simply delete the damaged database and create a new one?
Okay, I was able to delete the database and create a new one. All computers show up. All the computers have a “last communication” data at least a month old. Most are behind in their engine version - 4.7.x.x. When I try to run any kind of task from ADNM on the machines the error code I get is 0x7FFF021, which indicates not enough licenses. But when I check the licensing the customer has an unlimited license.
We have installed on a couple of new PCs over the past couple of days, from a network share, not from a deployment package, and these two machines are communicating. The have the green icon in the computer catalog. The others have the key icon. (One actually has a red icon although it shows last communication of today.)
There is some kind of communication happening as the policies for user interface settings are being applied immediately to the clients. But no updating or scheduled tasks are running.
How do I fix this?
NOTE - Just a quick update. I did find that the license file has not been loaded into the AMS Maintenace Tool. It was still showing the previous year’s license. However, this has not solved the problem. I’m still getting the key ocons and cannot perform and client tasks.
We were having the same problem. Applied some updates last night which I do believe contained some SQL updates. I changed the avast db ‘sa’ account password and updated the credentials through AMS Maintenance Tools in the start menu and clicked ‘Check DB’ in the tools window. Everything began working just fine afterwards.
