Article ID: 288691
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q288691
SYMPTOMS
If you move an Exchange 2000 database to a system that does not have the same Locale ID (LCID) and then try to defragment the database, it may report an index corruption. However, if you load the correct locale on this server, and then try to defragment the database, it does not report an index corruption.
NOTE: A Locale ID is a 32-bit value defined by Microsoft Windows that consists of a language ID, sort ID, and reserved bits that identify a particular language. For example, the LCID for English is 1033, and the LCID for Japanese is 1041.
CAUSE
If a database is moved between computers where the LCID installation status differs, there is potential for a silent index corruption. For example:
- If an LCID that was previously uninstalled is then reinstalled (or vice versa), there is potential for a silent index corruption.
- If you back up and then restore a database that is generated by a computer that has the LCID installed to a computer without the LCID installed, index corruption may occur.
- If a database is copied to a different computer, defragmented, and then copied back to the original computer, this also may silently introduce corruption if the LCID installation status differs between the two computers.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. 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 apply Exchange 2000 Service Pack 1 (SP1), if you try to defragment an Exchange 2000 database that contains indexes for a language that is not installed on that computer, a JET_errInvalidLanguageId error will be reported.
WORKAROUND
If you have already defragmented an Exchange 2000 database and it reported index corruption, load the correct LCID, and then defragment the database again.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.
MORE INFORMATION
For additional information about loading the correct LCID, click the article number below to view the article in the Microsoft Knowledge Base:
177561 HOWTO: Add and Enable Additional Languages in Windows NT
Keywords: kbbug kbfix KB288691
