Hello Everyone

Reading some of the recent posts, I wanted to take a moment to talk about the 80040e14 error when installing Microsoft CRM. There are 2 primary causes of the error that we have found in support. In a large environment with multiple domain controllers the 80040e14 error is a result of The Microsoft CRM installation failing as a result of Active Directory replication not replicating to all Domain Controllers in a timely fashion, prior to the Microsoft CRM installation getting to the point where it is installing the SQL users. It is possible that the SQL Server is referencing a Domain Controller that has not yet replicated the CRM Active Directory container.

We have 2 resolutions to this issue until it is resolved in an upcoming release.

Resolution 1 - Force replication to all domain controllers at the beginning of the Microsoft CRM installation, immediately after the installation wizard has installed any pre-requisite applications (such as .NET framework or XML Parser). Please wait until the installation is actually installing the first part of Microsoft CRM, which is the creation of the Organization Unit within Active Directory.

1. Go to Start Button | Programs| Administrative Tools | Active Directory Sites and Services Manager.

2. Double-click the Sites folder to expand it. There should be at least one site labeled Default-First-Site-Name. This may differ if you have manually configured additional sites.

3. Expand the Default-First-Site icon, expand the Servers folder, and then expand the given Active Directory server to find the NTDS Settings icon.

4. Click the NTDS Settings icon. One or more objects is listed in the right pane. One of those objects is a link to the domain controller you want. You can see the Friendly names by right-clicking an entry and viewing the name. One of the objects points to the domain controller you want. Right-click that entry, and then click Replicate Now. The replication is performed immediately, but your network performance influences the time it takes to update the target controller.

Forcing replication should allow your Microsoft CRM Server installation to complete successfully now.

Resolution 2 - Shut down all domain controllers except for the domain controller which has the Global Catalog Server. Once the CRM Server installation is completed, re-start the remaining domain controllers and continue configuring Microsoft CRM.



The second primary cause of the issue is a result the .mdf and .ldf files associated with the Microsoft CRM Server install Organization name within <system drive>:\Program Files\Microsoft SQL Server\MSSQL\Data may have not been deleted.


To resolve, Microsoft CRM will need to be uninstalled using the Uninstall Steps in Appendix C of the Implementation Guide, making sure that the .mdf and .ldf files have been deleted.

To verify the .mdf and .ldf files are removed:

1. Navigate to <system drive>:\Program Files\Microsoft SQL Server\MSSQL\Data

2. Verify the following .mdf and .ldf files that are associated with your Microsoft CRM Organization Name (the Organization Name that you installed Microsoft CRM with) have been deleted.

- <organization_name>_METABASE.mdf
- <organization_name>_METABASE.ldf
- <organization_name>_MSCRM.mdf
- <organization_name>_MSCRM.ldf
- <organization_name>_CRYSTAL.mdf
- <organization_name>_CRYSTAL.ldf

For example, if Microsoft CRM is installed with the Organization Name Adventure Works Cycle, an .mdf or .ldf file name would look like:

Adventure_Works_Cycle_MSCRM.mdf

3. Once these are removed, install Microsoft CRM again.


Any questions on this please let me know.

--
Regards,

Ryan Trudeau
Microsoft CRM Support



"Please do not send email directly to this alias. This alias is for newsgroup purposes only. All replies will be returned to sender as undeliverable."