Give the following rights to the Windows user
running WebLogic Server:

Act as part of the
operating system.

Create a token
object.

Replace a process level
token.

Verify that the Windows user running WebLogic
Server is a member of the Administrators group.

Reboot Windows NT to ensure all the
modifications take effect.

Verify that the Logon as System Account option
is checked. Note that the Allow System to Interact with Desktop option
does not need to be checked. Running the Windows NT Security realm under
a specific Windows NT user account does not work.

To update the rights in Windows
2000:

On the Windows Start menu, select
Programs->Administrative Tools.

Select Local Security Policy.

Go to Local Policies->User Rights
Assignment.

Give the following rights to the Windows user
running WebLogic Server:

Act as part of the operating
system

Create a token
object

Replace a process
level token

Verify that the Windows user running WebLogic
Server is a member of the Administrators group.

Reboot Windows 2000 to ensure all the
modifications take effect.

Verify that the Logon as System Account option
is checked. Note that the Allow System to Interact with Desktop option
does not need to be checked. Running the Windows NT Security realm under
a specific Windows NT user account does not work.

The following are common Windows NT error codes
that occur when using the Windows NT Security realm:

Error Code

Meaning

1326

The host machine running the security realm does
not have a trust relationship with the primary domain controller. The
host machine may not be a member of the domain or the domain may not
trust the host machine.

53

A
network error has indicated that the path to the primary domain
controller could not be located. This error can occur if the domain name
is misspelled or if the domain name is specified rather than the host
name of the primary domain controller.

A full explanation of the
Windows NT error codes is found in the winerror.h
file.