LEGACY CONTENT
This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. 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.

Introduction

When an upgrade is performed, and the initial installation is K2 blackpearl 0807 + KB000370 and K2 blackpearl + KB000450 is used for the upgrade, database script errors may be encountered and an error similar to the one below may be displayed:

"Could not locate entry in sysdatabases for database ’K2’. No entry found with that name. Make sure that the name is entered correctly."

Also, timeouts may be experienced while certain scripts are being executed.

Error Scenario

Note: The steps in this article describe one scenario under which this issue may occur. They are simplified and not all steps are shown or described.

The error occurs owing to the [K2ServerDBName] placeholder in K2ServerAlter.sql which has been replaced IN FULL (with square brackets) with ’k2.prod.K2Server’; which is the name of the database. However SQL Server does not accept this as a valid database name without the square brackets included.

A secondary problem may occur when the Database scripts time out after approximately 10 minutes, although a retry will be performed up to 3 times.

Error Messages

The following error message applies to this article:

  • Could not locate entry in sysdatabases for database ’K2’. No entry found with that name. Make sure that the name is entered correctly

Error Resolution


Option 1 (Recommended only for users familiar with the relevant databases)

To resolve the above issues, run the K2ServerAlter.sql script manually against the K2Server production database and the script should execute successfully.

The timeout value for the Database Scripts will be adjusted to accommodate a possible extention required to avoid a timeout.

Option 2 (This option is recommended for best results)

The corresponding Hotfix to resolve this issue is not available as a public download. Please contact your regional support centre to get the Hotfix.