Connector for Microsoft Dynamics configuration settings that can be used to control some of the default behaviors for logging and retries

There are some configuration settings that can be added or changed in the ConnectorServiceHost.exe.config to update default behavior with respect to retries and log cleanup; they are as follows: 

Config Setting




True: The Housekeeping task should run CleanupLog.proc.sql and CleanupRetryTask.proc.sql

False: The Housekeeping task will run only run CleanupTaskDeletionTracking.proc.sql (not recommended)

Caution: Log entries and expired Retries can degrade overall system performance if this setting is False


The time of day the housekeeping task should run, default is DateTime.UtcNow() or service start time

It may make sense to set this to a time of day that has less load, such as a time after normal business hours

Connector uses the DateTime.TryParse() method to parse this setting, see this article for the proper string format.

If the setting can't be parsed then the default of DateTime.UtcNow() is used for this setting


True: Housekeeping should run immediately upon service start (Default)

False: Housekeeping task should wait until next scheduled run time after service start



First usage: Number of days to keep retries that have completed successfully (Default = 3 days)

Second usage: Number * 2 = days to keep retries that were stopped by the user or ran out of retry attempts (Default = 3 *2 = 6)

Making this value smaller gives you less time to restart failed records; making it larger will give you more time to see the log.

Be aware that Making this number too large can affect performance as retries that have run out of attempts over time can degrade overall system performance

 Task Scheduling configuration settings:


Number of concurrent Retries the system will queue

Also number of connections to Microsoft Dynamics CRM that could potentially be created at any given time


Maximum attempts a given retry will make before stopping and waiting for the user interaction to resolve the issue



Number of seconds from initial attempt to first and second retry attempts, Default = 5

RetryInterval ^ CurrentRetryAttempt

5 to 5^MaximumRetries



Comments (13)
  1. Omer Awan says:

    can you give an example how to use HousekeepingCleanupLogs and related settings.

  2. thehetz says:

    @Omer – these settings should only ever be changed if you are experiencing overall system degradation and want troubleshoot what is going on.

  3. RSalie says:

    What is the default for MaximumRetries?

  4. siuchon says:

    Hi the hetz,
    I got log that said, “Text: Completed: 1000 record(s) have been written. 0 record(s) have been deleted. 0 record(s) have failed. 1000 record(s) were filtered. Total runtime was 1076.864551 seconds.” The map is to sync Open Statement (retail) to Sales Order in CRM.
    But after I check in CRM, there’s no Sales Order created. How can I trace this issue? Is there any log to know the content of those 1000 records.?

    Siu Chon

    1. thehetz says:

      The message – 1000 record(s) have been written. 0 record(s) have been deleted. 0 record(s) have failed. 1000 record(s) were filtered. Total runtime was 1076.864551 seconds – indicates that 1000 records were filtered, which means that they were NOT sent to CRM. You should check the filter on the map, because currently it is filtering all of your records.

      1. siuchon says:

        So I should wait again? I thought it was completed. Because here is what I got: ““Text: Completed: 1000 record(s) have been written……”

      2. siuchon says:

        Hi thehetz,
        I have waited for several hours, but the 1000 records haven’t created in CRM. Is there a way to see the content of those 1000 records?


        1. thehetz says:

          Did you change the filter on the map?

          1. siuchon says:

            Yes, I set some filter for that map.

  5. Mateus Miranda says:

    MaximumRetries is with 7, but the connector does not perform 7 attempts, any tips?

  6. sathish says:

    How to pass DateTime values in Connector

Comments are closed.

Skip to main content