Lync Server 2010

  1. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 Cause: Media file ...
  2. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 culture: %2 Cause: ...
  3. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 culture: %2 Cause: ...
  4. Mediation Server cannot reach the Gateway. Additional failures will not be logged. Cannot reach Gateway: %1 Cause: Gateway ...
  5. Mediation server caught an exception that it never expected. The exception may have side-effects where Mediation server cannot ...
  6. Mediation Server could not apply settings changes. The settings were ignored. Setting Name: %1 Property Description: %2 Old ...
  7. Mediation Server does not support changing these settings dynamically. The settings were ignored. Setting Name: %1 Property ...
  8. Mediation Server encountered a problem while trying to apply setting changes. Setting Name: %1 Property Description: %2 Old ...
  9. Mediation Server encountered an internal error but ignored the failure. Server will keep running. Exception: %1 Cause: Internal ...
  10. Mediation Server encountered an invalid setting that has been ignored. Setting: %1 Reason: %2 Cause: Settings configured ...
  11. Mediation Server failed to start because it was unable to contact the Management Store. Exception: %1 Cause: The Management ...
  12. Mediation server hit an internal exception from the signaling layer. The current call may be dropped. Mediation server will ...
  13. Mediation Server service could not be started. Exception: %1 Cause: Internal error or a previous failure. Resolution: Examine ...
  14. Mediation Server was able to contact the A/V Authentication Service. However, there were no valid relay candidates returned ...
  15. Members have read access to Lync Server 2010 configuration and are placed in the Local Administrators group of survivable ...
  16. Members of this group can enable and disable users for Lync Server 2010, move users, and assign existing policies to users. ...
  17. Members of this group can view the deployment, including user properties and policies, and can execute specific troubleshooting ...
  18. Members of this group can view the Lync Server 2010 deployment, including server information, in order to monitor deployment ...
  19. Members of this group have the lowest level of rights for E911 management. They can create E911 locations and network identifiers, ...
  20. Members of this group receive the same rights as RTCUniversalUserReadOnlyGroup to read Lync Server attributes on users with ...
  21. Message Queuing Server (MSMQ) and Message Queuing Directory Service Integration must be installed before attempting to install ...
  22. Microsoft Lync Server 2010, File Transfer Agent service could not be started. Exception information: %1. Cause: Startup errors. ...
  23. Microsoft Lync Server 2010, File Transfer Agent service encountered an error while accessing a file share and will continuously ...
  24. Microsoft Lync Server 2010, File Transfer Agent service is stopping. Reason: A shutdown request of type '%1' was received. ...
  25. Microsoft Lync Server 2010, File Transfer Agent service is stopping. Reason: Connection point in AD changed from '%1' to ...
  26. Microsoft Lync Server 2010, File Transfer Agent service is stopping. Reason: Machine '%1' is in pool '%2' that does not have ...
  27. Microsoft Lync Server 2010, File Transfer Agent service is stopping. Reason: Machine '%1' is not defined in the topology. ...
  28. Microsoft Lync Server 2010, File Transfer Agent successfully registered with the back-end, but a schema or sproc version ...
  29. Microsoft Lync Server 2010, File Transfer Agent will not be functional until the AD connection point refers to a central ...
  30. Microsoft Lync Server 2010, File Transfer Agent will not be functional until the AD connection point refers to a central ...
  31. Microsoft Lync Server 2010, Master Replicator Agent service could not be started. Exception information: %1. Cause: Startup ...
  32. Microsoft Lync Server 2010, Master Replicator Agent service encountered an error while accessing a file share and will continuously ...
  33. Microsoft Lync Server 2010, Master Replicator Agent service is stopping. Reason: A shutdown request of type '%1' was received. ...
  34. Microsoft Lync Server 2010, Master Replicator Agent service is stopping. Reason: Connection point in AD changed from '%1' ...
  35. Microsoft Lync Server 2010, Master Replicator Agent service is stopping. Reason: Machine '%1' is in cluster '%2' that does ...
  36. Microsoft Lync Server 2010, Master Replicator Agent service is stopping. Reason: Machine '%1' is not defined in the topology. ...
  37. Microsoft Lync Server 2010, Master Replicator Agent successfully registered with the back-end, but a schema or sproc version ...
  38. Microsoft Lync Server 2010, Master Replicator Agent will not be functional until the AD connection point refers to a central ...
  39. Microsoft Lync Server 2010, Master Replicator Agent will not be functional until the AD connection point refers to a central ...
  40. Microsoft Lync Server 2010, Replica Replicator Agent received too many unsupported version of data packages from central ...
  41. Microsoft Lync Server 2010, Replica Replicator Agent Service could not be started. Exception information: %1. Cause: Startup ...
  42. Microsoft Lync Server 2010, Replica Replicator Agent service encountered an error while accessing a file share and will continuously ...
  43. Microsoft Lync Server 2010, Replica Replicator Agent successfully registered with the back-end, but a schema or sproc version ...
  44. Microsoft SCP cannot be deleted for distinguished name (DN) "{0}". Make sure that no child container exists underneath the ...
  45. Microsoft Speech failed to generate the voice. Error message: %1 Language used: %2 Cause: Microsoft Speech might not have ...
  46. Microsoft Update offers security and important updates for Windows and other Microsoft software, including Lync Server 2010. ...
  47. Migrating an existing central management store from one SQL instance to another is a process that involves several steps. ...
  48. Minimum listening quality mean opinion score (MOS) of the audio received based on the packet loss, jitter, and codec used. ...
  49. Minimum listening quality mean opinion score (MOS) of the audio received based on the speech level, noise level, device characteristics, ...
  50. Minimum listening quality mean opinion score (MOS) of the audio sent based on the speech level, noise level, and glitches ...
  51. Missed call notifications cannot be sent. An attempt to use an Exchange UM Server for a missed call notification failed: ...
  52. Missing required service listening port setting in application configuration. Please add a key for this setting which specifies ...
  53. Modify the user account control flags as required for the account in question. You can try running New-CsKerberosAccount ...
  54. More than one Active Directory Attribute contains the same integer ID. Active Directory Attribute name: %1 Attribute index: ...
  55. More than one AD Attribute contains the same AD attribute name. AD Attribute name: %1 Attribute index: %2 Cause: The AbAttribute ...
  56. More than one AD Attribute identified as the groupType attribute. AD Attribute name: %1 Attribute index: %2 Cause: The AbAttribute ...
  57. More than one AD Attribute identified as the manager attribute. AD Attribute name: %1 Attribute index: %2 Cause: The AbAttribute ...
  58. More than one AD Attribute identified as the proxyAddresses attribute. AD Attribute name: %1 Attribute index: %2 Cause: The ...
  59. More than one valid certificate was found matching the computed subject and alternative names. Specify a certificate by using ...
  60. More than one {0} found in Active Directory with altSecurityIdentities attribute set to:{1}. Unable to determine the usage; ...
  61. More than one {0} found in Active Directory with sAMAccountName:{1}. Unable to determine the usage; Provide the identity ...
  62. Move operation failed for conference directory with ID "{0}". Cannot perform a rollback because data migration might have ...
  63. Move user operation failed. User: %1 Destination pool: %2 Error: 3 Cause: User being moved is not provisioned in the destination ...
  64. Move user operation failed. User: %1 New destination Pool DN: %2 Previous destination pool DN: %3 Cause: Destination pool ...
  65. Move user operation failed. User: %1 Source pool: %2 Destination pool: %3 Cause: Destination pool incompatible with source ...
  66. Moving the current back end location from "{0}" to "{1}\{2}" will cause problems with existing hosts unless you perform a ...
  67. MTLS connection with Web Conferencing Server closed due to throttling. FQDN of Web Conferencing Server server is %1. Cause: ...
  68. Multiple Active Directory compatibility entries were found for conference directory with ID "{0}". Determine which of the ...
  69. Multiple EUM addresses in proxyAddresses field is detected for the user %1. A user can have at most one EUM address in proxyAddresses ...
  70. Multiple federated Edge Servers have been defined in the current topology. Specify the ProxyPool parameter to indicate which ...
  71. Multiple incoming connections on internal edge from non-internal servers. In the past %1 minutes the server received %2 incoming ...
  72. Multiple invalid incoming certificates. In the past %1 minutes the server received %2 invalid incoming certificates. The ...
  73. Multiple policies per policy type is not allowed. URI: %1 The DN of the object is: %2 This update came from domain: %3 Cause: ...
  74. Multiple pool objects found in Active Directory with the name {0} or FQDN {1}. Ensure your deployment does not use conflicting ...
  75. Multiple requests for the default Dial Plan failed because a default is not defined. At least %1 different users have requested ...