Your location:Tech News>OS>Windows 2000>Win2000 troubleshooting list

Latest News

Win2000 troubleshooting list

Author:fsadmin

Views:

The launch of Win2000 marks the operating system has reached a new stage but because there are too many (I heard that there are more than 600 terrible?) it is in use Various problems followed one after another in the process. Below is a list of the problems I encountered in practice I hope it will help you a little bit.

1. When the security log is full pause the computer and take the following steps:
(1) Open the event viewer.
(2) In the console tree right-click 'Security Log' and then click 'Properties'.
(3) On the 'General' tab click 'Rewrite events older than n days' or 'Do not rewrite events (manually clear the log)'.
(4) Click 'Start' click 'Run' type regedit enter 'HKEY_LOCAL_MacHINESYSTEM CurrentControlSetControlLsa' right-click 'CrashOnAuditFail' create a 'REG_DWord' type with the value '1'.
(5) Restart the computer.
Warning:
(1): Editing the registry incorrectly may severely damage the system. Before making changes to the registry you should at least back up any useful data on your computer.
(2): After the end of this process when the security log is full Windows 2000 will stop responding and display the 'audit failed' message. When Windows 2000 is stopped to recover the security log must be cleared.
Note:
(1): You must log in as an administrator or a member of the management group to complete the process.
(2): To open the Event Viewer click 'Start' point to 'Settings' and then click 'Control Panel'. Double-click 'Administrative Tools' and then double-click 'Event Viewer'.
(3) If Windows 2000 is suspended because the security log is full the system must be restarted and the process must be repeated if the full log needs to be stopped in the future.

2. Recovery when Windows 2000 stops
(1) Restart the computer and log in with an account in the system administrator group.
(2) Open the 'Event Viewer' archive the currently recorded security events (if necessary) and then clear all events from the security log.
(3) Open the registry editor and find the following registry key: 'HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa'
Right-click on 'Lsa' from the pop-up menu create 'EG_DWORD' with a value of '1' delete and replace CrashOnAuditFail value. Exit the registry editor and restart the computer.
Note:
(1) If the registry has been configured with CrashOnAuditFail = 1 before and the security log is full Windows 2000 will stop responding and display an 'audit failed' message. If this happens use the steps above.
(2) To start the 'Registry Editor' click 'Start' click 'Run' type regedit and then click 'OK'.

3. Finding memory bottlenecks
Use the following counters in the performance tool to identify the memory resources that have bottlenecks:
(1) System Processor Queue Length
(2) Memory Pages/sec < /P>

4. Find the disk bottleneck
Use the following counters in the performance tool to identify the disk resource that has the bottleneck:
(1) PhysicalDisk% Disk Time and% Idle Time
(2) PhysicalDisk Disk Reads/sec and Disk Writes/sec
(3) PhysicalDisk Avg. Disk Queue Length
(4) LogicalDisk% Free Space
Also monitor the memory counter to determine whether there are too many memory pages to make the disk Use tension.
Note: Unlike the physical disk counter data the logical disk counter data is not collected by the operating system by default. To obtain performance counter data for logical drives or storage volumes you must type diskperf -yv at the command prompt. This causes the disk performance statistics driver used to collect disk performance data to report data on logical drives and storage volumes. By default the operating system uses the diskperf -yd command to include physical drive data. For more information about using the diskperf command type diskperf -? at the command prompt.

5. Find the processor bottleneck
Use the following counters in the performance tool to identify the processor resource that has the bottleneck:
(1) Processor Interrupts/sec
(2) Processor% Processor Time
(3) Process(process)% Processor Time
(4) System Processor Queue Length

6. Find network bottlenecks
Use the following counters in the performance tool to identify bottlenecks Network resources:
(1) Network Interface Bytes Total/sec Bytes Sent/sec and Bytes Received/sec
(2) Protocol_layer_object Segments Received/sec Segments Sent/sec Frames Sent/sec and Frames Received/ sec For NWLink performance objects counters related to frames only report zero. Use datagram-based counters for these objects.
(3) Server Bytes Total/sec Bytes Received/sec and Bytes Sent/sec
(4) Network Segment% Network Utilization

?FSO solution in Win2000 server

Recommend article

Relate article