Cannot deploy K2 Connect service to Staging environment

  • 5 February 2015
  • 1 reply
  • 2 views



 

Symptoms


We are attempting to deploy a K2 Connect service object to a new environment (Staging) for the first time from dev environment. We receive an error: "K2 blackpearl Server and K2 connect Server names are not the same". However, after clicking 'OK' on the error, the 'K2 blackpearl Settings' windows displays and you can see that it is pointing to correct staging. But, there is a message 'Valid K2 connect Server information not found'.

 

Diagnoses


The Dev environment didn't have direct access to Staging connect environment.
 

Resolution

Issue was resolved per following steps:

-Copy the .svd file to staging server.
-Add the .svd using the Add Service Object option from K2 connect Administration Tools.
-Refresh the Service Instance from the K2 connection Admin tool.




 

1 reply

Well.! I think you need to make sure if K2 offers Staging Environment. I know it is a very necessary part but still many of the infastructure are far behind in adapting the Staging environment. Do let me know if they provide such service. Moreover, I will be sharing this threat with my technical guy. If he is able to figure out any answer

Reply