• Article

MSExchangeIS 9519 (0xfffffbda): Missing Double Byte Character Set Locale Configured as the Default System Locale

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-01-23

The Microsoft® Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9519 events with error code 0xfffffbda in the Application log. The event indicates that a non-English default system locale was installed. After Exchange Server was installed, the default system locale was uninstalled.

Explanation

If the event MSExchangeIS 9519 with error code 0xfffffbda triggers on restarting the Exchange server, the Exchange databases will not mount. In addition, error events ESE 604 and MSExchangeIS 9519 are logged in the Application event log.

This behavior may occur if you previously had a non-English locale set as the default system locale. If you chose another locale as the default system locale, removed the non-English locale, and then restarted the Exchange 2000 Server or Exchange Server 2003, you experienced this event.

The event can also be identified as -1062, JET_errInvalidLanguageId. The event applies to the following versions of Exchange server:

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2003

  • Microsoft Exchange 2000 Server

User Action

To resolve the issue, reinstall the non-English locale or create new databases. If you reinstall the non-English locale, it does not have to be set as the default system locale.