Some requests were rejected as they exhausted the Max-Forwards limit. In the past %1 minutes, the protocol stack rejected %2 requests that were looping and exhausted the Max-Forwards limit. The last one was this SIP message: %3 Cause: This usually indicates an incorrect server configuration or a bad routing rule. Resolution: None needed unless the number of reported errors is large (> 100). This usually indicates an incorrect server configuration or a bad routing rule. Check whether all server routing rules are properly configured.
Some features are carried out by other server roles. You can enable those features by associating them with the Director ...
Some features are carried out by other server roles. You can enable those features by associating them with the Front End ...
Some features might not be working because we couldn't verify your credentials. Please exit the meeting and rejoin for full ...
Some records from a host name query were ignored. Host name query for the name %1 returned %2 records. A selection of %3 ...
Some requests were rejected as they exhausted the Max-Forwards limit. In the past %1 minutes, the protocol stack rejected ...
Some sites in your topology still contain sample data. Sample data will not be exported to Topology Builder. Are you sure ...
Sorry, but you're configured for hybrid voice, so there are no Lync Online settings available on this page. You can administer ...
Source item does not exist on backup pool and it will not be added in a future synchronization (Item Id: "{0}", Document ...
Source pool does not have any items with greater partial version than items on the backup pool and the batches version say ...