R0006P Version XJDE0001 BV failing on new install

[Dustin Withers]

Hello All,

I've gotten to the point in our install were I'm testing the report generation of the enterprise server. I'm using BV R0006P version XJDE0001 and it's failing with the error:
An error occured submitting batch R0006P, XJDE0001 to JDEENT1A

The deployment server log is complaining about a JDENET_ReceiveMsg:
3632/1412 MAIN_THREAD Thu Feb 28 20:48:14.299000 XMLRequest.cpp1260
ICU0000017 - ICU CodePage for 1252 is ibm-1252.

3632/1412 WRK:Starting jdeCallObject Thu Feb 28 20:48:15.549000 Jdb_rqst.c1341
JDB3800016 - Failed to validate Request handle

3312/2336 WRK:Starting jdeCallObject Thu Feb 28 20:48:42.158000 LaunchXMLUBE.c75
Submitting R0006P, XJDE0001 to JDEENT1A for XML specs

3312/2336 WRK:Starting jdeCallObject Thu Feb 28 20:49:44.299000 Jdeknube.c3851
KNT0000106 - JDENET_ReceiveMsg failed. Error = 11


And the logs on the Enterprise server have some "token" errors:
25084/-1208465728MAIN_THREAD Thu Feb 28 20:48:44.555241jdecsec.c1969
Failed to get extended token: eSecInvalidToken: The security token is invalid

25084/-1208465728MAIN_THREAD Thu Feb 28 20:48:44.555985jdeknube.c687
Get extended token failed.

25085/-1209002304MAIN_THREAD Thu Feb 28 20:48:44.552253PSEOneAuthToken.cpp147
IsValid: Token for user  is from untrusted node _LOCALNODE

25085/-1209002304MAIN_THREAD Thu Feb 28 20:48:44.552588PSAuthToken.cpp599
ValidateAuthToken: returning PSAUTHTOKEN_UNTRUSTED_NODE

25085/-1209002304MAIN_THREAD Thu Feb 28 20:48:44.552669jdeksec.c4220
Failed to validate auth token: token library unable to validate token

3835/-1208985920MAIN_THREAD Thu Feb 28 20:48:42.564054ipcmisc.c299
process 3835 <jdenet_n> registered in entry 12


If I run the BV with runube it works it's only when submitting it from the deployment server that it fails. I've installed the 8.97 tools, and the enterprise server is RHEL4 connected to an Oracle DB running on RHEL4.

Any ideas would be greatly appreciated...

Thanks,
-dustin

 

[WinPrice]

Dustin, based on the Token errors you are seeing, it sounds like you may not have the right settings in your tokengen.ini file on the web server.

The enterprise server also needs to have a [TRUSTED NODE] section added. There are a couple solutions for this on the Customer Connection you should look for that can provide more information.

 

[Dustin Withers]

Turns out it was a problem with our Full Package build...looking into that now. Thanks for the reply.

-dustin