Dynamics CRM 2015

  1. The Email Router cannot be installed because it is not supported on this operating system. See the Email Router software ...
  2. The Email Router Configuration Manager helps you configure Email Router configuration profiles, associate existing deployments ...
  3. The Email Router Configuration Manager was unable to read configuration information. Make sure no files in the current directory ...
  4. The Email Router Configuration Manager was unable to retrieve user and queue information from the Microsoft Dynamics CRM ...
  5. The Email Router Configuration Manager was unable to save and publish changes. Make sure no files in the current directory ...
  6. The Email Router could not connect to Microsoft Dynamics CRM using the specified SSL port. Verify that you have provided ...
  7. The Email router service cannot access system state file Microsoft.Crm.Tools.EmailAgent.SystemState.xml. The file may be ...
  8. The Email Router service cannot connect to the Microsoft Dynamics CRM server or the Microsoft Dynamics CRM Online server ...
  9. The Email Router service cannot create a Microsoft Dynamics CRM event log. Verify that the account that is running the email ...
  10. The Email Router service could not run the service main background thread. The Email Router service cannot continue and will ...
  11. The Email Router service has excluded a configuration update action to give the Email Router Configuration Manager access ...
  12. The Email Router service that is installed is not a supported version. The Email Router version is earlier then expected ...
  13. The Email Router service that is installed is not a supported version. The Email Router version is later then expected by ...
  14. The email {0} could not be sent because the account of the mailbox {1} is locked. To unlock the account, log on to the email ...
  15. The entity referenced by this process includes a currency value that does not exist in your organization. Select a different ...
  16. The entityLogicalName isn't valid. This value can't be null or empty, and it must represent an entity in the organization. ...
  17. The Exchange item {0} was previously linked to Microsoft Dynamics CRM. Would you like to create a new record in Microsoft ...
  18. The exchange rate set for the currency specified in this record has generated a value for a base currency field that is larger ...
  19. The exchange rate set for the currency specified in this record has generated a value for a base currency field that is smaller ...
  20. The existing workflows were not created by using the Microsoft Dynamics CRM Workflow Manager. These workflows cannot be upgraded. ...
  21. The external party can access only records that are associated with the external party as defined in the system settings. ...
  22. The external party can access only records that are associated with the external party or records that are associated with ...
  23. The fax cannot be sent because there is no data to send. Specify at least one of the following: a cover page, a fax attachment, ...
  24. The fax cannot be sent because this type of attachment is not allowed or does not support virtual printing to a fax device. ...
  25. The FetchXML parameter "{0}" cannot obtain multiple values. Change the parameter "{0}" to a single value parameter, and try ...
  26. The field cannot be created because the maximum number of fields for this entity has been reached. Delete an existing field ...
  27. The field specified contains invalid characters. The following characters are not allowed: {0} Remove any invalid characters ...
  28. The field {0} is either a rollup field or a rollup dependent field or a calculated field. Such fields are not allowed in ...
  29. The field {0} is not securable as it is part of entity keys ( {1} ). Please remove the field from all entity keys to make ...
  30. The field {0}, belonging to the entity {1}, cannot be deleted because this field is used to send email messages, and the ...
  31. The file path including file name can be no longer than 255 characters and the file name cannot contain the following characters: ...
  32. The file provided was not uploaded. Click the back button, select the solution file, and try again. If the problem persists, ...
  33. The file size of the following attachments exceeds the maximum size of {0} kilobytes: {1}. The mail merge cannot be completed. ...
  34. The file specifies a field that does not exist in Microsoft Dynamics CRM: {0}, {1}. Fix this inconsistency, and then import ...
  35. The file specifies a list value that does not exist in Microsoft Dynamics CRM: {0}, {1}, {2}. Fix this inconsistency, and ...
  36. The file specifies a record type that does not exist in Microsoft Dynamics CRM: {0}. Specify a valid record type, and then ...
  37. The files could not be uploaded because the file {0} for the Email Router '{1}' is empty or does not contain valid xml data. ...
  38. The fiscal settings of your organization have changed since the time this goal was changed. You might want to realign the ...
  39. The folder can not be found. If you changed the automatically generated folder name for this document location directly in ...
  40. The folder could not be created. The Microsoft Dynamics CRM List component on the SharePoint site might be an earlier version. ...
  41. The folder name contains invalid characters. Please use a different name. Valid folder names cannot ends with the following ...
  42. The following application(s) {0} might interfere with Setup. Close these applications before you continue the installation. ...
  43. The following components are missing from your solution. Import will fail if these components don't exist already in the ...
  44. The following components in this solution require you to install the latest product updates, which are available only in ...
  45. The following data will be migrated from the Email Router for email processing using server-side synchronization. To continue, ...
  46. The following list shows files currently in use, followed by the application that is using the file. Close the application ...
  47. The following option set values could not be mapped:{0}This could lead to potential import failures. To continue, click OK. ...
  48. The following permissions are required for organizational unit and all child objects: read, write, modify permissions, create ...
  49. The following potential scheduling problems have been found. You might not be able to schedule this activity until these ...
  50. The following properties will take effect only after the component is exported and imported as part of a managed solution. ...
  51. The following server roles are missing from this deployment:{0}{1}{1}To resolve this issue, either add a new Microsoft Dynamics ...
  52. The foreign key constraints in the Microsoft Dynamics CRM database are not consistent with Microsoft Dynamics CRM foreign ...
  53. The Front End Server role group includes the server roles for running client applications and applications developed with ...
  54. The Full Server role group is the default server configuration that includes all Microsoft Dynamics CRM server roles on this ...
  55. The full-text indexes on the Microsoft Dynamics CRM database are not consistent with Microsoft Dynamics CRM full-text indexes. ...
  56. The Granularity column value is incorrect. Each rule part must be a name-value pair separated by an equal sign (=). For example: ...
  57. The HTTPS protocol is required for this type of request. Enable the HTTPS protocol and try again. For more information, see ...
  58. The Import Customizations process can take several minutes to complete depending on the number of items being imported. Once ...
  59. The import failed for this solution: {0}. One or more required components are not installed on your system (view details). ...
  60. The import file does not have the format that Dynamics CRM uses to map the data to CRM fields. It is possible some hidden ...
  61. The import file is invalid. XSD validation failed with the following error: '{0}'. The validation failed at: '.{1} >>>> {2}.'. ...
  62. The import file is invalid. XSD validation failed with the following error: '{0}'. The validation failed at: '.{1} >>>> {2}.'." ...
  63. The import has failed because the system cannot transition the entity form {0} from unmanaged to managed. Add at least one ...
  64. The import of the solution {0} failed. The following components are missing in your system and are not included in the solution. ...
  65. The Import Organization Wizard cannot connect to the SQL Server or cannot find an organization database on {0}. Verify that ...
  66. The Import Organization Wizard cannot import a database if its name contains any of the following characters: tilde (~), ...
  67. The incoming delivery method for a forward mailbox can only be set to None, or Server-Side Synchronization or Email Router. ...
  68. The incoming delivery method is set to Forward Mailbox. The email messages will be retrieved through the Forward Mailbox ...
  69. The incoming or outgoing email delivery method cannot be set to Microsoft Dynamics CRM for Outlook for a mailbox associated ...
  70. The incoming or outgoing email processing on Exchange email servers requires credentials. Setting a connection type of No ...
  71. The input arguments of the linked child dialog have been modified. Click Set Properties to verify and save the new mappings. ...
  72. The installation has failed. Your installation is unable to continue since the following pre-requisites have not been met. ...
  73. The installation of the DisplayText_ProductName was successfully completed.Before users can use this language you must provision ...
  74. The installed version of Microsoft CRM Sales for Outlook cannot be upgraded to Microsoft Dynamics CRM "4" client for Microsoft ...
  75. The installed version of Microsoft Dynamics CRM Server cannot be upgraded to Microsoft Dynamics CRM 2016 because it is an ...