Processing Exception while reading ODP response

[Steinar Møller]

{"ExceptionType":"IPPException","ExceptionMessage":"Processing Exception while reading ODP response: ","ExceptionFaultCode":"12022","ExceptionMessageID":"12022_f758322c-3a7d-47ed-8c55-f4ac3d4282bf","ExceptionDetails":""}

We get this error several times during the day and this has been a problem the last couple of weeks.
It causes handling and problems with all this errors. 

What is status on this for when this will be fixed?

[adrianm]

I still get this error almost every day.

[Florian Haase]

We are up and running again after generating new tokens. But this stopped our whole integration plattform. Hope that this was a single-time event.

[Gabriella Hennings]

Hi 

Do you have any news or ETA concerning this matter? It's affecting almost all of our customers and we do not find it to be an accepteable solution to regenerate tokens for all our customers.

best regards Gabriella, Direktkonsult

[Yıldırım]

Hello Gabriella, we're still investigating this and will keep you posted as soon as we have an update.(Incident report: https://status.visma.com/incidents/vx11gtw6kv61)

[Magnus Johnsen]

The team is working on restoring the tokens, this will take a couple of hours, follow the status update above for more information. 

[andretvard]

Our customers are also affected by this problem.

[Magnus Johnsen]

We are working on finding the cause for the issue. We have noticed an increase in the issues during the night.

[Magnus Johnsen]

As @andreasaulin has mentioned, for now the soultion seems to be to generate a new token.

Currently this is the workaround available.

We are not yet able to provide an ETA on this issue.

We'll provide more information as soon as we can. 

Status on the API issues can be found here:
https://status.visma.com/incidents/vx11gtw6kv61

[andreasaulin]

And what will happen to the newly generated tokens when/if the old tokens start working again ...?

[Magnus Johnsen]

The old tokens should be invalidated as soon as you have generated new tokens. 

[sallbergerik]

Same for me, several integrations all down since yesterday.

Please try and fix this as soon as possible, would be much appreciated!

[teejay]

We have the same problem for all our integrations.

This needs to be fixed asap!

[andreasaulin]

A lot (all?) clients get this error message consistent right now

{
	"ExceptionType": "IPPException",
	"ExceptionMessage": "Exception while trying to validate user context in ODP based on token.",
	"ExceptionFaultCode": "12020",
	"ExceptionMessageID": "12020_677cbe00-b346-48ec-a26e-d0b4300b4786",
	"ExceptionDetails": ""
}

< HTTP/1.1 401 Unauthorized
< Date: Wed, 01 Jun 2022 05:09:18 GMT
< Server: Nginx
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< Content-Type: application/json
< ipp-request-id: dbfe87ed-f34e-4ac1-aaa5-4408c684e6ee
< Transfer-Encoding: chunked

[andreasaulin]

Works againg if generating new token, but this is not an acceptable solution. 

The need to generate about 100 new tokens - with all communication with customers and so on is not the way to go.

We need to know when this will be fixed.

[Timo_O]

Same problem with all our integrations, starting yesterday afternoon ( and this concerns several customers). Please get roesources and solve this problem asap! Wbr, Timo

[Magnus Johnsen]

Hi,

It looks like this is a general issue for Visma.Net services and is currently being worked on, please follow this status:
https://status.visma.com/incidents/r2gz4bgf5lvg

[Olivia Jansson]

Hi Magnus,

Do you have any updates regarding the ETA?

[adrianm]

Can confirm I have seen the same problem since end of last week.

Responses

{"ExceptionType":"IPPException","ExceptionMessage":"Exception while trying to validate user context in ODP based on token.","ExceptionFaultCode":"12020","ExceptionMessageID":"12020_4f0694e9-be22-4ba9-af3b-12eae08b27ac","ExceptionDetails":""}

{"ExceptionType":"IPPException","ExceptionMessage":"Processing Exception while reading ODP response: ","ExceptionFaultCode":"12022","ExceptionMessageID":"12022_df6b70fb-005e-4d9a-91e7-542156e95ca2","ExceptionDetails":""}

And today I have also received a few

{"ExceptionType":"IPPException","ExceptionMessage":"Invalid parameter exception: companyInContext","ExceptionFaultCode":"12002","ExceptionMessageID":"12002_12002_b938559f-f0b6-4bd7-9998-fd5f908e4b36","ExceptionDetails":""}

(same company id work both before and after the error message)