We have an Exchange 2007 CCR Cluster on Server 2008 X64 Enterprise.
Exchange 2007 CAS / Hub Transport role on Server 2003 x64.
Get error once run EMC from CAS -64 bit machine
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The following error(s) were reported while loading topology information:
Get-ActiveSyncVirtualDirectory
Failed
Error:
Unable to create Internet Information Services (IIS) directory entry. Error message is: Access is denied.
. HResult = -2147024891.
Access is denied.
.
Directory Path: IIS://<SVRNAME>.<domain>.com/W3SVC/1/ROOT/Microsoft-Server-ActiveSync
Detail:
server name: <SVRNAME>.<domain>.com
local machine name: <SVRNAME>
local machine fqdn: <SVRNAME>.<domain>.com
Access is denied.
Get-OabVirtualDirectory
Failed
Error:
Unable to create Internet Information Services (IIS) directory entry. Error message is: Access is denied.
. HResult = -2147024891.
Access is denied.
.
Directory Path: IIS://<SVRNAME>.<domain>.com/W3SVC/1/ROOT/OAB
Detail:
server name: <SVRNAME>.<domain>.com
local machine name: <SVRNAME>
local machine fqdn: <SVRNAME>.<domain>.com
Access is denied.
Get-OWAVirtualDirectory
Failed
Error:
Unable to create Internet Information Services (IIS) directory entry. Error message is: Access is denied.
. HResult = -2147024891.
Access is denied.
.
Directory Path: IIS://<SVRNAME>.<domain>.com/W3SVC/1/ROOT/owa
Detail:
server name: <SVRNAME>.<domain>.com
local machine name: <SVRNAME>
local machine fqdn: <SVRNAME>.<domain>.com
Access is denied.
Resolution:
I changed the DCOM Communication Properties on - 2003 Boxes to the following:
Run >> dcomcnfg
Component Services >> Computers >>
Right Click - My Computer
Choose Properties
Default Properties Tab:
Enable DCOM on this computer: Checked
Default Authentication Level: Connect
Default Impersonation Level: Impersonate
The only thing I changed was the Impersonation Level to "Impersonate"; which was by default, set to "Identify".
After the change; I restarted the EMC, and no more errors. Closing and reopening the EMC was essential or the errors would persist. Nevertheless, it is solved for now.
Reference:
http://msdn.microsoft.com/en-us/library/aa389284(VS.85).aspx
