Hi  @Sharpharp1, 

Thank you for logging this post to the community. Please log a support ticket for this issue, as further investigations will have to be carried out here. 

Kind regards, 

Percy

Hi  @Sharpharp1,

Further looking into this on our side, it appears that this can occur if you are still using SQL 2008 R2 after upgrading to 4.7 as this is not supported by us as per compatibiliity matrix below:

http://help.k2.com/blackpearl/support-matrix

If you are however using SQL 2012 and later please do log a support call to allow us to further investigate here.

Kind regards, 

Percy

Hi Percy,

I was on SQL Server Expre2008 (SP3)

Updated to SQL Server 2016 (SP1), tried again and still same error

Upon further investigation this afternoon i noticed the following: it appears that the compatibility level is still 100 on my DB (SQL Express) even after upgrading it to SQL Express 2016 (SP1)

If the level is 100, the K2 May Update will fail (during the Server update part) because it runs a couple of SQL script injections using the TRY_CONVERT function.

I had to manually change the level to 120, then ran the May K2 Update and it went through without failure.

Hope this helps others, i wasted a day on what should have been a simple procedure.

Hi,

We have created a KB for this issue, thanks for your input.

http://community.k2.com/t5/K2-blackpearl/SQL-Script-error-after-running-May-CU/ta-p/97395