Event Viewer System Logs

Open up Local Security Policy on this Win2K server (Start -> Programs -> Control Panel -> Administrative Tools -> Local Security Policy) and expand:
Security Settings -> Local Policies -> User Rights Assignment.
Check the right "Manage auditing and Security log".
See who, if anyone is Assigned the right. You should have Administrators listed at least!
My guess is that this right was changed to be blank, so no one can do this.
So, be logged in as an Administrator and add Administrators.

You might need to check the Group Policy settings for this same right, just to make sure it is not changed there, but I would bet this is a local problem, not a GP problem.

hope this helps

I checked the settings which were mentioned in the first answer. Permissions are correct and the appropriate groups (administrators) has been given the right.

Is there some other setting, variable, or permission that may pertain to this problem?

Thanks is advance.

Have you tried re-installing the service pack after they gave you the patch for the app?

Okay, now the problem is getting WORSE. Now we are unable to open the application log. The only log is the Security log which is accessable by the administrator. Here is a Log message and details. I cannot find anything in the Knowledge Base to point to this problem.

Date: 11/6/2002 Source: Security
Time: 8:26 Category: Object Access
Type: Failure Event ID: 560
User: Server\Administrator
Computer: server
Object Open:
Object Server: Security
ObjectType: Event
Object Name: \BaseNamedObjects\crypt32LogoffEvent
New Handle ID: -
Operation ID: {0,4190261}
Process ID: 3976
Primary User Name: administrator
Primary Domain: SERVER
Primary Logon ID: (0x0,0x35E0C8)
Client User Name: -
Client Domain: -
Client Logon ID: -
Accesses DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
Query event state
Modify event state

Privileges -
-----------------------------------------

You can try reseting the local security settings for the server by performing the following steps:

1. Open a CMD prompt.

2. Type:

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose

3. If you receive a warning message, it can be ignored. See the %windir%\Security\Logs\Scesrv.log file.

Remember to backup before trying this.

regards,