< class="prominent-subhead ">

While installing K2 Connect, the local server name is used instead of the cluster domain name

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


While installing K2 Connect in a K2 cluster configuration, the local server name is used instead of the cluster fully qualified domain name.


Your service instance may point to the local server name instead of the fully qualifed domain name. If you updated it in the SmartObject Services Tester tool, once you refresh the service instance from the K2 Connect Admin tool, it will reset to the local server name.


Our developers identified this as an issue and have resolved it in the K2 Connect 4.7.2 release.

Please contact K2 Support for the K2 Connect 4.7 codefix.