Skip to main content

Common Transaction Errors

When appointments fail to sync between Dime.Scheduler and NAV, the transaction log records why. This page collects the error messages you'll run into most often, explains what causes each one, and walks you through fixing it.

Request Channel Timeout​

The request channel timed out attempting to send after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. The HTTP request to 'http://[server]/[instance]/WS/[company]/Page/Appointment' has exceeded the allotted timeout of 00:01:00.

Cause​

A web service call between Dime.Scheduler and NAV took longer than the configured timeout (1 minute by default).

Most common cause: Dime.Scheduler can't reach the web service at all, usually because a firewall is blocking the connection.

Other causes include:

  • Network latency or connectivity issues
  • The NAV/NAV server is under heavy load
  • Large data payloads being transmitted
  • Slow database queries on the NAV/NAV side
  • The web service endpoint is processing complex business logic

Solution​

  1. Check firewall and network accessibility:

    • Verify that the NAV/NAV web service URL is accessible from Dime.Scheduler cloud
    • Open the required firewall ports to allow traffic from Dime.Scheduler to NAV/NAV
    • For on-premises: Ensure the web service endpoint is published and accessible externally
    • For cloud: Verify that the service is not blocked by network security groups or Azure firewall rules
    • Test connectivity using tools like telnet, curl, or browser access from Dime.Scheduler cloud

  2. Verify connector URL:

    • Navigate to Administration > Connectors in Dime.Scheduler
    • Verify the web service URL is correct and accessible

  3. Increase the timeout value if connectivity is confirmed:

    • Edit the NAV/NAV connector
    • Increase the Request Timeout value (e.g., from 60 to 120 seconds or higher)
    • Save the connector configuration

  4. Optimize NAV/NAV performance:

    • Review and optimize any custom code in the appointment processing codeunits
    • Check for database locks or slow queries
    • Ensure the NAV/NAV server has adequate resources
    • Review the NAV/NAV server event logs for performance issues

  5. Retry the transaction:

    • After resolving connectivity issues, retry the failed transaction from the Errors page
tip

Timeouts that cluster around specific times of day usually point to server load. Schedule heavy processing tasks outside of peak planning hours.

HTTP Request Unauthorized​

The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Basic realm=...'

This error, and variants like "401 Unauthorized" or "Invalid credentials", means the connector's authentication doesn't match what NAV/NAV expects, or the credentials are wrong.

Cause​

The authentication method set on your connector doesn't match the server, or your credentials are incorrect or expired.

Solution​

Step 1: Fix the authentication​

  1. Go to Administration > Connectors in Dime.Scheduler
  2. Edit your NAV connector
  3. Set authentication to the desired authentication method
  4. Fill in the required authentication fields
Using Basic auth?

If the test fails with a wrong password, check that the account isn't locked in Active Directory or NAV.

Step 2: If the test still fails​

Check these common issues:

ProblemSolution
OAuth: "Client secret expired"Generate a new secret in Azure Portal and update the connector
OAuth: "Invalid tenant ID"Verify the tenant ID matches your Azure AD tenant
Basic Auth: "Invalid username"Try without the domain prefix (just USERNAME)
Basic Auth: "Account locked"Unlock the account in Active Directory or NAV/NAV
"Permission denied"Verify the account has access to Dime.Scheduler tables

Step 4: Retry the failed transaction​

Once the test connection succeeds, retry the failed appointment from the Errors page.

General Troubleshooting Steps​

For any transaction error, work through these steps. For deeper guidance, see the NAV Troubleshooting guide.

  1. Check the transaction details:

    • Navigate to Administration > Transactions > Errors
    • Click on the failed appointment to view detailed error information
    • Review the error message, timestamp, and affected connector

  2. Verify connector configuration:

    • Navigate to Administration > Connectors
    • Review the connector settings for the affected back office system

  3. Check the NAV/NAV system:

    • Review the Dime.Scheduler Appointments table
    • Check for any error messages or processing failures
    • Verify the web service endpoints are available and responding

  4. Retry the transaction:

    • After resolving the underlying issue, retry the failed transaction
    • Monitor the transaction to ensure it completes successfully