Skip to main content
Nintex Community Menu Bar

Hi,

 

I am upgrading my development environment from K2 4.7 to K2 5.2.

While upgrading i got below warning

15279i59065E3FFF514DB1.jpg

i read the kb article: https://help.k2.com/kb002337.  in this it is mentioned that even if i continue with the setup, there will be error with SMO data or any other configuration.

i re-installed SQL server with correct collation but the existing K2 database is having the old collation.

can someone please help me with this and suggest me how can i change the collation.

 

 

Thanks in Advance

 

Regards,

Hemant

Hi,


 


It sounds like the K2 database is not using supported SQL collation. Perhaps, you can try the following suggestion, please make sure the envrionment is backup first.


https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/


 

Good day Hermant

 

This is a known issue, please follow this link: https://help.k2.com/kb002337 to resolve your issue.

 

Thank you

 

Kind regards

Thabang

Hi Hemant

 

update the SQL Server Instances Collation to a K2 Five supported collation.
 server admins  uninstal and reinstal the SQL Server Instance with the correct collation.

 reattached the 4.7 K2 Database and ran the K2 configuration.

 

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

 

Hi Hemant

 

update the SQL Server Instances Collation to a K2 Five supported collation.
 server admins  uninstal and reinstal the SQL Server Instance with the correct collation.

 reattached the 4.7 K2 Database and ran the K2 configuration.

 

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

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings