Article ID: 931308
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
SYMPTOMS
When you run an SAP R/3 program on a Microsoft Windows Server 2003-based computer, you may experience increased paging to the hard disk. Therefore, you may experience decreased system performance.
Note These paging volumes show an increase when compared to the paging volumes that are generated if you run the same program on a Windows 2000 Server-based computer.
CAUSE
In Windows Server 2003, the modified page writer thread is responsible for writing to the page file those pages that have been modified in memory. This modified behavior is designed to make sure that as many pages as possible are available at any particular time. This thread becomes active when a particular number of pages have been modified in memory.
The SAP R/3 program uses many worker process threads. Each of these worker process threads has a particular amount of memory allocated as a working set. Generally, the size of this working set is stable. However, the pages in this working set are frequently modified. This frequent page modification causes the modified page writer thread to write the pages to the hard disk. Therefore, Windows Server 2003 performs excessive paging operations when you run an SAP R/3 program.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
You must be running Windows Server 2003 Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1 (SP1) to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Important This hotfix is designed specifically for Windows Server 2003 SP2 and for Windows Server 2003 SP1. This hotfix is not designed for any later service packs that may be released for Windows Server 2003.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, 32-bit x86 editions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Ntkrnlmp.exe | 5.2.3790.2919 | 2,460,160 | 18-Apr-2007 | 11:58 | Not Applicable | SP1 | SP1QFE |
Ntkrnlpa.exe | 5.2.3790.2919 | 2,272,256 | 18-Apr-2007 | 11:14 | x86 | SP1 | SP1QFE |
Ntkrpamp.exe | 5.2.3790.2919 | 2,312,704 | 18-Apr-2007 | 11:13 | Not Applicable | SP1 | SP1QFE |
Ntoskrnl.exe | 5.2.3790.2919 | 2,420,736 | 18-Apr-2007 | 11:57 | x86 | SP1 | SP1QFE |
Ntkrnlmp.exe | 5.2.3790.4063 | 2,469,888 | 18-Apr-2007 | 12:50 | Not Applicable | SP2 | SP2QFE |
Ntkrnlpa.exe | 5.2.3790.4063 | 2,282,496 | 18-Apr-2007 | 11:54 | x86 | SP2 | SP2QFE |
Ntkrpamp.exe | 5.2.3790.4063 | 2,321,920 | 19-Apr-2007 | 13:21 | Not Applicable | SP2 | SP2QFE |
Ntoskrnl.exe | 5.2.3790.4063 | 2,430,464 | 18-Apr-2007 | 12:49 | x86 | SP2 | SP2QFE |
Windows Server 2003, 64-bit x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Ntkrnlmp.exe | 5.2.3790.2917 | 4,631,040 | 17-Apr-2007 | 06:42 | x64 | SP1 | SP1QFE |
Ntoskrnl.exe | 5.2.3790.2917 | 4,487,680 | 17-Apr-2007 | 06:42 | x64 | SP1 | SP1QFE |
Ntkrnlmp.exe | 5.2.3790.4061 | 4,569,088 | 17-Apr-2007 | 06:45 | x64 | SP2 | SP2QFE |
Ntoskrnl.exe | 5.2.3790.4061 | 4,499,968 | 17-Apr-2007 | 06:45 | x64 | SP2 | SP2QFE |
Windows Server 2003, 64-bit Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Ntdll.dll | 5.2.3790.2917 | 1,636,864 | 17-Apr-2007 | 06:43 | IA-64 | SP1 | SP1QFE |
Ntkrnlmp.exe | 5.2.3790.2917 | 6,519,296 | 17-Apr-2007 | 06:43 | IA-64 | SP1 | SP1QFE |
Ntdll.dll | 5.2.3790.4061 | 1,636,864 | 17-Apr-2007 | 06:44 | IA-64 | SP2 | SP2QFE |
Ntkrnlmp.exe | 5.2.3790.4061 | 6,535,680 | 17-Apr-2007 | 06:44 | IA-64 | SP2 | SP2QFE |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Additional query words: mySAP ERP
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinservperf kbhotfixserver KB931308