[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Microsoft Exchange 2003 Information Store Service Accessing Old Data Store Directory?

We have moved our Exchange data and log file to seperate disks and I was going to remove the old common disk as nothing should have been using it. However after removing the disk and rebooting neither of Public folder or Mailbox store would mount.  After I added the old disk back I was able to mount both fine?  I used File Monitor to observe disk access and found the Microsoft Exchange Information Store service is access E:\Temp a couple times a second looking for something, but there is no such file.  There are 2 GUIDs listed, I assued one for the Mailbox store and one for the Public folders. I tried reseting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Schema\<MDBGUID> to 0 for both and rebooting to try and refresh the Schema but the GUID remain the same and continue to try accessing the E:\Temp location with the same NO SUCH FILE error.
1 Solution
what error do you see in the eventvwr? also could you ensure the transaction log file name & the checkpoint file name also database file name in ESM points to the new store?

if they are correct then dismount the store, rename the drive to another drive letter & try to mount the stores back, let me know how it goes, if it doesnt then please get me the eventviewer details
WH_TechAuthor Commented:
Thank you for pointing me in the right direction. Once  I renamed the drive and tried to remount the store. I got a couple of errors that I could search for on Microsofts website. Ended up being a reference to a Temp path. http://support.microsoft.com/kb/307242

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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