Article ID: 911919
Article Last Modified on 3/23/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
SYMPTOMS
You are using two or more Microsoft Windows Server 2003-based computers that connect to a Storage Area Network (SAN). You make a partition change to the shared disk on the SAN from one of the computers. After you do this, other hosts that can see the same shared disk must be restarted to see the partition change in the disk management console.
CAUSE
This behavior is caused by the cached partition table mechanism that was introduced in Windows Server 2003. Even though the partition table has been changed, you cannot see the change in the disk management console. This behavior occurs because the Dmadmin.exe program does not re-read the real partition table. Instead, the disk management console just shows the cached table.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. 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
Hotfix information
Prerequisites
No prerequisites are required.
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 tool in Control Panel.
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Dmadmin.exe | 5.2.3790.2586 | 234,496 | 07-Dec-2005 | 02:32 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
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
Additional query words: dmadmin
Keywords: kbwinserv2003sp2fix kbqfe kbhotfixserver kbmgmtservices kbwinservperf kbwinservsetup kbstoragemgmt kbpubtypekc KB911919
