These buttons use cookies: Learn More


Can't find your answer below?
Submit a ticket and we'll get back to you as quickly as we can.
Submit a ticket
“The connection was closed unexpectedly.”

If the API does not run correctly, and the log file (GoorooRESTClientlog.txt) contains an error like this:

ERROR – Error calling API. Please see log file for full details. – System.AggregateException: One or more errors occurred. —> System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.

then a timeout at your end might be closing the connection to our server.

You can test this by running the Planner API with small files, which you can do like this:

  • find out where to download the API Client here
  • edit Goorooconfig.xml to insert your Planner API licence’s username and password
  • run the GoorooRESTClient.exe application.

That will run the Planner API using the small test files that come bundled with the API Client. If you get the response “OK” in your log file with these small files, but are getting an error with your own large files, then that suggests that a timeout at your end is causing the problem.

In that case, you will need to contact your IT department and tell them the following:

Gooroo Client API makes a https call to:

Depending on the amount of data being uploaded it can take a several minutes for the server to parse and convert to a report. What appears to be happening is your connection to the server is being killed after a certain period of time. Have the IT department reduced the amount of time that a http (or https) connection can remain open? We’ve tested calling the API using very small datasets from your machine which works fine so we know that a connection is definitely being made successfully.