Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article. User name used to access the target managed server, if different from the userOnGateway i. Boolean: if the target managed server trusts the gateway and credentials are delegated from the user's client machine. Boolean: if the user accessed the server using LAPS credentials.
This message indicates that a security exception was thrown while verifying the SPN. An error occurred while reading the configuration of the Recovery database. The connection string to the Recovery database is not configured. Verify the given registry key value. If you see any of the following messages, verify whether the app pool credentials from the IIS server can make a connection to the recovery database:. An error occurred while reading the configuration of the Compliance database.
The connection string to the Compliance database is not configured. Verify the value of this registry key. If you see any of the following messages, verify whether the app pool credentials from the IIS server can make a connection to the compliance database:.
Verify that the app pool account can connect to the compliance or recovery databases. Confirm that it has permissions to run the GetVersion stored procedure. It also queries the ApplicationHost. This error message indicates that it couldn't communicate with Active Directory, or it couldn't load the ApplicationHost. Verify that the app pool account has permissions to query Active Directory or the ApplicationHost. Also verify the site binding entries in the ApplicationHost. For the System.
UnauthorizedAccessException , verify that the app pool account has access to performance counter APIs. Indicates successful connection to the recovery or compliance database from the helpdesk website. Indicates successful connection to the recovery or compliance database from the self-service portal. Indicates that the SPNs required for the helpdesk website are correctly registered against the executing account. For more information on using these logs, see BitLocker event logs. These logs record events as they happen on your server via a user process, or a running process.
This information is very helpful in troubleshooting services and other issues, or to investigate a security problem. Windows references logs as events, while Plesk and most other systems call them logs.
For standardization, they call them logs in this article. Follow below to see how you can use the event viewer to review your logs and investigate issues. The first step in accessing the Event Viewer is to connect to your server. Gaining access to the server is accomplished through the Console button in Manage, or through a manual RDP connection. Once you have connected to your Windows server , you will need to log in to your administrator account.
Once logged in, click the Start menu, then Event Viewer. The event viewer is a system application included on all versions of Windows servers. This program allows you to view logs recorded to it by applications and the system. The event viewer has four main views you will see when you first launch the application:.
For this article, we will focus mainly on the Windows Logs. The project you are hosting may have you reference the application logs for programs you use, which may be outside the scope of this article. All logs are assigned an event level. This event level denotes the severity or seriousness of any issues noted in the logs. The default view of the list below is by acuity.
You will also notice that Windows logs are broken down into categories. These classifications are listed below, along with some quick info about each section. Application - Logs related to drivers and other system components. Security - Logs pertaining to successful and failed logins, and other authentication requests.
0コメント