Hello,
I had the trial running and everything was working fine. In preparation for rollout in production I have now installed the ADNM on the machine that will be used permanently (I have not yet purchased a license). The setup went without any issues and the avast!Management Server and Mirror services are running. No reboot was requested but I did so anyway. The database is installed to a SQL 2000 server (not MSDE). However when I try to log on to the ADNM (either locally or from another machine) I get the message titled “Unknow error” with “Unable to login as Administrator or connectin error” in the dialogue box. If I check the button “Detect Servers” it locates the server fine, but I cannot log on using the default username of “Administrator” and password of “admin”.
I went to the AMS Maintenance Tool and check the SQL connection and it is working. However I just looked at the \data\log\error.log file and it is showing entires listing “SYSTEM 572 Database command failed [CSQLQueue::DeleteExpriedRequests, 80004005]: Connectin failure”
I know the first trial I had running did expire and I can no longer log on to it, but that was a different machine and different SQL server - I don’t think that would affect the new installation?
Well it’s been about a week with no replies
I uninstalled on my server and did an install on another machine and it works. Today I read a post by ump (http://forum.avast.com/index.php?topic=26934.0) and he describes the same issue I was having. It would have been nice to have the IP address suggestion given to ump to try on my server before I uninstalled. I guess I assumed that if the “Detect Servers” button found the server then DNS was not an issue. Now I’ll have to wait to re-boot the server tonight (want’s a re-boot after uninstall), then re-install all over and see if the IP works.
Having said that - I am uneasy with the support. If I get no response to a post on an install question for a week (and a new post with the same problem gets 8 replies the day it is posted) what will be the response if I have issues when I go live ???
Hi jetter, sorry for the delay, I must have somehow missed your original post :-[
On a brighter side, this doesn’t happen too often - so I guess the chances that it will happen to you again are now quite miniscule
–
So, if I understand it correctly - you have redeployed the AMS software to another server - but still want to go back to the original server. Is that correct? And this new AMS, does it use the SQL Server that you wanted to use on the production AMS?
BTW I’m afraid the IP address trick (discussed in the other thread) wouldn’t help in your case - the error code the console was reporting in ump’s case was quite specific whereas “Unknown error” isn’t too useful… But I’m sure we’ll figure it out!
Hello Vlk, hope my last post didn’t sound too much like a flame ;D
I have installed the ADMN server 4 times now on two different machines. For clarity I’ll call them Server T and Server P. Server T is a machine used for testing and gets trashed from time to time. Server P is the one I want to use on a permanent basis.
Last month on a Server T to see if I liked the product - it worked
Last week on Server P (the intended permanent home) - install went ok, but could not log on
Last week uninstalled and then re-install on Server T - currently working
This morning -uninstall and re-install on Server P - install went ok, but cannot log on
The two machines are different, but the major difference as far as avast! would be concerned is that the Server T (working) uses SQL installed locally, where Server P (not working) uses SQL installed on a different machine. I don’t think that is the issue because the Test Connection utility in the Maintenance Tools checks out ok. The only other major difference is that Server P (not working) is running Trend Micro’s management utility.
Now, focusing on Server P - where I want it to go. At the log on I click the detect servers. It retrieves both Server T and Server P (in the syntax of machinename.domain), I select Server P - for user name I leave it as “Administrator”, for password I enter “admin”. I receive a dialog box titled “Unknown error.” with the text “Unable to login as Administrator or connection error”. Note that the first time I get a prompt for the Security Certificate, which I click on “Permit and Store”. This is consistent from both a local machine log on and from a remote machine that has the Administrator Console installed.
I have verified that the avast!Management Server service is running and I have also use the Maintenance Tool to verify the SQL connection tests ok.
Oh yea, I’m in Houston - it’s gonna be a nice day today 8)
I had this same problem with a new install and came here seeking answers. Wasn’t getting any, so I read the Administrator docs again. Must have missed this before. The default console login name/password is:
Administrator/admin
I’m puzzled why I never saw if offered up by support here even though it’s a pretty obvious solution to some of the posts I’ve seen.
