K2 4.5 1370 upgrade to 4.6.5


Badge +4

Now that we have migrated our environment to WS2K8R2 we started to upgrade our test environment, however we have hit a problem where the setup manager said the K2 databases as "incomplete".


After looking at the logs it appears this section related to the problem with the K2_K2SQLUM database and that not being upgraded properly.


 "7807","2013-05-02 02:16:09","Error","15","15002","ERROR","SourceCode.Database.Configuration.ConfigureDBs","15002 SqlException.Number != -2, so not handling it as a timeout. SqlException.Number = 8152. Exception: String or binary data would be truncated.
Encrypting existing passwords
The statement has been terminated.","anonymous","0.0.0.0","LUWIN90106:C:softwareK2 4.6.5 InstallationK2 blackpearl 4.6.5 (4.12060.1550.0)Installation","7807","064459e6457b46eaa0d171509180100a",""
"7808","2013-05-02 02:16:09","Info","15","15001","INFO","SourceCode.Database.Configuration.ConfigureDBs","15001 K2_K2SQLUM - Execution of script failed: SourceCode.Data.CustomUM_4_6.upgrade.sql","anonymous","0.0.0.0","LUWIN90106:C:softwareK2 4.6.5 InstallationK2 blackpearl 4.6.5 (4.12060.1550.0)Installation","7808","4e6a98cb7bdb4d0bbc523ed7e3c38280",""


The k2 host server now fails to start with the following error message:


"257755","2013-05-02 14:18:47","Error","System","2001","ServerStartError","SourceCode.Hosting.Server.Runtime.HostServerEngine.StartHostServer","2001 Error Starting Host Server: Could not find stored procedure 'Identity.FreeServerLocks'.","system","::1","LUWIN90106:C:Program Files (x86)K2 blackpearlHost ServerBin","257755","630f7291d099480e9579b6b26971cfb6",""


To me, it seems the upgrade ran into a timeout issue when applying the updates to the K2_K2SQLUM database, however when I rerun the setup manage it says this database is up to date, and all the others need updating....


I have raised a ticket, but thought it might be useful to see if anybody else has any suggestions on what to do.


Thanks,


5 replies

Badge +9

best would be to open a support ticket to insure a speedy resolution to your issue.

Badge +4

At the time I raised a support ticket and a resolution was provided.


The solution was a change to a database field that stopped the upgrade scripts from running, I believe a bug has been logged and if somebody encounters this error in the future support will be in a position to help them resolve it quickly.

Badge +9

thank you for the update

Badge +1

Can you give more detail on your solution to this problem? I ran into a very similar issue when trying to do the upgrade to 4.6.5 and opened a ticket, but haven't heard back from support with a solution yet. Thanks.

Badge

had the same issue. its the UserPassword field length issue. I modified it to be 200 characters length instead of default 30.


look at [K2SQLUM].[dbo].[K2Users] table 

Reply