GET on journaltransactions stops with empty data

[schimmel-hsleiden]

Hello everybody,

Every day we import data from Visma. We have a connection with the API through Azure API management. Since yesterday the import randomly stops with an error:

Error: System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host 

OR

System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host.

We restarted the import several times but keep getting an error at a random call. The calls are:

https://integration.visma.net/API/controller/api/v2/journaltransaction?periodId=202210&pageSize=1000...

We have not changed anything on our side. It stops when a reply size is '0' bytes.

Has anything changed on de Visma side? Is there some problems with the API?

Kind regards,

Frank Schimmel

Errors at times it occuredCall that fails without dataCall that fails without dataCall that fails without dataCall that fails without data

[Magnus Johnsen]

Hi,

This issue should be resolved now, it was caused by an incorrect configuration in the load balancer.

Please let us know if it occurs again.

Thank you. 

[schimmel-hsleiden]

Problem is still occurring.  The connection is not only lost with the journal transactions, but it happens randomly when many pages are retrieved. For example, it also happend with retrieving costumerinvoice that got a 0 byte response and stopped the connection.

Anyone of Visma looking into this problem?

Kind regards,

Frank

[Magnus Johnsen]

Hi,

We are looking into this.

Do you have a retry mechanism in place to resume the retrieval?

How often would you say this happens?

[schimmel-hsleiden]

Hi Magnus,

Since last Friday we did not have any trouble getting the data. Has anything changed on your side?

Kind regards,

Frank

[Magnus Johnsen · Accepted solution]

Hi,

As per my last reply:

"This issue should be resolved now, it was caused by an incorrect configuration in the load balancer.

Please let us know if it occurs again.

Thank you. "

[schimmel-hsleiden]

Hi Magnus,

We do not have a retry mechanism because it used to work fine. It happens randomly around once in '800' calls. We do about 2000 calls to retrieve all the records.

Thanks,

Frank

[Magnus Johnsen]

Hi,

Alright, we are currently investigating this on our end and will update you as soon as we know more. 

[KonsultVn]

Hi,

We are also having trouble extracting journaltransactions from visma.net API on several customers and we are getting the same error message "An existing connection was forcibly closed by the remote host". We haven't changed anything on our side. Have there been an update to the API that can affect the extract of journaltransactions?