JDE FAT client installation

[arulthas]

Hi ALL,

I want to install fat client in a XP workstation. At the end of the installation I get the following error from jdeinst.log which is “CInstaller::ConfigureSecurity (): Licensing configuration failed.” I understand at end of the installation the system will register the workstation name in the jde system. I don’t have this problem when I login as administrator. How can I perform the installation without changing the profile in client workstation?

Thank you.

Best regards,
Arulthas.

 

[ChelseaGirl]

If XP is anything like W2K, you have to make the OW (FAT Client) user a Administrator on the local PC.

 

[MajSimon]

ALso you should be on SP18.1 at a minimum and SP-22 if you are using XP with its SP1

 

[samuqeeth]

This will fix your problem with Win2K, XP Client workstations


Title: How To Avoid Registry Errors on Windows 2000 Client Machines Running OneWorld
Abstract: With Windows 2000, Microsoft has changed the security on the registry keys for the "Users" group causing Registry errors when running OneWorld.
Product OneWorld
Suite Technical
Release All
Document ID OTI-01-0082
Date Created 05/22/2001
Date Reviewed 04/17/2002
Date Revised 04/17/2002
Description of Problem:
OneWorld requires full control on several registry keys in order to run OneWorld. Since Microsoft has changed the security on the system registry with Windows 2000, any user that just belongs to the "Users" group does not have enough permissions to run OneWorld.
When logging onto OneWorld, the following error will be displayed for users who do not have enough permissions to update the registry:
Workaround/Fix for the Registry Errors:
1. The easiest and best solution seems to be making that NT user a member of the "Power Users" group on that Workstation. A "Power User" has enough NT permissions to be able to update the registry keys that OneWorld needs access to.
Note: It is not required to be a member of the "Power Users" group on the domain, but only for that local machine from which they are running OneWorld.
2. The alternative to making the local user a member of the "Power Users" group on the local machine is to use a registry "sniffer" program such as regmon to determine which registry keys need permissions to be edited. You can access this program by going to:

http://www.sysinternals.com/ntw2k/source/regmon.shtml

NOTE: JD Edwards does not support or help troubleshoot the use of this product in any way.

An in-house test determined that the following registry keys and their child/sub-keys need the permissions to be changed to full control in order for Windows 2000 user(s) to be able to properly run OneWorld:
HKEY_LOCAL_MACHINE\Software\JDEdwards
HKEY_CURRENT_USER\Software\JDEdwards
HKEY_CLASSES_ROOT\.jde
HKEY_CLASSES_ROOT\ONEWORLD.JDEAPPLICATION
HKEY_CLASSES_ROOT\JDEPPCOM.Column
HKEY_CLASSES_ROOT\JDEPPCOM.DataItem
HKEY_CLASSES_ROOT\JDEPPCOM.DataStructure
HKEY_CLASSES_ROOT\JDEPPCOM.Environment
HKEY_CLASSES_ROOT\JDEPPCOM.Library
HKEY_CLASSES_ROOT\JDEPPCOM.Table
HKEY_CLASSES_ROOT\JDEOBJECTBROWSETABCTRL
HKEY_CLASSES_ROOT\JDEdwards.Application
HKEY_CLASSES_ROOT\CLSID
HKEY_CLASSES_ROOT\TypeLib

NOTE: JD Edwards does not assume responsibility for any registry key modification that results in Operating System problems. Updating registry keys and modifying values without the proper knowledge of the ramifications of these changes may cause severe problems resulting in the Operating System having to be reinstalled. Please see your IT Administrator before changing registry key permissions, values, etc.