Client Security 14.xx or Server Security 14.xx (and later) not able to connect to Policy Manager Server - WithSecure Community
<main>
<article class="userContent">
<h3 data-version="5" data-article="000010258" data-id="issue">Issue:</h3>
<p>Client Security 14.xx (and later) or Server Security not able to connect to the configured Policy Manager Server (PMS). Consequently, the client is unable to autoregister itself to the PMS and cannot download policies or upload status-information.</p>
<h3 data-id="resolution">Resolution:</h3>
<p></p><p>To troubleshoot similar issues, open the following file on the computer running Client Security 14.xx and later:<br><br><b>C:\ProgramData\F-Secure\Log\BusinessSuite\pmpselectorplugin.log</b><br><br>Below is an example when communication with the PMS is working (PMS hostname is acme.com):<br><br><b>2019-03-08 09:08:34.991 [0e70.118c] I: *** LOGGING STARTED *** (UTC+2:00, session: 0x0)<br>2019-03-08 09:08:35.283 [0e70.118c] I: PmpSelectorPlugin::PluginMain: Starting: '100\PmpSelectorPlugin'<br>2019-03-08 09:08:35.284 [0e70.118c] I: ServerFinder::ServerFinder: Last known good server is {host: acme.com, http: 80, https: 443}<br>2019-03-08 09:08:35.284 [0e70.118c] I: `anonymous-namespace'::LoadPmsAddress: Forced PMS address loaded from cosmos: {host: acme.com, http: 80, https: 443}<br>2019-03-08 09:08:35.746 [0e70.118c] I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed<br>2019-03-08 09:08:42.801 [0e70.118c] I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed<br>2019-03-08 09:08:48.895 [0e70.118c] I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from acme.com<br>2019-03-08 09:08:49.436 [0e70.118c] I: UpdatablePmCertVerifier::RenewCertificates: Certificates renewed successfully. Count: 2<br>2019-03-08 09:08:49.436 [0e70.118c] I: CosmosUpdater::UpdateCosmos: Updating cosmos with PMS {host: acme.com, http: 80, https: 443}</b><br><br>Below is an example where communication is failing (PMS hostname acme2.com):<br><br><b>2019-03-01 12:32:56.185 [2b20.1a40] I: *** LOGGING STARTED *** (UTC+5:30, session: 0x0)<br>2019-03-01 12:32:56.612 [2b20.1a40] I: PmpSelectorPlugin::PluginMain: Starting: '100\PmpSelectorPlugin'<br>2019-03-01 12:32:56.614 [2b20.1a40] I: ServerFinder::ServerFinder: Last known good server is {host: acme2.com, http: 80, https: 443}<br>2019-03-01 12:32:56.644 [2b20.1a40] I: `anonymous-namespace'::LoadPmsAddress: PMS address loaded from cosmos: {host: acme2.com, http: 80, https: 443}<br>2019-03-01 12:32:56.653 [2b20.1a40] .W: ServerFinder::Ping: Ping to {host: acme2.com, http: 80, https: 443} aborted. There are no valid certificates<br>2019-03-01 12:32:56.653 [2b20.1a40] I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from acme2.com<br>2019-03-01 12:32:59.070 [2b20.1a40] *E: UpdatablePmCertVerifier::RenewCertificates: Failed to download certificate bodies. AsyncSendRequest failed: 12007</b><br><br>From the failed connection, the failure to connect is error 12007. Checking the Microsoft error-page:<br> </p>
<ul><li><a href="https://docs.microsoft.com/en-us/windows/desktop/winhttp/error-messages" rel="nofollow">https://docs.microsoft.com/en-us/windows/desktop/winhttp/error-messages</a></li></ul><p><br><b>Error 12007 translates to:<br><br>ERROR_WINHTTP_NAME_NOT_RESOLVED<br>12007<br>The server name cannot be resolved.</b><br><br><br> </p>
<p>Article no: 000010258</p>
</article>
</main>