Lync Server 2013

  1. The number of individual polling subscribe requests that were batched together in the call to RtcBatchQueryCategories sproc. ...
  2. The number of individual remote notification requests that were batched together in the call to RtcBatchDemuxRemoteNotifications ...
  3. The number of items returned does not match the number of items published. Cause: The number of items returned does not match ...
  4. The number of LookupUser API calls to resolve SIP users. LookupUser API may return cached data directly without querying ...
  5. The number of messages dropped at the external edge because a shared address space (cross-premise) configuration problem ...
  6. The number of messages dropped at the external edge because the domain is not locally supported and all federation is disabled. ...
  7. The number of messages dropped at the external edge because the domain resolved by DNS SRV to a server that is blocked in ...
  8. The number of messages dropped at the external edge because the federation type of the domain is incompatible with previous ...
  9. The number of messages dropped at the external edge because the user is not authorized to communicate with federated partners. ...
  10. The number of messages dropped at the external edge because the user is not authorized to communicate with public IM providers. ...
  11. The number of messages dropped at the external edge that cannot be routed to a hosting service because the domain is not ...
  12. The number of messages dropped at the external edge with a domain that resolved by DNS SRV to multiple FQDNs that match different ...
  13. The number of messages dropped at the external edge with an allowed partner domain that resolved by DNS SRV to a FQDN that ...
  14. The number of messages dropped because the domain of the Diversion user URI is not compatible with the domain of the To user ...
  15. The number of messages received from another forest that were dropped at the internal edge because the target user is not ...
  16. The number of messages that could not be routed because the message domain is not configured and does not appear to belong ...
  17. The number of per second LookupUser API calls to resolve SIP users. LookupUser API may return cached data directly without ...
  18. The number of remote user client messages dropped at the external edge because access for remote user clients is disabled. ...
  19. The number of requests currently in processing by application that have not yet been authenticated or are processed anonymously. ...
  20. The number of security records currently stored in the server. One security record is created for each user being authenticated. ...
  21. The number of SIP transaction or dialog state change events that are queued in SIP state machine waiting for processing of ...
  22. The number of time slices processed in the audio router per sec. This is the sum of all conferences. The value should be ...
  23. The number times a phone call to an Exchange UM server resulted in an error. These calls may have not failed from the caller's ...
  24. The older user are getting synchronized as part of current synchronization cycle for naming context %1 Source of replication ...
  25. The one to one enforcement in managed object is broken by the following relation: Agent Group "{0}" is linked with {1} managed ...
  26. The one to one enforcement in managed object is broken by the following relation: Agent Group "{0}" is linked with {1} managed ...
  27. The one to one enforcement in managed object is broken by the following relation: Queue "{0}" is linked with {1} managed ...
  28. The one to one enforcement in managed object is broken by the following relation: Queue "{0}" is linked with {1} managed ...
  29. The operation cannot continue because the Uri of the conference scheduling service is not available in the provisioning information. ...
  30. The operation failed due to a response from the server. For more information, examine the properties on the exception and ...
  31. The operation is invalid on an ApplicationEndpoint when a proxy has not been specified or the CollaborationPlatform does ...
  32. The outbound routing app was disabled. Cause: Lync Server configuration indicates that the Outbound Routing Application has ...
  33. The OutgoingFederation Application is waiting for the Lync Server to start. Cause: The OutgoingFederation Application is ...
  34. The parameter "{0}" needs to be a valid integer greater than or equal to {1} Kbps when {2} is set to {3} to enable an acceptable ...
  35. The parameter for remote computer cannot be used if the computer is not joined to the Lync Server Active Directory forest. ...
  36. The parameters selected for this report are not valid. Failed calls cannot be selected when this report is displayed by using ...
  37. The parameters selected for this report are not valid. Failed calls cannot be selected when this report is displayed by using ...
  38. The passive Match Making Service cannot connect to the active Match Making Service due to a security issue. Accessing the ...
  39. The passive Match Making Service cannot connect to the active Match Making Service. Access active Match Making Service: %1 ...
  40. The password expiration checking mechanism failed to initialize. The service will not be able to monitor the service account ...
  41. The per second rate of incomplete calls to Conferencing Attendant. This includes calls disconnected by the user and by the ...
  42. The per-second rate of anonymous user client messages dropped at the external edge because access for anonymous users is ...
  43. The per-second rate of authentication requests rejected because the they carried a proof Web Ticket issued by some other ...
  44. The per-second rate of authentication requests rejected because the they carried a proof Web Ticket issued outside of allowed ...
  45. The per-second rate of authentication requests that were challenged because they did not have expected credential information. ...
  46. The per-second rate of connections rejected at the internal edge from servers not configured in the internal servers list. ...
  47. The per-second rate of incoming requests dropped because they could not be processed (due to bad headers, insufficient routing ...
  48. The per-second rate of incoming responses dropped because they could not be processed (due to bad headers, insufficient routing ...
  49. The per-second rate of messages dropped at the external edge because a shared address space (cross-premise) configuration ...
  50. The per-second rate of messages dropped at the external edge because hosting of users on multiple deployments is disabled. ...
  51. The per-second rate of messages dropped at the external edge because the destination domain is not hosted by this service. ...
  52. The per-second rate of messages dropped at the external edge because the domain is not locally supported and all federation ...
  53. The per-second rate of messages dropped at the external edge because the domain resolved by DNS SRV to a server that is blocked ...
  54. The per-second rate of messages dropped at the external edge because the federation type of the domain is incompatible with ...
  55. The per-second rate of messages dropped at the external edge because the user is not authorized to communicate with federated ...
  56. The per-second rate of messages dropped at the external edge because the user is not authorized to communicate with public ...
  57. The per-second rate of messages dropped at the external edge that cannot be routed to a hosting service because the domain ...
  58. The per-second rate of messages dropped at the external with a domain that resolved by DNS SRV to multiple FQDNs that match ...
  59. The per-second rate of messages dropped at the external with an allowed partner domain that resolved by DNS SRV to a FQDN ...
  60. The per-second rate of messages dropped because the domain of the asserted identity URI is not compatible with the source. ...
  61. The per-second rate of messages dropped because the domain of the boss (on-behalf-of) URI is not compatible with the source. ...
  62. The per-second rate of messages dropped because the domain of the Diversion user URI is not compatible with the domain of ...
  63. The per-second rate of messages received from another forest that were dropped at the internal edge because the target user ...
  64. The per-second rate of messages that could not be routed because the message domain is not configured and does not appear ...
  65. The per-second rate of outbound messages dropped at external edge because the destination domain is internally supported. ...
  66. The per-second rate of remote user client messages dropped at the external edge because access for remote user clients is ...
  67. The per-second rate of requests that were routed based on route headers received from a server explicitly authorized to provide ...
  68. The per-second rate of security record creation by the server. One security record is created for each user being authenticated. ...
  69. The per-second rate of send operations that could not be buffered by the networking stack (exceeded buffer space limit imposed ...
  70. The per-second rate of send operations that were buffered by the networking stack and completed immediately (without blocking). ...
  71. The per-second rate of the connection establishment. Connection is considered established when peer credentials are verified ...
  72. The per-second rate of the connections dropped because the peer failed to exchange valid data with the server within establishing ...
  73. The per-second rate of the connections that were refused with Service Unavailable response because the server was overloaded. ...
  74. The percentage of the content from the sharer that did not reach the viewer (eventually overwritten by fresher content). ...
  75. The permissions set for this meeting require you to end your audio call before you can join by using the meeting link. Please ...