Seequent Start is an application that checks to see if your network will support the connection of Seequent web based services to your desktop applications.
Confidence to start
Seequent Start is with you all the way through this process. As you run ‘Start’ it instantly reports back on your connectivity to integrated Seequentweb based applications, if license information can be requested and received and what action you may need to take to remedy any issues – from either an IT or operational perspective.
- Check connectivity endpoints between Seequent services and your network
- Seequent Start runs within a minute and reports back on the progress
- Pinpoints any action you may need to take and directs you to appropriate help
Check access to Seequent web services
Seequent Start is designed to ensure you have a seamless experience with Seequent Software and it’s associated web services such as licensing, reporting and API connections.
- Tests access to Seequent web services from within your current web environment
- Creates a report of any issues for review by your Network Administrator or your local Seequent team
Webpages
- Redirect
- Online help
Licensing
- Fixed dongle
- Activation Code
- On Demand
- Seequent ID
Reporting
- Licenced items
- Reference codes
- Email report
- System report
- Time
Products
- Access to Central
Download Seequent Start
DownloadUnderstanding your Leapfrog web services test report
Access to Seequent web services can be tested using Seequent Start or from within your Leapfrog application. When you test whether Seequent web services are available, a report is generated that you can save for your own review. The report is also sent to Seequent, but your personal details will not be included if all tests pass. If a test fails, a Seequent support case will automatically be created, and someone from Seequent support will contact you to help you resolve the issue.
This guide provides information that will help you and your Network Administrator to interpret your web services test report. The Error Scenarios section of this guide includes information for Network Administrators that may help resolve any issues found. The Endpoint Impacts section describes the effects of any failure to connect to a particular endpoint.
This is applicable to reports generated from
- Start v2.0
- Leapfrog Works v3.0
- Leapfrog Geo v5.0
- Leapfrog Geothermal v4.0
If you need any further assistance interpreting Seequent Start test reports, contact support.
Error Scenarios
The error scenarios described include a generalised example of the errors displayed, along with suggestions for mitigating the issue.
Authenticated Proxy Problems
Cause: The active network configuration requires connections to the named endpoints to go through an authenticated proxy and the credentials are wrong.
Error Displayed
Endpoints
Actions to take: Check the credentials used in Leapfrog under the main menu (Settings > Network). If this does not fix the problem, consider whitelisting the failing hosts
Timeouts
Cause: Slow/intermittent internet connections can cause timeouts.
Error Displayed
Endpoints
Actions to take: Unfortunately causes of timeouts are varied and often tricky to diagnose.
- The cause can be temporary so the first action to try is to wait a while and try again.
- The problem can sometimes be caused by network connections not being closed properly (e.g. when switching between VPN and no VPN when a laptop is transitioned from home to work or vice-versa). The best thing to try here is restarting the machine and trying again.
- The proxy autodetection may not be working – try manually setting the proxy server (if there is one) or turn proxy support off (if there is no proxy server) under Settings> Network
- The proxy address may not be correct – check the proxy settings under Settings> Network
Poor Connections
Error Displayed
Endpoints
Actions to take
- Failures due to poor connections occur intermittently. By their very nature, the best cause of action is often to wait a while and try again.
- The problem can sometimes be caused by network connections not being closed properly (e.g. when switching between VPN and no VPN when a laptop is transitioned from home to work or vice-versa). The best thing to try here is restarting the machine and trying again.
Back End Failure
Error Displayed
Endpoints
Actions to take: Contact support, providing the test report, to further investigate the backend issue
HTTPS Certification Verification Problems
Cause: The HTTPS traffic is being inspected by web security software and the certificate used to resign the packets is not being recognised.
Error Displayed
Endpoints
Actions to take: Connections from Start and the Seequent Application to the HOSTNAME should be whitelisted to allow direct connections so the packets are not scanned and re-signed with the unknown certificate.
Contact Support, providing the Start testing report, to get help with adding the certificate used by the web security software to re-sign the packets to the certificate store used by the Seequent Applications.
Endpoint impacts
When Seequent products report an error in trying to connect to an endpoint, some failures are more critical than others. This section describes the severity of impact of not being able to successfully connect to an endpoint.