Problem

If GlobalSearch or GlobalCapture were originally installed to a local SQL server and then moved to a remote SQL server, the installer may try to apply updates to the default SQL instance: "(local)\GETSMART". This can be problematic if you have migrated your SQL databases to a remote SQL instance and no longer use the default instance.

Solution

Run the setup.exe from an administrative command prompt, using the parameter /v"IS_SQLSERVER_DO_NOT_USE_REG=1 IS_SQLSERVER_SERVER=<sqlserver> IS_SQLSERVER_AUTHENTICATION=0 ". Replace <sqlserver> with the name of your SQL server.

As with any upgrade, you must be running this as a user with full access to the SQL server, local administrator rights to the GlobalSearch Server, and domain admin rights (if the server is on a domain).

The example below shows how to do this with the GlobalSearch 4.5.2.101 installer and a remote SQL instance called "S9SQL\GetSmart". Please note that you must run the command prompt as an administrator (right-click and select "Run as administrator").

cmd

cd C:\GSMedia\4.5.2.101\AIO
setup.exe /v"IS_SQLSERVER_DO_NOT_USE_REG=1 IS_SQLSERVER_SERVER=S9SQL\GetSmart IS_SQLSERVER_AUTHENTICATION=0 "

Then, simply follow the on-screen instructions as normal to complete the upgrade.

Related articles

Page:

How To Identify And Defragment Fragmented SQL Indexes
Page:

Troubleshooting GlobalSearch Extensions
Page:

How To Perform a GlobalSearch and GlobalCapture Server Migration
Page:

Determine Software Version
Page:

How To Add & Configure COM Permissions

Browser not supported