When installing Exchange 2010 CAS role on a fresh Windows 2008R2 hyper-v virtual server, installation bombs when trying to create the 'EWS' virtual directory. The error message suggests that this directory (IIS:///W3SVC/1/ROOT/EWS) may already exist in AD, but while investigating I cannot find any evidence that this is true. This is the first 2010 server being brought up alongside an existing Exchange 2003 organization. The domains were prepped with no errors, and the server itself has all required prerequisites installed.
When I run the command the installer is trying to run to create the EWS virtual directory at the command line in a power shell, I get the same error. If i use the get-webservicesvirtualdirectory cmdlet it reveals that the installer or command line method DID in fact create the virtual directories, yet the installation still fails. If i remove-webservicesvirtualdirectory and remove the EWS virtual directory, then re-run the installer, it bombs at the same point.
Here is the error mesage:
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear(); $urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx"; new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;" was run: "The Active Directory object for virtual directory 'IIS://servername.domain.com/W3SVC/1/ROOT/EWS' on 'servername' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
The Active Directory object for virtual directory 'IIS://servername.domain.com/W3SVC/1/ROOT/EWS' on 'servername' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
Unexpected Error
I am not really sure how to troubleshoot from here. Can anyone offer some advice? It almost seems that the directory is being created in AD, but somehow IIS is not seeing it, or something like this.
