Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
andreasaulin
97
Posts
13
Kudos
3
Solutions
10-12-2024
11:54
Looks like it resolved at around 11:45. No updates at the status-page?
... View more
10-12-2024
10:24
There has been a lot of 5520 and 502 Bad Gateway since 09:00 today ...
... View more
26-11-2024
12:53
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 ...
... View more
06-11-2024
11:52
Looks like it got fixed at about 11:45, thats almost 24 hours after it was reported here
... View more
05-11-2024
12:38
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":""}
... View more
25-10-2024
11:02
Its been better today, but there were errors day all yesterday
... View more
24-10-2024
08:12
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
... View more
12-09-2024
07:48
We got the response back that our ip was blocked because of suspected DDOS. As with you, the same integration had been running for months and no significant change in volume. You should contact Visma and ask them to check if your IP is blocked as well. There must be a new firewall rule that is a bit agressive.
... View more
07-09-2024
21:00
At about 03:30 07.09 we started to get 403 forbidden back from the enpoint, making none of our intergrations working at the moment. Trying with the same credentials from a local machine works as it should, so it looks like our server is banned in a way? We have a few integrations that has not been migrated to the tennant flow, these still work
... View more
07-02-2024
14:56
Yes, the errors have been received through the day. 14:32, 13:38, 11:53 and so on
... View more
07-02-2024
14:33
There has been quite a lot of these errors today {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_19bb63bc-7e0b-4cb0-b4c4-f3bae3f021b5","ExceptionDetails":""} Something related to the maintenance that was last night? Example på calls/endpoints which have given the error: /controller/api/v1/shipment/?lastModifiedDateTime=2024-02-07 14:25:43&lastModifiedDateTimeCondition=%3E&pageNumber=1 /controller/api/v1/Inventory?availabilityLastModifiedDateTimeCondition=%3E&availabilityLastModifiedDateTime=2024-02-07 14:25:44&pageNumber=1 /controller/api/v1/carrier/ /controller/api/v1/customerSalesPrice?priceType=CustomerPriceClass&PriceCode=WEB&lastModifiedDateTimeCondition=%3E&lastModifiedDateTime=2024-02-07 13:31:20&pageNumber=1
... View more
17-01-2024
09:45
502 again now ...
... View more
05-01-2024
11:36
The same again now: 502 Bad Gateway
... View more
04-01-2024
10:12
New day with 502 Have received since 09:42 502 Bad Gateway
... View more
19-12-2023
08:07
The same again today ... 502 Bad Gateway
... View more
18-12-2023
08:54
And there is a lot of 502 Bad Gateway
... View more
14-12-2023
14:44
Sounds like the same error as this one: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Error-Branch-1-cannot-be-found-in-the-system/m-p/334212#M676 Only workaround I've found is to enable tenant-auth. Get the error. Switch back to the old token for 24 (or so) hours and then back to tenant again ... Not ideal to say the least.
... View more
07-12-2023
08:02
1 Kudo
Any updates? This is still an issue
... View more
24-11-2023
07:41
1 Kudo
This still fails the same way as it did before the latest update.
... View more
17-11-2023
13:52
Any updates here? Moving clients to tenant auth, and then move it back again, wait about 24 hours and then back to tenant, seems to be the only workaround for now, and thats not very user friendly
... View more
08-11-2023
09:13
Tested today with tenant auth, and today it worked. Looks like a cache issue with the credentials?
... View more
07-11-2023
14:32
We might have encountered this again. Moving one client away from the old token authentication and starting to use the new authentication has generated this error. Posting with the old token works (ipp-company-id and so on), but with the new authentication fails for the same request. We have seen cache-errors today so it might be related to that ... for now, we have to use the old token, and then try to switch to the new auth tomorrow again to see if it starts to work
... View more
07-11-2023
13:56
More errors today: We do see quite a few different errors regarding things not working as it should in the API New for today is {"message":"Connection to cache service failed"} Different endpoints and clients "ExceptionFaultCode":"5520" Different endpoints and clients "exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'." Different enpoints and clients and in addition timeouts from time to time (we are waiting 30 seconds for a reply)
... View more
30-10-2023
08:16
New 5520 today: Completed: /controller/api/v1/shipment/?lastModifiedDateTime=2023-10-30 08:06:30&lastModifiedDateTimeCondition=%3E&pageNumber=2 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_9123b2ca-33b0-4a0a-ad28-74865a8cf878","ExceptionDetails":""} Completed: /controller/api/v1/Inventory?availabilityLastModifiedDateTimeCondition=%3E&availabilityLastModifiedDateTime=2023-10-30 08:06:30&pageNumber=2 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_8dc0df8a-bbd5-46d7-a30b-dfcf41035018","ExceptionDetails":""}
... View more
27-10-2023
08:44
Not related to slowness, but we still receive 5020-errors and in addition there was a burst of 504 just a couple of minutes before your post
... View more
25-10-2023
10:51
What about the Redis-errors? Havent seen those before the move to Azure {"message":"An error has occurred.","exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'.","exceptionType":"System.InvalidOperationException","stackTrace":null,"innerException":{"message":"An error has occurred.","exceptionMessage":"Timeout performing EVAL (5000ms), next: EVAL, inst: 25, qu: 0, qs: 14, aw: False, rs: ReadAsync, ws: Idle, in: 0, serverEndpoint: 10.10.6.4:15001, mc: 1/1/0, mgr: 10 of 10 available, clientName: erp09670100003H, PerfCounterHelperkeyHashSlot: 505, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=27,Free=32740,Min=8,Max=32767), v: 2.1.58.34321 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)","ex
... View more
25-10-2023
07:13
During the night there has been occurrences of both 5520 and "The 'CompressedContent' type failed to serialize the response body for..."-error. I've logged about 150 of these the last 12 hours. Examples: Completed: /controller/api/v1/PurchaseOrder?lastModifiedDateTimeCondition=%3E&lastModifiedDateTime=2023-10-25 03:48:04&orderStatus=Hold&pageNumber=1 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_21dd55cf-35b0-440e-b5cb-ce19c4664747","ExceptionDetails":""} Url: /controller/api/v1/carrier/ Content received: {"message":"An error has occurred.","exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'.","exceptionType":"System.InvalidOperationException","stackTrace":null,"innerException":{"message":"An error has occurred.","exceptionMessage":"Timeout performing EVAL (5000ms), next: SET CONFIGCACHE_4b9b5db0-d272-11eb-b60b-0638767d04b5_lock, inst: 10, qu: 0, qs: 6, aw: False, rs: ReadAsync, ws:...
... View more
Activity Feed for andreasaulin
- Posted Sv: Increase in errors the last days on Forum in Developers Visma.net. 10-12-2024 11:54
- Posted Sv: Increase in errors the last days on Forum in Developers Visma.net. 10-12-2024 10:24
- Posted Re: Increase in errors the last days on Forum in Developers Visma.net. 26-11-2024 12:53
- Posted Re: Increase in errors the last days on Forum in Developers Visma.net. 06-11-2024 11:52
- Posted Re: Increase in errors the last days on Forum in Developers Visma.net. 05-11-2024 12:38
- Posted Re: Increase in errors the last days on Forum in Developers Visma.net. 25-10-2024 11:02
- Posted Increase in errors the last days on Forum in Developers Visma.net. 24-10-2024 08:12
- Kudoed Sv: All integrations getting 403 / 401 response suddenly for zunnu. 16-09-2024 13:26
- Posted Sv: All integrations getting 403 / 401 response suddenly on Forum in Developers Visma.net. 12-09-2024 07:48
- Posted 403 Forbidden from /connect/token on Forum in Developers Visma.net. 07-09-2024 21:00
- Posted Svar: Error 5102 on Forum in Developers Visma.net. 07-02-2024 14:56
- Posted Error 5102 on Forum in Developers Visma.net. 07-02-2024 14:33
- Posted Re: Bad Gateway messages when making calls to the Visma.Net ERP API on Forum in Developers Visma.net. 17-01-2024 09:45
- Posted Re: Bad Gateway messages when making calls to the Visma.Net ERP API on Forum in Developers Visma.net. 05-01-2024 11:36
- Posted Re: Bad Gateway messages when making calls to the Visma.Net ERP API on Forum in Developers Visma.net. 04-01-2024 10:12
- Got a Kudo for Re: Error: Branch '1 ' cannot be found in the system. 30-12-2023 22:26
- Got a Kudo for Re: Error: Branch '1 ' cannot be found in the system. 30-12-2023 22:26
- Posted Re: 500 Error in every API call, Visma.NET service API on Forum in Developers Visma.net. 19-12-2023 08:07
- Posted Sv: 500 Error in every API call, Visma.NET service API on Forum in Developers Visma.net. 18-12-2023 08:54
- Posted Sv: POST Supplierinvoice using new authentication results in No access to branch error message on Forum in Developers Visma.net. 14-12-2023 14:44
.gif "VISMA"){kind=icon}
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America