< class="prominent-subhead ">

Code Fix: An error occurs when installing K2 4.7 May 2017 Cumulative Update FP2 or FP3 in an environment where a non-default database name is configured 

~~repeating-content.html~~
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.

Issue Description

When installing the K2 4.7 May 2017 Cumulative Update FP2 or FP3 an error is logged in the installation log files due to a script that cannot execute. This only occurs on environments configured with a non-default database name.

Error

The error message states:

1:0: DBQuery.ExecuteTransactionalScript: 09:31:03:>> Exception: An exception occurred while executing a Transact-SQL statement or batch.

1:0: DBQuery.ExecuteTransactionalScript: 09:31:03:>> USE statement is not supported to switch between databases. Use a new connection to connect to a different database.

Resolution

  1. Ensure you have K2 4.7 installed.
  2. Download and Install the K2 4.7 May 2017 Cumulative Update from K2 Partner and Customer Portal.
  3. Get the K2 4.7 May 2017 Cumulative Update FP4 from Regional Support.
  4. Install the K2 4.7 May 2017 Cumulative Update FP4 to apply the fix.