About Me

My photo
This is a blog for John Weber. One of my joys in life is helping others get ahead in life. Content here will be focused on that from this date forward. John was a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). I used to write a variety of articles (https://tsoorad.blogspot.com) on technical issues with a smattering of other interests. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. The opinions expressed on this blog are mine and mine alone.

2011/07/20

Outlook Anywhere cannot be disabled

Onsite with a client and we are having issues with getting Exchange 2010 to enumerate CAS websites.

Here is the lovely error we got: 

-------------------------------------------------------

An IIS directory entry couldn't be created. The error message is The remote procedure call failed and did not execute.  . HResult = -2147023169 + CategoryInfo:NotInstalled: (servername\Rpc (Default Web Site):ADObjectId) [Get-OutlookAnywhere],

-------------------------------------------------------
Oh lovely.  Cannot enable, disable, or get anywhere with this.  Poked, prodded, googled, etc.  Nada.  Finally, in disgust, I believe what I am being told, to whit:

Action 'Disable Outlook Anywhere' could not be performed on object 'servername.'

Servername
Error:
The Outlook Anywhere feature has multiple configurations on servername.domain.com.

OK, so where does powershell get this data from?  AD.  So off we go to AD.  And what did I find hiding out:

CN=Rpc (Default WebSite),CN=HTTP,CN=Protocols,CN=servername, CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com

??

Two, count ‘em TWO RPC definitions.  Yup, the server (and AD) thought there were multiple configurations.  I carefully deleted one, and restarted the server.  And now I get much better response in enumerating Exchange web sites/services.  And OA can be configured again.

How it got there I have zero idea.  Three other CAS servers in the Org are just fine.  This one was just fine until about 1750 on 28 June 2011 when it was modified (according to AD) both at the same time.  Some sort of hitch in the get-along as far as I can tell.

YMMV.

4 comments:

Anonymous said...

Hi, I am having the same issue as yourself this morning.

I made a minor change to the properties of OWA yesterday and the change didn't show so I scheduled a reboot.

Came into work this moring and OWA doesn't work at all.
Getting exactly the same error as you had and can find no information about it other than this post!

I am struggling to fix it though.
Could I ask, how are you searching through AD to pull out that information?

tsoorad said...

I used ADSIEdit.

A.M. said...

Thanks for this! Much appreciated!
ADSIEdit is what I used as well.

tsoorad said...

glad to be of some help

test 02 Feb

this is a test it’s only a test this should be a picture