Can no longer log into AEAC after update

[lrk1000]

Some of my clients were not seeing a new license that was installed a few weeks ago.  These seemed to be clients that updated to 8.0.1603.

So I updated my Admin Console (now shows Nov2013 8.0.367).  Now, I try to log into the admin console and it doesn't detect the server!  Yes I did reboot after installing.  I go to maintenance and I get errors connecting to, checking, repairing, etc the db and trying to rebuild the db.  Log is attached.  I did create a new certificate when installing...

Any ideas?

Len

[wpn]

http://support.microsoft.com/kb/307002

seems like an authentication problem which COULD be related to the new certificate.

just to be sure, are all the services running?

[lrk1000]

All the services are running EXCEPT the Avast Enterprise Administration Server.  Its starting is marked as Automatic.  When I try to start it I get an error...

Could not start on local computer....
Error 42000 0xa410

see attached screen shot.

[lrk1000]

Does anyone have a suggestion on what I do now?   

[Avosec-UK]

Could you share your AEA log files? They are located in: "C:\Program Files\AVAST Software\Enterprise Administration\DATA\log".

Make sure to replace any sensitive information with dummy strings.

[lrk1000]

Here are log files...thanks.

[Avosec-UK]

It is a SQL server related problem. Check if the SQL server instance running. You could do this from the Services MMC console, the service name should be something like: SQL Server (INSTANCENAME).

If the service is running, try to reset the SQL SA password:
1. Open CMD (Command Prompt).
2. Type the following command: sqlcmd -S (local)\INSTANCENAME
3. Reset the password with the following commands:
> use master
> go
> alter login sa with password="Pass123"
> go
> exit
4. Change the SQL server credentials from Start > All Programs > avast! Enterprise Administration > AES Maintenance > SQL Conn..
The details should be as following:
- SQL Server instance: (local)\INSTANCENAME e.g. (local)\AVAST
- Database: avastent
- Login: sa
- Password: TheNewPassword e.g. Pass123

[avast@@dvantage77.com]

Thank you, sir, that is great information!

Sincerely,
 
J.R. "AutoSandbox Guy" Guthrie

"At this point in time, the Internet should be regarded as an Enemy Weapons System!"

[lrk1000]

SQL Server (AVAST) was running and SQL Server Agent (AVAST) was not.  When I tried to start the Server Agent, it stopped right away.  I stopped SQL Server, and then started SQL Server Agent, and then they both were running.  I tried getting into the Console again but still doesn't see the server.

Can you explain or give an example of what (local)\INSTANCENAME means?  I typed that literally and I get an error the that the server is not found or not available.

Thanks,

Len

[lrk1000]

I figured out \INSTANCENAME means \AVAST.  At least I put that in, and I was able to reset the password per above instructions. 

However, I still have no change trying to launch the console...no server found.

Here are the latest logs...

[Avosec-UK]

I figured out \INSTANCENAME means \AVAST.  At least I put that in, and I was able to reset the password per above instructions. 

However, I still have no change trying to launch the console...no server found.

Here are the latest logs...

You did make the changes in AES Maintenance tool right?

You could also try to type the server address manually in the logon box.

[lrk1000]

Yes, I was able to change the password in the Maintenance tool and now I can check the DB compatibility and it check as compatible.

Should I do any of the other options in the tool, like recreate the db with defaults or delete it all together?

Thanks,

Len

[Avosec-UK]

Yes, I was able to change the password in the Maintenance tool and now I can check the DB compatibility and it check as compatible.

Should I do any of the other options in the tool, like recreate the db with defaults or delete it all together?

Thanks,

Len

That's good. Now try to login into the console, but instead of finding the management server address, just type the IP address or the FQDN of the server.

The default administrator credentials are:
Username: Administrator
Password: admin

[lrk1000]

No luck...get "Unable to log in as Administrator or connection error"

Tried with both the IP and the FQDN.

Len

[Avosec-UK]

Did you check the service? Is it running?