HI VS

Take note of the following before you restore your database to a new server

https://help.k2.com/support-services/kbt135736?z=*personal details removed*42

http://community.k2.com/t5/K2-blackpearl/Database-Key-error/ta-p/90663

Should you find the information from the article useful or leading you to the answer please mark as "Solution and/or Kudo", as it will assist other k2 developers with relevant information in the near future.

Best Regards

Elvis

pK2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

Hi Elvis, 

Thank you so much for your reply.

But I don't think we can use this approach as I have mentioned before we have running applications with live instances on the new server.

What would you suggest to migrate this only application from the old server(4.6.11) to new (4.7) with its live instances?

Thanks,

Vishal

Hi VS

installing K2 blackpearl 4.7 against a new database is perfectly fine; however please allow the Setup Manager to create the database.
http://help.k2.com/support-services/kbt140634

2. Migrating solutions from 4.6.11 to 4.7 is possible and supported and will likely involve the P&D tool:
https://help.k2.com/kb001782

3. However, it is currently NOT possible to migrate any in-progress items. The only way to have these in-progress items is to upgrade the 4.6.11 database that was migrated for e.g SQL 2012 R2 server.

Should you find the information from the article useful or leading you to the answer please mark as "Solution and/or Kudo", as it will assist other k2 developers with relevant information in the near future.

Best Regards

Elvis

>K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

Good day VS,

This operation is not supported. There is no way to move “active process instances/workflow live instances” between environments. The best approach would be to restore the Database from the environment containing the Active instances into a different environment. You can only restore the full database and not specific tables.

Kindly feel free to mark as “Accepted solution, kudo and/me too” if you find this information answered your question or leads to your answer.

Thank you and kind regards,

Dumisani

K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.

Hi Vs;

Unfortunately, it is not possible to move an active instance of a workflow that was started on i.e. version 1 of the workflow to version 2 of the workflow.
Here is an example: suppose that you can deployed V1 of a workflow design, and 10 instances of that workflow start. Each of these instances will continue running on the V1 definition of the workflow for their entire lifetime, even if you deploy V2 of the workflow design. By default, Workflows start on the "Default" version of the workflow and this is usually the last version that was deployed when the workflow starts. While you can use the K2 management tools to declare a different version to be the default version of a workflow, this will not affect active instances of the workflow.

Referencing documentation:
(http://help.k2.com/onlinehelp/k2blackpearl/devref/current/default.htm#live_instance_management.html)

Additional Information:
http://help.k2.com/onlinehelp/k2blackpearl/devref/current/default.htm#Important_Notes.html

Should you find the above information useful kindly mark such as "Kudo and/or Accepted Solution ".

Regards;

Widson.

Good day Vishal

It is possible and normal to upgrade your K2 with active instances. This process will not affect any of the instances. The move to the new server can then be done by using the documentation explaining to do so. Click here for the document that is also listed below. Choose your relevant scenario and the steps can be followed. Just a small heads up, When moving the database an encryption and decryption process takes place. A script must be run to decrypt the database which can be found in the documentation here. A key is needed for this script but sadly a support ticket must be logged requesting the Key.

Documentation:

1. https://help.k2.com/kb001356

2. https://help.k2.com/support-services/kbt135736

If this response solved your problem please remember to mark it as a Kudo or Solution. This will show other users that this response is the answer to their question and they can just follow the solution accordingly.

Best Regards

Jacques.

�K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]