Seequent 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

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

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 v3.0
• Leapfrog Works 2021.1.2
• Leapfrog Geo 2021.1.2
• Leapfrog Geothermal 2021.1.2

If you need any further assistance interpreting Seequent Start test reports, contact support.

The error scenarios described include a generalised example of the errors displayed, along with suggestions for mitigating the issue.

Cause: Slow/intermittent internet connections can cause timeouts.

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

Actions to take: Contact support, providing the test report, to further investigate the backend issue

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.