1. Installing and configuring SQL server

1.1. Microsoft SQL Server 2000

/deprecated ! Please, use modern software only

1)     Install Windows 2000 Server + SP4 and network protocol TCP/IP, or any newer Windows version ("home" and "embedded" editions are not recommended for server side - you are going to install professional business application - that's why you have to use corresponding full-featured OS versions) or get computers with one of those mentioned pre-installed OS.

Before installing Microsoft SQL Server 2000 (or newer) one must set English language for non-Unicode programs by default (Control Panel → Regional and language options → Advanced).

2)     Set actual date and time (Start → Control Panel → Date and Time)

3)    Start installation of Microsoft SQL Server 2000 (MSSQL 2000) + Client Tools + SP4 (if the message about incompatibility of SQL Server and operating system will appears, press [Continue]):






·         When installing it's need to create a new SQL instance (not default) named GAME_KEEPER


·         Choose Mixed Mode on Authentication Mode screen

·        Set the password for sa login: 123456. It will be default password (after installation it's recommended to change it).

·        Program Files must be installed into C:\MSSQL folder, Data Files into C:\MSSQLDB  folder.


·        Choose Use the Local System accounts on Services Accounts screen



4)     Install Microsoft SQL Server 2000 Service Pack 4 (MSSQL 2000 SP4) in upgrade mode:










·        For working of Game-Keeper following services are needed: SQL Server, SQL Server Agent and Distributed Transaction Coordinator. It's necessary to ensure autorun for these services when system starts. The service Microsoft Search is not used in Game-Keeper

5)     Copy file xpGameKeeper.dll into folder C:\MSSQL\MSSQL$GAME_KEEPER\binn

6)     Configure access to MSSQL through TCP/IP, port 1433, using Server Network Utility (Start → All Programs → Microsoft SQL Server → Server Network Utility)


7)     Configure aliases GK_LOCAL and GK_CENTRAL using Client Network Utility





8) Add to Enterprise Manager → Microsoft SQL Servers → SQL Server Group → [name of the SQL Server] → Security → Linked Servers (right click – [New Linked Server…]) the GK_CENTRAL server. At first you can configure it so, that all queries will be executed on the remote server under sa login. Later you can make more subtle configuration.


9) Alias GK_LOCAL must refer to the server with gkArcade database, and GK_CENTRAL – to the server with gkHeadOffice database. If arcade works separately (without using the common corporate card server), both databases are installed on the one server, and both aliases look like\GAME_KEEPER

1.2. Microsoft SQL Server 2005-2012

2.1. You have to install server software as usually (named instance, mixed authentication) following those steps from above on alias creation (you need only GK_LOCAL for versions 3.19 and later).

2.2. In case of x64 SQL server - assign aliases both for x32 and x64 clients.

2.3. Do not forget to enable all protocols for server and allow connections in your firewall.

2.4. SQL server 'sa' (system administrator) or other user which you will use for GK3 must have 6 symbol password (at least), default is 123456. We offer you use 'gk' username.

2.5. If you install named instance of MSSQLS different from 'GAME_KEEPER', you have to edit gkAgent service dependance in registry path 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\gkAgent'  parameter 'DependOnService' change preset MSSQL server service name to that one of yours.

2. Database

2.1. Execute the installation of SQL-scripts using program gkInstall:

·        The installation process is described in a file with extension .make (default: gk3.make). It is situated in a folder New, copy it into a folder sql. Before running the installer check this file and edit if necessary parameters it contains (set instructions). Particularly, it is recommended to check variable DBPATH (a path to a physical placement of the base)

·        Run gk3Install.bat

·        Make sure it's alright (Script completed successfully)

·        Copy into sql folder files 305-306.* from folder 305-306

·        Copy into sql folder files 306-307.* from folder 306-307

·        Copy into sql folder files 307-308.* from folder 307-308

·        Copy into sql folder files 308-309.* from folder 308-309

·        Copy into sql folder files 309-310.* from folder 309-310

·        Copy into sql folder files 310-312.* from folder 310-312

·        Copy into sql folder files 312-313.* from folder 312-313

·        Copy into sql folder files 313-314.* from folder 313-314

·        Check and edit if necessary parameters that file *.make contains (set instructions)

·        Run 305-306.bat

·        Run 306-307.bat

·        Run 307-308.bat

·        Run 308-309.bat

·        Run 309-310.bat

·        Run 310-312.bat

·        Run 312-313.bat

·        Run 313-314.bat

·        Make sure it's alright (Script completed successfully)



3. Fixed IP address

3.1. You have to use persistent addressing in your network.

3.2. Set a static IP-address for server:

Control Panel → Network Connections → Local Area Connection

·        Press [Properties]

·        Choose [Internet Protocol (TCP/IP)] and press [Properties]. Set IP-address that belongs to your local network (if you have it) in the field IP address and subnet mask in the field Subnet mask. If you don't know what values it's need to set here ask your system administrator. It should look like this: 

·        Press [Advanced...] button, then [Add...] button in the table of IP addresses. Set here:

IP address: 172.31.32.* (instead of * put any number from 2 to 255)

Subnet mask:                                                                                       

·        Press [Add]. The result should be look like this: 


4. Libraries

4.1. Copy libraries (*.bpl and *.dll) into some folder (like: \windows\game-keeper\).

4.2. Set path to that folder in System variable Path (or Control Panel → System → Advanced → Environment variables → New).

4.3. Otherwise you can copy these libraries into folder \winnt\system32\ (detailed description see in “Cash station” manual).

5. Edit DB (extra)

5.1. You may need DB edition extra scripts in the following cases:

5.1.1. Erroneous values that cannot be changed using application GUI. For example, to change machine IP address you have to use query like

UPDATE [gkArcade].[gk].[MACHINES] SET [ADDR0]=32,[ADDR1]=103 WHERE [MACHINE]=1234

5.1.2. Translate the DB values to some language. You have to use script like in distributive translation package.

5.1.3. Upgrade DB version to new one. Usually scrips of this type provided by UCS in new version distributive.

6. gkPosServer

6.1. gkPosServer is the main DB connection provider in GK3 for clients like gkPos, gkAgent.

6.2. Clients are connected to gkPosServer using DCOM components (over the network - using Borland socket server).

6.3. You have to install scktsrvr.exe as windows service, use standard TCP port 211 for listening.

6.4. Configure windows component services (control panel - administrative tools) -> 'DCOM settings'. Set 'Identity'->'Interactive user' for "UCS Game-Keeper POS server" and "UCS Game-Keeper POS server Viewer". You may also specify user that you configured to autologin to this server on start. Do that after 6.6.

6.5. Copy \gkPosServer\ folder to server and set gkPosServer.ini file:

ServerName = GK_LOCAL
UserName = gk
Password =083204044C3D3D5012202010720A0C76
;Provider = SQLNCLI
ETickets = 0

6.6. You have to start gkPosServer.exe manually at least once after ini properly set in order to register DCOM.

7. gkMServer

7.1. gkMServer is the DB connection provider from GK3 distributive \gkEditor\ folder for client gkEditor.

7.2. In general, install like gkPosServer above.

7.3. Set gkMServer.ini

ServerName = GK_LOCAL
UserName = gk
Password = 083204044C3D3D5012202010720A0C76
;Provider = SQLNCLI11.1