Versions Compared

Old Version 4

changes.mady.by.user Andres Chaves

Saved on

compared with

New Version 5

changes.mady.by.user Square 9 Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
bgColor#fff
  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 into GlobalSearch or GlobalCapture

...

Panel
  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 of 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)

...