• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 574
  • Last Modified:

Exchange - mounting MDBDATA after restore

Hi!

Recently I used Storage Craft - shadow protect (for win SBS 2k3) to restore an image of windows SBS 2k3 on to a new server. Restore worked fine however when try to mount the exchange data from Exchange systems manager i get the following message:

" An internal processing error has occured. Try restarting ESM or the Exchange information store service or both. Examine the application log for events related to this error. The description fields of these events will contain specific error codes and may contain links to MS KB for troubleshooting"

ID no: c1041724
Exchange Systems Manager:

Now I have tried various troubleshooting method using eseutil.exe /r /p /I etc... but got no luck. So I suspect the problem could be related to the E00.log or Exxxx.log files being corrupted, if i delete these log files from the "live" exchange would it affect the exchange server or staffs emails in any way?

I want to delete these log files and then do a full restore, please let me know if you think this is going to create problems on the current exchange server? also if you know of any other methods that could work to mount the image on the new server

Many Thanks!!
0
J3D1-KN1G1-1t
Asked:
J3D1-KN1G1-1t
3 Solutions
 
KaltiCommented:
Hi,

Deleting transaction log files for a database is never a good idea unless you have a full backup and know exactly which log files have already been played into the database, which is hard. You can find information about this process here:

http://support.microsoft.com/kb/240145

May I ask if you checked the Application Log like the message says? I suspect there will be more detailed information about the error in Event Viewer, for instance I found this Microsoft Article which is possibly your problem: http://support.microsoft.com/kb/294318

However it is hard to know without more detiled inforamtion about the error. Basically I wouldn't recommend deleting log files unless you are absolutely sure that is going to fix the problem, and at the moment we need to get more information.

Cheers,
0
 
SuperTacoCommented:
Generally when restoring an Exchange DB form an image. that image is not VSS aware when it's taken.  You will have to recommit the transaction logs.  In the past I haev had to MOVE (Not delete) the logs and recreate the e00.log file and the temp.mbd, but this is ONLY last resort if you don't have a backup.
0
 
ash007Commented:
You need to run Eseutil /mh to check the state of Database & find which log files are missing. If any log files are missing you can check for missing log files & run soft repair using Eseutil /r  .
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now