Server Object
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The Server performance object consists of counters that measure communication between the local computer and the network.
| Counter Name | Description | Counter Type |
|---|---|---|
Blocking Requests Rejected |
Shows the number of times that the server rejected blocking server message block (SMB) requests due to insufficient count of free work items. This counter indicates whether the MaxWorkItem or MinFreeWorkItems server registry parameters might need tuning. |
|
Bytes Received/sec |
Shows the rate, in incidents per second, at which the server received bytes from the network. This counter indicates how busy the server is. |
|
Bytes Total/sec |
Shows the rate, in incidents per second, at which the server transmitted bytes through the network. This value provides an overall indication of how busy the server is. |
|
Bytes Transmitted/sec |
Shows the rate, in incidents per second, at which the server sent bytes on the network. This counter indicates how busy the server is. |
|
Context Blocks Queued/sec |
Shows the rate, in incidents per second, at which work context blocks were placed on the server's file system process queue to await server action. |
|
Errors Access Permissions |
Shows the number of times that attempts to open files on behalf of clients have failed with the message STATUS_ACCESS_DENIED. If this counter is high, it can indicate that someone is attempting to access random files without proper authorization. |
|
Errors Granted Access |
Shows the number of times that attempts to access files successfully opened were denied. This counter can indicate attempts to access files without proper authorization. |
|
Errors Logon |
Shows the number of failed logon attempts to the server. If this counter is high, it can indicate that password guessing programs are attempting to compromise the server's security. |
|
Errors System |
Shows the number of times that an internal server error was detected. Errors can reflect problems with logon, security, memory allocation, disk operations, transport driver interface operations, communication (such as receipt of unimplemented or unrecognized SMBs), or I/O Request Packet stack size for the server. Many of these errors are also written to the System log and Security log in Event Viewer. The server can recover from most the errors displayed by this counter, but they are unexpected and should be reported to Microsoft Product Support Services. |
|
File Directory Searches |
Shows the number of searches for files currently active in the server. This counter indicates current server activity. |
|
Files Open |
Shows the number of files currently opened on the server. This counter indicates current server activity. |
|
Files Opened Total |
Shows the number of successful attempts to open a file, performed by the server on behalf of clients. This counter is useful in determining the amounts of file I/O and overhead for path-based operations, and for determining the effectiveness of open locks. |
|
Logon Total |
Shows all interactive logon attempts, network logon attempts, service logon attempts, successful logon attempts, and failed logon attempts since the computer was last started. |
|
Logon/sec |
Shows the rate, in incidents per second, of all interactive logon attempts, network logon attempts, service logon attempts, successful logon attempts, and failed logon attempts since the computer was last started. |
|
Pool Nonpaged Bytes |
Shows the size, in bytes, of nonpageable computer memory that the server was using. This value is useful for determining the values of the MaxNonpagedMemoryUsage entry in the Windows Server 2003 family registry. |
|
Pool Nonpaged Failures |
Shows the number of times that allocations from the nonpaged pool have failed. If this counter is high, it indicates that the computer's physical memory is too small. |
|
Pool Nonpaged Peak |
Shows the maximum size, in bytes, of the nonpaged pool that the server had in use at any one point. This counter indicates how much physical memory the computer should have. |
|
Pool Paged Bytes |
Shows the size, in bytes, of pageable computer memory that the server was using. This counter can help to determine good values for the MaxPagedMemoryUsage registry entry. |
|
Pool Paged Failures |
Shows the number of times that allocations from the paged pool have failed. If this counter is high, it indicates that the computer's physical memory or page file are too small. |
|
Pool Paged Peak |
Shows the maximum size, in bytes, of the paged pool that the server has allocated. This counter indicates the proper sizes of the page file(s) and physical memory. |
|
Server Sessions |
Shows the number of sessions currently active in the server. This counter indicates current server activity. |
|
Sessions Errored Out |
Shows the number of sessions that have been closed due to unexpected error conditions. This counter indicates how frequently network problems caused dropped sessions on the server. This counter reports auto-disconnects as well as errored-out sessions. For a more accurate value for errored-out sessions, subtract the value of Sessions Timed Out from Sessions Errored Out. |
|
Sessions Forced Off |
Shows the number of sessions that have been forced to log off. This counter can indicate how many sessions were forced to log off due to logon time constraints. |
|
Sessions Logged Off |
Shows the number of sessions that have terminated normally. This counter is useful in interpreting the statistics from Sessions Timed Out and Sessions Errored Out. |
|
Sessions Timed Out |
Shows the number of sessions that have been closed because idle time exceeded the AutoDisconnect parameter for the server. This counter shows whether the AutoDisconnect setting is helping to conserve resources. |
|
Work Item Shortages |
Shows the number of times that STATUS_DATA_NOT_ACCEPTED was returned at receive indication time. This occurs when a work item is not available or cannot be allocated to service the incoming request. This counter indicates whether the InitWorkItems or MaxWorkItems registry entries might need to be adjusted. |