The issue occurs because the Mailbox Transport service creates log files that are not in the path of %exchangeinstallpath%\logging. In an Exchange installation where there is no drive D, the log files cannot be created, and therefore event ID 6003 is logged.

For example, you may receive the following error message when you try to access a remote share in Windows 8 or Windows Server 2012: Cannot access a remote file share. This can make it difficult to troubleshoot the Server Message Block (SMB) protocol and remote storage issues.

Fixes an issue in which the descriptions of event logs are not displayed correctly in the security event log. This issue occurs when you log on to a remote computer that is running Windows Server 2008 SP2 or Windows Vista SP2.

To mitigate this issue, implement one of the following solutions listed in order of preference: Enable support for Extend Master Secret (EMS) extensions when performing TLS connections on both the client and the server operating system.

Get error logs for troubleshooting purposes. Find the log file, select a logging level in Skype for Business, and enable or disable event logging in Windows.

Cause. This problem occurs if the Registry Event Source Flag is set to 0. Workaround. To work around this problem, use one of the following methods: Set the Server Audit Events to be written to a file instead of to the SQL Server Security log.

Cause. This issue occurs because the access check fails between the Client Access server and the Microsoft Office Store: (https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15). Resolution. If the server that's running Exchange Server has an internet connection, check the proxy server to see whether the following URL is enabled for access:

When the handle is lost, the Alert Engine "loses its place" in the event log and sends emails for ALL errors (for which there are alerts defined) in the Application event log after the new event log handle is obtained. Resolution. This fix is included in the following updates: Cumulative Update 3 for SQL Server 2017.

Symptoms. In your Log shipping configuration, the log backup process may fail because of underlying storage and infrastructure issues. In this situation, the log backup process is retried, and this could overwrite a potentially valid log backup file.

Symptoms. When you use a third-party backup software to perform a transaction log backup in Microsoft SQL Server 2012, a failed backup may result in breaking transaction log chain, and you cannot receive the error message.