I suddenly started to receive this error message when attempting to log in into console (it worked before!). The only thing I did between that is installation of windows updates, uninstall of Sophos AV management / library / client followed by restart. It brought up this error message every time since then Btw we are using Win 2003 Server…
We had similar problem on other machines I guess because the DEMO license expired and I didn’t feel bothered updating license file… After update, on other servers it started to work, but not on this one 3 reinstallations didn’t help - I tried everything…
avast! Management Server service kept not starting at windows restart until I changed value in file …Management tools\Data\avast4.ini . I changed DBCreated=0 to 1 as seen in other forum topic (I guess it should
be 1 as the database seemed to be created normally at install+mirror). Now I can start it manually and it works sometimes longer sometimes shorter… then it stops with error msg “The avast! Management Server service terminated with the following error: %%42000”. Even running or not, I still can’t log on to console. If going to the Maintenance tool, the license file seems OK and Check DBS brings up “AMS database is not compatible! (0x0000A410) *: Going to check version of database of avast! on MS SQL Server “SERVER6\avast” using user “sa”… Cannot execute avsVersion(), error 0x80004005…”. I cannot delete DB (doensn’t exist) or create DB (error 0x0000A410).
Yes, after not getting any answer here I asked AWR (our UK reseller). After all, I found the solution (but not reason why was all this happening). I simply renamed folder “C:\Program Files\Microsoft SQL Server” by placing “!” right before “Microsoft” so this folder was actually re-created by another ADNM reinstall. I believe there is something wrong inside this old folder and I can send it to you packed if you are insterested (it contains MSSQL$AVAST and MSSQL$SOPHOS folders).
Thanks for your help anyway
Martin
I’ve the same problem. Nevertheless, I’ve tried this method placing “!” right before “Microsoft”, but I didn’t work : sames errors. Could someone help me ? Because now I’ve re-install ADMN (with MSDE), but I can’t log; my clients aren’t protected… :-\
I have a 2003 SBS. And the system was correctly working since 3 months, and now… this problem. The certicate is correctly installed.
I’ve done the last re-installation 3 days ago, and nothing more. I have always the login problem, and same problem with the SQL (I’ve tried to check “sa” login and password automatically generated…)
If you could help me, I would be very recognizing, because I’ve just buy 3 years lisence for 11 PC …
mcpi, you said you just bought a license. Did you insert it to the program?
Is the “avast! Management Server” service running? (Control Panel → Administrative Tools → Services).
If not, could you please post the contents of the file \data\log\error.log?
The license is correctly inserted. And the “avast! Management Server” service is running (it was not the case, nevertheless, since I’ve started it, there’s noting more.)
I could send you the error report on Friday, because I’m not in the place now.
RIIIGGHHT !!! It works…
I’ve just uninstalled all avast’s programs, and manually deleted MSSQL repertory, and all entries of avast in registry… And all’s right now.
Thanks to Vlk for his help.
I have to config all my network now, but happy.
I’ve just migrated the AMS to another server (the initial install was on a desktop PC since at the time we didn’t have a spare Server for it).
Now I’ve imported the license successfully and then imported the database from a backup.
I get exactly the same error as shown in the screen shot above.
So short of doing what was done in the provious post (remove the lot and start again, how about we see if we can fix this?
Ah think i’ve solved it.
After the migration I renamed the Server to the same name as the previous one.
However the SQL connection was still referring to the previous name given to thi new box.
Simply changed that to the current name, and bob is your mothers brother.
However still does not let me login as Administrator with my altered password from the previous install.
Does that reset to the initial password when you do this?