Introduction
Tutorials
Getting familiar with GeoData Manager
Changing how GeoData Manager looks
Scenarios for using GeoData Manager
Reference
Installing GeoData Manager for the first time
Getting familiar with GeoData Manager
Changing how GeoData Manager looks
Scenarios for using GeoData Manager
Installing GeoData Manager for the first time
Installing GeoData Manager for the first time has two phases:
Download GeoData Manager from the GSDS website and install it on one computer, for evaluation. This is fully-featured, and free to use for the evaluation period. See here.
Purchase or lease the program, then set it up for regular use: register, install GeoData Manager on other network computers if required, install any dongle required and set up the preferences. See here.
Or:
GeoData Manager has several parts:
The GeoData Manager program itself and various data files that GeoData Manager creates.
Runtime libraries used by GeoData Manager. These must be installed before you install GeoData Manager.
The Python programming language that is used by GeoData Manager. This must be installed before you install GeoData Manager.
One or more databases of geothermal data for GeoData Manager. When you first install GeoData Manager it installs a sample database, with real geothermal data, for you to experiment with. As you use GeoData Manager you will create other databases to store your data.
GeoData Manager has modest system requirements, and will run on any Windows computer running Windows XP or later.
GeoData Manager is designed for large, long-term users, who will install GeoData Manager's database on a network and access it from several networked computers. Though for a small user it all be installed on one computer.
GeoData Manager can be installed in several configurations:
All on one computer:
GeoData Manager on user computers, main databases on network server:
GeoData Manager and main databases on network server:
There is one copy of GeoData Manager installed and each user computer runs this using Remote Desktop Connection. This configuration simplifies upgrading GeoData Manager, because you only have one copy to upgrade, however testing has shown that it can run significantly slower than configuration 2.
And you can have a combination of configurations 2 and 3, with GeoData Manager installed on the server (run via Remote Desktop Connection) and on one or more user computers.
You can not work with two copies of a GeoData Manager database and later merge them. If you have users at distant sites, then use configuration 4:
At the site with the server network run the GeoData Manager on each computer, for speed.
Away from site with the server network run GeoData Manager via Remote Desktop Connection through the internet or other connection.
Configuration 4 suits a laptop:
At the server network run the GeoData Manager on the laptop, for speed.
Away from the server network run GeoData Manager via Remote Desktop Connection through the internet or other connection.
Preferences:
When you run the GeoData Manager installed on a user computer, it stores the preferences on that user computer.
When you use Remote Desktop Connection to run the GeoData Manager installed on the server, it stores the preferences on the server.
These preferences will probably be different unless you make them the same, see below.
Preferences determine the 'look and feel' of GeoData Manager. A user's preferences are private to that user. You can share preferences with other users.
For configurations 2, 3 and 4: The main and test databases should be on the server. A database on a local computer would normally be for that computer only, for example a user's private demo or test database.
This describes setting up GeoData Manager and a sample database on one computer, for example for evaluation.
Here, n.n.n.n or n_n_n_n is the program version number read more.
Go to the GSDS website GeoData Manager download page.
Install the GSDS runtime libraries: From the website, download and run the runtime libraries (GSDS_Runtimes_n_n.exe).
Install the Python programming language: From the website, download and run the Python programming language (python-n.n.n.msi). Note: if you already have this or a more recent version of Python already installed on your computer then you don't need to install this.
Install GeoData Manager: From the website, download and run the latest version of GeoData Manager (gsds_gdman_n_n_n_n.msi). You must install the GSDS runtime libraries and the Python programming language before GeoData Manager.
Installing GeoData Manager creates a desktop shortcut. Start GeoData Manager. It displays the Database Manager window, with the default sample database:
Open the sample database: double-click sample database or click sample database and click Select DB.
GeoData Manager opens. To find how to use GeoData Manager, go to the first tutorial.
If you will use any SQL server databases, set up users and permissions for GeoData Manager.
Set up your preferences see here.
Consider installing an external 2-D contouring application. We suggest Surfer; GeoData Manager outputs many kinds of Surfer-compatible files.
To get a quote for buying or leasing GeoData Manager.
After you buy or lease GeoData Manager, you will receive a registration name and key code and perhaps one or more dongles. Then:
Decide on a configuration, install GeoData Manager and set up any network connections as required.
If you have received a dongle, install it:
Register your copy or copies of GeoData Manager: When you buy or lease GeoData Manager, you will receive a registration name and key code:
Click Help, then click About GeoData Manager ..., then click Registration.
Type or paste your registration name into Name
Type or paste your registration key code into Key.
Click Register, then click OK.
Make a couple of backup copies of the sample database supplied with GeoData Manager. The sample database is an Access database.
Put aside one of those copies of the sample database to be an Access test database when you upgrade GeoData Manager to a new version. Store it on the server if you have a network.
If you have any SQL Server databases, set up user names and permissions for GeoData Manager's users.
Create new, empty database for each geothermal site you have. See here and see here.
If you want GeoData Manager to have the same 'look and feel' for every user follow this procedure. Or you can do this any time later. If you don't do this now, run GeoData Manager for each user in turn and at the startup Database Manager window, add the databases to the list that the user will be using. Include the sample database so users can get familiar with GeoData Manager without worrying about damaging the database.
Institute and follow a procedure to back up your databases regularly. For example, an incremental backup every day and a full backup every week.
KEYLOK install program (install.exe)Do not plug the dongle into your computer until you are told to.
Run the KEYLOK installation program, install.exe. You should see:
Select KEYLOK 2 (USB w/Driver) and Standalone. Click Begin Install. You should see:
If you do not see this, it is likely that drivers have already been installed. In this case, go to the Windows control panel and uninstall the drivers; then start this again.
The Device Drive Installation Wizard is displayed:
Click Next. The device drivers are installed and you might see this:
Then:
Click Finish. You should see:
Do not click Close yet. Plug the dongle into a USB port on your computer. Still do not click Close. Wait for a few seconds as the device drivers are installed; you may see this notification:
Once the drivers have been installed, now click Close, and you are ready to go.
Go to the GSDS website, to the GeoData Manager download page.
Download the three dongle files:
Do not plug the dongle into your computer until you are told to.
Select a network computer to be the dongle server. This computer must be accessible to all clients computers that will run GeoData Manager. Usually the dongle server is the computer that holds GeoData Manager's databases.
Run the KEYLOK installation program, install.exe on the dongle server computer. You should see:
Select KEYLOK 2 (USB with driver) and Server. Click Begin Install; you should see:
If you do not see this, it is likely that drivers have already been installed. In this case, go to the Windows control panel and uninstall the drivers; then start this again.
Then the Device Driver Installation Wizard is displayed:
Click Next. The device drivers are installed and you might see this.
Then the Wizard is displayed again.When this screen closes, click Finish in the Wizard screen to complete the installation.
Click Finish. You should see:
Do not click Close yet. Plug the dongle to a USB port on your dongle server computer. Still do not click Close. Wait for a few seconds as the device drivers are installed; you may see this notification:
Once the drivers have been installed, now click Close.
On each of the other network computers (dongle clients):
Run install.exe on the client computer. You should see:
Select KEYLOK 2 (USB w/Driver) and Client. Click Begin Install; you should see:
Click Close to complete the installation on that computer.
Be sure you can ping from the client to the server
For example, from a Command Prompt:
ping _servername_ or ping _IP Address_ If pinging fails, all communications may be disabled between the client and server. Ensure there is a Trusted Zone defined in the firewall settings for the connection between the KEYLOK client and the server.
Configure security settings
For TCP/IP networking there needs to be a clear TCP/IP connection between the client and the server. The port used for communication is 4242 and must be open. Firewalls and security software must be set to allow klserver.exe and the protected application to communicate.
Is the TCP/IP dongle server klserver.exe installed and running?
Check to make sure that klserver.exe is installed in \Windows\System32 (32-bit OS) or \Windows\SysWow64 (64-bit OS) and that it is running as an automatic service.
You can check to make sure that klserver is running by going to a command prompt, typing net start klserver and pressing Return. The system should respond that the klserver service has already been started. If you get a response that the klserver service has been started successfully, go to Control Panel > Administrative Tools > Services and make sure that klserver is listed and that it is set to automatic to make sure that it starts each time the machine is booted.
Subnet
Please note that it is strongly recommended on a TCP/IP network that the 'subnet mask' be set the same for both the server and clients. Network 'properties' can be used to acquire the subnet mask.
Run VerifyNetworkKey
VerifyNetworkKey checks that an application can communicate with the dongle.
If the dongle is not found, you may have an out-of-date KEYLOK install program (install.exe). Download the latest install program and check that you have installed the latest version, If not:
If the dongle is found on the server, run VerifyNetworkKey on a client machine. If the dongle is not found from the client machine, then your KEYLOK interface file might be out of date. The interface file (KL2DLL32.DLL or NWKL2_32.DLL) used to interface with the KEYLOK API is not in sync with the driver. In this case, please contact us: software@gsds.co.nz.
This uninstalls GeoData Manager permanently. Note that if you are upgrading to a new version of GeoData Manager, you do not need to uninstall anything first.
If you want to keep your databases, backup your databases.
Otherwise delete each database in turn.
Open the Windows Control Panel, select Add or Remove Programs.
Select GeoData Manager and click Remove.
If Python is not used by other applications, select Python and click Remove.