Keep in mind that that Exchange 2007 had a throttle value on it courtesy
of the coding team of SBS 2008.
*msExchESEParamCacheSizeMax*. 64000
Just throwing that out as a fyi.
On 12/18/2014 10:40 PM, Daniel Chenault wrote:
I would expect a resource shortage or throttling.
Take a network trace. The wire never lies.
*From:* James Hill <mailto:[email protected]>
*Sent:* Thursday, December 18, 2014 6:52 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* RE: [Exchange] RE: Exchange 2013 application relay issue
Thanks Daniel.
It is using a 3^rd party plugin of some sort. The challenge is that
the issue did not occur on the previous server which was an SBS server
with Exchange 2007. So the LOB app providers point the finger at what
has changed (the new exchange server). I see their point.
Why does restarting the Transport service resolve the issue? Does it
force close a stuck connection perhaps?
James.
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Daniel Chenault
*Sent:* Friday, 19 December 2014 12:45 PM
*To:* [email protected]
*Subject:* Re: [Exchange] RE: Exchange 2013 application relay issue
Remote(socket error) specifically means the remote socket did not
acknowledge a packet. I'd focusing my efforts on the LOB app.
Hopefully it has extended logging of some type.
On Dec 18, 2014, at 18:42, "James Hill" <[email protected]
<mailto:[email protected]>> wrote:
Hmm.. I can’t see it there Michael. Here is the log:-
2014-12-18T23:17:34.874Z,SERVER\AppRelay,08D1E88C8D1C474A,30,192.168.2.21:25,192.168.2.103:52572,>,250
2.1.5 Recipient OK,
2014-12-18T23:17:34.890Z, SERVER
\AppRelay,08D1E88C8D1C474A,31,192.168.2.21:25,192.168.2.103:52572,<,DATA,
2014-12-18T23:17:34.890Z,SERVER\AppRelay,08D1E88C8D1C474A,32,192.168.2.21:25,192.168.2.103:52572,>,354
Start mail input; end with <CRLF>.<CRLF>,
2014-12-18T23:18:43.656Z,SERVER\AppRelay,08D1E88C8D1C474A,33,192.168.2.21:25,192.168.2.103:52572,-,,Remote(SocketError)
James.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *Michael B.
Smith
*Sent:* Friday, 19 December 2014 12:29 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* [Exchange] RE: Exchange 2013 application relay issue
You need to know which socketerror it is. If you enable verbose
logging on the connector, the error number is one of the fields.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *James Hill
*Sent:* Thursday, December 18, 2014 7:55 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* [Exchange] Exchange 2013 application relay issue
I’m currently investigating an issue for a client with Exchange
2013. They have a single Exchange 2013 SP1 server running in a
2012 R2 VM on 2012 R2 Hyper-V Host.
I have configured a receive connector (Apprelay) that allows their
LOB app (a payroll program) to send out emails.
From time to time the LOB app crashes while attempting to send out
emails via the Apprelay connector. After restarting the LOB app
it still isn’t able to send emails. However, restarting the
Exchange Transport service temporarily resolves the issue.
When it fails the SMTP log on the exchange server shows a socket
error:-
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Remote(SocketError)
I’m not sure where to look for the cause from here. Network
layer? Suggestions please?
James.
