Server 2008 Exchange 2007 Hello I am trying to enable outlook anywhere and i get the error below. I have try to run get-outlookanywhere |fl and i get nothing but the bash. I have rpc proxy installed. I see RPC and RpcWithCert virtual directory in IIS and i get user name password when i try accessing it though i remove them and re created them. In AD there is a RPCServices under System but it is empty. I have a certificate installed from godaddy. I have deleted the own certificate that was issued by the server. I don't know what else to check :( Please advise. Error: Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 EX1 Failed ---Error Begin---- The Active Directory object for virtual directory 'IIS://EX1.server.local/W3SVC/1/ROOT/Rpc' on 'EX1' 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 Warning: Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately fifteen minutes. To verify that Outlook Anywhere has been enabled, check the application event log on server EX1. Exchange Management Shell command attempted: enable-OutlookAnywhere -Server 'EX1' -ExternalHostname 'mail.server.com' -DefaultAuthenticationMethod 'Ntlm' -SSLOffloading $false Elapsed Time: 00:00:00 ---Error End----

Hi 'IIS://EX1.server.local/W3SVC/1/ROOT/Rpc’ I just search it. It seems to be object of IIS metabase. So restart IIS and try again. ADSUTIL is the tool to set IIS . But I am not good at this tool.

Restarting IIS is not the solution. I have restarted IIS lots of times and it did nothing. Any other suggestions? Is there a repair for Exchange without wiping the configuration?

Someone?

Disable Outlook Anywhere in Exchange. Wait at least 15 minutes and you should see something in the event viewer. Then remove the RPC proxy component from IIS. Run IISRESET. If the two RPC virtual directories are still in place, delete them and run IISRESET again. This writes the changes to the IIS metabase. Then reinstall the RPC Proxy component in IIS. Again run iisreset. Finally enable Outlook Anywhere, again waiting for the event in the Application log. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Simon Thank you for your reply. I have done what you wrote here and it reply the folowing error when trying to enable Outlook Anywhere: Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 EX1 Failed Error: The Active Directory object for virtual directory 'IIS://EX1.server.local/W3SVC/1/ROOT/Rpc' on 'EX1' 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 Warning: Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately fifteen minutes. To verify that Outlook Anywhere has been enabled, check the application event log on server EX1. Exchange Management Shell command attempted: enable-OutlookAnywhere -Server 'EX1' -ExternalHostname 'mail.server.com' -DefaultAuthenticationMethod 'Ntlm' -SSLOffloading $true Elapsed Time: 00:00:00 It say to "Remove the object from Active Directory". What do i need to remove?

I haven't seen this error with RPC before, so I am not sure what will work. Repeat what I wrote above, up to the point of reinstalling the component. So ensure that the proxy has gone from IIS components in Server Manager, the two virtual directories have gone and IISRESET was run to update the metabase. Then open the following location. C:\Windows\system32\inetsrv\config look for a file called ApplicationHost.config and take a copy so you can put it back if required. In that directory there shouldn't be many, if any references to /rpc or /rpc-with-cert. Now I can't be 100% sure what it is looking for, so you may have to experiment. If you find that it breaks something, then the copy will have to go back. Unfortunately you will be running iisreset a lot so the file is read by IIS. It isn't something I have done myself, so the above is a little bit of a guess I am afraid. It is where I would start if it was one of my servers. Otherwise it is going to have to be a call to Microsoft support, as they can remote in to the server and correct the issue for you. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.