Citrix installation problem

Hi JDEList,

Do any of you have experienced the problem in installation of Citrix fat client? When I tried to install a full package to our Citrix servers (all 14 of them), I have to go through this sequence of steps:
install (got the error of 'Unable to load jdel.dll' while running the installLic.exe)
reboot
install (this time work fine)

This made my installation need more than 1 hours to complete. This only happen on the Citrix server and will not happen on any client PC. And this only happen when I install full packages, update packages went well. Any suggestion?

Regards,
Alvin
Xe UPD6 SP20 AIX
Oracle 8.1.7.4.0
W2K Citrix MetaFrame XP
W2K deployment server

What method are you using when installing OneWorld on the Terminal Server?

I've seen the same thing when I install to my terminal servers. In general we do not reinstall JDE very often. Instead, I deploy the new package to a test terminal server, run r98CRTGL to get rid of the JITI. Run R92TAM to build the data dictionary (we run this once a month and use the same files for each build). Then I copy out the pathcode to all of the terminal servers. This needs to be done in off-hours to ensure no users are using the files.

Gregg Larkin
Global CNC Praxair

I tried both methods, command mode calling setup.exe and the windows add/remove software tools to call the setup.exe. No difference when I use either method.

Gregg,

FWIW

I don't know if you copy the whole \B7 folder or not, but you could get
away with only copying the \bin32 and \spec directories.

Thanks,
James

IBM Business Consulting Services
OneWorld CNC Consultant
Cell #: 608-207-5052



gregglarkin
<gregg_larkin@pra To: James Wilson/Chicago/IBM@IBMUS
xair.com> cc:
Sent by: Subject: Re: Citrix installation problem
owner-jdelist@jde
list.com


12/12/2002 03:10
PM
Please respond to
jdelist






I've seen the same thing when I install to my terminal servers. In general
we do not reinstall JDE very often. Instead, I deploy the new package to a
test terminal server, run r98CRTGL to get rid of the JITI. Run R92TAM to
build the data dictionary (we run this once a month and use the same files
for each build). Then I copy out the pathcode to all of the terminal
servers. This needs to be done in off-hours to ensure no users are using
the files.Gregg LarkinGlobal CNC Praxair
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=46729
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+

James,

Our client side deploy process is this:
1) Build a full package
2) Deploy Package to test Terminal server
3) Run R98CRTGL and R92TAM
4) Test the package
5) Run a batch program that copies out the pathcode (ie PD7333) to each terminal server. The batch application copies the directory as PD7333.new
6) The following day, I log in during off-hours (usually around 5:30 am). Kick off any users that may be on the system.
7) Run another batch program that changes the current PD7333 directory to PD7333.old. Then changes the PD7333.new directory to PD7333

Server Side Deploy process
1) Create a PD7333.new directory
2) Copy the Bin and Spec directories from the package directory to the new directory
3) Copy PD7333.new to my batch and application servers
The following morning:
4) I stop services on the enterprise server
5) Rename the directories
6) Restart services
7) Follow same process for batch and application servers

We do at least six deploys a month; 3 PD and 3 PY. Dev and other pathcodes on request. I deploy to 14 terminal servers.
In 2003 we will add in the web client into that mix as we start to migrate users off of terminal servers and onto the web client.

Gregg Larkin
Praxair Global CNC guy

XE, Update 6, SP19, Win2k cluster, SQL 2k, Citrix XP feature release 2