<div>
All the log files have been restored too?<br />
<br />
If so you need to force &nbsp;the DB to get into &nbsp;a consistent state with eseutil tool. &nbsp;Otherwise you won't mount. &nbsp;Do eseutil /cc &lt;path to restore.env file&gt; &nbsp;
</div>


All the log files have been restored too?

If so you need to force  the DB to get into  a consistent state with eseutil tool.  Otherwise you won't mount.  Do eseutil /cc <path to restore.env file>  

<div>
That failed so, I ran a eseutil /p to repair the DB. &nbsp;Checked status and tried to mount but failed. &nbsp;Could the Service Pack be an issue? &nbsp;Have not loaded any Exchange service packs on this server, not sure what the old server had. &nbsp;Is there anyway to tell with any eseutil commands?
</div>


That failed so, I ran a eseutil /p to repair the DB.  Checked status and tried to mount but failed.  Could the Service Pack be an issue?  Have not loaded any Exchange service packs on this server, not sure what the old server had.  Is there anyway to tell with any eseutil commands?

<div>
<div class="content wysiwyg-content">
Problems with old server, bringing a new server on-line with the same name, organization, etc as our old server. &nbsp; Have a current backup from NTBackup of the exchange db, dismounted new server db, renamed db files and restored DB from old server. &nbsp;Failed hard recovery of log files, so I ran useutil /p to repair db, verified integrity of DB which now shows clean shutdown with no log files req. DB still will not mount if though there doesn't seem to be any problems. Event Log shows 9518,9519,9175(MAPI provider failed). Not sure if the E2k3 service pack is at the same level, would this cause a problem? &nbsp;Might still be able to bring up the old server to check possibly.
</div>
</div>


Problems with old server, bringing a new server on-line with the same name, organization, etc as our old server.   Have a current backup from NTBackup of the exchange db, dismounted new server db, renamed db files and restored DB from old server.  Failed hard recovery of log files, so I ran useutil /p to repair db, verified integrity of DB which now shows clean shutdown with no log files req. DB still will not mount if though there doesn't seem to be any problems. Event Log shows 9518,9519,9175(MAPI provider failed). Not sure if the E2k3 service pack is at the same level, would this cause a problem?  Might still be able to bring up the old server to check possibly.

Restored Exchange 2003 Database won't mount - EventID 9518 &amp; 9519

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Restored Exchange 2003 Database won't mount - EventID 9518 &amp; 9519

Restored Exchange 2003 Database won't mount - EventID 9518 & 9519