Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: lrk1000 on February 03, 2014, 05:32:52 PM
-
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
-
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?
-
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.
-
Does anyone have a suggestion on what I do now? :-[
-
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.
-
Here are log files...thanks.
-
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
-
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!"
-
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
-
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...
-
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.
-
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
-
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
-
No luck...get "Unable to log in as Administrator or connection error"
Tried with both the IP and the FQDN.
Len
-
Did you check the service? Is it running?
-
Not sure which service you mean. All Avast services were running except [avast! Enterprise Administration Server]. I started that and still could not log in. Note: that service seems to shut itself off? After trying to log in, I went back to the services and it was stopped again.
-
The service [avast! Enterprise Administration Server] is not running, and it stops as soon as I start it. I get the attached message in the event log when I try to start the service.
Also I saw this other message from the event log about the SQL starting up when re-booting the computer. Not sure if this is normal.
Latest log files also attached.
Len
-
one more file to post...
-
What is the version of the SQL server? The requirement is SQL Server 2008 R2, could you confirm that you use the same one?
-
Yes, from the add/remove programs, that is what it looks like.
-
Okay let's confirm that:
1. Open CMD (Command Prompt).
2. Type "sqlcmd -S (local)\AVAST" to enter the SQL console.
3. Type the following commands:
> use avastent
> go
> select @@version
> go
4. Paste the Output here.
-
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\len kamholz>sqlcmd -S (local)AVAST
HResult 0x35, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [53].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or in
stance-specific error has occurred while establishing a connection to SQL Server
. Server is not found or not accessible. Check if instance name is correct and i
f SQL Server is configured to allow remote connections. For more information see
SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
C:\Documents and Settings\len kamholz>
-
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\len kamholz>sqlcmd -S (local)AVAST
HResult 0x35, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [53].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or in
stance-specific error has occurred while establishing a connection to SQL Server
. Server is not found or not accessible. Check if instance name is correct and i
f SQL Server is configured to allow remote connections. For more information see
SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
C:\Documents and Settings\len kamholz>
You have missed the backslash in the Instance name. It should be (local)\AVAST
-
Sorry about that...
C:\Documents and Settings\len kamholz>sqlcmd -S (local)\AVAST
1> use avastent
2> go
Changed database context to 'avastent'.
1> select @@version
2> go
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
------------------------------------------------------------
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)
Apr 2 2010 15:53:02
Copyright (c) Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 26
00: Service Pack 3)
(1 rows affected)
1>
-
Could you post the contents of avast.ini located in: C:\Program Files\AVAST Software\Enterprise Administration\DATA ?
-
[Languages]
0405=Czech
0407=German
0409=English
040A=Spanish
040C=French
0410=Italian
0411=Japanese
0412=Korean
0415=Polish
0416=Portuguese
Engine=1033
[Common]
ApprovedPerson=Helmel
ApprovedFirm=
ProductVersion=8.0
VersionLabel=Nov2013
MgmServerFwRulesCreated=1
ISA=0
ISAFolder=
[UserInterface]
HomePage0405=http://www.avast.com/
UserForum0405=http://forum.asw.cz/
Support0405=support@asw.cz
BuyForm0405=http://www.avast.com/go.php?verb=purchase-pro&lang=CZE
RegistrationForm0405=http://www.avast.com/go.php?verb=register-home&lang=CZE
HomePage0409=http://www.avast.com/
UserForum0409=http://forum.avast.com/
Support0409=support@avast.com
BuyForm0409=http://www.avast.com/go.php?verb=purchase-pro&lang=ENG
RegistrationForm0409=http://www.avast.com/go.php?verb=register-home&lang=ENG
HomePage0411=http://www.avast.com/
UserForum0411=http://forum.avast.com/
Support0411=support@avast.com
BuyForm0411=http://www.avast.com/go.php?verb=purchase-pro&lang=JPN
RegistrationForm0411=http://www.avast.com/go.php?verb=register-home&lang=JPN
HomePage0412=http://www.avast.com/
UserForum0412=http://forum.avast.com/
Support0412=support@avast.com
BuyForm0412=http://www.avast.com/go.php?verb=purchase-pro&lang=ENG
RegistrationForm0412=http://www.avast.com/go.php?verb=register-home&lang=KOR
HomePage0416=http://www.avast.com/
UserForum0416=http://forum.avast.com/
Support0416=support@avast.com
BuyForm0416=http://www.avast.com/go.php?verb=purchase-pro&lang=ENG
RegistrationForm0416=http://www.avast.com/go.php?verb=register-home&lang=POR
HomePage040C=http://www.avast.com/
UserForum040C=http://forum.avast.com/
Support040C=support@avast.com
BuyForm040C=http://www.avast.com/go.php?verb=purchase-pro&lang=ENG
RegistrationForm040C=http://www.avast.com/go.php?verb=register-home&lang=FRE
ShowHelpCheckList=0
[Communication]
ServerAddress=127.0.0.1
[SQL]
DBCreated=0
DataSource=LEN-II\avast
Catalog=avast
MSDE=1
-
Set DBCreated to 1 and try to start the 'avast! Enterprise Administration Server' service.
-
Ok, That allowed the service to start and stay running. So then I was able to launch the Admin Console and it was able to detect and connect to the server. So that part is all good now.
So my next step is to figure out if the clients are seeing the new license I put in a few weeks ago. This all started when the client software was updated, and then they got a message that their subscription expired.
-
Yes, I just checked a few clients who had trouble before, and now they see the proper subscription.
Thanks for all your help...I think I'm good.
Len