When debugging a K2.net™ 2003 database and you need to get it running in another environment, it is necessary to reset the security settings for the K2.net™ 2003 Service Manager, as this contains information about the original network environment.

As part of a debugging process on a K2.net™ 2003 database, it is sometimes necessary to reset the administrator security settings. The database could contain security information relating to the original network environment. Therefore, there could be no way of connecting to the K2.net™ 2003 Server using the K2.net™ 2003 Service Manager.

Resolution
The resolution would be to remove all user information from the database and add a new user to the database.

The user information is stored in the transaction database (called “K2” by default), in the “_ServerUser” table.

Steps required
1.  Stop the K2.net™ 2003 Server Service.
2.  Backup the “K2” and “K2log” databases.
3.  Delete all the records from the “_ServerUser” table.
4.  

Delete all the records from the “_ServerUser” table.
Run the following script on the database (K2) using SQL Query Analyzer.

-- Reset the security rights
delete from K2.._ServerUser

5.  

Add a new user to the database with Admin and Export rights:
Run the following script on the database (K2) using SQL Query Analyzer

-- Add a user to the _ServerUser table
-- Domain: Domain Name for user as specified in [Username]
-- Username: NT Logon for the user that requires Admin or Export rights
insert into K2.._ServerUser ([User],Admin,Export)
   values ('Domain\Username', 1, 1)

6.  Restart the K2.net™ 2003 Server Service.

Alternatively, you could directly edit the “_ServerUser” table from within SQL Server Enterprise Manager.

Important: Exercise extreme caution when making changes to the K2.net™ 2003 tables directly. Make sure that you stop the K2.net™ 2003 server and backup your database before attempting this.