Lync Server 2013
- Cmdlet cannot read from a path because it is running remotely. You can provide input by using byte stream. For example: Get-Content ...
- Cmdlet is running remotely. Read the input from a local file and write it in the form of bytes. For example: Get-Content ...
- Cmdlet is running remotely. Read the output in the form of bytes and write to your local file. For example: Export-CsConfiguration ...
- Cmdlet is running remotely. Read the output in the form of bytes and write to your local file. For example: Export-CsGroupChatData ...
- Cmdlet is running remotely. Read the output in the form of bytes and write to your local file. For example: Export-CsLisConfiguration ...
- CMS replica is not available. %1 failed to connect to CMS replica. Cause: CMS replica DB engine is not available. Resolution: ...
- Collaboration platform has failed to provision the data. Collaboration platform has failed to provision the data because ...
- Comparison of element "{0}" failed between primary and replica. Value found on primary "{1}", value found on replica "{2}". ...
- Complete the rename or removal of the first Lync Server pool before assigning the fully qualified domain name (FQDN) to a ...
- Compliance enables archiving a comprehensive record of activity on the system. If compliance is enabled, an adapter must ...
- Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
- Conf Services does not have a Web Services dependency. Topology is not configured correctly, cannot continue with backup ...
- Conference access number refers to a location profile with the description set to null. This is an invalid configuration. ...
- Conference directory is not found in backend. If this conference directory was recently created or moved, wait for replication ...
- Conference directory with ID "{0}" cannot be moved. The Active Directory compatibility data is in a state that is incompatible ...
- Conference directory with ID "{0}" is already being moved to service "{1}". That move operation must complete before you ...
- Conference directory with ID "{0}" is already homed on service "{1}". If you want to move the conference directory to another ...
- Conference directory with ID "{0}" is currently in the process of moving. No other operations can be performed until the ...
- Conference directory with ID "{0}" is missing compatibility data. Use the New operation to recreate the compatibility information ...
- Conference directory with ID "{0}" is not empty. If you delete this conference directory, you will affect users who use dial-in ...
- Conference directory with ID "{0}" was deleted, but some unused stale conference data was left behind on the back-end server. ...
- Conference directory with ID "{0}" was moved, but some stale conference data was left behind on the former service (DCOM ...
- Conference directory with ID "{0}" will not be checked to see if it is safe to delete because the operation was invoked with ...
- Conference escalation failed because the existing party did not join the conference. Additional participants cannot be added. ...
- Conference rollover failed. Conference: '%1' MCU Type: '%2' Existing Mcu: '%3' Cause: Conference rollover occurs when an ...
- Conference session could not recover from route set failure because its signaling session or subscription session is already ...
- Conferencing Announcement Service configuration has changed. No Conferencing Announcement Service AOR currently available ...
- Conferencing Announcement Service could not negotiate TLS and failed to establish a SIP connection. Reason=%1. Front End=%2. ...
- Conferencing Announcement Service did not detect a private contact object. %1. Cause: Administration issues. Resolution: ...
- Conferencing Announcement Service failed to establish a connection on the primary application endpoint. Conferencing Announcement ...
- Conferencing Announcement Service lost connection with the Microsoft Lync Server 2013 Front End. Front End=%1. Cause: This ...
- Conferencing Attendant could not negotiate TLS and failed to establish a SIP connection. Reason=%1. Front End=%2. Cause: ...
- Conferencing Attendant did not detect a private contact object. Cause: Administration issues. Resolution: If the application ...
- Conferencing Attendant failed to establish a connection on the primary application endpoint. Conferencing Attendant will ...
- Conferencing Attendant failed to join the conference. %1 Cause: Administration issues. Resolution: Verify that Conferencing ...
- Conferencing Attendant lost connection with the Microsoft Lync Server 2013 Front End. Front End=%1. Cause: This issue may ...
- Conferencing file is too big to be uploaded. User: %1 Error: %2 Cause: The conference file has exceeded the maximum allowed ...
- Conferencing sessions where the user sees an error that is not expected to happen in a well configured system (for example, ...
- Conferencing sessions where the user sees an error that might be expected to happen in a well configured system (for example, ...
- Configure these settings so that this user can set up audio conferences for others to participate in by using a traditional ...
- Configure these settings to allow calls between Lync and the traditional telephone network for this user. To edit the phone ...
- Configured application uri for script-only application did not match application uri in path. Path: %1 Cause: Powershell ...
- Congratulations %1!s!, the setup process is complete! Press Next to customize your settings or Done to start using your phone. ...
- Connection attempt to at least one service in a pool failed. Connection attempts to the following services have failed. Another ...
- Connection to back-end database succeeded, but failed to execute registration stored procedure on the back-end. This error ...
- Connection to Exchange is unavailable because you signed in directly on the phone. Do you want to sign out and sign in again ...
- Connection to Exchange is unavailable due to invalid network credentials. Do you want to sign out and sign in again using ...
- Connection to Exchange is unavailable due to invalid network credentials. Do you want to sign out and sign in again using ...
- Connection to Microsoft Exchange is unavailable due to invalid network credentials. For details, press the Menu button and ...
- Connection to Microsoft Exchange is unavailable due to invalid network credentials. For details, tap on Notifications seen ...
- Consult administration documentation to learn how Topology Builder is used to prepare a Lync Server deployment for final ...
- Consult the details of the error for more information on what object was missing. Re-run Enable-CSComputer to create this ...
- Consult the details of the error for more information on what object was missing. Re-run Enable-CSTopology to create this ...
- Consult the details of the error for more information on what object we failed to create. Check rights needed to create the ...
- Consult the details of the error for more information on what objects were found. Determine which of the extra entries are ...
- Consult the details of the error for more information on what permission was missing from what object. Re-run Enable-CSComputer ...
- Consult the details of the error for more information on what permission was missing from what object. Re-run Enable-CSTopology ...
- Consult the details of the error for more information on what permissions we failed to set. Check rights needed to add permissions ...
- Consult the details of the error for more information on what setting was incorrect. Re-run Enable-CSComputer to fix this ...
- Consult your Lync Server documentation to learn how to move or disable objects still homed on the pool. To find those objects, ...
- Consult your Lync Server documentation to learn how to move or disable objects still homed on the pool. To find those objects, ...
- Consult your Lync Server documentation to learn how to remove analog devices that are still using the gateway. To find those ...
- Contact list export from Exchange failed when running the command on Lync Server: {0}. Contact list export call from Exchange ...
- Contact list export from Exchange failed when running the command on Lync Server: {0}. Contact list export from Exchange ...
- Contact list export from Exchange failed when running the command on Lync Server: {0}. Contact list export from Exchange ...
- Contact list export from Exchange failed when running the command on Lync Server: {0}. Contact list export from Exchange ...
- Contact Object is not homed properly. Contact Object %1 is not homed properly. Error: 2. Cause: This could happen if the ...
- Corrupted journal files were fixed. Microsoft Lync Server 2013, Backup Service data content backup module does not detect ...
- Could not access update directory. Directory: %1 Cause: Expected directory does not exist. Resolution: Missing an expected ...
- Could not add an entry to the host authorization table. Attempt to add %1 to the host authorization table failed. Requests ...
- Could not compare if item (item id: "{0}", document name: "{1}") had a duplicate or if item with same key had different owners. ...
- Could not connect to a server in the pool. Failed to connect to a server in pool %1. Continue to retry. Cause: If the servers ...
- Could not connect to Machine:"{0}"using WMI. This might be stale data in WMI data repository or Active Directory. Please ...
- Could not connect to server. Failed to connect to server FQDN %1 (%2:%3) Type %4 in pool %5. Continue to retry. Cause: If ...
- Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...