Symptoms
Cannot publish the Service Object from Visual Studio to Prod Server
Diagnoses
Cannot publish the Service Object from Visual Studio to Prod Server . Gives an error , the cluster names are not same in k2 blackpearl and k2 connect server.
Resolution
Restarting the K2 service and the K2 connect service might resolve this issue . When you publish a service object it creates a proxy assembly in the background. This assembly is loaded into memory of the Connect service on startup.
When you execute a Smartobject based on the serviceobject, the connect serviceinstance also loads a proxy assembly into memory via the HostServer.
Now, if you make changes to the service object in connect and publish it again, part of the process is restarting the connect service in order to load the new version into memory.
The Blackpearl HostServer is not restarted which leaves a mismatching assembly signature in memory, hence the method not found errors.
If you are busy developing your service object, making changes to parameters and methods, it is best to restart both the connect service and HostServer after publish.
http://help.k2.com/HelpPages/K2Connect4.5.5/Publishing_Process.html
