Not totally true, we had to apply SP14.2 . This was suggested by Denver because we were experiencing "Memory Errors" applying Update 1 when 'Adding Object to OMW project' phase.
JDE's response is as follows: Your issue is tied to a licensing issue with OMW. OMW can't add objects to the project if the proper objects are not licensed. The fix resides in SP14.2 and forward.
The following is a detailed account of the upgrade:
1) First apply ESU JD4444
2) The 2nd pre-requisite JD7792, we had to reapply this ESU(after applying Update 1) and this was done yesterday. Here is JDE's response:
There is a problem with the busbuild for a client package if you have SP14.2 applied. The message you will see is:
> \\DPFN1\B7333\system\includev\port.h(186) : warning C4005: 'PREFIX' :
> macro redefinition
> \\DPFN1\B7333\system\include\jdedefn.h(190) : see previous definition of
> There is a one-off in the works for it. The one-off SAR number is 4971832.
> The child SAR is 4971728.
> It will also be fixed in SP15
You can ignore the messages for now as they are just warnings.
Let me know what you find with the investigation of the B4100430. I was able to successfully apply the ESU and build a package here. The problem lies in the fact that the Data Structure (D4101440A) listed does not appear to be there. So this would mean that there could have been a problem merging that data structure. You can remerge the ESU (JD7792) and force the data structure to merge. If you need assistance with that I have included a document that details how to reapply an ESU to force it to remerge all objects. Thanks!
3) Apply SP14.2
4) Then apply ASU Update 1
5) For SUN Solaris users: there is a typing error in 1 bussiness function, the detail is as follows:
Our investigation has revealed that all errors relate to one Business function B4300250. This error is that it cannot find the file referenced in the following statement: "include <B4302153.h>". On checking the source it was found that this statement was the only include statement with a capital B, all the other include statements were lower case b. This was changed in the source file and an update build run on this business function B4300250. This completed successfully.
We are now running a full server package build in the hope that this will solve the problem.
I hope this helps. Please do not hesitate to contact me if you have any problems. Mark Tyler(OneWorld Technical Consultant) from Denver has been working closely with me during the upgrade. I am sure he will be too happy to assist some of you.
Sun Solaris 7, Oracle8i, JDE B7333 Xe Update 1 SP14.2, NT4 w/s
>>> WWells@futurenext.com 13/03/01 11:57:38 >>>
It is independent of the SP level. It is supposed to be ALL ESUs since XE
was released up to the point where they cut the Update CD.
SAR 4894806 is one of 47 for ESU JD7444
SAR 4901324 is one of 5 for ESU JD7792
ESU is a pre-requisite for Update 1 and ESU JD7792 is a "post-requisite". JDEdwards has told us nothing about any SP requirement (although we just installed SP14.2 in preparation for JAS).
By the way does anyone know if any kind of package has to be built and deployed after ESU JD7444 is installed in preparation for Xe Update 1? i.e. is it enough to just have the objects from the ESU merged into Central Objects?
Oh yeah - one more question. Is ESU JD7444 an ESU or an ASU?
>> ESU is a pre-requisite for Update 1 and ESU JD7792 is a "post-requisite". JDEdwards has told us nothing about any SP requirement (although we just installed SP14.2 in preparation for JAS).
>> By the way does anyone know if any kind of package has to be built and deployed
>> after ESU JD7444 is installed in preparation for Xe Update 1?
>> i.e. is it enough to just have the objects from the ESU merged into Central Objects?
As I understand, you only need to install JD7444 to Planner
(That means, only to run setup.exe on deployment server)
But you'll better check with JDE.
>> Oh yeah - one more question. Is ESU JD7444 an ESU or an ASU?
Looks like ESU.
P.S. I did apply JD7444 only for Product Packaging, so I don't have any
experience with Update 1.
Important Message to our clients who have received One World
Xe, Update 1:
An issue has been discovered that will result in problems
during installation of One World Xe Update 1, or other ESUs that include
system codes for which you may not be licensed. This problem is resolved
with new Service Pack One-offs that are available on the Knowledge Garden,
Friday, March 9, 2001.
* B733P13x_OMW can be applied to any SP13.x Service Pack. Please
download using update number 4991235
* B733P14x_OMW can be applied to any SP14.x Service Pack. Please
download using update number 4962670
In addition, to minimize the number of downloads and
installation processes that you need to do, we have packaged three
additional corrections into these Service Pack One-offs that address the
* The ability to check in and check out versions from Object
Management Workbench (OMW)
* The issue with performing a Backup and Restore of an ESU
* Specification Merge would fail due to Check in records being deleted
by OMW during the installation process.
If you have not yet begun your install, please download and
install this Service Pack One-off first.
I have applied B733P13x_OMW and I still get an error:
Not licensed to run app. when loading the XE Update.
--- WWells <WWells@futurenext.com> wrote:
> Here is what I received from JDE today:
> Important Message to our clients who have received
> One World
> Xe, Update 1:
> An issue has been discovered that will result in
> during installation of One World Xe Update 1, or
> other ESUs that include
> system codes for which you may not be licensed.
> This problem is resolved
> with new Service Pack One-offs that are available on
> the Knowledge Garden,
> Friday, March 9, 2001.
> * B733P13x_OMW can be applied to any SP13.x Service
> Pack. Please
> download using update number 4991235
> * B733P14x_OMW can be applied to any SP14.x Service
> Pack. Please
> download using update number 4962670
> In addition, to minimize the number of downloads
> installation processes that you need to do, we have
> packaged three
> additional corrections into these Service Pack
> One-offs that address the
> following issues:
> * The ability to check in and check out versions
> from Object
> Management Workbench (OMW)
> * The issue with performing a Backup and Restore of
> an ESU
> * Specification Merge would fail due to Check in
> records being deleted
> by OMW during the installation process.
> If you have not yet begun your install, please
> download and
> install this Service Pack One-off first.
> To view this thread, visit the JDEList forum at:
> + - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - +
> This is the JDEList One World / XE Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> + - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - +
Before you applied SP13x_OMW you were getting a Memory Error - now you are getting a real Error Message - JDE call that progress!!! They knew what the memory error meant and didn't tell us - we had to wait for the service pack, download it and apply it, all to find out what the real error message was when we got the Memory Error when we tried to apply ESU's (that's all ESU's not just Update1). We waited 3 WEEKS for this!!!
Now to the real problem and cure (couldn't JDE have stepped us onto this, and saved us all the wait - after all fixing the problem removes the Memory Error message just as effectively and without a Service Pack).
The real cure is in Licensing - now I do not know about Update 1, but for our ESU problem the cause was the Planner environment. This was the first thing we set up, before we got a License Key, the fix was too too simple.
On the Deployment Server JDEPLAN go to Reset Software Protect Codes P98SRV (menu GH9052 Security Maintenance), select Rest Client Security and select Get Auth from the Exit Bar, this will reset the Client Security to the correct level. Hopefully this will allow you to apply the ESU or Update 1.
Now I do not know what happens if Update 1 is trying to update objects for which you genuinely are not licensed, may still give the same error, if it still does you will need to speak to JDE, but the above solved our problem when applying ESU's.
Again a little rant - why couldn't JDE suggest the solution not just fix the error message!!!!!
OW B732.1 SP11.3.1 (live)
OW733.3 Xe SP 13.1 (dev)
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + Some 95 and NT PC's