Dynamics CRM 2016 | Random Security Token Errors During Boomi Integration

Applies to Product - Microsoft Dataverse

What’s happening?

Customers are experiencing random security token errors when the Boomi integration calls the Dynamics CRM 2016 CE API. The errors include messages such as "Could not retrieve a new security token" and "1001 communication error."

Reason:
The underlying cause of the security token errors may be related to network connectivity issues, load balancer or firewall misconfigurations, server-side resource constraints, or issues with the Dynamics CRM authentication service. Additionally, the absence of ADFS (Active Directory Federation Services) in the configuration may lead to these errors, as Dynamics CRM On-Premises expects ADFS to handle authentication requests.

Resolution:

1. Network Connectivity: Monitor network connectivity for packet loss or latency during error occurrences. Implement retry logic within the Boomi integration to automatically retry token requests a few times before reporting an error.
2. Load Balancer/Firewall Configuration: Review load balancer and firewall configurations to ensure they are not impeding traffic from the Boomi server. Whitelist the Boomi server's IP addresses if necessary.
3. Server-Side Resource Monitoring: Monitor server performance (CPU, memory, disk) during error occurrences. Optimize server resources or consider scaling if bottlenecks are identified.
4. Authentication Service Check: Check Dynamics CRM event logs for errors related to authentication services. Consider restarting the relevant authentication services if errors are found.
5. Certificate Validation: Verify the validity of all SSL certificates involved in the integration. Renew or update certificates if necessary.
6. Application Pool Recycling: Adjust application pool recycling settings on the Dynamics CRM server to minimize disruptions during peak usage times. If possible, use a token refresh mechanism to avoid relying solely on cached tokens.
7. Testing with Postman: Use Postman or another application to test the API calls independently of Boomi to verify if the security token errors persist.
8. Log Capturing: Enable verbose logging on both the Boomi and Dynamics CRM sides to capture detailed error messages and timestamps during the occurrence of the errors.