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

Exchange system manager C103b405 error.

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.
0
bnussbaum
Asked:
bnussbaum
  • 2
  • 2
1 Solution
 
zelron22Commented:
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.
0
 
bnussbaumAuthor Commented:
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.
0
 
zelron22Commented:
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?  

0
 
bnussbaumAuthor Commented:
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.    
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

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