Failed to decrypt conversation id for format *==@p2p.thread.skype

[huyjack178]

Hi, currently, our old skype group has id with this format 19:I3RyYW5jaHVvbmc4Mi8kYW5ocGRfYnM7MzZjNzE3ZjFjMjI4YWI4MA==@p2p.thread.skype

And when send via bot framework, I got this Failed to decrypt conversation id error in portal Can you help me solve this problem?

[hcyang]

Hi @EricDahlvang, any update?

[EricDahlvang]

Please share the stack trace for the error.

What code is sending the message? Is this a recent error or a pre-existing bot? What does 'old skype group id" refer to from the perspective of the bot?

Unfortunately, the skype channel has been deprecated. As far as i know, existing bots should still function. But i need to check on this.

[huyjack178]

Hi @EricDahlvang, here you are

Operation returned an invalid status code 'BadRequest'
   at Microsoft.Bot.Connector.Conversations.SendToConversationWithHttpMessagesAsync(String conversationId, Activity activity, Dictionary`2 customHeaders, CancellationToken cancellationToken)
   at Microsoft.Bot.Connector.ConversationsExtensions.SendToConversationAsync(IConversations operations, String conversationId, Activity activity, CancellationToken cancellationToken)
   at Fanex.Bot.Skynex._Shared.MessageSenders.SkypeConversation.SendAsync(MessageInfo messageInfo) in D:\Builds\UnCompiled\NEXOPS\Bot\Fanex.Bot\src\bots\Fanex.Bot.Skynex\_Shared\MessageSenders\SkypeConversation.cs:line 55
   at Fanex.Bot.Skynex._Shared.MessageSenders.Conversation.ForwardMessage(MessageInfo messageInfo) in D:\Builds\UnCompiled\NEXOPS\Bot\Fanex.Bot\src\bots\Fanex.Bot.Skynex\_Shared\MessageSenders\Conversation.cs:line 116

[EricDahlvang]

Is this an existing bot, with a new exception? Did sending this same message in the same way work before, but now does not? Is it every time you send a message? Are you using a new bot to send to this group conversation?

If this exception is new, when did it first appear? Please elaborate more regarding the circumstances and history behind this error.

(transferring this issue to the services repository)

[MichaelHaydenAtMicrosoft]

Transferring to Skype Team

[konstlut]

This is a confirmed bug on Skype backend side. The issue has been mitigated for the specific bot and the general fix will be rolled out on the first week of January. @huyjack178 , @MichaelHaydenAtMicrosoft , @hcyang

[MichaelHaydenAtMicrosoft]

@konstlut Wanted to check to see if the fix was rolled out already and if we can close this issue since it has been mitigated.

[konstlut]

Yes, we believe the problem should be fixed for all bots and all conversations in Skype and Microsoft Teams. Thank you, @MichaelHaydenAtMicrosoft

[MichaelHaydenAtMicrosoft]

Thank you @konstlut! Closing issue.

[danghoanghai]

Thank you @konstlut! Closing issue.

hi @MichaelHaydenAtMicrosoft . I see that the issues have not fixed. Why this issue closed? I still keep monitoring it. hi @konstlut Please notify me when the issues have been fixed. Thanks :)

[MichaelHaydenAtMicrosoft]

@danghoanghai , can we get a fresh new set of logs? We want to check to see if there is another issue. Root cause for original issue has been addressed per our developers.

[danghoanghai]

@MichaelHaydenAtMicrosoft ya, sure. Here are the errors I got a few minutes ago before I comment on this post. If you need more information (group ID, bot ID), please contact me by my email. I will provide you, even add you and your bot into my error group. The error still Not Found. I have updated the latest version of Skype :) Here is my group conversation ID: 19:I3NlbGVuYTExNTg4LyQyMTgxYThkZDE4YWY3NDFj@p2p.thread.skype

[MichaelHaydenAtMicrosoft]

@konstlut, please see above comment for new customer logs.

[MichaelHaydenAtMicrosoft]

@danghoanghai, @huyjack178 - looks like our engineers found a different issue and adjusted the configuration. Can you try again and see if an error is generated? If so, please give us any error codes or timestamps that may be associated. Thank you!

[danghoanghai]

hi @MichaelHaydenAtMicrosoft the error is the same as above. Conversation not found. Here is the image with the timezone GMT +7 (Vietnam). Hope it will be helpful.

[MichaelHaydenAtMicrosoft]

Thank you! @konstlut please see above

[azenchenko]

@danghoanghai there seems to be two different issues that happened to your bot and in original report here. We have un-flighted your bot from experimental feature that might cause Conversation Not Found error. Can you please check again and let me know if there'd be an issue again by providing timestamp and conversationid. Thanks!

[MichaelHaydenAtMicrosoft]

@danghoanghai - See above. Please check to see if you are getting the same error. If so, please provide timestamp and Conv ID.

[hojojon]

@azenchenko @MichaelHaydenAtMicrosoft I still have the same problem as @danghoanghai does. The timestamp is "2021-02-24 10:04:55.043936+09:00" and my conversation id is "19:I2hlb3F1YXk3MC8kc2YuLi4xMjM7ZGRiZWFkZGEwYzdiOTgwZA==@p2p.thread.skype".

[kaisunc]

I'm getting

{"error":{"message":"Conversation id does not support uppercase characters"}}

for any target chat ids similar to hojojon.

[danghoanghai]

@danghoanghai - See above. Please check to see if you are getting the same error. If so, please provide timestamp and Conv ID.

hi Micheal, I still cannot send messages to my chat group. Here is the result from Azure: and here is my conversation ID: 19:I3NlbGVuYTExNTg4LyQyMTgxYThkZDE4YWY3NDFj@p2p.thread.skype

If you want to add your bot to this group for convenience to testing, please send me your contact or your bot contact privately. Thanks

[MichaelHaydenAtMicrosoft]

@danghoanghai @hojojon Thank you for your patience. From what I understand, there is an issue with our internal partner service that was mitigated with a workaround that doesn't work for some scenarios. They have disabled the workaround and would like you to repro one more time so as to help in the original issue being debugged and ultimately fixed. Apologies for asking you to do this again.

@azenchenko @konstlut can fill in the needed details here.

[danghoanghai]

@danghoanghai @hojojon Thank you for your patience. From what I understand, there is an issue with our internal partner service that was mitigated with a workaround that doesn't work for some scenarios. They have disabled the workaround and would like you to repro one more time so as to help in the original issue being debugged and ultimately fixed. Apologies for asking you to do this again.

@azenchenko @konstlut can fill in the needed details here.

thank Michael, I have tested and the bot can send messages now. Thank you for your support and thank dev team for the effort.

[hojojon]

@MichaelHaydenAtMicrosoft Thank you for your support. I've checked again and now I don't see any error. My bot works correctly as before.

[MichaelHaydenAtMicrosoft]

Great! Glad to hear that this now working! I am going to close this issue.