Microsoft KB Archive/883645

= The Licensing Logging service cannot find the domain controller and you cannot manage licenses when the License Logging service starts on a Windows Server 2003-based computer =

Article ID: 883645

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition

-





SYMPTOMS
When you try to use the License Logging service on a Microsoft Windows Server 2003-based computer, the following symptoms may occur when the License Logging service starts:
 * The License Logging service cannot find the domain controller.
 * You cannot manage licenses.



CAUSE
This behavior may occur when the License Logging service starts and then the Llssrv.exe process calls the DsGetDcName function. When this call occurs, the DsGetDcName function may return the following error message, based on the timing of the License Logging service status:

ERROR_NO_SUCH_DOMAIN

If the DsGetDcName function returns this error message, the Llssrv.exe process cannot find the domain controller, even if the Llssrv.exe process is running on the domain controller. Therefore, the Llssrv.exe process cannot find the master license server. A remote procedure call (RPC) exception occurs.



WORKAROUND
To work around this behavior, restart the License Logging service or do not use the License Logging service on a Windows Server 2003-based computer.

Note By default, the License Logging service is disabled in Windows Server 2003.

