Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
When you move Microsoft Dynamics CRM databases to a new instance of SQL Server, SQL Server jobs may not be created
Article ID: 910044 - View products that this article applies to.
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:
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.
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: