Exchange system manager C103b405 error.

Posted on 2009-04-17
Medium Priority
Last Modified: 2012-05-06
I'm am running exchange 2007 on server 2008.  I used to have exchange 2003, but removed it after installing exchange 2007.  I'm trying to access the public folders using the exchange 2003 esm.  When I try to expand the folder I get   Could not locate the root folder.  Ensure that your default virtual server is running and it is configured correctly.  If you have IIS Lockdown security tools on your server.  
ID No. c103b405
Exchange system manager

Originally I was getting an error message that dealt with not have the exadmin virtual directory in IIS, but I ran the New-OwaVirtualDirectory to create one.  Now I get this message.  We are not running a urlscan or have used IIS lockdown.  This server is also setup on a VM, if that makes a difference.
Question by:bnussbaum
  • 2
  • 2
LVL 15

Expert Comment

ID: 24172002
Why not use the public folder management console for Exchange 2007?  You can access it through the toolbox in the tree on the left in the Exchange Management Console.

Author Comment

ID: 24184322
Because we are having issues removing data from the public folders.  We tried running the movereplicadata and a remove command from the command shell.  But not all the data is being removed.  When I try to remove the data from the public folder management console it errors out.  So I want connect to it from the esm.
LVL 15

Expert Comment

ID: 24192822
I think there are issues using ESM on a 2007 box.  What are the errors you're getting when you try the movereplicadata?  What data is left behind?  


Accepted Solution

bnussbaum earned 0 total points
ID: 24193166
We uninstalled the CAS role so that we could reinstall the CAS role which would allow us to recreate the virtual directories that weren't created on the initial setup.  When we unisntalled the CAS role, it actually removed the exchange server from the exchange organization, which is what we wanted.  We verified that the exchange server did not show up as an exchange server anywhere in AD and ADSI edit before doing the next steps.  The issue then became that the Exchange server thought it still had the mailbox role installed.  If you tried to uninstall the mailbox role, it would error out saying this exchange server did not exist.  To correct this, we went into the registry and deleted the HKEY_LOCAL_MACHINE/software/microsoft/exchange key.  Then went to the c:\program files\microsoft folder and deleted the exchange server folder.  The Exchange CD would then let us install Exchange as if it was never installed on this machine before.  We then just installed the CAS role like we wanted from the beginning, and everything appears to be working now.    

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

750 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question