Unexpected network disconnect

[Former Member]

I am seeing a large number of unexpected network disconnect errors during transmit.  I can make it happen on one particular transaction and when it errors and I hit start the transmit proceeds fine through applying the transaction.  This is not occurring when I'm bringing down large amounts of data.  Any ideas?

[Former Member]

We are running smp3.0 10 p8;  Our agentry app is used primarily for work management and timekeeping.  I can reproduce the network disconnect after adding a point to an order and the order is downloaded again.   I can provide logs if we think any would show an issue.  This particular error is reproducible. 

[Former Member]

Can you please post the error log file.

[Former Member]

WHich log file is that .... i don't see one that says error?

[Former Member]

events.log file and SMPServer.log file

[Former Member]

There was nothing at 10:24 when i got the error in either log;  I'm just getting .console###Agentry Timer Thread#########Exception: 10:23:58 05/17/2016 : 16 (SQLBEException), SAInvalidLogin (3: SA_DBMS_API_Error, DB Code: 0, DB Text:IM002 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, ),  because one of the apps i have setup has an odbc that wasn't created in system

[Former Member]

i found this in the worker thread log :

2016/05/17 10:24:25.141:           Sending ReplaceBusinessObject

2016/05/17 10:24:25.141:           + User=workmanagement_qa-48905

2016/05/17 10:24:25.141:             + ANGEL Vine=3431094288

2016/05/17 10:24:25.141:               Sending response, type 23

2016/05/17 10:24:25.141:               + ANGEL Connection=10.205.150.33

2016/05/17 10:24:25.141:                 Attempt to send 2984 bytes of data

2016/05/17 10:24:25.141:                 + Data Chunk=0

2016/05/17 10:24:25.141:                   Sending 2984 bytes of data (with header)

2016/05/17 10:24:25.376:     + WorkFunction=0000000029C1F5C8

2016/05/17 10:24:25.376:       + User=workmanagement_qa-48905

2016/05/17 10:24:25.376:         + Application=workmanagement_qa

2016/05/17 10:24:25.376:           + User=workmanagement_qa-48905

2016/05/17 10:24:25.376:             Originator exception:

2016/05/17 10:24:25.391:             + User=workmanagement_qa-48905

2016/05/17 10:24:25.391:               + ANGEL Connection=10.205.150.33

2016/05/17 10:24:25.391:                 Sending disconnect for vine 3431094288

2016/05/17 10:24:25.391:             Message failure case: 13 (Receiver Exception)

2016/05/17 10:24:25.391:             + User=workmanagement_qa-48905

2016/05/17 10:24:25.391:               Received Business Object Fetch message 67 status changed to 'Failed'

[Former Member]

it sent 1 workorder object

[Former Member]

are you getting this error while fetching the workorder? or in different scenario?

did you change anything recently in to the application?

[Former Member]

This has been happening for some time in our qa environment (not in production yet), but I didn't think about it until someone else posted recently about it.  It made me think that we certainly cant' go to prod like this.  Yes I'm getting this when the process runs to find updated orders and its pulling down 1

[Former Member]

i would suggest reset(full reset) your Agentry client and test. if you are still getting the same error please try to debug in Java and check in which place it is throwing the error.

[Former Member]

i have reset many times throughout this process... no difference.  I don't have a java backend...how would I debug. 

[Former Member]

you can import the jar files to eclipse and debug. To see the class file you need some decompiler. please install decompiler plugin in eclipse and test.

[Former Member]

Can you give me some instructions on which jar files to import?

[bill_froelich]

Heather,

You don't have a java backend so there is no debugging you can do here.  You mentioned you are already on the latest server release which has the fix for a related issue.  I would suggest opening an issue with support especially since you can reproduce the problem.

--Bill

[Former Member]

THanks Bill... I submitted a ticket.