Avast WEBforum

Business Products => Archive (Legacy) => Avast Business => Avast Server Protection => Topic started by: ZH2 on July 22, 2015, 08:40:56 AM

Title: Administration Console wont start
Post by: ZH2 on July 22, 2015, 08:40:56 AM
Good day guys,


Fiirstly would like to say, I am VERY new to using avast. I have taken over a client site. So I am not 100% sure how this works yet. Trying to get this working, to figure it out. But cant access the Administration Console.

The log file is as follows: Hope someone can guide me.

[Header - Application started at 22-Jul-2015 05:53:05,486 local/05:53:05,486 UTC]
07-22 07:53:05,814 [1] INFO  Program - avast! Administration Console service (version: 1.3.2.21)
07-22 07:53:05,898 [1] INFO  Program - Running on Windows Server 2012 - Version 6.2.9200 (64bit)
07-22 07:53:06,327 [4] INFO  SbcCoreService - Service starting. Loading configuration
07-22 07:53:06,457 [4] INFO  DatabaseConnector - Performing initial connection to the database (Provided connection string: Data Source="C:\ProgramData\AVAST Software\Administration Console\db.sdf";Default Lock Timeout=30000;Mode="Read Write";Max Buffer Size=10000;Max Database Size=2048;Temp File Max Size=512).
07-22 07:53:06,877 [4] INFO  AbstractSbcDatabase - Opening connection with connection string: Data Source="C:\ProgramData\AVAST Software\Administration Console\db.sdf";Default Lock Timeout=30000;Mode="Read Write";Max Buffer Size=10000;Max Database Size=2048;Temp File Max Size=512
07-22 07:53:07,402 [4] INFO  DatabaseConnector - Successfully connected.
07-22 07:53:07,437 [4] INFO  DatabaseConnector - Performing initialization.
07-22 07:53:07,441 [4] INFO  AbstractSbcDatabase - Performing initialization.
07-22 07:53:14,669 [4] INFO  WebRequestConfiguration - Configuring proxy...
07-22 07:53:14,669 [4] INFO  WebRequestConfiguration - No proxy server specified. Direct connection will be used for web requests.
07-22 07:53:14,857 [4] WARN  AvastLoaderBase - Bad image format exception on file c:\program files\avast software\administration console\Avast.Messaging.Tcp.dll
07-22 07:53:16,108 [SchedulerCacheMediator] INFO  CacheMediator - Starting scheduler cache thread.
07-22 07:53:16,615 [4] INFO  SbcCoreService - Starting core.
07-22 07:53:16,876 [4] INFO  FileLicenceProvider - Loading license file from path C:\ProgramData\AVAST Software\Administration Console\license.avastlic
07-22 07:53:17,421 [4] INFO  FileLicenceProvider - Loaded license file for EPSP edition.
07-22 07:53:17,567 [MessageQueueThread] INFO  EngineProxyVisitor - Message queue thread started.
07-22 07:53:17,614 [CoreWorker] WARN  AvastLoaderBase - Bad image format exception on file c:\program files\avast software\administration console\Avast.Messaging.Tcp.dll
07-22 07:53:17,816 [CoreWorker] WARN  AvastLoaderBase - Bad image format exception on file c:\program files\avast software\administration console\Avast.Messaging.Tcp.dll
07-22 07:53:17,966 [CoreWorker] INFO  SystemMonitorManager - Starting system monitoring thread.
07-22 07:53:17,976 [CoreWorker] INFO  SystemHealthMonitor - Process memory: Non paged - 0/ Paged - 76/ Virtual - 742)
07-22 07:53:17,980 [CoreWorker] INFO  SystemHealthMonitor - Computer memory: physical-13311 pagefile-15999
07-22 07:53:17,980 [CoreWorker] INFO  SystemHealthMonitor - Available memory: physical-5999 pagefile-6887
07-22 07:53:17,991 [CoreWorker] WARN  AvastLoaderBase - Bad image format exception on file c:\program files\avast software\administration console\Avast.Messaging.Tcp.dll
07-22 07:53:18,025 [Scheduler] INFO  Scheduler - Scheduler thread has been started.
07-22 07:53:18,029 [SchedulerWorker0] INFO  Scheduler - Starting scheduler worker thread
07-22 07:53:18,029 [SchedulerWorker1] INFO  Scheduler - Starting scheduler worker thread
07-22 07:53:18,029 [SchedulerWorker4] INFO  Scheduler - Starting scheduler worker thread
07-22 07:53:18,029 [SchedulerWorker3] INFO  Scheduler - Starting scheduler worker thread
07-22 07:53:18,029 [SchedulerWorker2] INFO  Scheduler - Starting scheduler worker thread
07-22 07:53:18,190 [4] INFO  SbcCoreService - Binding SbcConnectionPoint to:
 (http://localhost:8731/Design_Time_Addresses/Avast.Sbc.Service.Core/SbcConnectionPoint/, https://localhost:8732/Design_Time_Addresses/Avast.Sbc.Service.Core/SbcConnectionPoint/)


07-22 07:53:18,357 [4] INFO  SbcCoreService - Starting SBC service host.
07-22 07:53:18,424 [4] INFO  SbcCoreService - Starting console service.
07-22 07:53:18,725 [4] INFO  SbcCoreService - Starting managed client listener
07-22 07:53:18,874 [4] INFO  EngineConnectionPointMonitorFactory - Starting engine connection point: b36cecc0-8ad2-42ae-adc5-95256d9208ac
07-22 07:53:18,894 [4] FATAL SbcCoreService - Service could not be started.
System.NotImplementedException: IClientMonitor protocol of tcp:// has not been implemented or properly registered.
   at Avast.Sbc.Service.Core.Rpc.Iface.ClientMonitorFactory.CreateInternal(String protocolPrefix, Int16 serverPort, TimeSpan generationSpan, IContextSbcEngineConnectionPoint contextSbcEngineConnectionPoint, SbcServerMessagingConfiguration configuration)
   at Avast.Sbc.Service.Core.Rpc.Iface.ClientMonitorFactory.CreatePrimary(SbcServerMessagingConfiguration configuration, TimeSpan generationSpan, IContextSbcEngineConnectionPoint contextSbcEngineConnectionPoint)
   at Avast.Sbc.Service.Core.EngineConnectionPointMonitorFactory..ctor(IServerCore serverCore, SbcServerMessagingConfiguration configuration, TimeSpan generationSpan)
   at Avast.Sbc.Service.SbcCoreService.OnStart(String[] args)
07-22 07:53:19,446 [SystemMonitor] INFO  ProviderStatusMonitor - Issuing new provider status cleanup operation.
07-22 07:53:19,451 [SystemMonitor] INFO  SystemHealthMonitor - Process memory: Non paged - 0/ Paged - 80/ Virtual - 771)
07-22 07:53:19,452 [SystemMonitor] INFO  SystemHealthMonitor - Computer memory: physical-13311 pagefile-15999
07-22 07:53:19,452 [SystemMonitor] INFO  SystemHealthMonitor - Available memory: physical-5994 pagefile-6887