Exchange system manager C103b405 error.

Posted on 2009-04-17
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
    LVL 15

    Expert Comment

    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

    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

    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

    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.    

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Find Ransomware Secrets With All-Source Analysis

    Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

    This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
    This tutorial will walk an individual through the process of upgrading their existing Backup Exec 2012 to 2014. Either install the CD\DVD into the drive and let it auto-start, or browse to the drive and double-click the Browser file: Select the ap…

    737 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

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now