Page 1 of 1

Better Error Messages

Posted: Fri Feb 24, 2017 8:41 am
by jyoung
I already mentioned better JavaScript Error messages and now I am suggesting better Server Module error messages or simply better error messages in general.

I was trying to run this query

Code: Select all

select_sql fields((#wk_Amount 'SUM(RPAAP)')) from_files((F03B11)) where('(#RPAN8 = :RPAN8) AND (#RPDIV < 102134) AND (#RPJCL >= 102134)')
* do stuff
endselect
And I kept getting an error message of
Message : (0586) - Component Manager request of type 3 (decimal value) failed with return code -1 (decimal value).
The second message suggested to check X_ERR.LOG.
Capture.PNG
Capture.PNG (34.05 KiB) Viewed 27738 times
This is the log file

Code: Select all

============================================================================== 
Thu Feb 23 15:29:15 2017 
Release 14.1.0 Build 4138 Windows 10 Enterprise Edition (10.0.0.0 Build 10586)
---LANSA Installation/Upgrade 14.1.0 Build: 4138 (11/17/2016 10:34:33 AM)
---EPC (17-11-2016 10:43:44)
---LANSA Installation/Upgrade 14.1.0 Build: 4138 (2/3/2017 10:04:13 AM)
---LANSA Installation/Upgrade 14.1.0 Build: 4138 (2/6/2017 9:40:28 AM)
---LANSA Installation/Upgrade 14.1.0 Build: 4138 (2/6/2017 10:44:09 AM)
---EPC (07-02-2017 12:19:20)
---EPC (07-02-2017 12:21:43)
---EPC (13-02-2017 14:54:55)
Message : X_COMP returned error code -1. Check X_ERR.LOG for more information.
Routine : X_Execute_WAM
Job Number: 007956 OS User : LANSA
DBII=LANSA DBUT=MSSQLS GUSR=QOTHPRDOWN PSTC=Y PROC=*WAM WAML=LANSA:XHTML WVAR=2 W3ST=1 WXSL=YY LANG=ENG PART=SYS USER=LANSA CMTH=T CDLL=LCOMGR32.DLL WSTY=IISB ITHP=N
ROOT=C:\Program Files (x86)\LANSA\X_WIN95
============================================================================== 
Thu Feb 23 15:29:15 2017 
Release 14.1.0 Build 4138 Windows 10 Enterprise Edition (10.0.0.0 Build 10586)
Message : (0586) - Component Manager request of type 3 (decimal value) failed with return code -1 (decimal value).
Routine : X_Execute_WAM
Job Number: 007956 OS User : LANSA
Nothing in here tells me what is wrong. (At least as far as I can tell).

The problem turned out to be that I missed typed a field name. #RPDIV should have been #RPDIVJ.

If the error message came back and said "Could not find RPDIV' it would have made finding the problem a heck of a lot easier.