Looks like it got fixed at about 11:45, thats almost 24 hours after it was reported here ... View more

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

Its been better today, but there were errors day all yesterday ... View more

Yes, the errors have been received through the day. 14:32, 13:38, 11:53 and so on ... View more

502 again now ... ... View more

The same again now: 502 Bad Gateway ... View more

New day with 502 Have received since 09:42 502 Bad Gateway ... View more

The same again today ...  502 Bad Gateway ... View more

And there is a lot of 502 Bad Gateway ... View more

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

Any updates? This is still an issue ... View more

This still fails the same way as it did before the latest update. ... View more

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

Tested today with tenant auth, and today it worked. Looks like a cache issue with the credentials? ... View more

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

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

I've sent a few examples to developersupport now ... View more

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

Got timeouts at about 13:00. Last 5520 was at 11:20 ... View more

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

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

A lot of 502 Bad Gateway since 08:59, and it's still failing ... View more

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

New strange error: Url: /controller/api/v1/paymentMethod/ 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: EVAL, inst: 2, qu: 0, qs: 7, aw: False, rs: ReadAsync, ws: Idle, in: 0, serverEndpoint: 10.10.6.4:15005, mc: 1/1/0, mgr: 8 of 10 available, clientName: erp096701000036, PerfCounterHelperkeyHashSlot: 15367, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=32,Free=32735,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)","exceptionType":"StackExchange.Redis.RedisTimeoutException","stackTrace":" at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor`1 processor, ServerEndPoint server) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2807\r\n at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor`1 processor, ServerEndPoint server) in /_/src/StackExchange.Redis/RedisBase.cs:line 54\r\n at StackExchange.Redis.RedisDatabase.ScriptEvaluate(String script, RedisKey[] keys, RedisValue[] values, CommandFlags flags) in /_/src/StackExchange.Redis/RedisDatabase.cs:line 1153\r\n at Microsoft.Web.Redis.StackExchangeClientConnection.<>c__DisplayClass11_0.b__0()\r\n at Microsoft.Web.Redis.StackExchangeClientConnection.RetryForScriptNotFound(Func`1 redisOperation)\r\n at Microsoft.Web.Redis.StackExchangeClientConnection.RetryLogic(Func`1 redisOperation)\r\n at Microsoft.Web.Redis.StackExchangeClientConnection.Eval(String script, String[] keyArgs, Object[] valueArgs)\r\n at Microsoft.Web.Redis.RedisConnectionWrapper.TryCheckWriteLockAndGetData(Object& lockId, ISessionStateItemCollection& data, Int32& sessionTimeout)\r\n at Microsoft.Web.Redis.RedisSessionStateProvider.GetItemFromSessionStore(Boolean isWriteLockRequired, HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actions)\r\n at Microsoft.Web.Redis.RedisSessionStateProvider.GetItem(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actions)\r\n at PX.Data.PXSessionStateStore.ProviderGetItem(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags)\r\n at PX.Data.PXSessionStateStore.LoadSessionItem(HttpContext context, String id, Boolean isReadonly, Object& lockId, Boolean& isNew)\r\n at PX.Data.PXSessionStateStore.WriteToSession(String id, Boolean isReadonly, Action`1 processMethod)\r\n at PX.Data.PXSessionStateStore.ProcessWithSessionContext(String id, Boolean isReadonly, Action`1 processMethod)\r\n at PX.Data.PXLongOperation.PXTaskPool.ReadSession(Object key, Boolean& abort)\r\n at PX.Data.PXLongOperation.PXTaskPool.TryGetValue(Object key, PXAsyncResult& result)\r\n at PX.Data.PXLongOperation.ClearStatus(Object key, Boolean abort)\r\n at PX.Data.PXLongOperation.ClearStatus(Object key)\r\n at PX.Data.PXGraph.Clear(PXClearOption option)\r\n at Visma.net.ERP.Api.Base.BaseRepository.d__4.MoveNext() in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\Base\\BaseRepository.cs:line 77\r\n at Visma.net.ERP.Api.CA.Repository.PaymentMethodRepository.d__12.MoveNext() in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\CA\\Repository\\PaymentMethodRepository.cs:line 129\r\n at Visma.net.ERP.Web.Api.Mapping.PaymentMethodMappingExtension.d__1.MoveNext() in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Web.Api\\Mapping\\PaymentMethodMappingExtension.cs:line 31\r\n at System.Linq.Buffer`1..ctor(IEnumerable`1 source)\r\n at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)\r\n at Visma.net.ERP.Web.Api.Mapping.PaymentMethodMappingExtension.ToDtoPaymentMethod(IPaymentMethodVo paymentMethodVo) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Web.Api\\Mapping\\PaymentMethodMappingExtension.cs:line 16\r\n at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)\r\n at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)\r\n at System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, Encoding effectiveEncoding)\r\n at System.Net.Http.Formatting.JsonMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, Encoding effectiveEncoding)\r\n at System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.WriteToStreamAsync(Type type, Object value, Stream writeStream, HttpContent content, TransportContext transportContext, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at PX.Api.Compression.BaseCompressor.d__4.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at PX.Api.Compression.CompressedContent.d__4.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.WebHost.HttpControllerHandler.d__22.MoveNext()"}} ... View more

And also some 5520 Url: /controller/api/v1/carrier/ Content received: {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_ee4a2531-eeb8-4d09-96ab-43322a86647b","ExceptionDetails":""} ... View more

Worked great for a long time, but got a bunch of 504 now ... View more