Scheduler and Server Packages

[kmittelmeier]

Good Morning,

Has anyone else experienced the problem of Scheduler not submitting jobs
after a Server Package has been deployed?

XE Update 1 Service Pack 18.1
Coexistent V4R5 A7.3 Cum 11
NT Terminal Server Service Pack 6
Citrix MetaFrame 1.8 Service Pack 1

 

[SSAJAROFF92]

Hi there :

Yes, I've been experiencing the same on SP 17.1 and SP 18.1 but no
fix has appeared yet.

Sebastian

 

[badda_bing]

Re: RE: Scheduler and Server Packages

We are also experiancing this problem. Check out SAR5838769. This details that the fix will be available in SP18.1_F1, I have had a chat to one of our local JDE CNC tech's and he thinks that the fix is in fact include in 18.1_C1 which is already released - I am still waiting for confirmation on this.

Paul

XE 17.1 Update 1
Windows 2000 Adv SP2 / SQL2000
Metaframe XP

 

[rhunt01]

Re: RE: Scheduler and Server Packages

Paul,

Can you confirm that SAR number for me? I found information on 5838769 but it didn't mention the scheduler. ...just cache/environment errors.

Thanks

Ryan Hunt
OneWorld XE; Update2; SP17.1_E1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8

 

[badda_bing]

RE: RE: Scheduler and Server Packages

Ryan,

The SAR is 5838769. Check the third to last paragraph in the Final
Disposition section, see text below;

A ORIGINAL REQUEST

On CallObject kernel, when the JDB cleared the caches
for
each environment, sometimes it leaved the cache handles
out
there without destroying the caches properly. This caused
a problem when a new user tried to sign on the same environm
ent, it would fail out with the error message
"JDB9900376 - Failed to initialize EXCL_APP_SEC Cache."

B FINAL DISPOSITION

There are two problems. The first problem is that some
unused environments were deleted,
but their caches were left behind without clearing up.
This causes JDB_InitEnv to fail out with error message:
"JDB9900376 - Failed to initialize EXCL_APP_SEC Cache."
written to jde.log. The second problem is that one environme
nt caches may not be
reloaded in some case. This might cause some kernel processe
s such as call object kernel or scheduler kernel to die
after
package deployment. The customers with service packs
before
B733_SP17 shouldn't have the second problem.
The solution is to clear up unused caches and load caches
for environment being missed.


The SAR above (5838769) details a fix will be in 18.1_F1 but if you have a
look at SAR 5838849 which should come back in the search for the original
one above, details the same problem but the fix is in SP18.1_C1 which has
already been released????

cheers,

Paul



XE 17.1 Update 1
Windows 2000 Adv SP2 / SQL2000
Metaframe XP

 

[hedgiehoghill]

Re: RE: Scheduler and Server Packages

That is the correct SAR number (5838769). I just pulled it off the KG this morning. Look towards the middle of the 'Final Disposition' section and you will see the portion about the scheduler kernel.

Good Luck,
Jeff

B73.3.2 SP11.1,NT,MS-SQL7 SP2
WIN2K/CTX 1.8a SP2/FR1 & Fat (LIVE)

XE-U4 SP 18_B1,Win2K SP2,MS-SQL2K
WIN2K/CTX 1.8a SP2/FR1 & Fat (TEST)

 

[Kazmir]

Yes , we have. We are troubleshooting that now. The schedule jobs states Error: Could not Submit. The jde.log says: JDB9900376 - Failed to initialize EXCL_APP_SEC Cache. I just checked the days we had server package installs and it begins erroring on the same days. So it looks to be the same issue. I have a call in to JDE.

Debbie Kazmir
AS400/Unix/NT SQL/Oracle
Encompserv (OneWorld XE; Update3; SP17.1_C1 NT/SQL)
Metaframe XP

 

[Soul Glo]

So is this infact fixed in SP18.1_C1 because I am trying to test the scheduler in a multiple foundation evn and I am geting the same error and I have 18.1_C1 applied...I just applied 18.1_D1 to the foundation Env...I try the scheduler again to see what happens....you know I wis they will concentrate on fixing things instead of coming with an SP one off every two weeks that breaks more things and don't fix any...just my 2 cents...I am getting tired of trying to play catch up to all the things they are breaking.

Cleola Isaacs
CNC Administrator/Network Analyst
Xe Update 2 SP 16
Enterprise AS/400
WTS NT 4.0

 

[hedgiehoghill]

Re: RE: Scheduler and Server Packages

Just a quick update for the people waiting on the SAR's related to this problem.

Title: SARs Scheduled to be released for "Failed to initialize EXCL_APP_SEC Cache" error delayed.
Abstract: The SARs 5836739, 5836763, 5838769 and 5838849 have all been pushed back to SP19.1

Product OneWorld
Suite Technical
Release Xe
Document ID OTI-02-0038
Date Created 04/02/2002
Date Reviewed 04/02/2002
Date Revised 04/02/2002

--------------------------------------------------------------------------------

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.


B73.3.2 SP11.1,NT,MS-SQL7 SP2
WIN2K/CTX 1.8a SP2/FR1 & Fat (LIVE)

XE-U4 SP 18_B1,Win2K SP2,MS-SQL2K
WIN2K/CTX 1.8a SP2/FR1 & Fat (TEST)

 

[Soul Glo]

HI,

There is a new Braking News article on this issue. JDE was supposed to fic it in the next one off for SP18.1 but they have pushed back to be fixed in SP19.1. The workaround is to recycle service after you do a full package deploy. Refer to article OTI-020038 on the KG

Cleola Isaacs
CNC Administrator/Network Analyst
Xe Update 2 SP 16
Enterprise AS/400
WTS NT 4.0

 

[Kazmir]

Correct. And SP19.1 will be out May 27th.
SP 19 comes out next week.

Debbie Kazmir
AS400/Unix/NT SQL/Oracle
Encompserv (OneWorld XE; Update3; SP17.1_C1 NT/SQL)
Metaframe XP

 

[Slick]

J.D. Edwards has told me that if the scheduler will still submit your jobs only in the environment that is set up as your default environment in the JDE.INI on the ES. I have done this and my jobs in PD7333 run as they should after a package is deployed, but my jobs in DV7333 and PY7333 do not run.