Article ID: 915799 - Last Review: December 7, 2006 - Revision: 2.2

Error message when you use the Copy Database Wizard in SQL Server 2005 to migrate the Microsoft Dynamics CRM 3.0 MSCRM database from SQL Server 2000: "Setting Source Connection (Error)"

View products that this article applies to.
The hotfix that is discussed in this article is not available for the Chinese version of Microsoft Dynamics CRM or for the Japanese version of Microsoft Dynamics CRM.

On This Page

Expand all | Collapse all

SYMPTOMS

When you use the Copy Database Wizard in Microsoft SQL Server 2005 to migrate the Microsoft Dynamics CRM 3.0 MSCRM database from Microsoft SQL Server 2000, you receive the following error message in the Copy Database Wizard:
Setting Source Connection (Error)
Messages
• Error 0xc0202009: Source - Activity [1]: An OLE DB error has occurred. Error code: 0x80040E37. (SQL Server Import and Export Wizard)
• Error 0xc02020e8: Source - Activity [1]: Opening a rowset for "[Database Name_MSCRM].[dbo].[Activity]" failed. Check that the object exists in the database. (SQL Server Import and Export Wizard)
• Exception from HRESULT: 0xC02020E8 (Microsoft.SqlServer.DTSPipelineWrap)
Note The Database Name placeholder is a placeholder for the actual MSCRM database name.

When you then run the select * from Activity SQL command against the MSCRM database in SQL Query Analyzer to determine whether the object exists in the database, you receive the following error message:
Server: Msg 208, Level 16, State 1, Procedure Activity, Line 75
Invalid object name 'ActivityBase'.
Server: Msg 4413, Level 16, State 1, Line 1
Could not use view or function 'Activity' because of binding errors."
Back to the top

CAUSE

This problem occurs because a view references a table that does not exist. The table does not exist because the database did not correctly migrate.
Back to the top

WORKAROUND

To work around this problem, use one of the following methods.
Back to the top

Method 1

Use the Detach Database command to remove the database from the instance of Microsoft SQL Server 2000. Then, use the Attach Database command to attach the database to the instance of Microsoft SQL 2005.
Back to the top

Method 2

  1. Back up the database in Microsoft SQL Server 2000.
  2. Install Microsoft SQL Server 2005.
  3. Restore the database in Microsoft SQL Server 2005.
Back to the top

RESOLUTION

This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
922815  (http://support.microsoft.com/kb/922815/ ) Update Rollup 1 is available for Microsoft Dynamics CRM 3.0
Back to the top

MORE INFORMATION

For more information about the Copy Database Wizard in Microsoft SQL Server 2005, see the following topic in the SQL Server 2005 Books Online:
Upgrade to SQL Server 2005 with the Copy Database Wizard
For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
887283  (http://support.microsoft.com/kb/887283/ ) Microsoft Business Solutions CRM software hotfix and update package naming standards
Back to the top
APPLIES TO
  • Microsoft CRM 3.0
Back to the top
Keywords: 
kbmbsupgrade kberrmsg kbbug kbhotfixserver kbqfe kbmbsmigrate KB915799
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations