SP20 Deployment

JDEList,

This weekend we applied/deployed SP20. The SP20 deployment documentation provided by JDE was not current. The documentation said we are going to be asked for SPC code during installation but we were not asked by the install manager for SPC code. JDE response line says it is ok even if you are not asked for the SPC, code.

Other than the documentation issue things went on smoothly. So far we have not seen any issue with the SP20. As it is hardly 3 days since we deployed SP20 I will share if any issue is noticed.

Fascinating. Its been JDE policy since SP17 (I think) to have Service Packs ask for an Auth Code on the install. I'm guessing that its something that the install team at JDE forgot about - but it'd be nice to see it disappear since I certainly don't like calling JDE at 5am on a Sunday Morning (which is when I usually install Service Packs !) - especially on Eastern Time !!!!

As long as OneWorld works (ie logs you in), it should be fine. I've been testing SP20 out locally for the past couple of weeks on my fat client - and was planning on installing it over the weekend into our development environment (until we hit an unrelated issue which made me push out the deployment a week) - but I plan to put in SP20 by next weekend definately.

I love the new webclient by the way - a MARKED improvement from before - and that, officially, is the first time ANYONE has heard me say I like the webclient !

Its not exactly ready for Production at larger implementations just yet - but the interface has vastly improved. I hope to be writing up more on how the Websphere Server works in the near future.

All in all, a good stable service pack.

Oh - one more thing, you'll note theres no "dot one" coming out for SP20 - it seems as if JDE has got rid of "base" service packs and "dot one" production releases. As far as I can see, for SP20 the "production" version is SP20_C1 - but thats purely looking at the time of release between SP20 and the 3 updates and correlating between older "base" levels and "dot one" releases. Not an exact science of course !

Maybe one day we'll learn to trust the "base" service pack releases !

Jon Steel
ERP 8.0 / Xe Upgrade Specialist

Has anyone tested/applied SP 20_C1 in an AS/400 environmnet. If so let me know if you had any issues with it.

Team JDEList,

Before SP20_C1 nightly scheduled jobs (68 jobs launched back to back in a single threaded queue) used to take approximately an average of 75 minutes to complete but now, those are finishing in less than 30 minutes. This is with the fact that there has been no change in the operational environment for our JDE deployment (I mean it is running with the same hardware and RDBMS and with the same old configuration)
Also the jobs submitted by users are getting executed at a blazingly fast speed.
JDE has done good job on SP20 and SP20_C1, thanks to JDE.
For those of you who are using output to CSV, the SP20 fixes the issue of wrong output and missing lines in CSV files.
As usual SP20 intoduces following warning/error in JDE logs on enterprise servers and workstations.

RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

JDE response line says this can be safely ignored if you are not using XPI or WebMethods or you can apply a SAR which fixes this issue if you are using XPI or WebMethods for EAI.

Anyways we are still watching SP20_C1, keep looking for more updates.

Fellow JDELister

Hi,

I've installed SP20 and SP20_B1 One-Off last week. I saw, (while calling JDEdwards to obtain a code) that was not necessary an SPC Code. I found call 5209884 related to this.

I also saw that there were some "errors" in log files when i started OW. I found in the KG SAR 6013347 related to this. after applying that ESU those errors disapeared.

I hope this helps.

OneWorld XE, SP 20, update 5, WindowsNT 4.0
MS SQL 7.0

Hi,

We upgraded to SP 20 over the weekend. Now we have problem with update packages deployment to the clients. When clients workstation click to accept the update package, OneWork will bomb out and disappeared from the screen.

Ironically we updated to SP 20 to resolve the problem of scheduler jobs on the ES when an update package is deployed to the ES. The problem now has shifted to the client workstation.

Regards,

Have you checked to be sure all anti-virus TSR's, etc. are disabled on the offending Workstation or Server during pkg. install? Sounds a bit like a security problem to me...

Hi,

Problem still exists with Anti-virus turned off.

There is a SAR for this problem - SAR 6184648. Status - 21 - Programming/Program Test.

Regards,

Hi

I just wonder - the people who had posted earlier on this thread who had implemented SP 20, whether they have the same problem as I am having with client workstation problem accepting update packages.

JDE Response Line is treating SAR 6184648 as non-critical and does not give a date when this will be resolved. To me this is critical as my IT staff is busy going around to each fat clients, and Citrix servers, to install update packages. It is a huge drain on my IT resources.

If we can get enough people to raise this with JDE, they will expediate this SAR.

Regards,

I picked up the same problem with the package deployments not working two weeks ago, it was on one client and I didn't think much of it. 3 Days later we loaded SP20 and SP20_C1 to try and resolve other problems and I then realised that the deployment of packages was a serious problem affecting everyone. I have logged a call with JDE and they are basically saying it's something on the network, which I have checked and double checked and cannot find any problems. An interesting thing though is that I have found 6 SAR's with the same problem and yet no resolution is forthcoming from JDE

We're running SP20_C1 for almost 2 weeks now.

haven't found any problems so far.
Only had a problem installing a newly build Full Package for our trainingsenvironment. After renaming the system dir on the terminal server it just installed fine.
No problems with update packages so far.

We also applied SP20C1 and successfully deployed update package to our machine. Everthing work fine and smooth.

Just had the same issue testing sp20_n1, downloaded sp20_o1 which fixed the problem.

Regards