{"id":32341,"date":"2026-08-03T09:06:23","date_gmt":"2026-08-03T09:06:23","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=32341"},"modified":"2026-08-03T09:06:23","modified_gmt":"2026-08-03T09:06:23","slug":"how-to-solve-unknown-error-nok-while-configuring-sage-x3-console","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2026\/08\/03\/how-to-solve-unknown-error-nok-while-configuring-sage-x3-console\/","title":{"rendered":"How to solve Unknown error: &#8216;NOK&#8217; while configuring Sage X3 Console"},"content":{"rendered":"\n<p>When setting up a new <strong>Sage X3 V12 Patch 39<\/strong> environment on a cloud-based Windows Server, we encountered an unexpected error while creating a new solution in the <strong>Sage X3 Configuration Console<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><imgtarget=\"_blank\" rel=\"noopener noreferrer\"><img fetchpriority=\"high\" decoding=\"async\" width=\"601\" height=\"492\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2026\/08\/Console.png\" alt=\"Console\" class=\"wp-image-32342\" srcset=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2026\/08\/Console.png 601w, https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2026\/08\/Console-300x246.png 300w\" sizes=\"(max-width: 601px) 100vw, 601px\" \/><figcaption class=\"wp-element-caption\"><strong>Fig_01: Console<\/strong><\/figcaption><\/figure>\n\n\n\n<p>The Configuration Console displayed the following message:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Connection failure Unknown error: NOK<\/h4>\n\n\n\n<p>At first, the error did not provide any useful information about the root cause, making the troubleshooting process more challenging.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting Performed<\/h2>\n\n\n\n<p>Before identifying the actual issue, we performed all standard troubleshooting steps to ensure the environment was configured correctly.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Verified all Sage X3 V12 Patch 39 prerequisites.<\/li>\n\n\n\n<li>Reinstalled all Sage X3 components, including the Database, Application Server, and related services.<\/li>\n\n\n\n<li>Confirmed that all required Windows services were running successfully.<\/li>\n\n\n\n<li>Verified that all required network ports were enabled and in the <strong>Listening <\/strong>state.<\/li>\n\n\n\n<li>Cross-checked firewall and network configurations.<\/li>\n\n\n\n<li>Reviewed server connectivity and DNS resolution.<\/li>\n\n\n\n<li>Validated the Sage Power User credentials.<\/li>\n\n\n\n<li>Restarted the Sage services after each configuration change.<\/li>\n<\/ul>\n\n\n\n<p>Despite completing all of the above steps, the <strong>Unknown error: NOK <\/strong>continued to appear.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Important Checks Before Creating a New Solution<\/h1>\n\n\n\n<p>Before creating a new Sage X3 solution, ensure the following:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1.&nbsp; Verify Required Ports<\/h3>\n\n\n\n<p>Confirm that all required Sage X3 ports are open and listening. Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>1818<ul><li>8124<\/li><\/ul><ul><li>9200<\/li><\/ul><ul><li>1433<\/li><\/ul>\n<ul class=\"wp-block-list\">\n<li>27017<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>(Port requirements may vary depending on your environment.)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.&nbsp; Validate the Sage Power User Password<\/h3>\n\n\n\n<p>Ensure that the Power User password complies with the configured Sage X3 password policy. A strong password should contain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Uppercase letters<\/li>\n\n\n\n<li><span style=\"color: initial;\">Lowercase letters<\/span><\/li>\n\n\n\n<li>Numeric characters<\/li>\n\n\n\n<li>Special character<\/li>\n\n\n\n<li>A supported password length (configured by your Sage X3 password policy)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">1.&nbsp; Firewall Configuration<\/h3>\n\n\n\n<p>Although optional, temporarily disabling the Windows Firewall during troubleshooting can help determine whether firewall rules are blocking communication between Sage components.<\/p>\n\n\n\n<p><strong>Note: <\/strong>Re-enable the firewall after testing and configure the appropriate inbound and outbound rules.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Root Cause<\/h1>\n\n\n\n<p>After extensive troubleshooting, we discovered that the issue was related to the <strong>cloud-based Windows Server environment<\/strong>.<\/p>\n\n\n\n<p>While installing the Syracuse component we need to specify full <strong>cloud-based Windows Server<\/strong><\/p>\n\n\n\n<p>abc-WEBxyz<\/p>\n\n\n\n<p>However, in a cloud\/domain environment, Sage X3 expected the <strong>fully qualified server name <\/strong>instead of only the hostname.<\/p>\n\n\n\n<p><strong>The correct value is:<\/strong><\/p>\n\n\n\n<p>abc-WEBxyz.cor.CLOUD\\X3V12<\/p>\n\n\n\n<p>instead of<\/p>\n\n\n\n<p>abc-WEBxyz<\/p>\n\n\n\n<p>Once we updated the server name to the fully qualified server name (including the domain and instance), the Sage X3 Configuration Console connected successfully.<\/p>\n\n\n\n<p>The <strong>&#8220;Unknown error: NOK&#8221; <\/strong>disappeared, and we were able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create the new Sage X3 solution<\/li>\n\n\n\n<li>Connect successfully to the Application Server<\/li>\n\n\n\n<li>Complete the Sage Configuration Console setup<\/li>\n\n\n\n<li>Continue with the remaining environment configuration<\/li>\n<\/ul>\n\n\n\n<p>The <strong>&#8220;Unknown error: NOK&#8221; <\/strong>in the Sage X3 Configuration Console can be misleading because it does not clearly identify the underlying problem. In our case, the issue was <strong>not related to the Sage installation, services, ports, or prerequisites<\/strong>. Instead, it was caused by using only the server hostname in a cloud-based environment.<\/p>\n\n\n\n<p>If you encounter this error while deploying Sage X3 on a cloud-hosted Windows Server, verify that you are using the <strong>Fully Qualified Domain Name (FQDN) <\/strong>(or the fully qualified server name expected by your environment) instead of only the server hostname. This simple change resolved the issue and allowed the installation to proceed successfully.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When setting up a new Sage X3 V12 Patch 39 environment on a cloud-based Windows Server, we encountered an unexpected error while creating a new solution in the Sage X3 Configuration Console. The Configuration Console displayed the following message: Connection failure Unknown error: NOK At first, the error did not provide any useful information about\u2026 <span class=\"read-more\"><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2026\/08\/03\/how-to-solve-unknown-error-nok-while-configuring-sage-x3-console\/\">Read More &raquo;<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,5,3162,6,8,3642,10,12],"tags":[1762,1780,1822,1839,1845,2871,1907,4591,4590],"class_list":["post-32341","post","type-post","status-publish","format-standard","hentry","category-configuration","category-features","category-greytrix","category-installation","category-sage-erp-x3","category-sage-x3","category-standard","category-sage-x3-upgrade","tag-sage-enterprise-management","tag-sage-erp-x3","tag-sage-x3","tag-sage-x3-blogs","tag-sage-x3-console","tag-sage-x3-functional-blogs","tag-sage-x3-migration","tag-sage-x3-new-installation","tag-sage-x3-patch-update"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=32341"}],"version-history":[{"count":1,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32341\/revisions"}],"predecessor-version":[{"id":32343,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32341\/revisions\/32343"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=32341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=32341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=32341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}