2016-04-12 10:05 AM
Hi,
I'm using ECAT 4.1 in my company.
Recently i was trying to start the console server.exe on the ECAT server, but an error was displayed on the command line.
I was trying a few more times to start it, and then i realize that the Console Server service is down. all my attempts to start the service fails.
See the attached two error screenshots for more information.
Please Help.
Thank You.
2016-04-13 06:55 AM
It seems like it's trying to start the HTTPS service twice or that something is already listening on that port could it be that there is an IIS service running. Or that maybe the API port was configure to 443 instead of 9443?
Without your configuration files it's hard to say? Have you opened at ticket with support?
Thank you,
Rui
2016-04-13 07:20 AM
Thanks for the reply,
I don't think that there is a configuration problem, because the system was working good until i was trying to import a new license file.
Also, I checked out, there is no IIS service running.
Any way, in the meantime i opened a ticket with the RSA support, but currently i got no solution.
Yossi.
2016-04-13 07:35 AM
If you are updating your license file please make sure there is only one file in the ECAT folder. If both are currently valid that could be the cause of your issue.
2016-04-13 08:03 AM
of course, i'm doubled check it before.
2016-04-13 08:07 AM
Sorry, just trying to help! The error is strange and as you can see from the error log it seems the issue is that for some reason the service tries to start a listener on 443 twice. Hopefully support will get back to you soon!
2016-04-13 08:19 AM
Don't get me wrong, i'm really appriciate that you trying to help me.
I'll wait to RSA Support then.
Thank you very much Rui!
Have a nice day
2016-04-13 08:31 AM
I know but I also know how frustrating it can be if all the suggestions are the same you already tried before. 😞
Here's a final one, I just checked on one of my systems, with the following command:
netsh http show servicestate
Nothing shows on port 443 if the service is stopped but there are results when the service is back up.
Apologies, yes, I'm still going from the assumption that something is using that port, could it be a "crashed" instance that just won't die? I'm guessing you also tried to reboot the server.
Thank you,
Rui
2016-04-13 08:34 AM
Oh! Just noticed something else too, sorry your screen is hard to read on a smaller screen... You are using ConsoleServer.exe not ConsoleServiceOutput.exe could it be that the service as since started and they are conflicting?
2016-04-13 09:54 AM
Look what i found.
See the attachment..