Attachment is missing for certificate Microsoft Teams Connector Certificate

LaraReddy
Tera Guru

Hi All,

Happy New year.

We have integrated the servicenow with MS teams and it's working fine. But at the system logs level we're seeing the below Error.

"Attachment is missing for certificate Microsoft Teams Connector Certificate - 90e8c322c7982d102450ed6c95c260c7: no thrown error"

moreover we gone through few threads but no luck to resolve the error.

Can anyone please guide us resolve the error.

Advance thanks.

1 ACCEPTED SOLUTION

@LaraReddy 

Thank you for marking my response as helpful.

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

5 REPLIES 5

Ankur Bawiskar
Tera Patron
Tera Patron

@LaraReddy 

since you said connection is established and everything is working fine and still that error is coming in logs, then it's surprising.

I believe that should be fine

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

LaraReddy
Tera Guru

Hi @Ankur Bawiskar  / @Sarthak Kashyap ,

Thanks for the response.

We have used the "ServiceNow for Microsoft Teams" plugin for this integration b/w service now and MS teams.

But as we mentioned the above error message triggering daily more than 200k times.

Is there any way to stop the triggering the error at logs table level without impacting the existing process OR  since it's asking to attach the "X.509 certificate" certificate , Is there way to generate and attach the required certificate.

During the process of establishing the connection, we have not attached any certificate at ServiceNow certificate table level.

Advance thanks.

Regards.


@LaraReddy 

So the integration is working fine but still the error is shown

Also since you mentioned you haven't used any certificate during setup of MS Teams, better to raise a case with ServiceNow as they can identify the source of that error

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader