Skip to main content
Nintex Community Menu Bar
Solved

The constructor to deserialize an object of type 'Microsoft.Exchange.WebServices.Data.ServicexmlSerialization' was not found

  • July 10, 2023
  • 6 replies
  • 318 views

Forum|alt.badge.img+6

Hi,

I am getting below exception when workflow instance is created in K2 5.6 and its stopping to send task email to the users.

The constructor to deserialize an object of type 'Microsoft.Exchange.WebServices.Data.ServicexmlSerialization' was not found

please assist.

Best Regards,

 

 

Best answer by Thriveni

Hi,

I have managed by performing Go To activity to skip that specific step and is resolved and we still monitoring with other instances.

Best Regards,

Thriveni

6 replies

Forum|alt.badge.img+11
  • Nintex Employee
  • July 11, 2023

Is this working for some emails or not working for all emails?

Was this working before and stopped working?

If you run ConnectionStringEditor.exe in [K2 > Host Server > Bin] directory, does the EWS connection strings have the Oauth Resources parameter populated?  Or is it still using basic/password authentication?


Forum|alt.badge.img+6
  • Author
  • Scholar
  • July 12, 2023

Dear TinTex,

 

Thank you for your information.

This is happened only with one instance within a workflow and other instances with in the same workflow is working fine with same user.

When I checked in view flow, this is pointing to workflow email (Not a task email) which sends email to initiator that the request is initiated.

if you have any idea could be appreciated.

Best Regards,

Thriveni


Forum|alt.badge.img+11
  • Nintex Employee
  • July 12, 2023

If it is only specific to a single instance of a workflow, then it is perhaps bad data that is being used in the email step.  I would check and compare if any of the data fields, item references, or attachments that are being used in this email step greatly differs from a working instance.

Perhaps these data fields, item references, or attachments are empty or null or returns an error or invalid value which results in this error.


MillaZ
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • July 17, 2023

Hi @Thriveni 
Have these answers resolved your question? 


Forum|alt.badge.img+6
  • Author
  • Scholar
  • Answer
  • July 17, 2023

Hi,

I have managed by performing Go To activity to skip that specific step and is resolved and we still monitoring with other instances.

Best Regards,

Thriveni


Forum|alt.badge.img+2
  • Rookie
  • January 22, 2024

Hi,

We encountered the same issue/error and was able to resolve it by Go to Activity, as this error is more related to sending an email activity from the workflow .

 

Regrads

Kal