Office System 2010

  1. The LobSystem has SystemWildcard or SystemWildcardEscapeFormat Properties with either invalid values or non-String Types. ...
  2. The LobSystem SystemUtility TypeName describes a class that does not implement Microsoft.Office.Server.ApplicationRegistry.Runtime.ISystemUtility. ...
  3. The LobSystem with Name '{0}' is of Type 'WebService' but does not include a System.Web.Services.Protocols.HttpWebClientProtocol ...
  4. The LobSystemInstance (External System Instance) '{0}' defines Property '{1}' of Type '{2}'. {1} of Type '{2}' must also ...
  5. The LobSystemInstance (External System Instance) '{0}' defines Property with Name '{1}' and value '{2}' must also define ...
  6. The LobSystemInstance (External System Instance) Property '{0}' has a value that prohibits '{1}' in the connection string. ...
  7. The LobSystemInstance (External System Instance) Property '{0}' has a value that requires '{1}' in the connection string. ...
  8. The LobSystemInstance (External System Instance) Property for the Single Sign-on provider specifies an invalid Type '{0}' ...
  9. The LobSystemInstance (External System Instance) Property with Name '{0}' and value '{1}' cannot be used for '{0}'. Type ...
  10. The LobSystemInstance (External System Instance) Property with Name '{0}' and value '{1}' contains invalid XML and cannot ...
  11. The LobSystemInstance (External System Instance) Property with Name '{0}' and value '{1}' is not supported in the current ...
  12. The LobSystemInstance (External System Instance) Property with Name '{0}' and value '{1}' represents a type which does not ...
  13. The LobSystemInstance (External System Instance) Property with Name '{0}' has a metadata exchange URI scheme '{1}' that is ...
  14. The LobSystemInstance (External System Instance) Property with Name '{0}' has invalid value '{1}'. Property with Name '{0}' ...
  15. The LobSystemInstance property for the single sign-on provider specifies an invalid Type '{0}' that does not implement M ...
  16. The LobSystemInstance Property with Name '{0}' has an invalid value '{1}'; it cannot be interpreted as a supported Database ...
  17. The LobSystemInstance with Name '{0}' is using a reserved Property named 'LobSystemName' whose value is not the same as its ...
  18. The local computer does not have enough space to download and store the found shapes. Increase the available space on the ...
  19. The local copy that you were editing has moved. To locate the file, click Browse. To open the last known version from the ...
  20. The local copy that you were editing has moved. To locate the file, click Browse. To open the last known version from the ...
  21. The local file system location of the workbook file cache. No value indicates that a subdirectory in the system temporary ...
  22. The local message file is corrupt and can't be read. Do you want to replace the local file with a new copy from the server? ...
  23. The local portion of the phone number cannot be determined. The number of digits may not be correct or the spacing between ...
  24. The local portion of the phone number cannot be determined; the number of digits may not be valid or the spacing between ...
  25. The local portion of the phone number was not found. If you entered the phone number using letters, change them to digits. ...
  26. The local resource ^1 cannot be replaced with the enterprise resource of the same name due to one of the following conflicts:} ...
  27. The local resource ^1 has the same name as an enterprise resource or user, and the name must be changed before the project ...
  28. The local var name '|1' is invalid. Local variable names must be less than or equal to 64 characters in length, may not start ...
  29. The locale %1 could not be found. As a result, a new workbook was created using the %2 workbook template. To enable workbooks ...
  30. The locale id, if this is not set then the locale of the user executing the command is used, if that doesn't exist the server ...
  31. The locally cached projects are listed below. On delete, selected projects are deleted from the local cache. Projects on ...
  32. The location entered is not a site collection relative path, or the specified Site Directory does not exist in the current ...
  33. The location field exceeds the limit of 99 characters. Type fewer characters before you click OK or excess letters will be ...
  34. The location that you have chosen to save this workbook may have different security settings. This may cause your workbook ...
  35. The location you chose to save this workbook is not a Trusted Location. You can only save workbooks to Trusted Locations. ...
  36. The location you have entered is not an HTTP URL. Web Folder locations must be HTTP URLs which point to a folder on a Web ...
  37. The location you have entered points to an individual file on a Web server. Web Folder locations must point to a folder, ...
  38. The location you selected for your new Document Workspace is a restricted or non-trusted site. If you are certain that this ...
  39. The location you specified is not a SharePoint site (version 2 or later) on your local intranet. Enter a valid location and ...
  40. The location, '^0', is not valid. Type the valid name and location, such as C:\location\file name, or try browsing to the ...
  41. The lock status, quota template or individual quota values for this site collection cannot be changed because the content ...
  42. The log file '|1' already exists. Would you like to overwrite this file? (If you click No, the Viewer will append conflict ...
  43. The logo is being used by another file and cannot be saved as part of your business information. Close other instances of ...
  44. The lookup field is not valid because the reference list or list column does not exist. Delete the field and recreate it. ...
  45. The lookup field was not created. The database engine could not lock the table '|1' because it is already in use by another ...
  46. The lookup row source SQL statement must include the source table primary key field and that field must be the bound column. ...
  47. The lookup table data entry option is set to restrict the field to only those items in the list. This may invalidate some ...
  48. The lookup table is already checked out to you for modification in another session. If you have the lookup table checked ...
  49. The lookup table is already checked out to you for modification in another session. Would you like to force check-in the ...
  50. The lookup table is currently in use by a custom field and cannot be deleted. Delete the custom field referencing the lookup ...
  51. The lookup table is in use by one or more custom fields. Delete the custom fields that are referencing the lookup table and ...
  52. The lookup table specified for the custom field is of a different type. Specify a lookup table that is of the same type as ...
  53. The lookup table specified for the custom field is of a different type.} Specify a lookup table that is of the same type ...
  54. The lookup table value contains separator characters. Do not specify separator characters from the mask in the lookup table ...
  55. The lookup table value specified does not fit the mask for the level. All lookup table values have to fit the mask for that ...
  56. The lookup table value specified does not fit the mask for the level.} All lookup table values have to fit the mask for that ...
  57. The Lookup Table will not be added to the enterprise}If a lookup table name is not provided the lookup table associated with ...
  58. The lookup that you defined is not guaranteed to return a single value. If more than one value is returned, only the first ...
  59. The macro action BrowseTo requires a valid Path argument. A valid Path argument is of the form: MainForm1.Subform1>Form1.Subform1 ...
  60. The Macro Conversion Wizard can't be started.@This wizard may not be installed, or this wizard has been disabled.@To reenable ...
  61. The macro or function set to the BeforeUpdate or ValidationRule property for this field is preventing |9 from saving the ...
  62. The macro \"^1\" cannot be found.}Try the following: \- Verify that you spelled the macro name correctly. \- If the global ...
  63. The macros in this file do not match the digital signature. Only a macro virus would cause this. Please scan for viruses, ...
  64. The macros in this template are in Word 2.0 format and will not be converted. Do you want to continue to open the template? ...
  65. The mail merge could not be completed. Check that the recipient list is not empty and that the cursor is placed in the main ...
  66. The Mail Merge Wizard cannot continue because the database is in exclusive mode. Close and reopen the database to run this ...
  67. The mail session could not be opened. You may be out of memory. Close other applications, and then try again. You may also ...
  68. The main program is not responding. Microsoft Graph is unable to update |. To correct the problem, try the following: Switch ...
  69. The main program is trying to close Microsoft Graph, but Microsoft Graph has an open dialog box. Switch to Microsoft Graph, ...
  70. The Managed Metadata Service is inaccessible because the current web application has not been granted permissions to access ...
  71. The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service ...
  72. The managed path you specified is in use by a site collection. Specify a different managed path name or delete the site collection ...
  73. The ManagedLinkAttribute is only supported on properties of type String or Uri, or on properties that implement IList and ...
  74. The map could not be exported, so the data was not exported. Use XmlMap.IsExportable to determine whether the map can be ...
  75. The MAPI store '|' is known but is not available in the current profile. This can occur if you use a profile that is designed ...