{"id":4446,"date":"2026-06-08T17:52:25","date_gmt":"2026-06-08T14:52:25","guid":{"rendered":"https:\/\/support.withsecure.com\/en\/?post_type=support_article&#038;p=4446"},"modified":"2026-06-08T17:52:25","modified_gmt":"2026-06-08T14:52:25","slug":"client-security-or-server-security-is-not-able-to-connect-to-policy-manager-server","status":"publish","type":"support_article","link":"https:\/\/support.withsecure.com\/en\/support-articles\/client-security-or-server-security-is-not-able-to-connect-to-policy-manager-server\/","title":{"rendered":"Client Security or Server Security is not able to connect to Policy Manager Server"},"content":{"rendered":"<h3>Issue:<\/h3>\n<p>Client Security or Server Security is not able to connect to Policy Manager Server.\u00a0<\/p>\n<p>Consequently, the client is unable to auto register itself to the Policy Manager Server and cannot download policies or upload status-information.<\/p>\n<h3>Resolution:<\/h3>\n<p>To troubleshoot similar connectivity issues, open the following file on the computer:<\/p>\n<ul>\n<li><b>C:\\ProgramData\\F-Secure\\Log\\BusinessSuite\\pmpselectorplugin.log<\/b><\/li>\n<\/ul>\n<p>Below is an example when communication with the PMS is working (PMS hostname is acme.com):<\/p>\n<p><span style=\"font-family: courier new,courier,monospace;\"><b>2019-03-08 09:08:34.991 [0e70.118c] \u00a0I: *** \u00a0LOGGING STARTED \u00a0*** (UTC+2:00, session: 0x0)<br \/>2019-03-08 09:08:35.283 [0e70.118c] \u00a0I: PmpSelectorPlugin::PluginMain: Starting: &#39;100\\PmpSelectorPlugin&#39;<br \/>2019-03-08 09:08:35.284 [0e70.118c] \u00a0I: ServerFinder::ServerFinder: Last known good server is {host: acme.com, http: 80, https: 443}<br \/>2019-03-08 09:08:35.284 [0e70.118c] \u00a0I: `anonymous-namespace&#39;::LoadPmsAddress: Forced PMS address loaded from cosmos: {host: acme.com, http: 80, https: 443}<br \/>2019-03-08 09:08:35.746 [0e70.118c] \u00a0I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed<br \/>2019-03-08 09:08:42.801 [0e70.118c] \u00a0I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed<br \/>2019-03-08 09:08:48.895 [0e70.118c] \u00a0I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from acme.com<br \/>2019-03-08 09:08:49.436 [0e70.118c] \u00a0I: UpdatablePmCertVerifier::RenewCertificates: Certificates renewed successfully. Count: 2<br \/>2019-03-08 09:08:49.436 [0e70.118c] \u00a0I: CosmosUpdater::UpdateCosmos: Updating cosmos with PMS {host: acme.com, http: 80, https: 443}<\/b><\/span><\/p>\n<p>Below is an example where communication is failing (PMS hostname acme2.com):<\/p>\n<p><b><span style=\"font-family: courier new,courier,monospace;\">2019-03-01 12:32:56.185 [2b20.1a40] \u00a0I: *** \u00a0LOGGING STARTED \u00a0*** (UTC+5:30, session: 0x0)<br \/>2019-03-01 12:32:56.612 [2b20.1a40] \u00a0I: PmpSelectorPlugin::PluginMain: Starting: &#39;100\\PmpSelectorPlugin&#39;<br \/>2019-03-01 12:32:56.614 [2b20.1a40] \u00a0I: ServerFinder::ServerFinder: Last known good server is {host: acme2.com, http: 80, https: 443}<br \/>2019-03-01 12:32:56.644 [2b20.1a40] \u00a0I: `anonymous-namespace&#39;::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] \u00a0I: 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<\/span><\/b><\/p>\n<p>From the failed connection, the failure to connect is error 12007. Checking the Microsoft error-page:<br \/>\u00a0<\/p>\n<ul>\n<li>https:\/\/docs.microsoft.com\/en-us\/windows\/desktop\/winhttp\/error-messages<\/li>\n<\/ul>\n<p><b>Error 12007 translates to:<\/p>\n<p>ERROR_WINHTTP_NAME_NOT_RESOLVED<br \/>12007<br \/>The server name cannot be resolved.<\/p>\n<p><\/b>Additionally, you may run the Connectivity Tool to verify the current connectivity status to the Policy Manager Server. You can find this tool in the product settings window under <strong>Support<\/strong> &gt; <strong>Tools<\/strong>, then click the <strong>Run connectivity tool<\/strong> button.<\/p>\n<p>\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Client Security or Server Security is not able to connect to Policy Manager Server. <\/p>\n<p>Consequently, the client is unable to autoregister itself to the PMS and cannot download policies or upload status-information.<\/p>\n","protected":false},"template":"","support_article_product":[106],"class_list":["post-4446","support_article","type-support_article","status-publish","hentry"],"acf":{"source_foreign_id":"000005229","source_version":3,"source_system":"salesforce","source_date_updated":"2026-06-08 14:52:25","import_hash":"e65c2ee773359bf706b47da63e9c5e8753257e12","vanilla_article_id":32516,"vanilla_url":"https:\/\/community.withsecure.com\/en\/kb\/articles\/32516-client-security-or-server-security-is-not-able-to-connect-to-policy-manager-server","vanilla_kb_id":30,"vanilla_category_id":103,"machine_translated":false,"reactions_helpful_yes":0,"reactions_helpful_no":0},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article\/4446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/support_article"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=4446"}],"wp:term":[{"taxonomy":"support_article_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article_product?post=4446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}