AnsweredAssumed Answered

ConsoleServer.exe not running

Question asked by Yossi Nagar on Nov 23, 2016
Latest reply on Nov 27, 2016 by Yossi Nagar

Like • Show 0 Likes0
Comment • 5

Hi,

I'm having again problem with the ConsolServer.exe file.. every time i'm trying to run it, the window pop-up for less than half a second and closed and i'm unable to read the red error.

Attached some text from the ConsoleServer log file if it's can help someone understand my issue.

Thanks.

Yossi.

23/11/2016 16:50:06
ConsoleServer has started with following configuration:

Ports
LocalHttpsServerPort : 443
LocalUdpServerPort : 444

Database
RemoteSqlServer          : <<ECAT SERVER>>
DatabaseName             : ECAT$PRIMARY
DbSaUser                 :

Paths and Files
QueuedDataPath : C:\ECAT\Server\QueuedData

Yara/Opswat
AntiVirusConfiguration   :
YaraScannerExe           :
YaraScannerRules         :

Certificates
LocalHttpsServerCert     : EcatServerExported
LocalHttpsClientCert     : EcatClientExported
IMBrokerClientCertificateThumbprint   :

Live connection
liveserver               :
liveuser                 :
liveport                 :
livepassword             :

23/11/2016 16:50:15
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

23/11/2016 16:50:18
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

23/11/2016 16:50:26
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

23/11/2016 16:50:38
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

23/11/2016 16:56:02
[10] System.ComponentModel.WarningException:
LIVE Kernel Download failed.

Inner-Exception:
[10] System.ComponentModel.WarningException:
Cannot bulk load because the file "C:\ECAT\Server\QueuedData\KernelData.csv" could not be opened. Operating system error code 3(The system cannot find the path specified.).
SQL Error Code: 80131904
SQL Error 4861 in (2): Cannot bulk load because the file "C:\ECAT\Server\QueuedData\KernelData.csv" could not be opened. Operating system error code 3(The system cannot find the path specified.).
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at a.b.X᜛.ᜁ(String A_0)
   at EConsole.Server.LiveClient.DownloadKernel(Xᝐ ImportKernelUpdateRequest, String& reason)

23/11/2016 16:59:14
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

David Waugh

Nov 23, 2016 11:21 AM

Correct Answer

Hi your netstat shows that something is already on ports 443 and 444, so that is why console service cant start. You can use a tool such a process explorer to find out which process is listening on those ports and potentially kill it.

Alternatively give the server a reboot will free things up.

C:\Program Files\RSA\ECAT\Server>netstat -na | findstr 44
TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
TCP    [::]:443               [::]:0                 LISTENING
UDP    0.0.0.0:444            *:*

See the reply in context

No one else had this question

Outcomes

David Waugh

Nov 23, 2016 10:16 AM

Check that there isnt already an instance of consoleserver.exe running. (Perhaps by using task manager and looking at the processes for all users), or checking in Services.

You can also use netstat to confirm if the ports used by consoleserver.exe are currently in use. This again points to either another instance of console server or another application using the same ports.

C:\Program Files\RSA\ECAT\Server>netstat -na |findstr 44
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9443 0.0.0.0:0 LISTENING
TCP 192.168.123.250:445 192.168.123.229:55938 ESTABLISHED
TCP 192.168.123.250:52738 192.168.123.27:445 ESTABLISHED
TCP 192.168.123.250:56508 10.148.128.210:445 ESTABLISHED
TCP 192.168.123.250:58790 72.21.81.200:443 TIME_WAIT
TCP [::]:443 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:9443 [::]:0 LISTENING
UDP 0.0.0.0:444 *:*
UDP [::]:444 *:*

Ports TCP 443 and UDP 444 are the default ports for console server. 9443 is the api server.

Also do you mean to open consoleserver.exe or consoleserveroutput.exe which shows you what console server is doing?

1 person found this helpful

Actions

Yossi Nagar @ David Waugh on Nov 23, 2016 10:31 AM

Hi David,

There is no already an instance of consoleserver.exe running.

Also, I've ran the netstat command, here the results:

C:\Program Files\RSA\ECAT\Server>netstat -na | findstr 44
TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
TCP    0.0.0.0:9443           0.0.0.0:0              LISTENING

TCP    [::]:443               [::]:0                 LISTENING
TCP    [::]:445               [::]:0                 LISTENING
TCP    [::]:9443              [::]:0                 LISTENING
UDP    0.0.0.0:444            *:*
UDP    [::]:444               *:*

C:\Program Files\RSA\ECAT\Server>

(I removed some unnecessary ip addresses..)

And i mean to open the ConsoleServer.exe. The ConsoleServerOutput.exe is already running but showing nothing regards the ConsolServer.exe crashing..

Actions

David Waugh

@ Yossi Nagar on Nov 23, 2016 11:21 AM

Alternatively give the server a reboot will free things up.

1 person found this helpful

Actions

Yossi Nagar @ David Waugh on Nov 27, 2016 8:18 AM

A simple restart to the server solved the problem.

Thank you David.

Actions

David Waugh

Nov 23, 2016 12:00 PM

In the error message too from the logs it is pointing to there being another instance running:

23/11/2016 16:59:14
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)

1 person found this helpful

Actions

5 Replies

David Waugh Nov 23, 2016 10:16 AM
Mark Correct
Correct Answer
Check that there isnt already an instance of consoleserver.exe running. (Perhaps by using task manager and looking at the processes for all users), or checking in Services.

You can also use netstat to confirm if the ports used by consoleserver.exe are currently in use. This again points to either another instance of console server or another application using the same ports.

C:\Program Files\RSA\ECAT\Server>netstat -na |findstr 44
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9443 0.0.0.0:0 LISTENING
TCP 192.168.123.250:445 192.168.123.229:55938 ESTABLISHED
TCP 192.168.123.250:52738 192.168.123.27:445 ESTABLISHED
TCP 192.168.123.250:56508 10.148.128.210:445 ESTABLISHED
TCP 192.168.123.250:58790 72.21.81.200:443 TIME_WAIT
TCP [::]:443 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:9443 [::]:0 LISTENING
UDP 0.0.0.0:444 *:*
UDP [::]:444 *:*

Ports TCP 443 and UDP 444 are the default ports for console server. 9443 is the api server.

Also do you mean to open consoleserver.exe or consoleserveroutput.exe which shows you what console server is doing?
1 person found this helpful
Like • Show 0 Likes0
Actions
- Yossi Nagar @ David Waugh on Nov 23, 2016 10:31 AM
  Mark Correct
  Correct Answer
  Hi David,
  
  There is no already an instance of consoleserver.exe running.
  Also, I've ran the netstat command, here the results:
  C:\Program Files\RSA\ECAT\Server>netstat -na | findstr 44
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9443           0.0.0.0:0              LISTENING
  
  TCP    [::]:443               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:9443              [::]:0                 LISTENING
  UDP    0.0.0.0:444            *:*
  UDP    [::]:444               *:*
  
  C:\Program Files\RSA\ECAT\Server>
  (I removed some unnecessary ip addresses..)
  
  And i mean to open the ConsoleServer.exe. The ConsoleServerOutput.exe is already running but showing nothing regards the ConsolServer.exe crashing..
  Like • Show 0 Likes0
  Actions
  - David Waugh @ Yossi Nagar on Nov 23, 2016 11:21 AM
    Unmark Correct
    Correct Answer
    Hi your netstat shows that something is already on ports 443 and 444, so that is why console service cant start. You can use a tool such a process explorer to find out which process is listening on those ports and potentially kill it.
    
    Alternatively give the server a reboot will free things up.
    
    C:\Program Files\RSA\ECAT\Server>netstat -na | findstr 44
    TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
    TCP    [::]:443               [::]:0                 LISTENING
    UDP    0.0.0.0:444            *:*
    1 person found this helpful
    Like • Show 0 Likes0
    Actions
    - Yossi Nagar @ David Waugh on Nov 27, 2016 8:18 AM
      Mark Correct
      Correct Answer
      A simple restart to the server solved the problem.
      Thank you David.
      Like • Show 0 Likes0
      Actions
David Waugh Nov 23, 2016 12:00 PM
Mark Correct
Correct Answer
In the error message too from the logs it is pointing to there being another instance running:

23/11/2016 16:59:14
[1] System.NotSupportedException:
Multiple instances of process not supported.
at a.b.X᝝.ᜀ(String[] A_0, Boolean A_1)
1 person found this helpful
Like • Show 0 Likes0
Actions

ConsoleServer.exe not running

Outcomes

Related Content

Recommended Content