I received this error after restarting Exchange: "The server was unable to add the virtual root '/Exadmin' for...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
the directory '\.BackOfficeStorage' due to the following error: The system cannot find the path specified. The data is the error code." How do I prevent this Exchange error?
Have an Exchange question you want answered?
If you have a question about something in Exchange that has you stumped, email us at firstname.lastname@example.org. We may feature your question in a future Ask the Expert piece.
If you are still running an Exchange 2000 deployment, this error is the least of your problems. The Exchange error you are seeing is not an issue. It is -- or was -- usually caused by IIS services starting up before Exchange Services. Don't worry about this. Instead, you need to consider your options for getting your Exchange deployment up to date immediately.
If you are on Exchange 2000 and want to get reasonably current, a migration to Exchange 2007, then over to Exchange 2010 or Exchange 2013 is the recommended path. Although it's possible to perform an in-place upgrade to Exchange 2003, Microsoft no longer supports this, and therefore any problems during the upgrade will present a serious risk, as you will be on your own. For organizations still on Exchange 2000, Exchange Online may indeed present the best option because then the task of keeping up to date will be taken care of by Microsoft. Although you will need to keep clients reasonably up to date, you won't need to worry about Exchange any longer.
If updating your deployment isn't an option and you need to solve this problem, consider either creating a scheduled task to run iisreset five minutes after system boot, or making the MSExchangeIS a dependency of the World Wide Web. I'd usually suggest the former because you wouldn't need to change the default Exchange installation. However, because Exchange 2000 isn't supported anyway, there's little harm in using the latter suggestion, since Microsoft won't support any issues you encounter either way.
About the author:
Steve Goodman is an Exchange MVP and works as a technical architect for one of the U.K.'s leading Microsoft Gold partners. Goodman has worked extensively with Microsoft Exchange since version 5.5 and Office 365 since its origins in Exchange Labs and Live@EDU.
Dig Deeper on Legacy Microsoft Exchange Servers
Related Q&A from Steve Goodman
Admins don't have to sidestep the default settings for deleting logs, but if needed, these PowerShell cmdlets will get the job done.continue reading
When calendar invites don't appear in your view like they should, follow these steps to fix the problem.continue reading
Trying to increase message size limits but hitting a brick wall? Try this simple trick.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.