This page covers common connection issues for both Dataverse and SQL Server connections, with symptoms and solutions for each.
Dataverse Connection Errors
Error: "Unable to connect to Dataverse environment"
Symptoms: Connection test fails immediately, no response from server
Possible Causes:
• Incorrect Dataverse URL format
• Environment is offline or being updated
• Network firewall blocking outbound connections
Solutions:
1. Verify URL format: https://yourorg.crm.dynamics.com (no trailing slash)
2. Check Power Platform Admin Center for environment status
3. Ensure firewall allows HTTPS (port 443) to *.dynamics.com
Error: "Connection timed out"
Symptoms: Connection test hangs, then fails after 30+ seconds
Possible Causes:
• Slow or unstable network connection
• Proxy server not configured
• VPN connection issues
Solutions:
1. Test network connection by opening the Dataverse URL in a browser
2. Configure system proxy settings if required by your organization
3. Disconnect and reconnect VPN, or try without VPN
SQL Server Connection Errors
Error: "Cannot connect to SQL Server"
Symptoms: Connection test fails with network-related error
Possible Causes:
• Incorrect server name or address
• SQL Server not configured to accept remote connections
• Azure SQL firewall blocking your IP address
Solutions:
1. Verify server name format: yourserver.database.windows.net (for Azure SQL)
2. In Azure Portal, add your client IP to the SQL Server firewall rules
3. Ensure SQL Server Browser service is running (on-premises only)
Error: "Database 'X' not found"
Symptoms: Server connects but database access fails
Solutions:
1. Verify the database name is spelled correctly (case-sensitive)
2. Confirm the database exists on the specified server
3. Ensure your account has access to the database
💡 Tip: Use the Test button in Connection Management to verify connectivity before attempting a sync operation.