Problem
I'm logging into GlobalSearch, but I can't see archives, searches, documents, etc
...
I'm logging into GlobalCapture, but I can't see any of the modules
Solution
Chances are, if this is happening you're running Domain Authentication and the upgrader has built The installer will sometimes create a local SSAdmin group and a local SSAdministrator. This , even when configured for Active Directory authentication. Having a local SSAdmin group and local SSAdministrator causes conflicting logins, which results in the above problemproblems. To fix this, do the following
| Panel |
|---|
|
- Confirm that you're using Domain Authentication with your SysAdmin, Your GS Server Admin or Reseller if you're not sureyour 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.
- Use the "Run" application in the start menuOpen , or press "Windows + R"
- Run "compmgmt.msc"
- Unfold the "Local Users and Groups" tab
- Open the "Groups" folder and remove SSAdmin, if it exists
- Open the "Users" folder and remove SSAdministrator, if it exists
- Try logging back in and seeing if the issue is remedied
|
info- Close your web browser and try to log back in to GlobalSearch or GlobalCapture
|
| Warning |
|---|
|
If you're your Square 9 instance is using local /or workgroup authentication, do not perform the above steps. It WILL break your install and will likely result in the need to repair the systemDeleting 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
There's a chance that the upgrade scripts couldn't run on the database during the upgrade. Running these after the upgrade is a good way to alleviate some common 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.
| Panel |
|---|
- Open SQL Server Management Studio Take backups of your production databases (SSMS)
- Back up your GlobalSearch production databases (default is "GetSmart") as well as your SSMaster database
- Open your getsmart directory on your server and load the SSMasterUpgrader.sql script into a new query window in SSMS and run itIn your server's application directory (default "C:\GetSmart"), locate the file "SSMasterUpgrader.sql" and open it in SSMS.
- Execute the SSMasterUpgrader script.
- Once that completes, open the "UpgradeScript.sql file into a new query window" file also found in the same folder
- 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)Run the scriptIt is possible you'll see an error message related to docusign tracking - disregard this.If you see . 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).
- Execute the script
- 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.
- This script can take a moment to run. To cut back on deadlocks, it's best to run this outside of normal production hours or during off-peak 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.
- Repeat step 3 5 for each of your production databases, if you have more than one.
- This The UpgradeScript.sql script should NOT not be run on any of the other system SQL databases (IE e.g. - ssProcessing, Square9Users, ssMaster or ssCapture)
|
...
There are many causes for authentication server errors after an upgrade. Most commonly, however, it has to do with the Auth Server being set improperly "AuthServer" setting being improperly set in a couple places.
If you are using local/workgroup authentication, your Authentication Server should be authserver is the name of your app server.
If you are using Active Directory domain authentication authentication, your Authentication Server should be authserver is the name of your domain.
Please ensure the "AuthServer" (or "AuthenticationServer" in some places) is set properly to either the domain or server name (depending on your setup) in these locations:
- YOURDRIVE:\inetpub\wwwroot\Square9API\web.config
- YOURDRIVE:\inetpub\wwwroot\Square9REST\web.config
- YOURDRIVE:\Getsmart\ssinterface.exe.config
...