Troubleshooting the "RUN0000050" Error in Logs for EnterpriseOne Interactive Applications

Purpose of Document

E1: FDA: Form Design Aid Information Center > Troubleshooting > Note 1090533.1

This document is intended to help troubleshoot the RUN0000050 error in the jde.log. This error, in general, occurs when a standard EnterpriseOne interactive application is copied to modify certain routine(s) and when a special version is not created for the original interactive application. This error occurs when the interactive application is designed to call a business function that retrieves Processing Option data from a specific object and version in the F983051 Versions List table.

Example of Error message in jde.log

RUN0000050 - Unable to retrieve DB Record for Application P4210, Version TEST03 from F983051.

What causes the error?

This error occurs when an interactive application calls a business function that retrieves Processing Option data from a specific object and version.  When this interactive application is copied to a new object name in order to modify the application, if a version is not created for the original interactive application, this error will occur when the application attempts to retrieve the processing option information through the business function.  For example, if a new version CUST001 is created for the new interactive application, but this version does not exist for the original, copied application, the application will fail with the RUN0000050 error. 

How does EnterpriseOne get the version data?

EnterpriseOne gets the version data through the API AllocatePOVersionData as below,

For this example,

• return type is LPDST4210
• lpdsProcOptions is long pointer which contains processing option data structure

What is the default version when an input version is not specified?

ZJDE0001

What are the error codes and messages?

• 1243 - Invalid Version
• 3143 - File can not be accessed.
• 4363 - Null Pointer
• 0002 - Record Invalid
• 015K - Invalid response, system not installed.
• 016F - Invalid Version
• 016K - Version is not available to client
• 072I - Processing Option Version is Invalid
• 072J - Processing Option Version is Invalid
• 078J - Select from table F983051 failed
• 080S - Version Invalid
• 48I - Processing Option Version is invalid
• 573G - Error/Processing Options - see detail
• E42B4 - Processing Option Version is Invalid

How is the error set?

• bContinue = FALSE
• bContinueProcess = FALSE
• bEncontroTemplate = FALSE
• bError = (BOOL) TRUE
• bError = TRUE
• bErrorFound = TRUE
• bIsError = TRUE
• eReturn=ER_ERROR
• idErrorFlag = 2
• idErrorFlag = ER_ERROR
• idJDBReturn = ER_ERROR
• idReturn = ER_ERROR
• idReturnCode = ER_ERROR
• idReturnValue = ER_ERROR
• idRetVal = ER_ERROR
• iFatalError++
• IntToMathNumeric(1,&lpDS->mnReturnCode)
• iReturnValue = 0
• jdeErrorSet ()
• jdeErrorSet (lpBhvrCom, lpVoid, (ID)0, _J("072I"), (LPVOID)NULL)
• jdeStrcpy (lpDS->szErrorMessageID, _J("0002"))
• jdeTraceSz(NULL, _J("B3402010 - R3465 Version Not Found: ")
• lpBeginDoc->idEditError = ER_ERROR
• lpDS->cErrorCode = _J('1')
• lpDS->cErrorCode_ERRC = _J('1')
• lpDS->cErrorCode_EV01 = _J('1')
• lpDS->cErrorFlag = _J('2')
• lpDS->cErrorFlag=_J('1')
• lpDS->cPOTemplateFound = _J('N')
• lpDS->cStatus = _J('1')
• lpDS->nErrorCount += 1
• lpdsControl->cTEMBFPOPayTypeDescFlag = _J('0')
• return (ER_ERROR)
• return ER_ERROR

How can I resolve the issue?

When this issue is encountered, there are a couple possible scenarios:

• A custom application copied from a standard EnterpriseOne application ends in error.
• A custom application copied from a standard EnterpriseOne application does not stop working, but returns incorrect results.

To minimize any issue caused by copying a standard application that meets this criteria, define a version with the same name and appropriate processing option values for the standard object.  (For example if you have copied P4210 and named it P554210):

1. Study the version you have created for P554210 (if the Version ID is CUST001)
2. Create the exact same version ID for the source application (P4210)
3. Synchronize the processing options between P4210|CUST001 and P554210|CUST001

What applications are designed in this manner and may end in error when copied?

The following table contains standard EnterpriseOne interactive applications which have been designed to get processing option template information through a business function.