Image Image Image Image Image Image Image Image Image Image

Technology Blog with Jason Slater | April 25, 2014

Scroll to top

Top

2 Comments

Dealing with inconsistent state error in Exchange 2007

Jason Slater
  • On Thursday, 5 April 2007
  • http://www.jasonslater.com

I received the following error when starting up Exchange 2007. The interesting thing is that it seems to be referring to the older Exchange Server. I am going to move the edb files from the root directory on that server later today to see if it makes any difference.

——————————————————–

Microsoft Exchange Warning

——————————————————–

The following warning(s) were reported while loading topology information:

get-StorageGroup

Completed

Warning:

Object First Storage Group has been corrupted and it is in an inconsistent state. The following validation errors have been encountered:

——————————————————–

OK

——————————————————–

Warning: Could not convert property SystemFolderPath to type NonRootLocalLongFullPath. The path cannot be root directory.Parameter name: path

Warning: Could not convert property LogFolderPath to type NonRootLocalLongFullPath. The path cannot be root directory.Parameter name: path

Warning: LogFolderPath is mandatory.

Warning: SystemFolderPath is mandatory.

get-Mailbox

DatabaseCompleted

Warning:

Object Mailbox Store (OLD) has been corrupted and it is in an inconsistent state. The following validation errors have been encountered:

Warning:

Exchange cannot store database (.edb) files in the root directory. Please choose another location. The specified file path is ‘G:priv1.edb’.

UPDATE: Moving the files from the root Folder fixed the problem

Comments

  1. Tony

    Hi Jason,

    I seem to have this problem. We migrated from Exchange 2000 to Exchange 2007. We are running on service pack 1 now, but the problem is that we removed our exchange 2000 server permanently. We had major problems with public folders and eventually moved off of them. We seemed to have message routing problem after we moved all the mailboxes from exchange 2000 to 2007, where messages were going to the First Administrative Group (Exchange 2000) instead of exchange 2007. So the messages would bounce. So we removed the First Administrative group with ADSI Edit and it killed public folders. Any ideas on how to fix public folders would be very helpful at this point.

    Thank you
    Tony

  2. danny

    Jason,

    Moving log files and database files from the root directory will solve the error messages. You can check it easily from the exchange management shell. Run the following command:

    Get-StorageGroup -Server oldservername

Submit a Comment


+ one = 9