If you are updating your JumpAgent GUI without prompting from Healthjump, please notify us by sending an email to firstname.lastname@example.org. If we are aware of an update, we can check that there is still a clear connection and that all the queries run successfully, to avoid any unexpected issues. Thank you, The Healthjump Team.
Updating the JumpAgent GUI & Common Errors:
- Locate the JumpAgent GUI (most likely on the desktop).
- If you do not know the location of where it was installed, you can search for JumpAgent in your desktop applications search bar.
- Open the JumpAgent GUI.
- Edit any outdated information in JumpAgent GUI. Make sure passwords are up-to-date.
- Click “Test Connection”. A pop-up window should appear saying “Successfully Saved”. Click “Ok”.
- After a few seconds, another pop-up window should appear saying “Connection successfully established”.
- If “Connection Successfully established” has appeared then please go to Service.msc. If “Connection Failed” has appeared then please go to ‘Common Errors and How to Fix Them’.
- Go to JumpAgent and Right Click.
- Restart JumpAgent.
- Go back to the JumpAgent GUI and click “Test Connection” again.
- If “Connection successfully established” appears again then please connect with your Healthjump Representative saying the connection was made. We can double check on our end that everything is working properly.
Common Errors and How to Fix Them:
- Connection Failed:
- Ensure that all the database information is correct. Then click Test Connection again.
- If the connection fails again, open the error log by following these steps.
- Go to C:/Program Files (x86)/Healthjump/JumpAgent and open the file ErrorLog.txt
- Once ErrorLog.txt is opened you can scroll to the bottom for the most recent error messages. Example errors below:
- “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.” This most likely means that either the database IP address or the port number was entered incorrectly in the JumpAgent GUI.
- “Login failed for user”. This means the database username and/or password were entered incorrectly in the JumpAgent GUI.
- Once you have resolved the configuration issues in the JumpAgent GUI you can click Test Connection and you should see the “Connection successfully established” pop-up.
- Restarting the JumpAgent service:
- Go to services.msc → JumpAgent - Right Click, select Start or Restart
- Retest connection.
- If using Windows Authentication instead of SQL credentials to access database:
- Go to Services.msc → JumpAgent - Right click, select Properties.
- Go to Log On
- Fill in the Windows Authentication credentials you entered in the JumpAgent GUI.
- Apply → Okay.
- Retest connection.
If none of these solutions help:
Please contact your Healthjump representative or email us at email@example.com. They can provide you with a link to schedule a call with us so we can further assist you.