XE Scheduler Problem on SP 19

Hi

We have this problem with the XE Scheduler. The error message "Error: Could not Submit". We have to restart the JDE services on the Enterprise Server (ES) to resolve. We have also found out that this behaviour occurs whenever we deploy server packages to the ES.

Has anyone encountered this? How was it solved?

OneWorld XE, SP 19, Update 5
ES - Win NT 4.0 SP 6a
Database - MS SQL Server 7.0 SP 3

Regards,

Hi
We have the same problem. You should something similar to this in your log
on your server:-

6/242 Tue May 07 14:00:48 2002 JDB_CACH.C519
JDB9900376 - Failed to initialize EXCL_APP_SEC Cache.

176/242 Tue May 07 14:00:48 2002 JDB_CTL.C4408
JDB4200001 - Failed to validate User handle

176/242 Tue May 07 14:00:48 2002 JDB_CTL.C3673
JDB1100023 - Failed to create Cache

176/242 Tue May 07 14:00:48 2002 JDB_CTL.C2607
JDB1100010 - Failed to Load Environment

There is a document on the KG that has some more details. I cut and paste
this below from the KG and one of these SARs should help. You need to be on
SP19.1 to fix it.

Title:
SARs Scheduled to be released for, Failed to initialize EXCL_APP_SEC Cache,
error delayed.
Issue:
SAR Numbers: 5836739, 5836763, 5838769 and 5838849 are no longer scheduled
for their intended release service pack, but will first been seen with
SP19.1.
Resolution:
Customers waiting on these SAR to be released in their previously scheduled
specific service packs will now have to wait until the release of SP19.1
Workaround:
The only workaround for this issue is to stop and restart the services
after the deployment of a server package.  Services do need to be up to
deploy it, but then they will need to be stopped and restarted to
reinitialize the cache for the CallObject and Scheduler kernels.

Cheers
Kieran

Xe Sp17.1 Update 3 As400 V4R5, Win2K Sp2

CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.

Have a look at SAR 5838769. You're only option is to go to sp19.1. I have also discovered that this affects the JAS server (services also need to be bounced after package deploymen on ES).

I had these same symptoms & I'm on the AS400. I put on some PTFs to resolve
it. I would expect there must be some updates you need to apply to your
Enterprise Server also that would work for you. Contact JDE and they will
help you to resolve it.

good luck!



We have this problem with the XE Scheduler. The error message "Error: Could
not Submit". We have to restart the JDE services on the Enterprise Server
(ES) to resolve. We have also found out that this behaviour occurs whenever
we deploy server packages to the ES.

Has anyone encountered this? How was it solved?

OneWorld XE, SP 19, Update 5
ES - Win NT 4.0 SP 6a
Database - MS SQL Server 7.0 SP 3

Regards,




Lori
OW Xe SP19 Update 5
AS400 V5R1 NT
Citrix
email: [email protected]

We have also experienced the same problem and JDE support advised us to
move to SP19.1 and this resolved the problem.

I had these same symptoms & I'm on the AS400. I put on some PTFs to
resolve
it. I would expect there must be some updates you need to apply to
your
Enterprise Server also that would work for you. Contact JDE and they
will
help you to resolve it.
good luck!
We have this problem with the XE Scheduler. The error message "Error:
Could
not Submit". We have to restart the JDE services on the Enterprise
Server
(ES) to resolve. We have also found out that this behaviour occurs
whenever
we deploy server packages to the ES.
Has anyone encountered this? How was it solved?
OneWorld XE, SP 19, Update 5
ES - Win NT 4.0 SP 6a
Database - MS SQL Server 7.0 SP 3
Regards,
Lori
OW Xe SP19 Update 5
AS400 V5R1 NT
Citrix
email: [email protected]
--------------------------

Agreed. We went to SP19.1 from SP19 last week for just this reason. Fixed the problem and experienced no other issues (yet...)