MelissaS
Active Member
We recently went live with a second Win2000 apps server. We are getting random jobs ending in status E. All of the jde.log say the same things for these jobs ending in error:
2600/3192 Tue Jul 29 13:24:58 2003 jdeksec.c3192
KNT0000306 - JDENET Error = eTimeOut
2600/3192 Tue Jul 29 13:25:59 2003 jdeksec.c3192
KNT0000306 - JDENET Error = eTimeOut
2600/3192 Tue Jul 29 13:25:59 2003 jdeksec.c812
SEC0000002 - Unable to connect to security server jdeprod
Running OneWorld with user's signon and password
This may or may not work depending on the databases' security.
2600/3192 Tue Jul 29 13:25:59 2003 JDB_CTL.C3030
JDB1100015 - Failed to complete Security check
2600/3192 Tue Jul 29 13:25:59 2003 RUNBATCH.C699
JDB_InitEnvOvr failed with rcode = 0
2600/3192 Tue Jul 29 13:25:59 2003 IPCPUB.C3515
API ipcSawUnregisterProcV1 : process 2600 unregistered in entry 61
2600/3192 Tue Jul 29 13:25:59 2003 RUNBATCH.C1459
Processing PrintUBE request failed - see previous messages
I know that these people have valid username/passwords because after the job ends in error - they can turn right around and run it successfully. This problem does not happen on our first apps server. With the addition of the two apps servers - we have added a lot more queues. Is there some setting on the security server ini that I need to adjust to accommodate the addition of these new connections coming from the additional 2 apps servers?
Thanks!
2600/3192 Tue Jul 29 13:24:58 2003 jdeksec.c3192
KNT0000306 - JDENET Error = eTimeOut
2600/3192 Tue Jul 29 13:25:59 2003 jdeksec.c3192
KNT0000306 - JDENET Error = eTimeOut
2600/3192 Tue Jul 29 13:25:59 2003 jdeksec.c812
SEC0000002 - Unable to connect to security server jdeprod
Running OneWorld with user's signon and password
This may or may not work depending on the databases' security.
2600/3192 Tue Jul 29 13:25:59 2003 JDB_CTL.C3030
JDB1100015 - Failed to complete Security check
2600/3192 Tue Jul 29 13:25:59 2003 RUNBATCH.C699
JDB_InitEnvOvr failed with rcode = 0
2600/3192 Tue Jul 29 13:25:59 2003 IPCPUB.C3515
API ipcSawUnregisterProcV1 : process 2600 unregistered in entry 61
2600/3192 Tue Jul 29 13:25:59 2003 RUNBATCH.C1459
Processing PrintUBE request failed - see previous messages
I know that these people have valid username/passwords because after the job ends in error - they can turn right around and run it successfully. This problem does not happen on our first apps server. With the addition of the two apps servers - we have added a lot more queues. Is there some setting on the security server ini that I need to adjust to accommodate the addition of these new connections coming from the additional 2 apps servers?
Thanks!