Where to look when GlobalForms doesn't start or behave as expected, and what to collect before contacting Square 9 Support.
Log files
All logs are in the logs folder of the install folder (C:\GlobalForms\logs by default).
|
File |
Contains |
|---|---|
|
|
Errors from the GlobalForms service, such as startup failures, configuration errors and connection problems. Check this first. |
|
|
Each web request, when request logging is turned on. See Request Logging. |
|
|
Each automatic update: date and versions |
|
|
Present only if an update was rolled back automatically |
Check the service
-
Open Services and find GlobalForms Forms Server. Its status should be Running.
-
Or, in PowerShell:
sc.exe query GlobalForms -
To restart it:
Restart-Service GlobalForms
Common problems
|
Symptom |
Likely cause |
See |
|---|---|---|
|
The service stops right after starting |
Invalid JSON in |
|
|
The page doesn't load, but the service is running |
Firewall blocking the port, or a wrong address |
|
|
HTTP works but HTTPS doesn't |
Certificate or key can't be loaded, or the port is in use |
|
|
A setting change has no effect, or disappeared after an update |
Edited |
|
|
Users can't sign in |
Wrong sign-in name format, sync not run, or single sign-on setup |
|
|
A form can't load outside data or shows a blank embedded frame |
Security headers blocking the site |
|
|
Lookups return no data |
Route or database settings, or quotes around |
|
|
Emails aren't sent |
SMTP settings or mail server rules |
|
|
The server didn't update |
Updates turned off, no network access, or install-on-restart mode |
|
|
Images or styles stopped working after an update |
Files had been added to the program folders, which updates replace |
In the browser
For problems in a form, open the browser's developer tools (F12). The Console tab shows script errors and blocked requests. The Network tab shows failed requests and their status codes.
Contacting Square 9 Support
Collect the following before opening a case at square-9.com/support:
-
Your GlobalForms version (in
install-info.json, or the most recent entry inlogs\update-history.json) -
The contents of the
logsfolder -
A copy of
config\local.jsonwith passwords and secrets removed -
The steps to reproduce the problem, and any error shown in the browser