GlobalSearch is a complex program, tying multiple external systems together and relying heavily on Microsoft infrastructure. We run two distinct database systems, integrate with Active Directory, and a host of 3rd party software and hardware.

We’ve compiled an article with This guide contains fixes for common installation issues. Please feel free to consult the Installation Guide for the proper process and prerequisites for your install.

...

SQL Server Install Failure

Problem

In the event that the SQL Server Installation fails out on GS Installation, it may have failed out due to permissions set on the database for the database to build its own permissions set. In the event that it can’t do that, When installing GlobalSearch 4.5.2 or older, or installing GlobalCapture 2.1.2 or older, the MS SQL Server installer may fail and you may receive an error like thisthe one shown below. This may also be due to the can also occur when SQL Server and Active Directory existing exist on the same machine. It is not suggested that SQL and Active Directory exist in the same space, but in the event that this cannot be avoided, follow the steps below.

Fix

During the install, at the Server Configuration, change the Account Name for the Database Engine to NETWORK SERVICE. If NETWORK SERVICE does not work, use NT AUTHORITY\SYSTEM. This will use a preset user to build the database properly.

...

No problem. We have a set of CMD scripts that you can run piece by piece or as a .bat file to write all your services. Please see this Knowledge Base article HERE

Creation of a Link Item Database Fails During Installation

Problem

On installation you are prompted with this error before the installer fails out

Solution

This is likely a missing file from the SQL Server that can be installed via a SQL Server feature pack. Normally this is packaged with the install, but you can download and run the feature packs from Microsoft's website to have the component reinstalled.

Related articles