This article has been archived. It is offered "as is" and will no longer be updated.
You move Microsoft Dynamics CRM 3.0 databases to a new instance of Microsoft SQL Server. After you do this, you install Microsoft CRM 3.0 and then click to select the Connect to Existing Databases option. However, the following SQL Server jobs are not created:
Organization_Name.Update Contract States
MSCRM Identity Reseeding
MSCRM Index Reindexing
MSCRM Stored Procedures Priming
Start_Incremental on Organization_Name_ftcat_documentindex
If you upgrade to Microsoft Dynamics CRM 3.0 from Microsoft CRM 1.2 and if these SQL Server jobs were deleted in Microsoft CRM 1.2, not all the jobs are re-created during the upgrade. If you run the Environment Diagnostics tool after the upgrade, you receive the following warnings:
Job <OrganizationName>_MSCRM.Update Contract States could not be found in the sysjobs table.
Job Start_Incremental on <OrganizationName>_MSCRM.ftcat_documentindex.[7.5] could not be found in the sysjobs table.
OrganizationName is the placeholder for the actual organization name that is used when you install Microsoft Dynamics CRM.
You also experience this problem if you have multiple installations of the Microsoft Dynamics CRM databases on the same server that is running SQL Server. For example, you installed Microsoft Dynamics CRM two times by using different organization names, and the Microsoft Dynamics CRM databases all reside on the same server that is running SQL Server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this problem, you can copy the script from other SQL Server jobs in another Microsoft CRM environment. For more information about how to copy scripts from other SQL Server jobs, contact Microsoft Product Customer Support Services. For information about technical support for Microsoft Dynamics CRM, visit the following Microsoft Web site: