Microsoft BizTalk Server
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
357 questions
This is resolved.
O365 Email adapter: Failed to retrieve the token
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 74%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
BizDev
5
Reputation points
We have installed and configured BizTalk TMS service on one of our BizTalk servers. I have configured BizTalk receive location to use O365 email adapter to read emails. When I start this receive location I get these warnings and eventually this receive location shuts down. I have confirmed user name and password are correct by manually logging in to the mailbox using outlook.com
Can someone share their thoughts on how to resolve this error ?
Event 5740
The adapter "Office365 Outlook Email" raised an error message. Details "Internal error: Failed to retrieve the token.
".
Event 5740
The adapter "Office365 Outlook Email" raised an error message. Details "The Event Log Error Threshold was reached. The adapter will continue polling, but further event log entries will be suppressed. ".
Event 5649
The adapter "Office365 Outlook Email" raised an error message. Details "The Event Log Error Threshold was reached. The adapter will continue polling, but further event log entries will be suppressed. ".
{count} votes
-
Colin Dijkgraaf 1,346 Reputation points2023-01-18T20:37:52.3566667+00:00 BizTalk 2016 with Feature Pack 3? Which CU? You should be on BizTalk 2016 CU9. If BizTalk 2020 you should be on CU4.
Are you seeing any entries in Windows Event Viewer -> Application for Source: BizTalk Server TMS? If that is working correctly you should see "Service started successfully." and "Service heartbeat"
Hopefully you aren't seeing entries like.
Internal error: Failed to load identifiers. Details: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) -
BizDev 5 Reputation points
2023-01-19T14:38:50.4733333+00:00 Hi Colin
We are using BizTalk 2016 with Feature Update 3 with CU9. Related to BizTalk TMS, I see "Service started successfully" but I don't see "Service heartbeat" entries. I am not seeing "pre-login handshake." related entries. Additionally we had installed TMS on both servers (we have two BizTalk servers) but I have disabled it on one of the server and now TMS is only running on master secret server.
-
Colin Dijkgraaf 1,346 Reputation points
2023-01-20T03:00:12.25+00:00 Yes, if you have more than one node, TMS should only run on one of them, so you should add those to cluster manager.
It is good that you aren't seeing the pre-login handshake, that only occurs if there is an error with TMS connecting to Office 365.
Not so good that you are not seeing the Service heartbeat. That indicates that the service is running correctly.
Sign in to comment
1 answer
Sort by: Most helpful
-
BizDev 5 Reputation points
2023-01-30T16:52:23.1966667+00:00 -
Colin Dijkgraaf 1,346 Reputation points
2023-01-30T19:19:23.5566667+00:00 Can you state how it was resolved? So if others encounter the same issue they know how to resolve it.
Sign in to comment -