• Welcome to the upgraded JDELIST forum and thank you for your patience.
    Please restrict discussions and issues regarding the new forum software to the Off Topic forum. We will be monitoring that forum for issues.
    If you have trouble logging in, please reset your password using the forgotten password form: https://www.jdelist.com/community/index.php?lost-password/
    If you are unable to successfully reset your password, please contact us: Click here!
    We hope that you enjoy the upgraded forum.
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

PD7333 INI FILE AFTER PACKAGE DEPLOYMENT

sharling

Member
[frown]

When I build a full package on our PD7333 environment and deploy to a Workstation or WTS, the INI file on the receiving PC gets updated with the following:

[DB SYSTEM SETTINGS]
DefaultEnv=CONVDQ0060

[REPLICATION]
DefaultEnvironment=CONVDQ0060

CONVDQ0060 is another environment that we no longer use, and if you try and sign into to the PC/WTS with the new PD7333 package it throws up another sign in box.

To rectify this I have amend the two CONVDQ0060 entries and enter PD7333.

My question is where is it picking up the CONVDQ0060 Environemnt?

I have checked the JDE.INI file from the B7333/OneWorldClientInstall/Misc directory and nowhere does it indicate CONVDQ0060.

This issue only happens with the PD7333 environment, and not with our PP7333 and PG7333 enviornments which are on the same Deployment Server.

Any help would be greatly appreicated
 

Soul Glo

Member
When you go through the package build director do you have any features defined. check to make sure. Also check to see if you have any other INI file that it might be picking up.
 

sharling

Member
Cleola

Thanks for the reply. There are no special features defined for PD7333. The
builds are exactly the same for PD7333, PP7333 and PG7333, hence the
mystery. I have searched the Deployment Server for all JDE.INI files but
cannot find a reason why CONVDQ0060 is being defaulted in.

Thanks and Best Regards

Steve
 
Hi,

Can you check the JDE.INI that is on your deployment server in the client directory. That is the JDE.INI that gets sent to the client everytime you do a full package.

I guess you will see CONVDQ0060 as your environment.
 

sharling

Member
Hi

Thanks for the reply.

I don't have a JDE.INI file in my Client Directory on the Dep Server, only
the following files:

jdeapp.ddp
jdeapp.xdp
jdeclnt.ddc
jdeclnt.xdc
jdecode.dde
jdecode.xde
jdemod.ddm
jdemod.xdc
ODBCDataSource.inf
Security.inf

Thanks
Steve

** Shared Knowledge = Better Knowledge **

Implementing B7333 (Xe) SP18.1, SQL
 
I am experiencing the same issue. However, my problem is with the PY7333 packages. It changes the environment to my JAS path code by appending the J to PY7333. My INI file looks like the following:

[DB SYSTEM SETTINGS]
DefaultEnv=JPY7333
[REPLICATION]
DefaultEnvironment=JPY7333

The INI on the server contains the correct information. Somehow during the deployment it gets changed. Our DV7333 and PD7333 environments are not affected.
 

sharling

Member
Hi

I think I may have a fix for this problem. Check out your Environment master
P0094. At Package Build time the package looks at P0094 and looks for the
first instance of a PY7333 Pathcode, and as the Environment JPY7333 comes
before PY7333 alphabetically, it is putting JPY7333 as your Def Env instead
of PY7333.

To fix this, either rename the JPY7333 Environment to something else after
P, so ZPY7333 for example, or change the Pathcode from PY7333 to something
else.

Cheers
Steve Harlington
 
Top