Dynamics CRM 2016

  1. The file size of the following attachments exceeds the maximum size of {0} kilobytes: {1}. The mail merge cannot be completed. ...
  2. The file specifies a field that does not exist in Microsoft Dynamics CRM: {0}, {1}. Fix this inconsistency, and then import ...
  3. The file specifies a list value that does not exist in Microsoft Dynamics CRM: {0}, {1}, {2}. Fix this inconsistency, and ...
  4. The file specifies a record type that does not exist in Microsoft Dynamics CRM: {0}. Specify a valid record type, and then ...
  5. The files could not be uploaded because the file {0} for the Email Router '{1}' is empty or does not contain valid xml data. ...
  6. The fiscal settings of your organization have changed since the time this goal was changed. You might want to realign the ...
  7. The folder can not be found. If you changed the automatically generated folder name for this document location directly in ...
  8. The folder could not be created. The Microsoft Dynamics CRM List component on the SharePoint site might be an earlier version. ...
  9. The folder name contains invalid characters. Please use a different name. Valid folder names cannot ends with the following ...
  10. The following application(s) {0} might interfere with Setup. Close these applications before you continue the installation. ...
  11. The following components are missing from your solution. Import will fail if these components don't exist already in the ...
  12. The following components in this solution require you to install the latest product updates, which are available only in ...
  13. The following data will be migrated from the Email Router for email processing using server-side synchronization. To continue, ...
  14. The following list shows files currently in use, followed by the application that is using the file. Close the application ...
  15. The following option set values could not be mapped:{0}This could lead to potential import failures. To continue, click OK. ...
  16. The following permissions are required for organizational unit and all child objects: read, write, modify permissions, create ...
  17. The following potential scheduling problems have been found. You might not be able to schedule this activity until these ...
  18. The following properties will take effect only after the component is exported and imported as part of a managed solution. ...
  19. The following server roles are missing from this deployment:{0}{1}{1}To resolve this issue, either add a new Microsoft Dynamics ...
  20. The foreign key constraints in the Microsoft Dynamics CRM database are not consistent with Microsoft Dynamics CRM foreign ...
  21. The Front End Server role group includes the server roles for running client applications and applications developed with ...
  22. The Full Server role group is the default server configuration that includes all Microsoft Dynamics CRM server roles on this ...
  23. The full-text indexes on the Microsoft Dynamics CRM database are not consistent with Microsoft Dynamics CRM full-text indexes. ...
  24. The Granularity column value is incorrect. Each rule part must be a name-value pair separated by an equal sign (=). For example: ...
  25. The HTTPS protocol is required for this type of request. Enable the HTTPS protocol and try again. For more information, see ...
  26. The Import Customizations process can take several minutes to complete depending on the number of items being imported. Once ...
  27. The import failed for this solution: {0}. One or more required components are not installed on your system (view details). ...
  28. The import file does not have the format that Dynamics CRM uses to map the data to CRM fields. It is possible some hidden ...
  29. The import file is invalid. XSD validation failed with the following error: '{0}'. The validation failed at: '.{1} >>>> {2}.'." ...
  30. The import has failed because the system cannot transition the entity form {0} from unmanaged to managed. Add at least one ...
  31. The import of the solution {0} failed. The following components are missing in your system and are not included in the solution. ...
  32. The Import Organization Wizard cannot connect to the SQL Server or cannot find an organization database on {0}. Verify that ...
  33. The Import Organization Wizard cannot import a database if its name contains any of the following characters: tilde (~), ...
  34. The incoming delivery method for a forward mailbox can only be set to None, or Server-Side Synchronization or Email Router. ...
  35. The incoming delivery method is set to Forward Mailbox. The email messages will be retrieved through the Forward Mailbox ...
  36. The incoming or outgoing email delivery method cannot be set to Microsoft Dynamics CRM for Outlook for a mailbox associated ...
  37. The incoming or outgoing email processing on Exchange email servers requires credentials. Setting a connection type of No ...
  38. The input arguments of the linked child dialog have been modified. Click Set Properties to verify and save the new mappings. ...
  39. The installation has failed. Your installation is unable to continue since the following pre-requisites have not been met. ...
  40. The installation of the DisplayText_ProductName was successfully completed.Before users can use this language you must provision ...
  41. The installed version of Microsoft CRM Sales for Outlook cannot be upgraded to Microsoft Dynamics CRM "4" client for Microsoft ...
  42. The installed version of Microsoft Dynamics CRM Server cannot be upgraded to Microsoft Dynamics CRM 2016 because it is an ...
  43. The installed version of Microsoft Dynamics CRM Server cannot be upgraded to Microsoft Dynamics CRM 2016. For more information, ...
  44. The installed version of Microsoft Outlook is not supported by the Microsoft CRM client. Please upgrade to the current release ...
  45. The installed version of Microsoft Outlook is not supported. Make sure that Outlook 2010 or higher version is installed. ...
  46. The instance of Microsoft SQL Server where the organization database is located is unavailable. Make sure that SQL Server ...
  47. The Internet-facing Discovery Web Service domain cannot be the same as, or a parent of, the Discovery Web Service internal ...
  48. The Internet-facing Organization Web Service domain cannot be the same as, or a parent of, the Organization Web Service internal ...
  49. The Internet-facing Web Application Server domain cannot be the same as, or a parent of, the Web Application Server internal ...
  50. The JavaScript web resources in your system contain a reference to the Microsoft Dynamics CRM 4.0 (2007) Web service endpoint. ...
  51. The key must be between 10 and 100 characters in length, and must have at least one numeral, at least one letter, and one ...
  52. The language installed on your company's system isn't available on the app. Please contact your system administrator to set ...
  53. The level selected for Create, in the User Settings record type on the Business Management tab, must match or exceed the ...
  54. The linked record in Microsoft Dynamics CRM could not be deleted. You can delete the record in Microsoft Dynamics CRM manually. ...
  55. The list component is installed on the SharePoint site. However, for folders to be created automatically, the List component ...
  56. The list of related records is not available when you create a process. To create a related record from a process, add a ...
  57. The location mapping for OneNote is inactive. Contact your administrator to activate the OneNote location record for this ...
  58. The location of one or more mailboxes could not be determined while receiving email. The mailboxes didn't synchronize. For ...
  59. The location of one or more mailboxes could not be determined while receiving email. The system will try to receive email ...
  60. The location of one or more mailboxes could not be determined while sending email. The mailboxes didn't synchronize. For ...
  61. The location of one or more mailboxes could not be determined while sending email. The system will try to send email again ...
  62. The location of the mailbox {0} could not be determined while receiving email. The owner of the associated email server profile ...
  63. The logged-on user does not have a valid Microsoft Dynamics CRM account. For information about having an account created, ...
  64. The logged-on user or the selected user is either disabled in the system or does not have any roles assigned. For more information, ...
  65. The logic in this step contains missing or invalid information. Specify all the missing information, correct any problems, ...
  66. The Lookup could not be resolved to a record in the system. You must select the record for the system to use before you can ...
  67. The lookup field of this relationship is referenced by the following objects. All references must be removed before the relationship ...
  68. The mailbox can't synchronize appointments, contacts, and tasks because the location of one or more mailboxes can't be determined. ...
  69. The mailbox cannot be activated because an associated user or queue is inactive. Activate the associated user or queue and ...
  70. The mailbox didn't synchronize appointments, contacts, and tasks because a folder for the mailbox {0} in Microsoft Exchange ...
  71. The mailbox didn't synchronize appointments, contacts, and tasks for the mailbox {0} because an error occurred while establishing ...
  72. The mailbox has been disabled for synchronizing appointments, contacts, and tasks because a folder for the mailbox {0} in ...
  73. The mailbox location could not be determined while receiving email through your mailbox {0}. The owner of the associated ...
  74. The mailbox location could not be determined while receiving email. The mailbox {0} didn't synchronize. The owner of the ...
  75. The mailbox location could not be determined while sending email through your mailbox {0}. The owner of the associated email ...