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

Can not mount Exchange mailbox store after upgrading hard drive Windows Server 2003 SBS

We moved a Windows Server 2003 (Small Business) to larger hard drives, using Acronis Image Server software.  Everything worked after the migration, except that we could not mount the mailbox store nor the public store in System Manager (in First Storage Group).

We placed the original hard drives back in the server, started it up, stopped all Exchange services, and copied all contents of C:\Program Files\Exchsrvr to an external hard drive.  We placed the new drives back into the server, started it in safe mode, and copied the files into C:\Program Files\Exchsrvr.  The server was restarted, and the public store was mounted but the mailbox store was not.

When we try to manually mount the mailbox store, the error is:

"An internal processing error has occurred.  Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both."
ID no: c1041724
Exchange System Manager

We attempted a repair by using esutil.exe on the priv1.edb database, saw no errors.  Still can not mount Mailbox Store.

Any ideas?
0
4RunnerBob
Asked:
4RunnerBob
  • 5
  • 4
  • 2
  • +1
1 Solution
 
mass2612Commented:
Hi,

Do you have any free space on the C:\ partition? Check the permissions on the store.

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

Is the database showing as clean shutdown state using eseutil /mh C:\Program Files\Exchsrvr\Priv1.edb
0
 
KCTSCommented:
0
 
KCTSCommented:
... this one seems to be a bit more specific to your problem http://support.microsoft.com/kb/830408
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually this is the KB article that's specific to the issue:  http://support.microsoft.com/kb/294318

However, the fact that you only copied the contents of C:\Program Files\Exchsrvr  makes me wonder if all of the Exchange Database and Log files were indeed located in C:\Program Files\Exchsrvr or if they were perhaps on another partition?  

Jeff
TechSoEasy
0
 
4RunnerBobAuthor Commented:
PLEASE NOTE THAT OUR ORIGINAL POST INCORRECTLY STATED that we were able to mount the public store after copying the contents of C:\Program Files\Exchsrvr from the original drives to the newly imaged drives.  WE CAN NOT MOUNT EITHER THE MAILBOX STORE nor the PUBLIC STORE.

Thanks for each suggestion.  We have about 15GB of free space.

I have followed the steps outlined in the multiple KBs, with no change in the error message.  If I remove the new hard drives, and connect the original hard drives, we can run Exchange normally, mounting the priv1.edb and pub1.edb databases.  (Remember that we created an image of the original drives, then imaged the new drives.  Everything works when we use the new/imaged drives, except that we cannot mount the mailbox store nor the public stores.)  

It appears that the image was created while Exchange was running, so we started the server with the original drives, shut down Exchange, and copied C:\Program Files\Exchsrvr to a portable hard drive, then copied these files to the new hard drives as described in the original posting.  

Are there any other files that need to be copied or recovered from the original drive?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I probably should have pointed you to this KB article to begin with... sorry about that.

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

I've used this numerous times to recover an Exchange Store on an SBS, and it works quite well.

Jeff
TechSoEasy
0
 
4RunnerBobAuthor Commented:
Ran eseutil /mh on both priv1.edb and pub1.edb, both reported cean shutdown status.
Ran eseutil /r E00 on both databases, soft recovery terminated with error -528 (current log file missing).
Ran eseutil /p on both databases (integrity check successful)
Ran eseutil /d on both databases (defragged OK)
Ran isinteg -s server -fix -test alltests (Error:  Isinteg cannot initiate verification process"

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
"Ran eseutil /r E00 on both databases, soft recovery terminated with error -528 (current log file missing)."

This would then mean you would follow this directive in the KB article:
"Note If you do not have the log files, you cannot complete the soft recovery process. Go to step 6. You must also start the Information Store service."

So that looks fine.

"Ran isinteg -s server -fix -test alltests (Error:  Isinteg cannot initiate verification process"

I'm assuming here that instead of "server" you actually used the name of your server?  Confirmed by using nbtstat -n to make sure that the servername was properly set?

If so, I'd refer you then to http://support.microsoft.com/kb/823022 to make sure that the permissions are all correct.

Jeff
0
 
4RunnerBobAuthor Commented:
Do we need to backup the working Exchange database files (and other files?) from the old server hard drive to the new server hard drive?

If we install the original server drive in the server, we can start it and Exchange works fine.  We had originally imaged the server, with Exchange running.  (Dumb move, we agree.)  When we used the image to move our server to larger hard drives, everything worked except Exchange.  Since that day, we have started the server with the original drives and copied the contents of C:\Program Files\Exchsrvr\MDBDATA to an external hard drive.  We restarted the server with the new drives installed, and copied in the contents of the MDBDATA folder.

We have been able to confirm that the priv1.edb and pub1.edb show a state of "clean shutdown".  Other tests (listed above) return normal results, until we tried to run isinteg.  (As you can see earlier in this thread, "isinteg cannot initiate verification process".)

If there is a better way to back up the working files from one hard drive, and restore them on the new hard drive, let us know.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If you can still restart the server with the original drives... then why don't you do that... STOP Exchange... Create a NEW Image... and then restore just the MDBDATA folder from your new image?

Jeff
TechSoEasy
0
 
4RunnerBobAuthor Commented:
Additional information from the Event (Application) log:

We started the services for MS Exchange Information Store and MS Exchange Management.

Event log entries are:

MSExchangeSA   ID 1000
"Microsoft Exchange System Attendant is starting.  Microsoft Exchange Server System Attendant, service startup complete, version 6.5 (build 6944.0)."

MSExchangeSA   ID 9007
"Microsoft Exchange System Attendant is initializing 'DSACCESS.DLL'."

MSExchangeDSAccess   ID 2068
"Process MAD.EXE (PID=4264).  DSAccess initialized successfully."

MSExchangeSA   ID 9006
"Microsoft Exchange System Attendant is loading 'DSPROXY.DLL'."

MSExchangeSA   ID 9006
"Microsoft Exchange System Attendant is loading 'ABV_DG.DLL'."

MSExchangeSA   ID 9006
"Microsoft Exchange System Attendant is loading 'DS2MB.DLL'."

MSExchangeSA   ID 9007
"Microsoft Exchange System Attendant is initializing 'DS2MB.DLL'."

MSExchangeSA   ID 9006
"Microsoft Exchange System Attendant is loading 'madfb.dll'."

MSExchangeSA   ID 9007
"Microsoft Exchange System Attendant is initializing 'madfb.dll'."

MSExchangeSA   ID 9006
"Microsoft Exchange System Attendant is loading 'OABGEN.DLL'."

MSExchangeSA   ID 9013
"Microsoft Exchange System Attendant is being started for Exchange server 'SERVER'."

MSExchangeSA   ID 9012
"Microsoft Exchange System Attendant is ginding to domain controller 'SERVER.lcm.local'."

MSExchangeSA   ID 9008
"Microsoft Exchange System Attendant is starting 'DS2MB.DLL'."

MSExchangeSA   ID 9008
"Microsoft Exchange System Attendant is starting'ABV_DG.DLL'."

MSExchangeSA   ID 9008
"Microsoft Exchange System Attendant is starting 'madfb.dll'."

MSExchangeFBPublish   ID 8192
"Virtual machine SERVER is starting with flags 0x00000001."

MSExchangeSA   ID 9316
"Registering Service Principal Name for exchangeRFR."

MSExchangeSA   ID 9014
"Microsoft Exchange System Attendant has been started for Exchange server 'SERVER' successfully."

MSExchangeSA   ID 9007
"Microsoft Exchange System Attendant is initializing 'DSPROXY.DLL'."

MSExchangeSA   ID 9070
"The Directory Service Referral interface (RFRI) started successfully."

MSExchangeSA   ID 9316
"Registering Service Principal Name for exchangeMDB."

MSExchangeSA   ID 9095
"The MAD Monitoring thread is initializing."

MSExchangeSA   ID 9096
"The MAD Monitoring thread is initialized."

EXOLEDB   ID  100
"Microsoft Exchange OLEDB has successfully started."

EXCDO   ID 8195
"Calendaring agent is initialized successfully."

EXCDO   ID 8246
"Calendaring agent has successfully started the background thread."

ESE BACKUP   ID 905
"Information Store (5932) Server registered: Microsoft Exchange Server / Microsoft Information Store (callback DLL mdbrest.dll, flags 0x103)."

ESE   ID 100
"Information Store (5832) The database engine 6.05.6944.0000 started."

ESE   ID 102
"Information Store (5932) First Storage Group:  The database engine started a new instance (0)."

ESE ID 300
"Informaiton Store (5932) First Storage Group:  The database engine is initiating recovery steps."

ESE   ID 301
"Information Store (5932) First Storage Group:  The database engine has begun replaying logfile D:\Program Files\Exchsrvr\MDBDATA\E00.log"

ESE   ID 494
"Information Store (5932) First Storage Group:  Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrver\mdbdata\priv1.edb', which is no longer present.  The database was not brought to a consistent state before it was removed (or possibly moved or renamed).  The database engine will not permit recovery to complete for htis instance until the missing database is re-instated.  If the database is truly no longer available and no longer required, please contact PSS for futher instructions regarding the steps required in order to allow recovery to proceed without this database."

[Comment on log entries by 4RunnerBob:  The file priv1.edb does exist in C:\Program Files\Exchsrvr\MDBDATA.]

ESE   ID 454
"Information Store (5932) First Storage Group: Database recovery/restore failed with unexpected error -1216."

ESE  ID 101
"Informaiton Store (5932) The database engine stopped."

MSExchangeIS   ID 9518
"Error 0xfffffb40 starting Storage Group /DC=local/DC=lcm/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=LCM/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN-SERVER/CN-InformaitonStore/CN-First Storage Group on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed."

MSExchangeIS   ID 9518
"Error 0xfffffb40 starting Storage Group /DC=local/DC=lcm/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=LCM/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=SERVER/CNInformationStore/CN=First Storage Group on the Microsoft Exchange Information Store. <NULL>."

MSExchangeIS   ID 1001
"The Microsoft Exchange Informaiton Store has started. Service startup complete, version 6.5 (build 6944.3)."

MSExchangeMGMT   ID 2
"Starting the Microsoft Exchange Management service."





0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Okay... that's a completely different error than you first stated in your question.  

Assuming that you have a good backup already... please run:

ESEUTIL /R /I

To force a recovery of the store.

Jeff
TechSoEasy
0
  • 5
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now