Problem

I'm logging into GlobalSearch, but I can't see archives, searches, documents, etc

-OR-

I'm logging into GlobalCapture, but I can't see any of the modules

Solution

The installer will sometimes create a local SSAdmin group and a local SSAdministrator, even when configured for Active Directory authentication. Having a local SSAdmin group and local SSAdministrator causes conflicting logins, which results in the above problems. To fix this, do the following

  1. Confirm that your GlobalSearch and/or GlobalCapture instance(s) are configured for Domain Authentication. If you are unsure, consult with your system administrator, Square 9 server administrator, or Square 9-certified reseller.
  2. Use the "Run" application in the start menu, or press "Windows + R"
  3. Run "compmgmt.msc"
  4. Unfold the "Local Users and Groups" tab
  5. Open the "Groups" folder and remove SSAdmin, if it exists
  6. Open the "Users" folder and remove SSAdministrator, if it exists
  7. Close your web browser and try to log back in to GlobalSearch or GlobalCapture

Please Be Advised

If your Square 9 instance is using local or workgroup authentication, do not perform the above steps. Deleting the local SSAdmin group or local SSAdministrator when using local authentication will result in an unusable system and will need repair.

Problem

GlobalSearch moves very slowly after an upgrade

Solution

When upgrading GlobalSearch, the installer will automatically update the SQL databases. If the scripts did not or could not run during the upgrade, it can cause slowness. Running these scripts manually after the upgrade can alleviate the performance issues.

  1. Open SQL Server Management Studio (SSMS)
  2. Back up your GlobalSearch production databases (default is "GetSmart") as well as your SSMaster database
  3. In your server's application directory (default "C:\GetSmart"), locate the file "SSMasterUpgrader.sql" and open it in SSMS.
  4. Execute the SSMasterUpgrader script.
  5. Once that completes, open the "UpgradeScript.sql" file also found in the same folder
    1. At the top of the query, after "USE", change the placeholder database name to the name your production database (IE - the database you see in SSMS). This may be referenced in multiple places, depending on the version of GlobalSearch. For this reason, it is recommended that a text replacement is performed on the entire script to swap out the name (CTRL + H).
    2. Execute the script
      1. In some versions, you may see an error regarding the "ssDocusignTracking" table. This is expected. If you see any other errors, please reach out to Square 9 Support for assistance.
      2. This script can take some time to process and can cause a significant drop in performance in GlobalSearch while running. For this reason, it is recommended that the script is run outside of regular production hours.
  6. Repeat step 5 for each of your production databases, if you have more than one.
    1. The UpgradeScript.sql script should not be run on any of the other SQL databases (e.g. - ssProcessing, Square9Users, ssMaster or ssCapture)


Problem

I'm seeing an authentication server error when trying to log into GlobalSearch after an upgrade

Solution

There are many causes for authentication server errors after an upgrade. Most commonly, however, it has to do with the "AuthServer" setting being improperly set in a couple places.

If you are using local/workgroup authentication, your authserver is the name of your app server.

If you are using Active Directory authentication, your authserver is the name of your domain.

Please ensure the "AuthServer" (or "AuthenticationServer" in some places) is set properly in these locations:

  • YOURDRIVE:\inetpub\wwwroot\Square9API\web.config
  • YOURDRIVE:\inetpub\wwwroot\Square9REST\web.config
  • YOURDRIVE:\Getsmart\ssinterface.exe.config