SMP3 sp11 pl02 - unexpected network disconnect on removal of order

[Former Member]

I am still receiving unexpected network disconnects even after upgrading our SMP server to sp11 pl02.  Is there any workarounds for this issue?

[Former Member]

THis is still an issue and happening when I'm running client and server locally so I don't think its really a network issue.

[mark_pe]

Heather,

Your symptom above is what is normally seen in a time out issue.

I based this statement above on this part of your title "

disconnect on removal of order

" :

Removal of order is a process wherein the device uses its processing power to individually remove each order as indicated by the backend.

This situation is normally resolved with the following techniques:

Cause 1: Device is memory limited

Solution 1: Get a better device  (Try to use stronger device like iOS more than WinCE 6.5 mobile)

Solution 1b: If you are stuck with an older device (Motorola MC-X where X is the model) then try to limit the design by reducing the blueprint (ex: Remove unused screens and others) from the editor and republish it.

Cause 2: Time out issue

Solution 2: Increase time out for both server and client (need to double check logs that you are hitting the max and you may need to tweak time out).  Double check your settings in transmitconfiguration area in editor or SMP 3.0 cockpit settings.

Cause 3: The transmit is taking too long that sometimes you just simply gets disconnected from the Wireless area. 

Solution 3: Do LAN line transmit or make sure you have a good signal area on wireless transmit.

Hope this helps.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

mark ... cause 1 shouldn't be the case -- I'm running on an HP laptop running with 16g memory;

cause 2 - could you be more specific about these settings... I've attached what I have in the cockpit and transmitconfigurations.ini;  can you give me some suggestions for changes.   we are running in a clustered environment with and alias https://agentry-qa.network.com/wmqa .... should that be set in the serverAdress as such;  What should the timeout settings be

[Former Member]

I don't think the issue is without timeout ... whne I'm getting this its working with 1 order

[mark_pe]

Heather,

It seems you have a big time out for your settings.  Normally you just look at the logs to see when you started your transmit  time zero (t0)  and when it failed time failed (tf).  From here you can determine your best time out settings to specify.

I only see your client screen but underneath the transmit screen you need to look at the messages.log file when it failed (F).

HP laptop means it has power so my cause 1 cannot be used here.  I just had to share it because people may not know a transmit can fail if they are using smaller devices (32 meg memory).

WiFi could still be an issue (cause 3).  But I noticed in your picture above, you have it setup for reconnect ever 60 seconds (reconnectAttemptPeriod).  Do you want to try if your issue is a disconnect to setup your retry for every 5 seconds instead of 60 seconds?  The theory here is just in case you have a transmit drop out.  This is because when you stated it works when you press transmit again then it could be just a WiFi drop out.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

mark... this is from my messages log... I got it right after sending client info

I,  9,  1,  1, 08/19/2016 14:27:02,    ,    0,  580,            , ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB Q,  9,  1,  1, 08/19/2016 14:27:02,    ,    0,  580,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB A,  9,  1,  1, 08/19/2016 14:27:02,    ,    0,  580,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB S,  9,  1,  1, 08/19/2016 14:27:12,  16,    4,  580,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB I, 202, 20,  2, 08/19/2016 14:27:12,    ,    0,  1576,            , ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB Q, 202, 20,  2, 08/19/2016 14:27:12,    ,    0,  1576,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB A, 202, 20,  2, 08/19/2016 14:27:12,    ,    0,  1576,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB C,  9,  1,  1, 08/19/2016 14:27:12,    ,    4,  580,      48905, >unknown< S, 202, 20,  2, 08/19/2016 14:27:12,  0,    2,  1576,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB R, 202, 20,  2, 08/19/2016 14:27:12,  3,    2,  1579,      48905, ANGEL: 8370CA52-7467-45B3-94E9-92916377E8EB F, 202, 20,  2, 08/19/2016 14:27:12,    ,    2,  1579,      48905, >unknown<

[Former Member]

The last line has the Failure but I'm not sure what its telling me....

[mark_pe]

Heather,

After looking at your message.log. It is a hard stop and not a time out issue.  So either you have a means to do a hard stop like a specific time out setup or a firewall that thinks that the transmit requires a hard stop.  May try to at least double check you have no security firewalls at work here. 

As mentioned you can also try setting your retry attempt to 5 seconds just in case, it fails (F) the system will try to restart the transmit without the need for you to press the transmit button.  There are special features in the transmit that detects a retry and special feature that detects if you are transmitting in the middle of building a table.

I am not sure how many Workorders do you get before you get kicked out too.  What is the # of WO's before failure?  Or how many WO's do you have?  You said it works with 1 order.  So at least we have a basis of success. So what is the basis of failure?  The time is so quick for you to get an F.  Are you using VPN during transmit?  Is this VPN with iOS - there are reports on VPN disconnects with iOS OS?

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Thanks Mark!  I am saying that I can get the unexpected network disconnect with 1 order... sometimes it goes right through and other times it stops ...no reason really.  I will try setting the retry to 5 and see if that helps at all.  I am not on an IOS device.  I am running windows 7.

If it were a firewall, I would think it would happen every time...Thoughts?

[mark_pe]

Heather,

Okay doing 1 or more workroders are inconsistent.  It just happens once in a while.  Try to see if it firewall related.  Try to turn off firewall and let it run.  See if it stops.  If not then that may be a lead.  The reason I stated firewall, this was based on an older issue that we cannot duplicate and it happens randomly.  It turned out to be a firewall and/or load balance issue. 

The firewall stops it (thinking it was an attack). The load balance issue, think that the transmit is writing to a hard drive that it should not be so it turns it off (or the load balancer has a default time out of 5 minutes and it cuts it all the time). 

For the load balancer issue, I heard from that issue that if nobody sets up the timer correctly (just took default) it has a hard stop of 5 minutes.  Most companies always take the out of the box load balance default settings and they don't realize that it also stops transmits.  You have to ask yourself, do you have loadbalancer? If yes, did anybody setup the default time or hard stop of it? If not there is a default hard stop timer to stop the transmit.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Mark... I downloaded and applied the new server patch and am still getting the error 11.  this is what it said in the log .... I doubt the loadbalancers hard stop (which i checked and thats not the issue) is within 7 ms?  We are in training ready for go live in 2 weeks... is there any more information i can provide to help troubleshoot this?

2016/08/31 10:02:21.611:     + WorkFunction=000000015DB7F558

2016/08/31 10:02:21.611:       + User=wmqa-48905

2016/08/31 10:02:21.611:         + Application=wmqa

2016/08/31 10:02:21.611:           Server timezone = Eastern Daylight Time, Daylight Savings = Yes, Time difference = 14400

2016/08/31 10:02:21.611:           Received Client Time Info: client 10:02:21 AM 8/31/2016 server 2:02:21 PM 8/31/2016

2016/08/31 10:02:21.611:           Client Time Zone: Eastern Daylight Time

2016/08/31 10:02:21.611:           + User=wmqa-48905

2016/08/31 10:02:21.611:             + ANGEL Vine=3639809988

2016/08/31 10:02:21.611:               Sending response, type 27

2016/08/31 10:02:21.611:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:21.611:                 Attempt to send 35 bytes of data

2016/08/31 10:02:21.611:                 + Data Chunk=0

2016/08/31 10:02:21.611:                   Sending 35 bytes of data (with header)

2016/08/31 10:02:21.892:     + WorkFunction=000000015DB7F558

2016/08/31 10:02:21.892:       + User=wmqa-48905

2016/08/31 10:02:21.892:         + Application=wmqa

2016/08/31 10:02:21.892:           + User=wmqa-48905

2016/08/31 10:02:21.892:             + ANGEL Vine=3639809990

2016/08/31 10:02:21.892:               Sending response, type 74

2016/08/31 10:02:21.892:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:21.892:                 Attempt to send 10 bytes of data

2016/08/31 10:02:21.892:                 + Data Chunk=0

2016/08/31 10:02:21.892:                   Sending 10 bytes of data (with header)

2016/08/31 10:02:27.955:     + WorkFunction=000000015DB7F558

2016/08/31 10:02:27.955:       + User=wmqa-48905

2016/08/31 10:02:27.955:         + Application=wmqa

2016/08/31 10:02:27.955:           Sending ReplaceBusinessObject

2016/08/31 10:02:27.955:           + User=wmqa-48905

2016/08/31 10:02:27.955:             + ANGEL Vine=3639809992

2016/08/31 10:02:27.955:               Sending response, type 23

2016/08/31 10:02:27.955:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:27.955:                 Attempt to send 2865 bytes of data

2016/08/31 10:02:27.955:                 + Data Chunk=0

2016/08/31 10:02:27.955:                   Sending 2865 bytes of data (with header)

2016/08/31 10:02:28.408:     + WorkFunction=000000015DB7F558

2016/08/31 10:02:28.408:       + User=wmqa-48905

2016/08/31 10:02:28.408:         + Application=wmqa

2016/08/31 10:02:28.408:           + User=wmqa-48905

2016/08/31 10:02:28.408:             Originator exception:

2016/08/31 10:02:28.408:             + User=wmqa-48905

2016/08/31 10:02:28.408:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:28.408:                 Sending disconnect for vine 3639809992

2016/08/31 10:02:28.408:             Message failure case: 13 (Receiver Exception)

2016/08/31 10:02:28.408:             + User=wmqa-48905

2016/08/31 10:02:28.408:               Received Business Object Fetch message 298 status changed to 'Failed'

[Former Member]

here are the details from the Messages.log

S, 202, 20, 294, 08/31/2016 10:02:21,  26,     6,  2255,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

R, 202, 20, 294, 08/31/2016 10:02:21,  27,     6,  2290,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 202, 20, 294, 08/31/2016 10:02:21,  27,    41,  2290,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

I, 200, 20, 295, 08/31/2016 10:02:21,    ,     0,   161,            , ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

Q, 200, 20, 295, 08/31/2016 10:02:21,    ,     0,   161,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

A, 200, 20, 295, 08/31/2016 10:02:21,    ,     0,   161,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 200, 20, 295, 08/31/2016 10:02:21,   0,     2,   161,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

C, 202, 20, 294, 08/31/2016 10:02:21,    ,    41,  2290,       48905, >unknown<

I, 623, 20, 296, 08/31/2016 10:02:21,    ,     0,    50,            , ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

Q, 623, 20, 296, 08/31/2016 10:02:21,    ,     0,    50,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

A, 623, 20, 296, 08/31/2016 10:02:21,    ,     0,    50,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 623, 20, 296, 08/31/2016 10:02:21,  67,   113,    50,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

C, 200, 20, 295, 08/31/2016 10:02:21,    ,     2,   161,       48905, >unknown<

R, 623, 20, 296, 08/31/2016 10:02:21,   0,   113,    52,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 623, 20, 296, 08/31/2016 10:02:21,  74,   123,    52,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

I, 622, 20, 297, 08/31/2016 10:02:21,    ,     0,   509,            , ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

Q, 622, 20, 297, 08/31/2016 10:02:21,    ,     0,   509,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

A, 622, 20, 297, 08/31/2016 10:02:21,    ,     0,   509,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

C, 623, 20, 296, 08/31/2016 10:02:22,    ,   123,    52,       48905, >unknown<

S, 622, 20, 297, 08/31/2016 10:02:22,  74,    10,   509,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

I, 201, 20, 298, 08/31/2016 10:02:22,    ,     0,   661,            , ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

Q, 201, 20, 298, 08/31/2016 10:02:22,    ,     0,   661,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

A, 201, 20, 298, 08/31/2016 10:02:22,    ,     0,   661,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

C, 622, 20, 297, 08/31/2016 10:02:22,    ,    10,   509,       48905, >unknown<

S, 201, 20, 298, 08/31/2016 10:02:27,  23,  3733,   661,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

R, 201, 20, 298, 08/31/2016 10:02:27,   0,  3733,   663,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 201, 20, 298, 08/31/2016 10:02:27,  23,  6598,   663,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

R, 201, 20, 298, 08/31/2016 10:02:28,   0,  6598,   665,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 201, 20, 298, 08/31/2016 10:02:28,  23, 10167,   665,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

R, 201, 20, 298, 08/31/2016 10:02:28,   0, 10167,   667,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

S, 201, 20, 298, 08/31/2016 10:02:28,  23, 11470,   667,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

R, 201, 20, 298, 08/31/2016 10:02:28,   3, 11470,   670,       48905, ANGEL: F278B057-4DCC-4FC8-9650-0EC6E3219C9E

F, 201, 20, 298, 08/31/2016 10:02:22,    , 11470,   670,       48905, >unknown<

[mark_pe]

Heather,

Hi. Let me try to look at your logs above in detail.  I am just finishing some meetings and after I am done, let me look at your data. You are using SMP 3.0 SP11 PL02. That is support recommendation to at least resolve one of the Error 11 issue that is most problematic.  Let me look at it closely and put it in my schedule to review.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

I upgraded the server to smp 3.0 sp11 pl03 this morning

[mark_pe]

Heather,

Sorry. Just got out of the meeting when I saw your comments.

So from your logs you have these 2 keywords in the log file.  You may need to look at the events.log and find the "Thr" Thread log for more details if it will give you more hints.

So what we have right now are the following:

• F, 201, 20, 298, 08/31/2016 10:02:22,    , 11470,   670,       48905, >unknown<
• AND
• This error
  

2016/08/31 10:02:28.408:                 Sending disconnect for vine 3639809992

2016/08/31 10:02:28.408:             Message failure case: 13 (Receiver Exception)

2016/08/31 10:02:28.408:             + User=wmqa-48905

2016/08/31 10:02:28.408:               Received Business Object Fetch message 298 status changed to 'Failed'

Error 13 is a transaction error tied to a business logic exception from the backend.  There has to be a failed Java transaction on the fetch when downloading your Object.

So there seems to be some Object Fetch - Populating data properties of one of your Objects.  This may be a Java + BAPI transaction that is happening that is failing.  With this failure, you got a disconnect message towards your SMP 3.0 server to disconnect the client.

So this could be a hard error tied to what is being fetch from the backend.  You may need to know or find out what is being retrieved.  You may check your SMPServerName-smp-server.log to make sense during the point of failure 10:02:28.408 (time frame).  Make sure your logs are in detail or full debug mode in both SMP 3.0 + JavaBE.ini so you can get more information.

Hope that after doing this step, you may get a hint or flag on what may be going on.  It may be just a hard error on the type of data you are downloading for your user.  is this happening for one user or all user?  I am speculating a hard error on the type of retrieval tied to that object.

In your title it is tied to removal of order.  Need to look at why it cannot remove it.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Mark... thanks for the info.  I don't have a java / sap backend.  We have an oracle backend.  And the error is sporadic so I'd be suprised if it was part of the fetch , but I could be wrong.  So since we don't have a java/ sap backend, is there a different set of troubleshooting steps we should do?

[Former Member]

this is happening sporadically for all users.  If it is a "hard" error, would it show in the log in debug mode?  I'm already running in a debug mode and can provide all the logs.

[mark_pe]

Heather,

This means that your debugging will be much easier as it is just DBMS or Oracle error.  So this is a hard error from the Object Fetch that may be tied to a SQL Oracle query.  You need to review your Agentry logs tied to Backend-SQL for details of the error.  If it is in deed a DBMS error then that will give you a hint on what to do.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Mark... there are no DBMS or oracle errors.  THe issue happens when its replacing / removing based on what queries had already ran.

[Former Member]

Here;s a piece of the thread log... its had alredy run all the quieries and was ready to send 32 orders... i could see it processed the first 4 in my transmit window before i got the error.  As soon as i hit start in the transmit window it immediately started and processed tall the records .

2016/08/31 10:02:27.767:           Fetch 'GetWorkorders': Committing transactions for Object 'Workorder' Read

2016/08/31 10:02:27.767:           ChickamingBackEndUserFetchConnection::endFetchObjectRead not supported

2016/08/31 10:02:27.767:           HTTPXML-HTTPXMLSystemConnection: commit transaction

2016/08/31 10:02:27.767:           + BackEnd=SQL-SQLSystemConnection

2016/08/31 10:02:27.767:             Oracle-SQL-SQLSystemConnection: commit database transaction

2016/08/31 10:02:27.767:             Commit database transaction

2016/08/31 10:02:27.783:           0 to delete

2016/08/31 10:02:27.783:           32 to send <--- all the oracle queries ran and the system knows how many to send

2016/08/31 10:02:27.783:           Sending ReplaceBusinessObject

2016/08/31 10:02:27.783:           + User=wmqa-48905

2016/08/31 10:02:27.783:             + ANGEL Vine=3639809992

2016/08/31 10:02:27.783:               Sending response, type 23

2016/08/31 10:02:27.783:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:27.783:                 Attempt to send 3733 bytes of data

2016/08/31 10:02:27.783:                 + Data Chunk=0

2016/08/31 10:02:27.783:                   Sending 3733 bytes of data (with header)

2016/08/31 10:02:28.252:     + WorkFunction=000000015FA6F5E8

2016/08/31 10:02:28.252:       + User=wmqa-48905

2016/08/31 10:02:28.252:         + Application=wmqa

2016/08/31 10:02:28.252:           Sending ReplaceBusinessObject

2016/08/31 10:02:28.252:           + User=wmqa-48905

2016/08/31 10:02:28.252:             + ANGEL Vine=3639809992

2016/08/31 10:02:28.252:               Sending response, type 23

2016/08/31 10:02:28.252:               + ANGEL Connection=10.205.157.69

2016/08/31 10:02:28.252:                 Attempt to send 1303 bytes of data

2016/08/31 10:02:28.252:                 + Data Chunk=0

2016/08/31 10:02:28.252:                   Sending 1303 bytes of data (with header)

[Former Member]

Mark... Where was the value that you had me set to make the transmit retry on error.  I don't think that's happening... i waited 10 minutes after error 11 and it never did try again

[mark_pe]

Heather,

Transmit retry on error, that is a different category or feature set of Agentry.  That is Error Handling (not a trivial topic and normally goes to SAP Services).

From your new log shown above, you are at the stage of sending data to the client from both Oracle and SMP 3.0.  So the culprit here is that the Agentry client may not be listening or got disconnected by means of the following (or one of the following):

• It could be that your device is sleeping (is it powered down or sleep mode or < 25% of battery left)
  • some devices defaults to turn off WiFi/GPRS on less than 25% of battery left
  • Need you to adjust power mode to keep all power
• From the start of the transmit to the point of failure could be more than 5 minutes?
  • Out of the box time out or idle time out for Agentry clients are typically 5 minutes.
  • What is your idle time out settings in the SMP 3.0 cockpit set to?
  • You can also see this in the initial Agentry.ini
  • This idle time out is when the user is not doing anything it forces the agentry client to lock it up.
  • You may also check your transmitconfiguration Angel connection in the editor on how long you have it set to stay connected to server?  If you have not set this this means it is hard coded for 5 minutes.
• Between all your logs, some of your logs stated Error 13 problem in the backend but your other logs stated it is sending to client
  • This means we have 2 different scenarios happening at the same time
  • Are you sure it is not firewall?
  • Can you do a test that is local to your environment to make sure Firewall (and turn off your firewall)  is not an issue across the network?

Best Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Transmit retry on error, that is a different category or feature set of Agentry. That is Error Handling (not a trivial topic and normally goes to SAP Services).Are there any documents on this ?  I will read and just handle it.

From your new log shown above, you are at the stage of sending data to the client from both Oracle and SMP 3.0.  So the culprit here is that the Agentry client may not be listening or got disconnected by means of the following (or one of the following):

• It could be that your device is sleeping (is it powered down or sleep mode or < 25% of battery left) *** NO … on full power; not sleeping I’m watching transmit run
  • some devices defaults to turn off WiFi/GPRS on less than 25% of battery left
  • Need you to adjust power mode to keep all power
• From the start of the transmit to the point of failure could be more than 5 minutes? ** No transmit started at 10:02:20 and errored at 10:02:28 ; 8 ms
  • Out of the box time out or idle time out for Agentry clients are typically 5 minutes.
  • What is your idle time out settings in the SMP 3.0 cockpit set to?  Are you talking about the Inactive timeout on the application-specific settings under the server section ?  If so its 2400
  • You can also see this in the initial Agentry.ini
  • This idle time out is when the user is not doing anything it forces the agentry client to lock it up.
  • You may also check your transmitconfiguration Angel connection in the editor on how long you have it set to stay connected to server?  If you have not set this this means it is hard coded for 5 minutes. Below is a copy of my trasnmitconfigurations.ini file

  [Network]

keepAlivePeriod = 2000

reconnectAttemptPeriod = 60

serverAddress = https://agentry-qa.fenetwork.com/wmqa   - is this right?  This is the server url that the client connects wi

attemptOnlinePeriod=60

serverInactiveTimeoutOverride=2000

• Between all your logs, some of your logs stated Error 13 problem in the backend but your other logs stated it is sending to client
  • This means we have 2 different scenarios happening at the same time
  • Are you sure it is not firewall?
  • Can you do a test that is local to your environment to make sure Firewall (and turn off your firewall)  is not an issue across the network  ?
• **how do I test this and why would it work immediately following the error and run through fine?  Because we use fully qualified server names wouldn’t it go through the firewall anyways?

[mark_pe]

Heather,

Another theory is that on different areas of the setup,some are in seconds and some are in milliseconds. I believed we updated some of the KBAs that pointed to seconds but it is in milliseconds. Need to find the keyword in the main documentation if it is in seconds or milliseconds because that could be the big deal that cuts communication.

I always have to bring firewall up as normally with incidents and tickets with different customers, the hardest one and the one that has no answer or solution always ends up to be firewall/load balaner issue but you need a firewall expert to review it.

Unless.. you are using a WinCE Windows Mobile 6.5 device and the reason for it getting disconnected is memory.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Mark .. I want to see if i can get a retry setup when we get these unexpected network disconnects in the transmit.  Who  can i discuss this with and how do i get a hold of them?

[mark_pe]

Heather,

The only link you will have that is "Free" or non-consulting base is this link.

Automatically reconnect the Agentry mobile client on drop connection or error 14 - SAP Mobility - SC...

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Mark-- Are you sure those settings still apply? I Noticed you wrote that in 2013.,  I tried them and didn't notice any retries at all.

[Former Member]

Mark, the keepAlivePeriod  isnt vaild on SMP 3, after the Transmit type was changed from ANGEL to Websockets.

[mark_pe]

Heather,

I believe that auto reconnect still applies. There were reports of incidents before for SMP 3.0 that uses this technique and it didn't work for some Android devices but it works on WPF and iOS devices so the Android Engineer had to do a workaround to make the Android clients work. That feature is more for wireless dropouts.  Your error above is more a hard error (Error 13).  The auto reconnect is if you are walking and you are in the middle of a transmit then all of a sudden your signal went bad then this should kick in.  It might be client based.  So my guess is load balancing or firewall or VPN or anything that will make the client shut the communication or it could be just the device itself like Windows Mobile 6.5 (Last time I check: we dropped this OS and device support for newer application ex: Work Manager 6.4 as it cannot handle the bigger blueprint [it dies during transmit - not enough memory] of higher versions of the product).

Best Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

WHat's the best way to troubleshoot the VPN /network issue?  I don't think its a loadbalance issue because we connect direclty to our training environment via a url https://servername:8081/wmtrain.    What are we looking for?

Could it be server related and not network?

THanks!

[mark_pe]

Steve,

Hi.  They probably remove the keyword - KeepAlivePeriod then.  These are the SMP 3.0 keywords supported for SMP 3.0 SP09 (Doc).  So basically from the auto reconnect adjust accordingly.  There are still keywords for auto reconnect that you can used under session.

~~~~~~~From SMP 3.0 SDK 9.0 doc ~~~~~~~~~~~~~~~~

1. TransmitConfigurations.ini

Within the TransmitConfigurations.ini file there is one section for each transmit configuration defined within the application, denoted as[<TransmitConfigurationName>], where<TransmitConfigurationName> is the name of the definition within the application project. Each section can contain override values for any and all attributes within a given transmit configuration definition.The following example shows several options that are valid within each section of the TransmitConfigrations.ini override file. The value forstayLoggedIn overrides the general attribute Stay Logged In.[<TransmitConfigurationName>]stayLoggedIn=trueretryPeriod=30retryAttempts=5onlineRetryAttempts=5synchronousRetryAttempts=5synchronousRetryPeriod=30serverInactiveTimeoutOverride=300All other attributes within the transmit configuration definition can be overridden using the proper key and value pair. Any attributes not overridden within this file are sent to Agentry Clients as defined in the application project.When using this override file for multiple Agentry applications, each server should have its own version of this file with its required configuration settings unique to that server instance.

1. TransmitConfigurations.ini Attributes

For information about the definition attributes, see Transmit Configuration inDeveloper > Agentry App Development > Agentry Language Reference > Application Level Definitions Overview.

Table 1: General Settings
Override Item	Setting	Acceptable Values	Description
	Name		The unique name of the transmit configuration. This value must be unique for all transmit configurations defined for the application.
displayName	Display Name	Any printable text.	Each transmit configuration defined in the application is listed in the Transmit Dialog on the Agentry application, so choose an appropriate Display Name that is clear to the application end user.
connectType	Connect Type	WebSockets over HTTPS	The communications protocol used when synchronizing with SAP Mobile Platform Server
xmitConfigGroup	Group	Transmit Configuration Group Name	The group into which the transmit configuration is organized within the application. Two default options are provided, Fast and Slow, or you can create a new group by entering a name in this field. It is then available in the drop-down list for all transmit configurations within the same application project.
failoverTo	Failover to	Name of other transmit configuration definition.	If the Agentry application is unable to connect the server using the first transmit configuration, you can select a failover transmit configuration. You can set to this attribute to any other transmit configuration within the application.
checkDataTables	Check Data Tables	true/false	Specifies whether the data tables within the application are synchronized when the transmit configuration is used.NoteConsider not selecting this attribute for transmit configurations intended for slower connection types..
checkComplexTables	Check Complex Tables	true/false	Specifies whether complex tables within the application are synchronized when the transmit configuration is used.NoteConsider not selecting this attribute for transmit configurations intended for slower connection types.
Table 2: Session Attributes
Override Item	Setting	Acceptable Value	Description
trackXmitEvents	Track Transmit Events	true/false	Whether to track transmit events.
stayLoggedIn	Stay Logged In		Select to indicate that the client user remains logged in and the application remains connected to the server to support real-time communications within the mobile application, which includes background sending and push behaviors. Set this attribute when an Agentry application requires a constant network connection to the back-end data.
promptOnLogin	Prompt on Log In	true/false	Select to display a prompt when the connection between the application and the server is lost, and the application attempts to reconnect.
promptOnLogout	Prompt on Log Out	true/false	Select to display a prompt when the Agentry application is logged out of the server.
serverInactiveTimeoutOverride	Inactive Timeout	Duration value in number of seconds.	Specifies the time limit in seconds to keep the application connected to the server, both when there is no data transmission activity between the client and server, and during an actual transmit. If you experience frequent disconnects, increase this number.
attemptOnlinePeriod	When Off-line	-1: Stay Off-line1+: Attempt to work on-line every [1+] seconds	If the connection to the server is lost, indicates whether to stay offline or attempt to reconnect at the specified interval.
onlineRetryAttempts	Attempts	Number of attempts to connect to server.	If you select to reconnect when offline, indicate the number attempts to reconnect. If the reconnect attempts fail, how the application responds depends on the Transmit Configuration attributes you defined. For example, the application can display a prompt or switch to the failover transmit configuration.
reconnectAttemptPeriod	Reconnect Attempt Period	Duration value in number of seconds	If online, indicates how often the client should try to reconnect.
retryPeriod	Retry Period	Duration value in number of seconds	If the connection to the server is lost, indicates how long to attempt to reconnect.
synchronousRetryPeriod	Synchronous Retry Period	Duration value in number of seconds	How often to retry a synchronous transmit.
synchronousRetryAttempts	Synchronous Retry Attempts	Number of synchronous attempts to connect to server.	Number of retries to make in a synchronous transmit.
synchronousPlaySuccessSound	Synchronous Play Success Sound	true/false	Whether to play a sound on synchronous success.
synchronousPlayFailureSound	Synchronous Play Failure Sound	true/false	Whether to play a sound on synchronous failure.
synchronousFailureSound	Synchronous Failure Sound	string	Identifies the failure sound to play, if enabled. If left blank, a default error beep is used.
synchronousSuccessSound	Synchronous Success Sound	string	Identifies the success sound to play, if enabled. If left blank, a default "OK" beep is used.

NoteThe synchronous transmit settings refer to communication that results from a transmit step in an Agentry action, not background sending nor pushes.

Table 3: Background Sending
Override Item	Setting	Acceptable Values	Description
backgroundConnection	Allow background sending from client	true/false	Whether to send transactions over background sending.
retryPeriod	Retry Period	Duration in number of seconds	If background sending is enabled, specifies the amount of time in seconds to wait between failed attempts to send a transaction.
retryAttempts	Retry Attempts	Number of background sending attempts to connect to server	If background sending is enabled, the number of attempts to send the transaction over background sending.
Table 4: Push
Override Item	Setting	Acceptable Values	Description
	Allow server to push data to client	None	Select to allow the server to push data to the application. A Pushes module definition must exist for the application. Users connecting to the server are logged in as Push Users.NoteYou must set this attribute before you can set the other Push attributes for the transmit configuration..
retryPeriod	Retry Period	None	If Allow Server to Push Data to Client is selected, specifies how long the server waits before attempting to resend data for a push when a failure occurs.
attempts	Attempts	None	If Allow Server to Push Data to Client is selected, specifies how many attempts to push data to the application when a failure occurs.

Table 5: Modem Settings
Override Item	Setting	Modem Attribute	Description
networkConnectionCheck	Check for Modem Connection	true/false	Select to specify whether that the Agentry application checks for a modem connection when using the transmit configuration prior to beginning the transmit.NoteYou must set this attribute before you can set the other Modem Connection attributes for the transmit configuration.
networkConnectionName	Connection Name	Name of Windows network connection.	Two options: Any Dial-up Connection requires that the user establishes the network connection manually outside the mobile application before beginning the transmit. In this case, the remaining modem connection attributes are disabled. Name of any Windows network connection configured on the client device. This option uses the settings of the specified connection to establish the modem connection to the network.
connectNetwork	If Not Connected	true/false	Specifies that the application attempts to create a connection using the specified Windows network connection when there is no current connection. If this option is not selected, the remaining modem connection attributes are disabled.
networkConnectionPrompt	Connect Prompt	Any printable text. Carriage returns not allowed. Text will auto-wrap when displayed on client.	Provides a message or instructions to the user on the client prior to attempting to create a modem connection. Leave blank if no message is required.
dialUsernamePrompt	Prompt User for Dial-up Username	true/false	If selected, prompts the user to enter a user name for the network connection, which is used as the login name for the network connection once the modem’s hand shaking processes are successful. If this option is not selected, the Agentry application login is used.
dialPasswordPrompt	Prompt User for Dial-up Password	true/false	If selected, prompts the user to enter a password for the network connection. If this option is not selected, the Agentry application password is used.
modemInitWait	Modem Init Wait	Duration value in milliseconds	Specifies the amount of time in milliseconds to wait for the client device’s modem to initialize before beginning the dial-up process.
postConnectWait	Post-connect Wait	Duration value in milliseconds	Specifies the amount of time in milliseconds to wait after the network connection is made before beginning the transmit process between the client and server.
closeConnectionPeriod	Close Connection	Duration value in seconds.	Specifies when to close the modem connection once no more data is being transmitted between client and server: Never If the connection is idle for the specified number of minutes and seconds.
remindToTurnOnModem	Remind to Turn On Modem	true/false	Whether to remind user to turn on modem.
remindToTurnOffModem	Remind to Turn Off Modem	true/false	Whether to remind user to turn

Best Regards,

Mark

[Former Member]

Are we still thinking that none of these settings would help with the error 11 that I'm seeing?

[Former Member]

What is track transmit events? where does it track them?

[Former Member]

I wanted to post back that although we are still getting error 11s, they seem to be reduced by reducing the number of versions running on the server and reducing the logging levels.  There is still an issue that I don't believe is network related because its happening within 15 seconds of the transmit running and not everytime.

[mark_pe]

Heather,

Error 11 is tied to threads or running out of available threads to be given to the mobile user.

By reducing log level, you reduce the requirement of the system to produce the threads.  So this is probably why it helps out.  The more debug level the more threads in general.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member]

Here's more info from one of the thread logs:

2016/08/11 16:09:28.236:           Sending DeleteBusinessObjects for 67 objects

2016/08/11 16:09:28.236:           + User=wmqa-48905

2016/08/11 16:09:28.236:             + ANGEL Vine=1286163698

2016/08/11 16:09:28.236:               Sending response, type 22

2016/08/11 16:09:28.236:               + ANGEL Connection=10.205.184.189

2016/08/11 16:09:28.236:                 Attempt to send 686 bytes of data

2016/08/11 16:09:28.236:                 + Data Chunk=0

2016/08/11 16:09:28.236:                   Sending 686 bytes of data (with header)

2016/08/11 16:09:29.158:     + WorkFunction=00000000415AF158

2016/08/11 16:09:29.158:       + User=wmqa-48905

2016/08/11 16:09:29.158:         + Application=wmqa

2016/08/11 16:09:29.158:           + User=wmqa-48905

2016/08/11 16:09:29.158:             Originator exception:

2016/08/11 16:09:29.158:             + User=wmqa-48905

2016/08/11 16:09:29.158:               + ANGEL Connection=10.205.184.189

2016/08/11 16:09:29.158:                 Sending disconnect for vine 1286163698

2016/08/11 16:09:29.158:             Message failure case: 13 (Receiver Exception)

2016/08/11 16:09:29.158:             + User=wmqa-48905

2016/08/11 16:09:29.158:               Received Business Object Fetch message 138 status changed to 'Failed'

[nageshcaparthy]

Hi Heather,

There may be many reasons for disconnects and trying to find the root cause is most important to fix the issue. I would request to get the SMP Servers logs to debug mode and check the logs for the reason of disconnect. If possible you may also check the client logs, not sure what applications you have.

Usually, such issues takes time to find the cause. Please share the details like what are the error screens or messages that you see when you are talking about unexpected network disconnect.

Regards,

Nagesh

[Former Member]

Nagesh... We are running an agentry application.  THe error shows up in the transmit window.  I will generate server logs to share.  There are no client logs that i know of.

[nageshcaparthy]

If its Agentry looping in Bill Froelich for further assistance.

Regards,

Nagesh

[Former Member]

Is there a code number with the error?

What lines are before the line with the error?
Are you able to open the URL in a web browser and get the "I am here" page?

[Former Member]

Unexpected disconnection from server 11

Here's a sample:

Yes the server is up and available.  I can immediately hit start in the transmit and it will continue rolling through as expected.

[Former Member]

Stephen... any updates on this?