to get a personalized navigation.
to get a personalized navigation.
There has been an increase in errors from VN.net the last days
The errors differs, but here are som examples:
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_0551a52e-1086-4c00-8164-5f355e2a870b","ExceptionDetails":""}
{"message":"VismaId: 9c80050b-9c11-49d6-b487-16d89c7d7ec0. A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"}
{"message":"An error has occurred.","exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'."...
{"ExceptionType":"java.net.SocketException","ExceptionMessage":"Error occured while connecting to the service when trying to get response code (IOException)","ExceptionFaultCode":"5521","ExceptionMessageID":"5521_53a13aa9-a8b1-4291-ac6f-b0784f1afc97","ExceptionDetails":""}
{"message":"VismaId: 4f62f048-52f3-4509-a5a7-720b935adb41. Object reference not set to an instance of an object."}
and
502 Bad gateway
Every month our customer sends an API call to General Ledger of approximately 13,500 lines. Previously this took approximately 45 minutes. Since last week they have received 500 reports. We have already divided the post into parts of 500 lines. Sometimes things go well now, but it takes upto 20 minutes per call, or we get error 500.
There has been a lot of 5520 and 502 Bad Gateway since 09:00 today ...
Looks like it resolved at around 11:45. No updates at the status-page?
We are also seeing these errors, getting more and more of them today, like
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_2fe64907-c623-4721-9919-e00a6b3e1a81","ExceptionDetails":""}
Hi Andreas,
Are you still experiencing these issues?
BR,
Suzdar
There is a lot of
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_50b445de-c6e3-4f53-9833-63647ebd8ab0","ExceptionDetails":""}
right now. This is not optimal during black week ...
Hi,
We are still seeing these errors, one of them from this morning:
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_1c2cd972-4c1c-401b-9ae5-88020e219396","ExceptionDetails":""}
Are you looking into this or do you know what the problem is?
Its been better today, but there were errors day all yesterday
It is most likely a hiccup. Let me know if it happens again 🙂
There is a lot of errors again today
{"message":"VismaId: b3f1c965-b643-4061-931e-bb7ea47ede38. A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_b850bbee-a8b8-421e-afc1-3e2711b4a652","ExceptionDetails":""}
Looks like it got fixed at about 11:45, thats almost 24 hours after it was reported here
Copyright © 2022 Visma.com. All rights reserved.