1) Right click on your OWA, ActiveSync rule or create a new one
2) Click Properties
3) Click the tab ‘Paths’
4) Click Add
5) Add the line, as shown in the screen shot below
6) Apply changes
This was tested on a Windows 2003 server. The issue was, when the server was rebooted, the ISA services had to be manually started and would not start automatically.
1) Click Start
2) Click run
3) Type regedit and click OK. (Ensure you have a backup)
4) Navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
5) Right click and create a new DWORD key
6) Name the DWORD key ServicesPipeTimeout
7) Click decimal and type value of 60000 (This is 60 seconds)
8.) Reboot the server and services should start automatically
You receive multiple event 23002 alerts within the event log. See below:
Message group: Alert24
Application: Event Log
Text: EventType: Warning, EventSource: Microsoft ISA Server Web Proxy, EventID: 23002,
EventDescription: ISA Server was unable to decompress a response body from www.domainname.co.uk because the response was
compressed by a method which is not supported by ISA Server. This happens when a Web server is configured to supply responses
compressed by a method that is not supported by ISA Server regardless of the type of compression requested.
If you want ISA Server to block such responses, configure the policy rule’s HTTP policy to block the Content-Encoding header in responses.
Otherwise, such responses will be forwarded without decompression to the client and can be cached.
You can cancel or reduce the frequency of the alert generated by this event in ISA Server Management.
A solution is to disable the compression filter by clicking configuration within ISA, add-ins and then disabling the filter.