Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Connect to Microsoft Exchange using HTTP

Hi all,

We have strange problem with outlook 2007 to an exchnage 2003 server.

If we remove the check from the “Connect to Microsoft Exchange using HTTP” all is fine and if we enable it the connections is flapping to the server in outlook.

Found CSCtg04561, but wrong version on server.

Any sugestion?


Jan Rockstedt

Cisco Employee

Connect to Microsoft Exchange using HTTP

Hi Jan,

What is the version on client and server side WAAS ? This defect is fixed in upcoming 5.x and 4.4.x code.

We do not have any such known issues but with that being said, will need more data in the form of sysreport, traces, MAPI debug level logs, etc to confirm. The best way is to open a TAC case with Cisco.


New Member

Connect to Microsoft Exchange using HTTP


4.4.3b on the server side 4.4.3 on the client side.

It tried yesterday with no accelerator mapi write-opt, same problem.

If it's been fixed as you write, then it must be an known problem?

Regards Jan

Cisco Employee

Connect to Microsoft Exchange using HTTP

Hi Jan,

The defect - CSCtg04561 is fixed in upcoming release. As mentioned above, this is not a known issue but may be specific to your environment.

Now, as this is related to HTTP, I would suggest you to look at connection details for the client side. Please use followign CLI command to find out the conenction details:

show stat conn | in

If this shows THDL / TSHDL / TSDL, means this is over HTTP / HTTPS blade. In that case you may want to play with HTTP AO rather than thinking MAPI issue.

Here is what I would suggest:

1. Open a TAC case with Cisco TAC team.

2. Generate and collect following logs for them for quick analysis:

     a. Collect Sysreport from client and server side WAEs.

     b. Start packet capture on client and server side WAEs, client itself and possibly on exchange server.

     c. Reproduce problem 2-3 times.

     e. Stop packet capture.

     f. Generate one more sysreport on both WAEs.

     g. Transfer packet capture file from WAE, 2 x sysreports from client side and server side WAEs.

     h. Provide client ip, exchange server ip and username, if possible.

This will help TAC to expedite the resolution.

Hope this helps.