This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
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.
After applying the K2 4.7 Cumulative Update the following error is displayed:
":0: ExecuteSqlScript.Execute: 16:27:12:>> Logged Error: Script execute failed: System.Exception: Script execution exception: Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Could not find stored procedure 'SP_SIGNPROCEDURE'. The statement has been terminated. at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) at SourceCode.Install.SQL.DBQuery.ExecuteTransactionalScript(String scriptFile, String connectionString) at SourceCode.Install.Package.Actions.ExecuteSqlScript.Execute(ITarget target) 1:0: MainWindow.UpdateStatus: 16:27:12:>> STATUS: Processed: Data\Patches\697420 + 711832.sql 1:0: Component.ExecuteTarget: 16:27:12:>> Logged Error: Target did not complete successfully: Data\Patches\697420 + 711832.sql 1:0: Component.ExecuteTarget: 16:27:12:>> Package not set to break on failure. 1:0: Log.WriteIndent: 16:27:13:>> Start RunQuery 1:1: DBQuery.RunQuery: 16:27:13:>> Query: INSERT INTO [HostServer].[HostServerSetting] ([Name], [Value]) VALUES ('Patch: 4.16060.2000.2 K2 blackpearl Server' ,'K2 blackpearl Server') 1:1: DBQuery.RunQuery: 16:27:13:>> Added 0 rows 1:0: Log.WriteUnindent: 16:27:13:>> End RunQuery 1:0: ComponentControl.ParseStatus: 16:27:13:>> Warnings, before: 0 after: 0 1:0: ComponentControl.ParseStatus: 16:27:13:>> Errors, before: 0 after:"
Looking at the SQL scripts from the Cumulative Update package in the error below:
"Target did not complete successfully: Data\Patches\697420 + 711832.sql"
We executed the following script directly on the K2 DB (697420 + 711832.sql) and received the same error. However this time the error also pointed to a database trigger that was not part of the K2 Cumulative setup.
It was noted that there was a trigger applied by one of the users with SQL access.
The database admin disabled the trigger and the cumulative update was successfully applied.