Re:

Re:

Generally obsolete ini message comes if the One World client installation
has not been done through add remove programs in control pannel of TSE.
We had faced the same problem once.

Hope this helps.

Arup Choudhury
Sr. Manager - Business Applications
Lafarge India Limited
Calcutta
India




Sony Jacob
<jacobs@paternoim To: jdelistml@jdelist.com
ports.com> cc:
Sent by: Subject:
owner-jdelistml@j
delist.com


03/07/2001 09:34
PM
Please respond to
jdelist





Hi
We did an upgrade from B7332 to B7333(jdexe) and we followed the usual
procedure for installing the fat clients on the terminal servers and
publishing the application. Terminal servers were in install mode during
the instillation, however we have noticed a good deal of profile corruption
and obsolete JDE.ini file errors, our TS has the current MDAC also . Has
anyone else had the same issues if so how was this resolved ?


Sony Jacob
Network Administrator
Terlato Wine Group
MCSE, CCNA ,CCA
Jacobs@paternoimports.com
(847) 444 5686
 

gcotten

Active Member
Re:

This error occurs when there is a lot of network traffic and the jde.ini file does not get jiti down and you end up with a 4 line jde.ini file. We have found that if you have too many installs going at one time, this will happen.

Greg
 

rhunt01

Well Known Member
Re:

You may also want to check out the following document on the knowledge Garden...

OTI-01-0111. Title: Obsolete JDE.ini error on Windows 2000 Terminal Server.

Good Luck


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