OWA Log Off

[erlareynis8]

We are having problem with OWA. Whenever the user clicks the Log Off button it takes them to a page that says "the page cannot be displayed" and it is a "HTTP 500 Internal Server Error". Before it used to come up with a Microsoft Outlook Web Access window asking the user to close the browser which would then bring up another confirmation screen. What can we do to bring back this secure log off option for our users?

 

[Xelitus]

I'm having the exact same issue and I can't seem to resolve it through creating virtual apps or adjusting permissions.

Any help would be greatly appreciated.

XeLiTuS

 

[wallst32]

From IIS, go to the virtual directory exchweb under the default web site. Change its directory access permissions to match the permissions set in ESM exchange and public HTTP virtual servers. If you're using SSL this probably means checking just the basic authentication box and leaving all others unchecked.

 

[Xelitus]

I appreciate the input wallst32. Yes I'm using SSL. But now it seems I'm getting a new error. With the changes you suggested this is the error I now recieve:

https://servername/exchweb/bin/USA/logoff.asp

HTTP 403.1 Forbidden: Execute Access Forbidden
Internet Information Services

Background:
You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed.

After receving this new message I attempted to change the Execute permissions to Scripts and Executables on the bin\usa virtual directory and it just gives me the original error message HTTP 500 server error.

Any additional insight would be very welcome!

Thanks,
Xelitus

 

[wallst32]

Have you made many modifications to the default settings (scripts+exec should have been default on bin)?

When you changed the permissions on exchweb did you also propogate them down to all child nodes (including bin)?

Are you specifiying default domains in the authentication settings? If so, make sure these match everywhere also.

As long as ISM exchweb and ESM http virtual directory permissions match exactly, you shouldn't have any problems.