locked
Event ID 139 MSExchange Owa WAC - There was an error setting up WacConfiguration RRS feed

  • Question

  • Getting the following error message once per day it seems:

    There was an error setting up WacConfiguration. Wac will be disabled and we will fall back to stellent. The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'

    Exchange 2013 CU9 on 2012R2 (currently coexisting with one Exchange 2007 server). Everything seems to work fine, just wondering if there is something I need to do to address this error?

    Can't find a whole lot about this particular error searching online...

    Thursday, August 20, 2015 4:20 PM

Answers

  • Thank you gentlemen, there doesn't seem to be a lot of info on this at all. And like I said, everything is working so I don't think it's a problem, but just wanted to see if anyone else has encountered it.

    I checked Get-OrganizationConfig and can't even see a WacUrlHostname property (only a WACDiscoveryEndpoint which is null).

    If it is related to Office Web Apps, we do not have a Web Apps Server installed so I guess I will just continue to ignore the error. I'm finding a lot of little errors or warnings like this in 2013 that seem to be of no consequence which is kind of irritating but oh well.


    Sorry, endpoint is what I meant! But yes, you can ignore. I think the assumption is that everyone configures it..

    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Ed CrowleyMVP Thursday, August 20, 2015 11:21 PM
    • Marked as answer by David Wang_ Tuesday, September 8, 2015 5:35 AM
    Thursday, August 20, 2015 9:46 PM
  • Thank you gentlemen, there doesn't seem to be a lot of info on this at all. And like I said, everything is working so I don't think it's a problem, but just wanted to see if anyone else has encountered it.

    I checked Get-OrganizationConfig and can't even see a WacUrlHostname property (only a WACDiscoveryEndpoint which is null).

    If it is related to Office Web Apps, we do not have a Web Apps Server installed so I guess I will just continue to ignore the error. I'm finding a lot of little errors or warnings like this in 2013 that seem to be of no consequence which is kind of irritating but oh well.

    • Proposed as answer by David Wang_ Friday, August 21, 2015 3:10 AM
    • Marked as answer by David Wang_ Tuesday, September 8, 2015 5:36 AM
    Thursday, August 20, 2015 6:20 PM

All replies

  • When citing an entry in the event logs, please post the entire event log entry.  You are welcome to use the handy-dandy "copy to clipboard" button in the event log detail window to assist you with this.

    Did you install Office Web Apps on that server?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."


    Thursday, August 20, 2015 4:40 PM
  • Nothing extra installed on server...just did a straight Next,Next Next of Mailbox and CAS roles.
    Log Name:      Application
    Source:        MSExchange OWA
    Date:          8/20/2015 7:28:25 AM
    Event ID:      139
    Task Category: Wac
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mail.domain.local
    Description:
    There was an error setting up WacConfiguration. Wac will be disabled and we will fall back to stellent. The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange OWA" />
        <EventID Qualifiers="49152">139</EventID>
        <Level>2</Level>
        <Task>10</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-08-20T11:28:25.000000000Z" />
        <EventRecordID>51656</EventRecordID>
        <Channel>Application</Channel>
        <Computer>mail.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'</Data>
      </EventData>
    </Event>

    Thursday, August 20, 2015 4:56 PM
  • I can't find anything on that, sorry.  You might look at the output from Get-OrganizationConfig to see if anything might be misconfigured.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Thursday, August 20, 2015 5:47 PM
  • If you havent enabled the org for Office Web Apps Integration, you will see that error after CU6 IIRC.

    If you want to enable integration  see:

    https://technet.microsoft.com/en-us/library/JJ150495(v=EXCHG.150).aspx

    Otherwise, you can ignore that error from what I have seen.


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Thursday, August 20, 2015 6:00 PM
  • Thank you gentlemen, there doesn't seem to be a lot of info on this at all. And like I said, everything is working so I don't think it's a problem, but just wanted to see if anyone else has encountered it.

    I checked Get-OrganizationConfig and can't even see a WacUrlHostname property (only a WACDiscoveryEndpoint which is null).

    If it is related to Office Web Apps, we do not have a Web Apps Server installed so I guess I will just continue to ignore the error. I'm finding a lot of little errors or warnings like this in 2013 that seem to be of no consequence which is kind of irritating but oh well.

    • Proposed as answer by David Wang_ Friday, August 21, 2015 3:10 AM
    • Marked as answer by David Wang_ Tuesday, September 8, 2015 5:36 AM
    Thursday, August 20, 2015 6:20 PM
  • Thank you gentlemen, there doesn't seem to be a lot of info on this at all. And like I said, everything is working so I don't think it's a problem, but just wanted to see if anyone else has encountered it.

    I checked Get-OrganizationConfig and can't even see a WacUrlHostname property (only a WACDiscoveryEndpoint which is null).

    If it is related to Office Web Apps, we do not have a Web Apps Server installed so I guess I will just continue to ignore the error. I'm finding a lot of little errors or warnings like this in 2013 that seem to be of no consequence which is kind of irritating but oh well.


    Sorry, endpoint is what I meant! But yes, you can ignore. I think the assumption is that everyone configures it..

    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Ed CrowleyMVP Thursday, August 20, 2015 11:21 PM
    • Marked as answer by David Wang_ Tuesday, September 8, 2015 5:35 AM
    Thursday, August 20, 2015 9:46 PM