none
Publishing OWA - You have attempted to access a restricted URL RRS feed

  • Question

  • Hi There,

    I know there are similar topics in this forum, but until now I was not able to get a result from following the information.

    I'm publishing OWA via UAG SP1, Update 1 (TMG + SP2)

    I'm using the "Apply an Outlook Web Access look and feel" option from the Advanced Trunk Configuration, Authentication tab.

    After i enter my credentials name and password, i receive a warning: You have attempted to access a restricted URL

    On the Web Monitor I see this:

    A request from source IP address ##.##.###.###, user j.surname@domain.com
    on trunk httpstrunk; Secure=1 for application Internal Site of type
    InternalSite failed. The URL
    /InternalSite/HASH_90a9c086-fa75-4d75-bea7-d31cbe9a9c93 contains an illegal
    path. The rule applied is Default rule. The method is GET.

    With the debugging ON:  On the Windows client machine i see this:

    HTTP error 404.0 - Not Found
    The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

    IIS Webcore
    Requested URL http://localhost:6001/Internalsite/HASH_<number>
    Physical Path: c:\program....\MS FF UAG\von\InternalSite\HASH_<number>
    Logon Method: Anonymous
    Logon User: Anonymous

    When I use the UAG login page instead of the "Apply an Outlook Web Access look and feel" it is working and I do see the OWA GUI correctly!

    Now the strange think is, after I get the error, when I put in the webservers address (https://mail.domain.com/owa) ones more then I do get to see the OWA GUI correctly!

    Now, an other the strange think is that on an mobile client, the "light version" gets selected automatically and then I do see the OWA GUI correctly!

    As it turned out later, this topic is about the same issue and points to the potential culpritt being the MS12-026 patch.

    http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/ade6cc85-98eb-40b4-9baa-5248704cd207

    Thanks for your help in advance.

    John



    • Edited by JohnDBE Wednesday, April 18, 2012 2:04 PM
    Friday, April 13, 2012 3:31 PM

All replies

  • John,

    I configured my UAG array exactly as you have done and now I do not get the error in the login process to OWA. The error started for me after applying MS12-026 released with the April security patches, but is is the same error as you get.

    A request from source IP address <source_addr>, user <username> on trunk <trunk_name>; Secure=1 for application Internal Site of type InternalSite failed. The URL /InternalSite/HASH_c0d29d6f-8aca-4768-8080-2596927a315a contains an illegal path. The rule applied is Default rule. The method is GET.

    Tuesday, April 17, 2012 2:59 PM
  • Hi David,

    Yes I have seen your topic on this issue after i posted mine.
    Of course I didn't know that MS12-026 was the root cause of the issue, because i configured OWA after i installed the patch.

    Do you think we are the only two guys that patched our UAG servers and publish OWA with OWA Look & Feel?
    There must be others out there.

    I hope someone from Microsoft can pick this up from this forum.

    John

    Tuesday, April 17, 2012 3:06 PM
  • Looks like it's just us so far, but since you have it two I can show my contact at Microsoft it's not just my installation and get it pushed along.

    Thanks

    Dave

    Tuesday, April 17, 2012 3:36 PM
  • Dave thats cool, i wish i had such a contact too.
    Please keep me informed, thanks in advance.
    Wednesday, April 18, 2012 6:08 AM
  • A ticket has been opened with PSS.

    Will follow up with the outcome of that.  So far it's in the investigation stage.

    Friday, April 20, 2012 6:00 PM
  • Hi David,

    Did you get any info? I installed MS12-026 and had to uninstall it but it seems like the issue is random now... sometimes it works, sometimes it doesn't.

    I get the same exact error.

    Mike

    Wednesday, April 25, 2012 1:39 AM
  • Hi Mike,

    No I have nothing new to report.  I should be having a conference call with Microsoft sometime this week to get an update on the issue.  I'll post back here with anything new to add.

    Dave

    Wednesday, April 25, 2012 3:10 PM
  • Hi David

    We have the same problem. Do you have any news?

    Heinz 

    Monday, May 7, 2012 7:38 AM
    • Proposed as answer by David Humber Tuesday, June 5, 2012 5:59 PM
    • Unproposed as answer by David Humber Tuesday, August 7, 2012 4:15 PM
    Tuesday, May 15, 2012 2:29 PM
  • For all those still following this thread.

    SP 2 has been released and will correct this issue observed in MS12-026.

    Get the service pack here.

    http://support.microsoft.com/kb/2710791

    • Proposed as answer by David Humber Tuesday, August 7, 2012 4:15 PM
    Tuesday, August 7, 2012 4:15 PM