How to Assess SMS Data Source Processes

  • Article

You can determine the status of SMS synchronization processes (DTS jobs) by viewing their progress in the SCRM Administrator console. However, you can view much more detailed information by following the procedures below for each major process.

If a DTS job appears to remain in one state for too long, you can view the current job state by running a SQL query. For more information, see How to Run SQL Queries for Detailed SMS DTS Job Status.

To troubleshoot specific problems, see Troubleshooting SCRM 2006.

To verify that the schedule process completed successfully

  1. View the SCRMLog.log file to verify that the schedule file is picked up by the SMS server.

  2. In the log file, determine whether there are any errors finding or reading the schedule file.

  3. Determine whether the schedule file is in the Outbound directory. It is removed when it is processed by the SCRM SMS Site Service (SCRMClientSvc.exe).

  4. If the log file shows errors connecting to the SCRM server and the schedule file is still in the Outbound directory, verify that the path specified in the log is available from the SMS server and that the account has been given permissions to the path specified in the log.

  5. If no entries are seen in the log file, verify that the SCRM SMS Site Service is running.

  6. If the schedule file appears to have been processed, verify that the SQL Agent job for the sync job has been created.

  7. If the SQL Agent Job is present and the time for which the job was scheduled has passed, verify that the SQL Agent job is enabled and is not failing.

  8. If the SQL Agent Job is failing, verify that the account for which the job runs is a member of the SC DW SMS DTS group on the SMS site server.

To verify that the data extraction process from SMS completed successfully

  1. To verify that data extraction has started, check the record in the SCRM_MTD_SyncSchedule table and verify that the status is set to InProgress.

  2. If the status of the job is not set to InProgress within five minutes of the schedule being added to the database, do the following:

    1. Verify that the SyncProcessAgentJob SQL Agent job is enabled and scheduled to run every five minutes.

    2. Verify that the account for which the SyncProcessAgentJob SQL Agent job is configured to run is a member of the SC DW SMS DTS user group on the SMS site server.

    3. Check the job history to see whether the job is failing when it runs. If the job is failing on the first step, Manage SyncProcess, check the ManageSynchProcess_Log.log in the C:\Program Files\Microsoft System Center Reporting Manager\Log directory.

    4. Verify that another job is not in the SCRM_MTD_SyncSchedule table with a status of InProgress. If so, this job must be completed before a new one can start.

  3. To verify that all data has been extracted, check the SCRM_Message.log file for Extraction Finished and check the DATA directory. There should be 91 .dat files.

To verify that the file copy to SCRM completed successfully

  1. View the SCRMLog.log file. When data extraction has completed, the SCRM SMS Site Service copies the files to the share on the SCRM server. The progress of the file copy is logged in the SCRMLog.log file.

  2. If nothing is logged in the SCRMLog.log file, verify that the SCRM SMS Site Service has started.

  3. Verify that the .dat files are in the DATA directory.

  4. If the SCRMLog.log file shows errors copying the files, do the following:

    1. Check the value of the ShareDirectory entry in the SCRM_MTD_Configuration table to verify that it is the correct path to the Staging Share.

    2. Verify that the user account that the SCRM SMS Site Service starts can connect to the Staging Share and write data to its Inbound directory.

  5. To verify that the file transfer process has completed successfully, check that File Transfer Finished is written to the SCRMLog.log file and to the SCRM_Message.log file.

To verify that the ETL process completed successfully

  • Review the SCRM_ExtractStatus.log file for success or errors.