Weird Problems with RPC over HTTPS Clients

[RoderickM]

I have clients at a remote site that are using RPC over HTTPS to access their e-mail using Outlook 2003. They can access everything just fine, but they are having a few annoying issues, such as their rules running minutes after e-mail is delivered to their mailbox and when they send mail it looks like the message is stuck in the outbox, but it is not, the mail was actually sent, it is just that the outbox did not refresh. What leads me to believe that it has to do with RPC over HTTPS is because only the users using it are having these weird problems. Any ideas?

 

[ShackDaddy]

Have you run Outlook with the /rpcdiag switch on to see if there is anything strange reported? You can also collect performance counters on the server related to client-side RPC activity. Look in the MSExchangeIS object. There are counters there like these:

Client: RPCs Failed: Server Unavailable
Client: RPCs Failed: Server Too Busy / sec
Client: RPCs Failed: Call Failed / sec
Client: RPCs Failed: Call Cancelled / sec
Client: RPCs Failed: All other errors / sec
Client: RPCs Failed: Access Denied / sec
Client: RPCs Failed / sec
Client: Background RPCs Failed / sec
Client: Foreground RPCs Failed / sec
Client: Latency > 10 sec RPCs
Client: Latency > 5 sec RPCs
Client: RPCs Succeeded / sec

Keep an eye on them and troubleshoot with what you find. If you see problems in the stats, let us know and one of us can point you to next steps.

ShackDaddy
Shackelford Consulting