How to manually install GeoTrends in Webtrends Analytics 8.1x without performing a modified installation


Webtrends Analytics 8.1x


This article outlines how to manually install the GeoTrends module without performing a modified installation.


In order to perform the installation the .msi file must be extracted from the Webtrends installer and manually installed. First, download the Webtrends 8.1x installer from the following URL:


The GeoTrends data file must also be downloaded. The installer and data file are fairly large, so for customers with slow internet connections it is recommended they be downloaded in advance of the scheduled time of installation.

After completing the download, double-click the wt-webtrends.exe file and the embedded WinZip self-extractor pop-up displays. Unzip to the default location or a custom path, navigate to that path (while leaving the installer window open), and copy the “Webtrends GeoTrends.msi” file from the \msi folder to another location. Next, cancel the installer, after which the extracted installation files will be deleted (but the “Webtrends GeoTrends.msi” file will be retained because it has been copied elsewhere).

Following that, modifications may need to be made to the system database so the module is recognized within the installation. The modifications require a database editor for the appropriate database, be it MySQL or MS SQL.

After making the initial preparations, follow the steps below to manually install the GeoTrends module:
1. Stop all Webtrends services except the Webtrends – MySQL service (unless using MS SQL, in which case leave the SQL Server service running).

2. Delete the following folder (if present):


3. Run the GeoTrends msi installer with logging enabled from the command line. Ensure the paths to the installer msi and the Webtrends root directory are correct.

In the path below, change MasterUser and SchedUser to be the MySQL account username and change MasterPass and SchedPass to the password for the account.

For installations using MySQL, run the following command from the command line, replacing the contents of all < > strings with the system-specific information:

msiexec /i “\Webtrends GeoTrends.msi” /qb /l*v “\logs\install\GeoTrends Server.log” installdir=”” master_user= sched_user= master_pass= sched_pass= master_host=localhost sched_host=localhost db_type=MySQL geotrends_dat=”” addlocal=all ignore_systemcheck=true master_port=3306 sched_port=3306

For installations using MS SQL, run the above command, but replace “db_type=MySQL” with “db_type=SQLServer” and delete “master_port=3306 sched_port=3306” at the end.

4. Restart all Webtrends services.

Note: When installing on a system that does not have the system database on it, specify the system that contains the wt_sched and wtmaster database in the “MASTER_HOST=LOCALHOST” and “SCHED_HOST=LOCALHOST” strings, where “LOCALHOST” is the IP address or host name of the machine on which the system database is installed.

If the command is run while the MySQL service is running it should take care of the necessary database entries to activate the option to enable GeoTrends. Verify by editing a profile and under Analysis > Internet Resolution, the option to enable GeoTrends will be selectable. If not, follow the steps below:

5. Stop all Webtrends services except the Webtrends – MySQL service (unless using MS SQL, in which case leave the SQL Server service running).

6. Edit the database and verify/modify the following tables:

In wt_sched.wt_servicerole, verify that GeoTrends has a token id of 1004.

In wt_sched.wt_hostservicerole, add the entry for GeoTrends, with the hostid listed for the machine GeoTrends is installed on and with token id of 1004 (verify the hosts in wt_sched.wt_host).

In wtmaster.wt_module, make note of the module id listed for GeoTrends.

In wtmaster.wt_servermodule, add the entry for GeoTrends, using the next sequential number for ServerModuleID, the proper value for ServerID, the module id you found in wt_module, and type the version running (which should be the same as all others in the list).

7. Close the database editor and restart all services.