[isapros] Re: RPC filter - connectivity changed
- From: "Jason Jones" <Jason.Jones@xxxxxxxxxxxxxxxxx>
- To: <isapros@xxxxxxxxxxxxx>
- Date: Tue, 15 Aug 2006 23:36:34 +0100
Ori/Jim,
Bit more info from testing today:
Created connectivity verifiers late last week for all exchange back-end
servers and was onsite today when the RPC filter failed again.
Symptoms
Basically what happens is that for no apparent reason all MAPI clients
lose access to Exchange and ISA logs repeated alerts saying "RPC filter
- connectivity changed". Accompanying these ISA logs, the application
logs says "unable to connect to ExchangeIP:135 connection failed"
quickly followed by "Connection to ExchangeIP:135 connection restored".
These errors loop to say connected then disconnected. Every time you
start a MAPI client and try to access Exchange more and more ISA alerts
are created and more and more application errors are generated.
During all this time, the RPC connectivity verifiers show good
connectivity to all Exchange servers.
Looking at the ISA logs, I traffic being logged as allowed, but every
connection seems to be followed by an instant "0x80074e24
FWX_E_CONNECTION_KILLED" entry.
Workaround/Current Fix
If you restart the firewall service on all array members then MAPI
clients can successfully connect to Exchange and continue working until
the filter fails again. Sometimes this is a few hours, sometime this is
a few days. These system is currently only in pilot so only has <15
users at the moment, so shouldn't be due to RPC filter load issues.
Is this another PSS call in the making? :-\
Any more ideas???
Cheers
JJ
________________________________
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Ori Yosefi
Sent: 09 August 2006 07:39
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RPC filter - connectivity changed
It does indeed sound strange.
I haven't heard of such a problem before, so I don't have any
recommendations how to fix it.
I would recommend that you add a connectivity verifier, if possible, to
the server. You can see if when you get the RPC alert you also get a
connectivity alert. It may provide some hints.
I would also suggest contacting PSS to get someone from Microsoft
investigate it.
HTH,
Ori.
________________________________
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Jason Jones
Sent: Wednesday, August 09, 2006 1:26 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RPC filter - connectivity changed
Thanks Ori - kinda how I expected the alert to be.
I get the ISA alerts 2/3 times every couple of weeks and lots of event
log errors, saying "RPC server available", then "RPC server unavailable"
in a complete loop. The only way to solve the issue is to reboot all
array members - ouch! Whilst ISA is in this state all existing MAPI
clients remain working, but all new sessions fail.
However, I can see no reason why the Exchange server (the RPC published
server) should suddenly appear unavailable - I also cannot see why the
destination server is at fault if a reboot of ISA fixes the problem.
Kinda feels like ISA is getting confused to me :-\
JJ
________________________________
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Ori Yosefi
Sent: 08 August 2006 18:23
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RPC filter - connectivity changed
This alert is issued when a published RPC server has gone offline / came
back online.
When attempting to establish a connection with the RPC server, if the
connection attempt fails (for the first time) then this alert is issued.
Later on, when a connection attempt is successful (for the first time)
then this alert is issued again.
HTH,
Ori.
________________________________
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Jason Jones
Sent: Tuesday, August 08, 2006 8:10 PM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] RPC filter - connectivity changed
Hi,
Anyone seen the "RPC filter - connectivity changed" ISA alert? Under
what scenario does this get trigged?
Is this an ISA problem or an indication that the published RPC server is
at fault?
Cheers
JJ
<<rpc filter.JPG>>
Other related posts:
