Article ID: 325584
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q325584
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you use a MAPI-based program that calls the GetMailboxTable function, you may receive the following error message:
CAUSE
This problem may occur if the Microsoft Exchange 2000 Server computer that you are running the MAPI-based program on hosts more than 65,535 mailboxes. The problem occurs because MAPI has a limit of 65,536 entries or 64 kilobytes (KB) in a MAPI table.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later) 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.
Date Time Version Size File name -------------------------------------------------------------- 08-Aug-2002 21:49 6.0.5771.40 958,976 Emsmdb32.dll
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
After you install this hotfix, you must also add the GetMailboxTable skip value registry entry. To do this, follow these steps.
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.
- Click Start, click Run, type regedit.exe, and then click OK.
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\MSExchangeAdmin - On the Edit menu, point to New, and then click DWORD Value.
- Type GetMailboxTable skip value, and then press ENTER.
- On the Edit menu, click Modify.
- In the Base area, click Decimal, and then type the value that you want to use in the Value data box.
Type 1 if you want the GetMailboxTable function to obtain the first 65,536 entries. Type 65,536 if you want the GetMailboxTable function to obtain higher-numbered entries; the information that is returned starts with entry 65,537. - Quit Registry Editor.
Note To obtain one set of entries after you obtain the other set, you must change the value in the Value data box (see step 6), and then you must call the GetMailboxTable function again.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Keywords: kbhotfixserver kbqfe kberrmsg kbqfe kbexchange2000presp4fix kbbug kbfix KB325584
