Signature Discrepancy Between Database and Streaming File
[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: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool has determined that you have a signature discrepancy between your Exchange database (.edb) file and its corresponding Exchange streaming database (.stm) file.
Each database in Exchange 2000 Server and Exchange Server 2003 is made up of two files: the .edb MAPI database file and the .stm streaming database file. Matched pairs of these files share a common database signature. If the database signature does not match, the files are not matched.
You should treat the .edb and .stm files as if they are a single file. They should always be moved or copied together.
To correct this error
Investigate the history of the database files. It is likely that files have been manually copied, moved or deleted. You must correct this problem before the database can be recovered.
If you cannot locate matching .edb and .stm files, you may be able to use Eseutil.exe to repair only the .edb file and use Eseutil with the /createstm switch to discard the .stm file. This method results in the loss of all information in the streaming database.
Note
If all database users connect to the database by using a MAPI client such as Microsoft Office Outlook®, the information stored in the streaming database is minimal. If users connect to the database by using POP3, IMAP or Outlook Web Access clients, then the streaming database contains some or all of the users' mailbox contents.
For more information about how to repair an Exchange database, see Microsoft Knowledge Base article 812357, "How to maintain your Exchange database after you repair by using the Eseutil /p tool in Exchange Server 5.5, in Exchange 2000 Server, and in Exchange Server 2003" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=812357).