runube from command line on Win2003 server

[DSauve]

I know that this topic has been covered before on the JDEList, but I've tried everything I can think of and it still doesn't work. I'm trying to run a UBE from a command line on our Win2003 server. Here is the command file I'm running, followed by the output that appears in the jdexxx.log file on our enterprise server:

D:
cd D:\peoplesoft\ddp\b9_JDDVPY\system\Bin32
runube username password py9 *ALL R014021 XJDE0001 QBATCH Batch Hold Save printername


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



5172/8632 Mon Dec 19 14:02:47.150 IPCMISC.C294
process 5172 <runube> registered in entry 10

5172/8632 Mon Dec 19 14:02:47.150 RUNUBE.C499
Startup for User=username, Env=py9, Role=*ALL, Report=R014021, Version=XJDE0001

5172/8632 Mon Dec 19 14:02:47.166 RUNUBE.C526
bAPListening=0

5172/8632 Mon Dec 19 14:02:47.400 jdeksec.c1237
SEC0000003 - Security Server returned eSecUnknownUser for user username for eSecValidate

5172/8632 Mon Dec 19 14:02:47.400 JDB_CTL.C3002
JDB1100015 - Failed to complete Security check

5172/8632 Mon Dec 19 14:02:47.416 RUNUBE.C532
JDB_InitEnvOvrExtended failed with rcode = 0

5172/8632 Mon Dec 19 14:02:47.416 IPCMISC.C294
API ipcSawUnregisterProcV1 : process 5172 unregistered in entry 10

I've tried to run this from directly on the enterprise server, logged in as the same user as is running the E1 server process. Any ideas on what else I can check? Thanks in advance for any help you can offer.

 

[brother_of_karamazov]

From the looks of the log the OneWorld user you specified as "username" is not known to the system.

"Security Server returned eSecUnknownUser for user username for eSecValidate"

Are you certain that you are using a good username?



[ QUOTE ]
I know that this topic has been covered before on the JDEList, but I've tried everything I can think of and it still doesn't work. I'm trying to run a UBE from a command line on our Win2003 server. Here is the command file I'm running, followed by the output that appears in the jdexxx.log file on our enterprise server:

D:
cd D:\peoplesoft\ddp\b9_JDDVPY\system\Bin32
runube username password py9 *ALL R014021 XJDE0001 QBATCH Batch Hold Save printername


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



5172/8632 Mon Dec 19 14:02:47.150 IPCMISC.C294
process 5172 <runube> registered in entry 10

5172/8632 Mon Dec 19 14:02:47.150 RUNUBE.C499
Startup for User=username, Env=py9, Role=*ALL, Report=R014021, Version=XJDE0001

5172/8632 Mon Dec 19 14:02:47.166 RUNUBE.C526
bAPListening=0

5172/8632 Mon Dec 19 14:02:47.400 jdeksec.c1237
SEC0000003 - Security Server returned eSecUnknownUser for user username for eSecValidate

5172/8632 Mon Dec 19 14:02:47.400 JDB_CTL.C3002
JDB1100015 - Failed to complete Security check

5172/8632 Mon Dec 19 14:02:47.416 RUNUBE.C532
JDB_InitEnvOvrExtended failed with rcode = 0

5172/8632 Mon Dec 19 14:02:47.416 IPCMISC.C294
API ipcSawUnregisterProcV1 : process 5172 unregistered in entry 10

I've tried to run this from directly on the enterprise server, logged in as the same user as is running the E1 server process. Any ideas on what else I can check? Thanks in advance for any help you can offer.

[/ QUOTE ]

 

[Joel]

Can you do the same with the psft user.
If that too fails, try removing the security server entry from the ini and try with the psft user - All da best

 

[SULLY1]

Don

I agree with Joel. Use the PSFT user and the OneWorld password, which is the password you would actually sign into the OneWorld application with. It's not the database user or the Enterprise server user.

Patty

 

[DSauve]

Thank you, Jeff, Joel and Patty. I tried this out again using the JDE E1 user (we don't use the PSFT user - we're on 8.9), and it's working great now. Thanks for your help -- it made my day!