If different workstations require different scanner settings, there are two configuration options.

Always show scanner selection

  • The simplest method is to always display the scanner selection. In this case, the user must perform one more click at his workstation. The locally installed scanner driver takes care of the correct settings, such as rotation, mirroring, etc. Only one workstation needs to be created in the GP Manager.
    This method does not work if the Windows driver (Windows Image Acquisition (WIA)) is used and different GP Manager settings for rotating, mirroring, etc. are required between the workstations.

    • The two INI files in the single workstation are responsible for displaying the selection dialogue:
      • Gp_Scan_Fuss.ini - Contains the settings for scanning feet.
      • Gp_Scan_Tritt.ini - Contains the settings for scanning footprints.
    • In both INI files, the parameter FILE_TWAIN to an INI file in the .\GpSystem\INI directory. The settings for displaying the scanner selection dialogue are stored in this file.
    • For the dialogue to appear, the parameter B_Unconditional_Dialogue_Call = Yes can be set. The parameter B_Create_Twain_Property_List = No must always be set. If the value is set to Yes, the GP Manager crashes more frequently.

Do not display scanner selection - The GP Manager manages the scan settings

  • If settings are to be managed by the GP Manager, the following INI files must be customised in the individual workstation.
    • Gp_Scan_Fuss.ini - Contains the settings for scanning feet.
    • Gp_Scan_Tritt.ini - Contains the settings for step track scanning.

The two files contain references to other INI files with settings. This is done with the parameters:

  • FILE_Calibration to calibrate the scanner (rotate/mirror image, etc.)
  • FILE_TWAIN with the settings for the Twain dialogue

The files referred to are located in the folders .\GpSystem\KAL\ and .\GpSystem\INI\.

  • In the FILE_Calibration file contains settings for displaying the image. Among other things, the image can be rotated and mirrored here. This can be adjusted individually for the left and right image. If different settings are to be used for scanners: Select differently named files for each workstation and customise them.
  • In the FILE_TWAIN file, the parameters for the scanner selection dialogue are set. If the parameter B_Create_TWAIN_Property_List = Yes the GP Manager crashes. To preselect a scanner, the parameter T_Scanner is set to the value of the scanner name.
    Proceed as follows:

    • Set B_Erzeuge_SannserListe = Yes
    • Restart the GP Manager
    • Open the file C:\Temp\GpTemp\Twain_List.txt
    • Copy the scanner name and insert it after T_Scanner = in the correct Twain file.

If you selected the wrong login method when installing SQL Express, you can change the GpSQL.ini so that the GP Manager can still connect to the database. This saves you having to reinstall Microsoft SQL Express.

To do this, change the INI file as follows:

T_SERVER = server name
T_USER = release
T_PASSWD = release

If you want to start the GP Manager on a server that does not have a 3D-capable graphics card, you can proceed as follows.

Create a single location for the server and edit the GpMan.ini in the single location. All modules should be deactivated in the INI file except GP_Basis and GP_Data. If you now start the GP Manager on the server, you can still use the database functions.

This is particularly interesting if you want to import GPF files on the server.

If an SQL connection is not possible, you can proceed as follows to test the SQL connection:

Create a new file (for example, a text document). The file extension is then changed to UDL (for example: Text.txt -> Test.udl). Double-click to start the data link properties dialogue. In this dialogue you can enter the server data yourself to test the connection:

  • Server name: Selection via drop-down menu or server\instance name (example values:\GEBIOM or Server2000\GEBIOMV7)
  • User name and password are in the rule:
    • User: sa
    • Password: GeBioM2012
  • database on the server is usually:
    • GpBank

The database connection can then be terminated with "Test connection" should be checked. If no connection is established, proceed as follows:

  1. Is the service started on the server? Computer management -> Services
    • With a server solution, in addition to the instance SQL Server (INSTANZNAME) the following services must also be started.
    • SQL Server Browser
    • SQL Server Agent (INSTANZNAME)
  2. Is there a GpBank.ldf and GpBank.mdf in the correct folder?
  3. Can the server be reached (Does DNS work, can the server be reached with the "ping" command?)
  4. Is a firewall blocking access to the server (see Server installation)?

Release of the GP Manager for working with multiple workstations

  1. Share the GP Manager folder. Click with the right mouse button on the GP Manager link and select "Open file path
  2. Select the parent folder in the address bar and then right-click on the GP Manager installation folder (default: c:\GeBioM_SQL or c:\GPM_V7).
    In the context menu, select Properties -> Release -> Extended release -> Authorisations enter the folder for the group "Everyone" with the authorisation Full access free.

Release of the database for the workstations

To ensure that the database is not only available locally, the database must be configured so that it can be accessed externally.

  1. First start the SQL Server Configuration Manager for your SQL Express version. You can find this in the start menu via "All programmes" -> "Microsoft SQL Server 20XX" -> "Configuration tools"-> "SQL Server 20XX Configuration Manager
    • For Windows 10, the Manager is no longer displayed under "All apps" as it is a snap-in. Search for C:\Windows\SysWOW64\QLServerManager12.msc for the 2014 version. Older versions have smaller numbers. Alternatively, you can search your drives for SQLServerManager*.msc.
  2. In the configuration manager on the left, select "SQL Server network configuration" you can then see the SQL instances that are currently running on the server. Depending on the GP Manager version, select the instance GEBIOM resp. GEBIOMV7. Then activate "Named Pipes" and "TCP/IP" for the instance.

An exception may need to be entered in the server's firewall so that the individual workstations can access the database. As the path to the service differs depending on the version installed, first make sure that the path to the SQL service is correct.

  1. Check the path by entering a Right click on Computer make. Select "Manage" -> "Services and applications" -> "Services" -> "SQL Server (instance name)
  2. Right-click on the service and select "Properties". Copy the "Path to the EXE file„.
  3. Enter the Port 1433 and 1434 in the firewall for this service.
  4. Allow access for the SQLBrowser.exe, This is located in a standard installation under : C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe

Make sure that the services for the SQL server are also started. If the computer is to be set up for server operation, the browser and the agent must be started in addition to the SQL instance.

Ensure that the following services are started and are automatically started by Windows when the system is started (Computer Management -> Services). Alternatively, you can access service management by selecting "services.msc" start.

  2. SQL Server Browser

Customise the GpSQL.ini on the clients

The GpSQL.ini must be adapted on the clients. There should only be one GpSQL.ini in the entire GP Manager folder. This means that this file should not be located in the folders of the individual workstations. The correct location is: C:\GeBioM_SQL\GpSystem\INI\GpSQL.ini resp. C:\GPM_V7\GpSystem\INI\GpSQL.ini

  1. Customise the entry T_Server = (local)\GEBIOM in such a way that you (local) through the Server namesor the IP address of the server.
  2. Make sure that T_User = sa is set.
  3. The value T_PASSWD = GeBioM2012 must be set

Setting the data path

The data paths on the clients must be adapted so that the clients store the measurement data on the server and also search for the measurement data there. To do this, create a Sys.ini file with the following content in the GpSystem\INI folder:


or for version 7


Make sure that you are using the correct share name and restart the GP Manager.

  • Copy the GpTools folder of an existing GP Manager installation to the setup file. In the example below, the path C:\Installation medium\ is selected as an example. You can choose any path. The name of your setup file (exe) may differ from the example.
 C:\Installation medium\Full version_V7_R7.exe
 C:\Installation medium\GpTools\
  • This however, only worksif both GP Manager versions (setup file and installation) Largely identical are!
  • Create an INI folder with an ini.zip
     C:\Installation medium\INI\
     C:\Installation medium\INI\ini.zip
    • The following folder structure should be created in the ini.zip file:
       GpSystem\GPSYSTEM_single place\
    • You can copy the GPSYSTEM_Einzelplatz folder from an existing GP Manager version. It should contain the INI files!

The data path in which the GP Manager stores its binary data and milling data must be entered in the Sys.ini. If the GP Manager is installed on a server, the share in which the data is saved should be specified here. For example \\Servername\GPM_V7\GpData


There are two versions of GpMan.ini. The .\GpSystem\INI folder contains a GpMan.ini which is used to define individual workstations.

In the .\GpSystem\GpSystem_Einzelplatz folder, one of the tasks of GpMan.ini is to activate/deactivate activated modules. This is useful for a server installation if modules are not needed at some workstations.


The GpSQL.ini contains the access data for the SQL server and the location of the SQL server. The example below shows (local)\GEBIOMV7, a dot can also be used instead of (local), i.e. .\GEBIOMV7