AXAPTA job returns error but Uproc ends Completed

Document ID : KB000103779
Last Modified Date : 29/06/2018
Show Technical Document Details
Issue:
Under certain conditions the uxstrax.exe fail with the error -1 which is not managed correctly by the Axapta model script. 
The Uproc ends Completed while the job fails or remains running.

The job log of the AXAPTA job contains:
###
<time date> | Warning: No AOS associated with the group <group> is running. The task <Task ID> - Application d'assistance à la planification won't be able to be executed.
<time date> | (GetNbAOSAlive) error getting the status of the AOS: Warning : Pointer reached the limit of number of cursor
<time date> | Warning: No AOS associated with the group <group> is running. The task <Task ID> - Application d'assistance à la planification won't be able to be executed.
<time date> | --------------------Intermediate report -------------------- 
<time date> | Number of waiting tasks: 0
<time date> | Number of running tasks: <x>
<time date> | Number of ended tasks: 0
<time date> | Number of tasks in error: 0
<time date> | ------------------------------------------------------------ 
<time date> | (ShowBatchJobProgress)error getting progress:External component has thrown an exception.
<time date> | Progress of the job = -1%.
<time date> | The job is not completed (status: Executing).
<time date> | Continue the polling...
<job name>: Execution is successful.
###
Cause:
The error codes lower than 0 (zero) were not handled correctly
Resolution:
Workaround for existing scripts:
Modification of the Axapta model script to treat error -1 by changing the condition: 
from
if %RETURN_CODE% GTR 0 GOTO TRT_ERR 
to 
if %RETURN_CODE% NEQ 0 GOTO TRT_ERR 

Changing the variables:
UNI_AX_BYPASSAOSCHECK
UAX_JOBCTLCYCLE
UAX_JOBEXECTIMEOUT
Prevents that the error code becomes -1 
 

Solution:
Update to a fix version listed below or a newer version if available.

 

Fix version:

Component(s): Application Server 

Dollar Universe 6.9.41 - Planned release date: 2018-10-01