Srv - eventerror

[shibi 10]

Hi Leute

 

Ich hab derzeit ziemlich wenig zeit, dass ich hier öfters vorbeischaue...

 

Wir haben einen Server neu aufgesetzt, und dann von einem anderen server Alle Daten sowie den "System State" zurückgesichert.

 

Ich habe das Problem, dass der Server genau jede Minuten diesen Fehler ins Protokoll schreibt:

 

 

Event Type: Error

Event Source: Srv

Event Category: None

Event ID: 2020

Date: 24.03.2003

Time: 11:43:37

User: N/A

Computer: WSVAT03

Description:

 

The server was unable to allocate from the system paged pool because the pool was empty.

 

Data:

0000: 00 00 04 00 01 00 54 00 ......T.

0008: 00 00 00 00 e4 07 00 c0 ....ä..À

0010: 00 00 00 00 9a 00 00 c0 ......À

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

0028: 4a 00 00 00 J...

 

 

Ich habe das Pagefile schon neu geschrieben... aber vergeblich! Nach einem Neustart schreibt er diesen Fehler längere Zeit nicht mehr...

 

DANKE

 

PS: Ich finde dieses Board ist einfach ein wahnsinn... (positiv gemeint natürlich)! :)

[grizzly999 11]

Ich hatte den Fehler noch nie gesehen, aber ich poste Dir mal, was die KB dazu sagt:

 

Symptoms

When your server is under a heavy load, the Server service may repeatedly log the following error (in the System Event log) that indicates that the server is out of paged pool memory:

 

Source - SRV

Type - Error

Event ID - 2020

Description -

 

The server was unable to allocate from the system paged pool because the pool was empty.

Data -

0000: 00040000 00540001 00000000 c00007e4

0010: 00000000 c000009a 00000000 00000000

0020: 00000000 00000000 0000000b

 

 

 

Cause

Several factors may deplete the supply of paged pool memory. Enabling pool tagging and taking poolsnaps at different time intervals may help you to understand which driver is consuming paged pool memory. If the poolsnaps indicate that the MMST tag (Mm section object prototype ptes) is the largest consumer and is over 80 megabytes (MB), there is a large probability that there are a very large number of files that are open on the server. By default, the Memory Manager tries to trim allocated paged pool memory when the system reaches 80 percent of the total paged pool. The possible maximum paged pool memory on a computer is 343MB of paged pool, and 80 percent of this number is 274MB. If the Memory Manager is unable to trim fast enough to keep up with the demand, the event that is listed in the "Symptoms" section of this article may occur. By tuning the Memory Manager to start the trimming process earlier (for example, when it reaches 40 percent), it would be possible to keep up with the paged pool demand during sudden peak usage, and avoid running out of paged pool memory.

 

 

 

Resolution

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

 

The following tuning recommendation has been helpful in alleviating the problem:

 

Start Registry Editor (Regedt32.exe).

 

 

Locate and then click the following key in the registry:

 

 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management

 

On the Edit menu, click Add Value, and then add the following registry value:

Value name: PoolUsageMaximum

Data type: REG_DWORD

Radix: Decimal

Value data: 40

Setting the value at 40 informs the Memory Manager to start the trimming process at 40 percent of PagedPoolMax rather than the default setting of 80 percent.

Value name: PagedPoolSize

Data type: REG_DWORD

Radix: Hex

Value data: 0xFFFFFFFF

Setting PagedPoolSize to 0xFFFFFFFF (-1), allocates the maximum paged pool in lieu of other resources to the computer.

 

 

Quit Registry Editor.