Known Issue: Moving or Restoring a K2 database to a new SQL Server instance results in a SCSSOKey error

  • 16 February 2021
  • 1 reply
  • 29 views

Badge +6




 








Known Issue: Moving or Restoring a K2 database to a new SQL Server instance results in a SCSSOKey error



























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.




 



When you move or restore your K2 database on a new SQL server instance, you may receive the following error in your HostServer logs or in Console Mode:



 



Error 2001 Error Starting Host Server: Please create a master key in the database or open the master key in the session before performing this operation. 
The key 'SCSSOKey' is not open. 
Please open the key before using it.
;Error Invoking 'StartHostServer' : .Net SqlClient Data provider : Please create a master key in the database or open the master key in the session before performing this operation.
The key 'SCSSOKey' is not open. Please open the key before using it.


Image



 



 



 



Cause



The SCSSOKey was not rebuilt on the new SQL server instance after the K2 database move or restore.



Resolution



To resolve this issue, contact K2 support.



 










1 reply

thanks for quick response.

Reply