Views Reply Votes
Paul Xue
Paul
 5
custom QDoc works in one Receiver but not the other
1197
4
00
Posted: Mar 26, 2018   
Votes
Paul Xue
Paul
 5
Replied 

Hi,

It seemed the new Receiver was not set up/created correctly. Even standard QDocs do not work with the new Receiver as well.

It also seemed that when a QDos was processed, the program was run but never got to the second frame.

 after testing with a standard QDoc - maintainGeneralizedCode, qxtendserver.log showed:

2018-03-27 17:29:32,476 ERROR com.qad.qxtend.events.SubmitDataEvent 17IterationEvent. 2Iteration.handleEvent - Field encountered twice in an iteration: generalizedCode - id: ttprimarykey#0:progMap_fieldInfo1851 num processed 8

 

How to find out what's wrong with the new Receiver

 

00
Replied: Mar 26, 2018
Votes
Paul Xue
Paul
 5
Replied 

Further testing showed that this is an AIM related issue.

When we disabled AIM, QXtend Inbound worked as expected for both standard and custom QDoc.

Both QDocs didn't work when AIM was re-enabled.  

Have logged an Incident with QAD Support.

00
Replied: Mar 28, 2018
Votes
Paul Xue
Paul
 5
Replied 

Found below article on QAD KB. Confirmed with QAD Support and have received a patch. 

 

EventExceptionex001 error when AIM is turned on

Author: Radha Shankar Article ID: AB-14775 Views: 7 Created: 2018-02-22 23:38 Last Updated: 2018-02-22 23:38

0 Rating/ Voters

https://knowledgebase.qad.com/kmp/admin/images/local/FirstTheme/ico-rating-g.gifhttps://knowledgebase.qad.com/kmp/admin/images/local/FirstTheme/ico-rating-g.gifhttps://knowledgebase.qad.com/kmp/admin/images/local/FirstTheme/ico-rating-g.gifhttps://knowledgebase.qad.com/kmp/admin/images/local/FirstTheme/ico-rating-g.gifhttps://knowledgebase.qad.com/kmp/admin/images/local/FirstTheme/ico-rating-g.gif

Issue/Symptoms:

EventExceptionex001 error when AIM is turned on.

When AIM is turned off, there is no error.

Facts/Environment:

QAD 2016EE

Qxtend 1.8.7

AIM 3.2

Resolution/Fix:

Please contact QAD technical support for QXTS-615. This fix is part of the standard ERP-trunk for the upcoming release QAD 2017EE.

The ERP-trunk fix is part of MFGS-7842.

 

 

 

 

00
Replied: Apr 02, 2018
Votes
Paul Xue
Paul
 5
Replied 

SOLVED.

Patch provided by QAD Support fixed the problem. Be mindful of the propath, make sure that 

${appdir}/2016ee/dist/qxtadpt/ 

is in front of 

${appdir}/2016ee/dist/mfg/

as the installation instructions came with the path did the other way around, which appeared the problem wasn't fixed.

 

10
Replied: Apr 04, 2018
Forums
All
Forum Help
Help Using Forums