Dynamics NAV 2015

  1. The synchronization failed because the %1 field in the %2 table is of an unsupported type. Please contact your system administrator. ...
  2. The synchronization failed because the %1 user has no entities to synchronize. Try again later and if the problem persists ...
  3. The synchronization failed because the %1 user has no entities to synchronize. Try to synchronize again. If the problem continues, ...
  4. The synchronization failed because the correlation for the %1 field of the %2 collection in the %3 entity cannot be found. ...
  5. The synchronization failed because the correlation for the %1 field of the %2 entity cannot be found. Try again later and ...
  6. The synchronization failed because the synchronization data could not be obtained from Microsoft Dynamics NAV for the %1 ...
  7. The synchronization failed because the synchronization data could not be obtained from Microsoft Dynamics NAV. Try again ...
  8. The synchronization failed because the synchronization data could not be sent from Microsoft Dynamics NAV. Try again later ...
  9. The synchronization failed because the synchronization data from Microsoft Dynamics NAV could not be sent. Try again later ...
  10. The synchronization failed because the synchronization data from Microsoft Outlook cannot be processed. Try again later and ...
  11. The synchronization folder must contain items that are of the same type with those you are synchronizing. Please make adjustments ...
  12. The synchronization for an item in the %1 entity completed with an error. Please try to synchronize this item again later. ...
  13. The synchronization has failed because the synchronization data from Microsoft Outlook cannot be processed. Try again later ...
  14. The system failed to publish or update the Database Server for Microsoft Dynamics NAV Classic Service Connection Point in ...
  15. The system failed to publish the Database Server for Microsoft Dynamics NAV Classic Service Connection Point in Active Directory. ...
  16. The system failed to publish the Database Server for Microsoft Dynamics NAV Classic Service Connection Point in Active Directory. ...
  17. The system failed to remove the Database Server for Microsoft Dynamics NAV Classic Service Connection Point from Active Directory. ...
  18. The system failed to remove the Database Server for Microsoft Dynamics NAV Classic Service Connection Point from Active Directory. ...
  19. The system failed to retrieve the global catalog from Active Directory. This can be caused by network problems, or it can ...
  20. The system failed to retrieve the global catalog from Active Directory. This can be caused by network problems, or it can ...
  21. The system failed to retrieve the object %2 from Active Directory. The system returned the following error: %1 Contact your ...
  22. The system failed to update the Database Server for Microsoft Dynamics NAV Classic Service Connection Point in Active Directory. ...
  23. The system failed to write the Database Server for Microsoft Dynamics NAV Classic Service Connection Point GUID to the registry. ...
  24. The system is ready to install the update.\ \You must not enter any data into Microsoft Dynamics NAV until the update has ...
  25. The system published the Database Server for Microsoft Dynamics NAV Classic Service Connection Point in Active Directory. ...
  26. The system removed the Database Server for Microsoft Dynamics NAV Classic Service Connection Point from Active Directory. ...
  27. The table changes were saved, but they contain schema changes that cannot be synchronized to the database with the Microsoft ...
  28. The taxable EC revenues reduced with the taxfree EC revenues reg. Art. 6 Abs. 2 differ from the total of declarable EC revenues.\KZ ...
  29. The tenant ID is invalid. A tenant ID must have a maximum length of 63 and can only contain the characters A-Z, a-z, 0-9, ...
  30. The tenant {0} is based on an earlier version of Microsoft Dynamics NAV. To connect to it with this version, you must synchronize ...
  31. The time '{0}' is not valid in the current time zone. For example, when the clock is adjusted forward, any time in the period ...
  32. The time zone identifier "{0}" was not recognized. Use quotation marks around the identifier and place the identifier after ...
  33. The timeout has expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ...
  34. The total length of first name, middle name and surname is %1 character(s)longer than the maximum length allowed for the ...
  35. The total of taxable revenues reduced by the total of taxfree revenues differs from the total of to be taxed revenues.\KZ ...
  36. The total of taxfree revenues is bigger than the total of taxable revenues.\KZ 011+012+015+016+017+018+019+020 > KZ 000+001-021. ...
  37. The total quantity of items in the warehouse is 0, but the Adjustment Bin contains a negative quantity and other bins contain ...
  38. The transaction cannot be completed because it will cause inconsistencies in the %1.1 table. Check where and how the CONSISTENT ...
  39. The transaction cannot be completed because it will cause inconsistencies in the {0} table. Check where and how the CONSISTENT ...
  40. The transaction type cannot be changed after a transaction has started. A transaction starts when the first database operation, ...
  41. The type library does not define a method or property called %3. Use the Symbol Menu to browse the methods and properties ...
  42. The type of the constant must be compatible with that of the %2.1 field, and the length of the constant must not exceed the ...
  43. The type of the constant must be compatible with that of the {2} field, and the length of the constant must not exceed the ...
  44. The Unit of Measure Code %1 for Item %2 does not exist. Identification fields and values: Production BOM No. = %3, Version ...
  45. The Unit of Measure Code %1 for Item %2 does not exist. Identification fields and values: Production BOM No. = %3, Version ...
  46. The upgrade table '{0}' created for table '{1}' cannot be used because the differences in their structure cannot be processed ...
  47. The UpgradeTableId set for old table {0} with ID {1} is not valid. The UpgradeTableId must be set to an existing compiled ...
  48. The URL must start with two forward slash (/) characters followed by at least two more forward slash (/) characters if no ...
  49. The user "{0}" cannot be deleted because the user has been logged on to the system. You must set the user's state to "Disabled". ...
  50. The user will not be able to sign in because no authentication data was provided. Are you sure that you want to close the ...
  51. The user will not be able to sign in unless you change the state to Enabled. Are you sure that you want to close the page? ...
  52. The value '{0}' contains wildcard characters. Wildcards cannot be used with operators =, ., >, =, and <=. If the value '{0}' ...
  53. The value for {0} ({1}) exceeds the maximum length that is defined by SQL Server. The value for {0} cannot exceed 128 characters. ...
  54. The value of %1 field must be a whole number for the item included in the service item group if the %2 field in the Service ...
  55. The value of %6 parameter %7 is outside of the permitted range. The current value is: %11.20. The permitted range is: from ...
  56. The value of the %1 field must either be %2 or match the synchronization direction of the %3 entity because these entities ...
  57. The value of {0} parameter {1} is outside of the permitted range. The current value is: {2}. The permitted range is: from ...
  58. The value on this property cannot be set. To set the property value, use the ShellObject that is associated with this property. ...
  59. The values are incompatible: The value '%4', which is of type '%1', is not compatible with the value '%104', which is of ...
  60. The variable %6 is defined more than once. An example could be: 'File' exists as both a data type and a global variable. ...
  61. The variable has the type %10.1. The counter in the FOR sentence should be a numeric, boolean, date, time, byte or char variable. ...
  62. The variable ID %1 for the variable %2 is reserved for C/SIDE-defined variables only. The minimum ID number allowed is %3. ...
  63. The VARIANT2DATE function has encountered a parameter that cannot be converted. Use either variant or date as the argument. ...
  64. The VARIANT2DATE function has encountered an argument that the program cannot convert. Use either variant or date as the ...
  65. The VARIANT2TIME function has encountered a parameter that cannot be converted. Use either variant or time as the argument. ...
  66. The VARIANT2TIME function has encountered an argument that the program cannot convert. Use either variant or time as the ...
  67. The Vendor Bill List %1 contains Vendor Bank Accounts without IBAN. The IBAN must be filled before you can create the payment ...
  68. The warehouse shipment was not created because an open warehouse shipment exists for the Sales Header and Shipping Advice ...
  69. The warehouse shipment was not created because the Shipping Advice field is set to Complete, and item no. %1 is not available ...
  70. The Windows account specified in '%1' does not have permission to run services on this computer. Please use another account ...
  71. The Windows Installer service is not accessible in Safe Mode. Try again when your computer is not in Safe Mode, or use System ...
  72. The witholding tax amount (field AU001019): %1, is greater than the maximum allowed value taxable base (field AU001018): ...
  73. The Word layout does not comply with the current report design (for example, fields are missing or the report ID is wrong).\The ...
  74. The Word layout does not comply with the current report design (for example, fields are missing or the report ID is wrong).\The ...
  75. The Word layout does not comply with the current report design (for example, fields are missing or the report ID is wrong).\The ...