Log management tool fails to start

On Windows™ operating systems, the log management tool might fail to start from Web Administration Tool. This problem is related to user privileges.

On Windows systems, the correct way to start the directory server and administration server is through services. However, processes that are started through services are always run with the SYSTEM user's privileges, regardless of the login credentials of the user.

For example, if you create a directory server instance, myinst1, log in as the myinst1 user, and start the server and administration server by using the services, then the processes are run with the SYSTEM user's privileges. In this scenario, the log management tool, idslogmgmt, does not work if it is started or stopped from Web Administration Tool. The reason is because log management requires Web Administration Tool to be started or stopped by using the instance owner's credentials. The start or stop log management request from Web Administration Tool goes to the administration server, which is running as the SYSTEM user. Therefore, starting or stopping the log management tool through the administration server fails.

If the administration server is started from the command line by using the credentials of myinst1, then the process would run with the myinst1's privileges. Therefore, starting or stopping the log management tool by using Web Administration Tool works.