ADNM Password issues on Various servers!!!!

Hi there,

Hoping you can help me, I have been reselling and implementing the AVAST ADNM service to most of my clients, and I keep hitting the same problem over and over, after appx 1 month of the install it always seems to fail on the password when I go to login.

I always leave the settings at default, and this is not restricted to one machine, I have at least 6 servers currently all doing the same.

Is this a known bug or am I making an error on the install??

Default details I am using are Administrator and password = admin

I find I spend a lot of time having to uninstall the ADNM and reinstall just to do simple task of adding the Antivius to a new desktop, which as I’m sure you will understand is quite time consuming.

Please can someone shed some light on this problem as I love the product and the level of protection we get from Avast

Many thanks

Marc

Hi and welcome to the forum.

Are you using the free 60 day trial on these machines? If the trial period is over, it won’t allow you to log into the ADNM console.

If not, make sure that the “Avast Management Server” service is running on the effected machines.

Also, could you provide the exact error that you get when you attempt to login?

HI there,
Thanks for your reply, I can confirm that all have full valid subscriptions as we are an offical reseller

Have checked the service and also tried restarting with no joy, Just on my way to fix another server with same issue so will post the message word for word when I arrive.

Many thanks

Marc

maybe u can post them in screenshots

next to that its always a security risk to leave a password at the default one… specially as reseller u should not practice this behaviour its also a business risque for you, if ur customers server get “hacked” using the standard password u will get a lawsuite and lose unconditionally (at least if i was ur customer and this would happen to me, i would sew ur ss to hll and back ;)).

try to install ADNM and change the password from the default administrator account, maybe it is also a (undocumented) security measure that blocks access if the standard password is used for a long time

for me, this happens every 3-5 days.

the fix is always one of these steps, in order, try until it works:

  1. stop ALL related services: avast management, mirror, sql agent, mssql
  2. start all services, try to log in.
  3. reboot the server, try to log in
  4. delete the database from sql, make a new one from ams-maintenance, and it will work.

obviously be smart about backup/restore if that’s your thing… but this happens to us when the sql database balloons up over 3-4gb

which OS are u using and what is the file system the database is on?

I have had a similar problem with not being able to log into the ADNM console. The ADNM server won’t start after about 30 days have passed. I checked the Windows Event log under Antivirus and found the following error message:

Error Event 90: Error 0000A410 has occurred while opening license file C:\Program Files\Alwil Software\Management Tools\DATA\Avast 2009 license.dat. Is the license file correct?

Well, heck no, the license file is named “license.dat”!!!

For the heck of it, I copied the “license.dat” file and created a new one called “Avast 2009 license.dat” Restarted the ADNM service, and it came right up. Was able to log in as Administrator.

Did I miss something? Is there ANYWHERE it tells you to go and rename the license file to the above? Did somebody forget to change the name of the license file in the standard distribution?

Hope this helps someone else!

I am also having the same problem. I have six different networks with seperate servers and about every 30 days or so the password does not work. The only solution I have found is to uninstall the whole thing and start over. Its getting very old.

Is there anyway to disable the password login all together. I work many other networks with trend micro and symantic and every Admin I know asks the same question why even password protect it, they all keep the defaults as well

HI all,

Having been up to my eyeballs in it last few weeks I have not had time to reply, but have visited lots of my clients and find that sometimes restarting the service solves the log on and others is does not. I really can’t seem to pin point the error, but glad to hear I’m not the only one suffering from this issue.

I will strive to get some log files created from the database and the ADMN and will post asap.

I shall also see if changing licence name works for the ones where restarting the console does not solve.