Could not connect to the Prognosis client Error: 10061

[Anon]

A few days after upgrading to Prognosis foundation v10 from the demo version we ran into the following error, which prevents logon.

Could not connect to the Prognosis client (127.0.0.1:6767). Socket Failed to Connect. Error: 10061.

[GeraldC]

oohh the old 10061 Socket Failed to Connect error. This is one of those more generic errors, and could mean a number of things. Sometimes the wvlog.txt sheds more light on it but it's best to generate and send a Diagnostic.zip to the IR Support team for the best advice. Let us know if you have any trouble getting in touch with them.
HTH

[Negassi]

When I tried to login to WEB UI I see an error 10061. What does it mean? This happened after we applied a new license KEY.

[SCOTT_BALDWIN]

Hello Negassi,

Prognosis Web UI error 10061 usually means the Prognosis service is not running so the Web UI is not able to connect to anything.

The most common cause of this error is a License issue. The WVLOG (in the Prognosis\Server\Configuration directory) should provide additional information about the cause.

After applying a new License to a Windows server, the Prognosis service should be stopped, wait a few seconds, then start the Prognosis service. A restart of the Prognosis service may not completely close all Prognosis processes, causing the new License to not be correctly recognized by Prognosis.

If the Prognosis service stop, wait, start doesn't resolve the issue, a Prognosis Support case should be opened for further troubleshooting.

Thank you,

Scott Baldwin