[K2 connect] K2 Blackpearl server and K2 Connect server names are not the same
kbt141803
PRODUCTK2 connect 4.7
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.
LEGACY/ARCHIVED CONTENT
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.
Issue
When attempting to publish a K2 Connect service object in Visual Studio, the following error appears:
"K2 Blackpearl server and K2 Connect server names are not the same"
Symptoms
In Visual Studio, when opening the K2 Service Object Designer and selecting the K2 Blackpearl Settings icon: The server names under K2 Blackpearl Server and K2 Connect Service are not the same server.
Troubleshooting Steps
The server name in K2 Blackpearl Server is read from the SmartObject Server environment field in your Environment Library. Please check your default Environment Library, and make sure the connection string in SmartObject Server is pointing to the correct server.
If your SmartObject Server environment field is correct, yet the server name in K2 Service Object Designer is still showing the wrong server, then it is likely your Visual Studio is connected to a different K2 environment. In that case:
- Open K2 Object Browser
- Click on the arrow besides the Environment header
- Select Change Server
- Change the server to the correct environment's server
Once that is done, check if the server names in K2 Service Object Designer has been updated. Once the server names match, republish the service object again.
