In certain scenarios the location of the SQL database where the K2 and K2Log databases were installed may change, e.g. customers may want to scale their solution. This article will guide the users to components that need to be reconfigured.
This document will help K2.net administrators and developers better understand the conditions affecting their K2.net 2003 Named User License (NUL) systems. The most common symptom of exceeding NUL conditions is when the following dialog box is displayed:
The following components will need to be reconfigured in a scenario where the location of the SQL Server has changed.
K2.net 2003 Server
K2.net Service Manager
Direct File Manipulation
* Only used for SQL Authentication. These values will not be present when using integrated authentication to connect to SQL Server
There are no direct references to the K2.net Transaction and Log databases in K2.net Studio as all communication is direct to the K2.net Server Windows service. Exceptions are custom queries made in SQL Data and Server events and the connection for these should rely on String Table entries configured for the Project. See the K2.net Help file for information on using the String Table.
K2.net 2003 Workspace
The K2.net Workspace web application does not do any data mining directly, it relies on the K2.net Workspace Web service for all report data retrieval from the K2.net Log database. If the SQL Server has been relocated, the web service's configuration file will need to be updated using the following steps.
K2.net Out of Office Component
The Out of Office (OOO) component's main interface for capturing user settings a web page displayed from within Workspace. This page will save the information gathered from the user directly to the K2.net Transaction database. The web.config file of the Out of Office web site would thus need to be updated.
K2.net 2003 Collaboration Tools
The K2.net Collaboration Tools will need to save information captured by the SharePoint configuration to the K2.net Transaction Database. When the SQL Server hosting the K2.net Transaction database is moved, Collaboration Tools' configuration will need to reflect this change. To implement the change:
K2.net 2003 Archiving Components