2 things that either this is a SG that had Logs and System pointing to a location that does not exists or its that the Logs and System path are pointing to the Root of the drive thats not recommended.
Main Topics
Browse All TopicsDoing an Exchange 2007 Migration. The new 2007 server is in a child domain (child.domain.corp) with an existing 2003 Exchange server. There is also an existing 2003 Exchange server in the parent domain. I've successfully installed the new exchange server after prepping domains/schema/etc... When I open the EMC, I get this:
--------------------------
Microsoft Exchange Warning
--------------------------
The following warning(s) were reported while loading topology information:
get-StorageGroup
Completed
Warning:
Object PARENTDOMAINMAILSERVER\Fir
Warning:
Could not convert property SystemFolderPath to type NonRootLocalLongFullPath. The path cannot be the root directory.
Parameter name: path
Warning:
Could not convert property LogFolderPath to type NonRootLocalLongFullPath. The path cannot be the root directory.
Parameter name: path
Warning:
LogFolderPath is mandatory.
Warning:
SystemFolderPath is mandatory.
Warning:
Object PARENTDOMAINMAILSERVER\Dat
Warning:
Could not convert property SystemFolderPath to type NonRootLocalLongFullPath. The path cannot be the root directory.
Parameter name: path
Warning:
SystemFolderPath is mandatory.
Any idea what this is all about? This is referring to a storage group on the exchange server in the parent domain. AFAIK there are no issues with it. Does 2007 run consistency checks on 2003 storage groups?
Thanks for any help.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: MesthaPosted on 2009-06-09 at 16:40:09ID: 24586919
Pretty sure that means that one of the paths in the configuration of the storage group is something like
D:\
Instead of
D:\Directory
It is bad practise to have either the transaction logs or the system path configuration on a storage group in the root.
It is quite simple to fix. If you have everything in the root of the drive, create a directory structure similar to
Exchange Logs
-- First Storage Group
-- Second Storage Group
etc
then move the logs and system path on each storage group through ESM in to the relevant folder.
Simon.