Troubleshooting
Find a fix
Search for what you're seeing, or browse by area. Each symptom links straight to the page that explains the cause and the fix.
Find your symptom
Appointments don't show up in Business Central
Usually a missing or invalid connector, or BC is unreachable from Dime.Scheduler.
Appointment in BC is stuck on "Error"
Dime.Scheduler delivered it, but BC couldn't process it. Check the Dime.Scheduler Appointments table in BC.
Request channel timed out
Firewall is blocking traffic from Dime.Scheduler to BC, or the request is too slow.
HTTP Request Unauthorized
Wrong credentials, expired secret, or missing API permissions on the BC side.
BC complains about time synchronization
Server clocks are drifting. Token validation fails when clocks are off by more than a few minutes.
A user forgot their password
Forms users can self-reset. Windows / Entra ID users go through their network admin.
I changed a role but the user still has the old permissions
They need to log out and back in. Roles are evaluated at login.
New translations don't appear in the planning view
Translations are cached in the browser. A hard refresh (Ctrl+F5) clears the cache.
Chrome won't open dynamicsnav:// or bc:// links
Known Chromium issue. Workaround: edit the Preferences file to whitelist the protocol.
Browser blocks file:// links to documents on a share
Browser security blocks navigating across security boundaries. Use a local file extension or a different scheme.
Browser won't ask for the user's location
Location prompt is disabled in browser site settings. Enable it per browser.
Exchange: "Invalid client" or AADSTS700016
Wrong Client ID, Tenant ID, or expired Client Secret in the Azure app registration.
Exchange: "Insufficient privileges" or consent required
API permissions are set but admin consent was never granted in Azure AD.
Zapier won't authenticate
API key is wrong, scoped incorrectly, or the Dime.Scheduler URL is malformed.
A Zap doesn't trigger
Trigger conditions or filters are too narrow, or the polling interval hasn't fired yet.
Component is blank or layout looks broken
Profile or layout misconfiguration, or stale browser cache.
NAV web service calls fail
NAV web services not published, wrong tenant, or company name mismatch.
Look up an error code
Failed transactions carry a stable code in square brackets, e.g. [DSBC003]. Paste it here to jump straight to the cause and fix.
50 of 50
DSCFG001Back-office not allowedBusiness Central Fix configurationDSCFG002Missing required fieldBusiness Central Fix configurationDSCFG003Back-office returned no dataBusiness Central Fix configurationDSCFG004Schema mismatchBusiness Central Fix configurationDSCFG005Wrong system type (REST vs SOAP)Business Central Fix configurationDSCFG006OAuth credentials unparseableBusiness Central Fix configurationDSCFG007Malformed connector URLBusiness Central Fix configurationDSCFG008HTTP request unauthorizedBusiness Central Fix configurationDSCFG009HTTPS required for SOAPBusiness Central Fix configurationDSCFG010Unsupported connector configurationBusiness Central Fix configurationDSCFG011OAuth client rejected by Entra IDBusiness Central Fix configurationDSCFG012HTTP endpoint not foundBusiness Central Fix configurationDSCFG013Entra ID tenant not foundBusiness Central Fix configurationDSCFG014Entra ID app not in tenantBusiness Central Fix configurationDSHTTP001HTTP transient (429/5xx)Business Central Retried automaticallyDSHTTP002HTTP proxy tunnel failureBusiness Central Retried automaticallyDSBC001HTTP request unauthorizedBusiness Central Fix configurationDSBC002BC endpoint not foundBusiness Central Fix configurationDSBC003BC server too busyBusiness Central Retried automaticallyDSBC004Request channel timeoutBusiness Central Retried automaticallyDSBC005BC communication faultBusiness Central Retried automaticallyDSBC006SOAP "unknown type" faultBusiness Central Fix configurationDSBC007SOAP "service not found" faultBusiness Central Fix configurationDSBC008BC REST API missing Location headerBusiness Central Fix configurationDSBC009SOAP HTTP transient (429/5xx)Business Central Retried automaticallyDSBC010BC insufficient permissionsBusiness Central Fix configurationDSDB001SQL transientBusiness Central Retried automaticallyDSDB002Database accessBusiness Central Retried automaticallyDSDB003Concurrency conflictBusiness Central Retried automaticallyDSDB004SQL timeoutBusiness Central Retried automaticallyDSUNK001UndiagnosedBusiness Central UndiagnosedDSWBHK001Webhook not allowedWebhook Fix configurationDSWBHK002Empty or malformed URLWebhook Fix configurationDSWBHK003Wrong connector typeWebhook Fix configurationDSWBHK010Partner endpoint timeoutWebhook Retried automaticallyDSWBHK020Partner HTTP failureWebhook Retried automaticallyDSWBHK030Circuit breaker openWebhook Retried automaticallyDSEX001Expired client secretExchange Fix configurationDSEX002Invalid client secretExchange Fix configurationDSEX003Unknown client IDExchange Fix configurationDSEX004Unknown or malformed tenant IDExchange Fix configurationDSEX005Other rejected credentialsExchange Fix configurationDSEX006Incomplete credentialsExchange Fix configurationDSEX010Credentials rejected after the callExchange Fix configurationDSEX011Exchange integration disabled for the assigned resourcesExchange Fix configurationDSEX012Invalid user in the directoryExchange Fix configurationDSEX020No mapping entryExchange Retried automaticallyDSEX021Event already deletedExchange Retried automaticallyDSEX030Access denied by the Azure AD appExchange Fix configurationDSEX040Microsoft Graph transientExchange Retried automatically
First steps for any issue
If your symptom isn't listed above, run through these in order. They resolve a large share of incidents on their own.
- 1Check the transactions logMost integration problems show up here first. Open errors and read the latest failure message.
- 2Verify connectivityConfirm the back-office system is online and that firewalls allow traffic from Dime.Scheduler to it. 504 / timeout errors almost always come from here.
- 3Re-check authenticationCredentials, secrets and API keys expire. Make sure the configured account hasn't rotated, locked, or lost the required permissions.
- 4Hard-refresh & re-loginFor UI oddities and stale data: Ctrl+F5, try an incognito window, and log out and back in to pick up role and translation changes.
Browse by area
User Troubleshooting
Resolve common issues users encounter when working with the planning interface.
Login Issues • Planning Board • Profile Layouts • Permissions
Administration
Diagnose and fix administrative configuration and setup problems.
User Management • Field Templates • Settings
Business Central Integration
Troubleshoot data synchronization and integration issues with Business Central.
Connection Issues • Transaction Errors • Authentication • Timeouts
NAV Integration
Resolve integration problems with Microsoft Dynamics NAV.
Web Services • Appointments • Data Sync
Exchange Integration
Fix calendar synchronization and Exchange connectivity issues.
Calendar Sync • Authentication • Mailbox Access
Zapier Connector
Resolve automation and workflow issues with the Zapier integration.
Authentication • Triggers • Actions • Data Formatting
Still stuck?
Gather the error message, a screenshot, the exact steps to reproduce, and the time it started. For urgent issues affecting production systems, contact support directly with that diagnostic information ready.