JDENET Error = eConnectionFailed

[Sebastiau]

I am working on Win2000 server, E810, Ms SQL 2000.
I installed deployment and enterprise servers. Succesfully I builded the full package with production environment. I also succesfully deployed and installed it on my workstation. But .... life is hard and I encountered the problem when I wanted to run my workstation. During this connection JDE.log on workstation looks:

504/408 Mon Feb 14 10:42:29.046 jdb_ctl.c2803
Starting OneWorld

504/408 Mon Feb 14 10:43:37.562 jdeksec.c4336
KNT0000305 - JDENET Error = eConnectionFailed

504/408 Mon Feb 14 10:44:38.578 jdeksec.c4336
KNT0000305 - JDENET Error = eConnectionFailed

504/408 Mon Feb 14 10:44:42.921 jdeksec.c1175
SEC0000002 - There is some problem with security server B9ENT Running OneWorld with user's signon and password This may or may not work depending on the databases' security.

504/408 Mon Feb 14 10:44:42.921 jdb_ctl.c3289
JDB1100018 - Failed to get past Security check


504/408 Mon Feb 14 10:44:45.640 msc_signon.cpp222
ValidateUser failed from SignOn

504/408 Mon Feb 14 10:44:46.890 jdb_ctl.c2893
JDB1100012 - Failed to validate Sign on


504/408 Mon Feb 14 10:44:46.953 jdb_ctl.c828
JDB4100001 - Failed to validate Env handle
-------------------------------------------------------
And also on the enterprise server there was generated the log which looks like:

96/984 Mon Feb 14 11:04:23.828 cleanup.c117
Initializing Cleanup Program.
Any errors in this log file will not interfere with normal OneWorld Operation.

996/984 Mon Feb 14 11:04:23.828 cleanup.c144
Initializing EnvironmentD810 . . .

996/984 Mon Feb 14 11:04:23.906 JDETAMIO.C285
TAM: tamfopen d:\peoplesoft\ddp\e810\d:\peoples\spec\glbltbl.xdb error 123-The filename, directory name, or volume label syntax is incorrect. WinErrNum=123.

996/984 Mon Feb 14 11:04:24.015 JDETAMIO.C285
TAM: tamfopen d:\peoplesoft\ddp\e810\d:\peoples\spec\glbltbl.xdb error 123-The filename, directory name, or volume label syntax is incorrect. WinErrNum=123.

996/984 Mon Feb 14 11:04:25.078 jdbodbc.C5158
ODB0000163 - wSQLTables warning. rc=1

996/984 Mon Feb 14 11:04:25.078 jdbodbc.C5158
ODB0000164 - STMT:00 [01000][0] [Microsoft][ODBC SQL Server Driver][SQL Server]Unknown sp_ddopen procedure


996/984 Mon Feb 14 11:04:25.078 jdbodbc.C5187
ODB0000163 - wSQLFetch failure. rc=-1

996/984 Mon Feb 14 11:04:25.078 jdbodbc.C5187
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

996/984 Mon Feb 14 11:04:25.078 JDB_DRVM.C1537
JDB9900189 - Failed to verify that table exists in Business Data - PROD

1)I think the problem is in that wrong path but I can not find where this path is created.
2)Or the problem could be with my user and his security settings.

Maybe you saw previously something like that?

 

[cbruce]

On your enterprise server, B9ENT, open the jde.ini (located in d:\PeopleSoft\ddp\e810\system\bin32

Find the [INSTALL] section and see what the B9= is set too. This should be d:\peoplesoft\ddp\e810

If this path is not set correctly, it will cause the problems you are seeing.

If this was the problem and you changed your JDE.INI to the correct value, restart the JDE services for the change to take effect.

Cheers

 

[Sebastiau]

Hi again,
It was set properly. But... after your suggestion I started to digg and I found that in jde.ini on Enterprise server was mistake :
------------------
[DB SYSTEM SETTINGS]
Default PathCode=PD810 was previously d:\peoplesoft\ddp\e810\PD810
----------------------------
Thanks for quick response.

But still I can not start my workstation. It looks that it can not find ODBC DSN probably because it is not defined. But where workstation keeps such a information?

My workstation Jde.log looks:

1304/1516 Mon Feb 14 17:22:38.578 JDBODBC.C1177
ODB0000163 - SQLDriverConnect failure. rc=-1

1304/1516 Mon Feb 14 17:22:38.578 JDBODBC.C1177
ODB0000164 - DBC:00 [IM002][0] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

1304/1516 Mon Feb 14 17:22:38.578 JDBODBC.C1187
ODB0000010 - SQLDriverConnect failed. ODBC DSN: .

1304/1516 Mon Feb 14 17:22:53.859 jdb_drvm.c735
JDB9900164 - Failed to connect to
Best regards.

 

[cbruce]

Could you post you jde.ini?

 

[Sebastiau]

Yes obviously you can find in attachment my Jde.ini from enterprise and Jde.ini from workstation.

 

[cbruce]

You need to set up ODBC datasources for each SQL datasource. During your install, you should have been prompted for this.

You can always add ODBCs later:

You can check to see if your sql ODBC datasources are present.

1. Goto to Control Panel | Administrative Tools | Datasources (ODBC)
2. Click on system DSN tab
3. You should see the JDE SQL odbc's

If you do not see all of the ODBC's, you can add them as follows:

1. Run P986115
2. Select System - XXX
3. Click Find on Work with datasources
4. For each MSSQL datasource, click the row exit (ODBC Datasource)

Cheers

 

[Sebastiau]

Yes of course but....
I can not start my workstation so how can I add datasources?
I can do it only on development server but it creates datasources on that server, am I right?
I created obviously my own ODBC datasource on workstation but PSFT doesn't see him because it doesn't have info about him.

Only what I can do on workstation is to edit section [DB SYSTEM SETTINGS] in jde.ini on workstation, and write there proper name of datasource and database name (copied from jde.ini from eneterprise server) and create similar ODBC datasource on workstation.
But .... I was not successful unfortunately

 

[winterc]

On B8.9 and above(someone else can elaborate if I am wrong) you do not need to set up workstation or server ODBC datasources as they now use OLE DB or ADO. I think it is OLE. Anyway, doublecheck your datasource definitions. These definitions define the datasource as SQL with the associated DB name and password to allow access. For example "Business Data - Prod" is SQL on NT and the DB name JDE_PRODUCTION and ID is PRODDTA. Make sure you have provided the proper DB security from the original install and creation of the DB's.

 

[cbruce]

The client jde.ini has errors in the
[DB SYSTEM SETTINGS] section:

you need it to look something like this (sorry, I do not have an example from an MSSQL db):

Version=43
Default User=PSFT
Default Role=*ALL
Default Env=PD810
Default PathCode=PD810
Base Datasource=System - 810
Object Owner=sy810
Server=<ENTER YOUR ENTERPRISE SERVER NAME HERE>
Database=<ENTER YOUR DATABASE NAME HERE>
Load Library=
Decimal Shift=Y
Julian Dates=Y
Use Owner=Y
Secured=Y
Type=O
Library List=
Library=
DatabaseName2=PS810
DatabaseInstance=
ServerPort=1433
JDBNETUse=N
UnicodeFlag=Y
LOBFlag=Y
Default Pwd=_

----------

You can always sign into OneWorld from the deployment server PLANNER environment. From there you should be able to see the SQL datasources.

Good luck,

 

[Sebastiau]

Hi again,
I found interesting info on my workstation in jdeinst.log. Probably this is the source of all problems. I reinstalled my workstation again.


PeopleSoft Deployment Server Install Log:
Summary
------------------------------------------------------------------------------------------------------------------------------------------------------
OS Version Win2000 Service Pack 4 (VER_PLATFORM_WIN32_NT 5.0)
Installer Version 022304:0840_OneWorld_EO8.93_GA
Launch String E:\\Setup.exe
Launch Time Tuesday, February 15, 2005 10:51 AM
------------------------------------------------------------------------------------------------------------------------------------------------------~~~
Line# Msg# Time Level Message
------------------------------------------------------------------------------------------------------------------------------------------------------
1 1 10:51:37 I Install Started
2 1 11:01:19 W CInstaller::FindMostRecentPlanner(): No planner datasources found
3 3 11:01:19 W CInstaller::AddODBC(): Unable to copy planner location from planner datasource to previous planner datasource: cannot open key SOFTWARE\ODBC\ODBC.INI\NULL Previous planner datasource needs to be configured manually
Install Time: 00 hours, 11 mins, 52 secs.
Congratulations! Setup completed successfully.

The problem is, what I found that I forgot to define "Creation ODBC datasources" during package assembly. But during the installation I encountered the problem "Licensing configuration failed." !!! and after that "License violation"?! Is that normal? Because with B9 my friend didn't have such problems...

 

[Sebastiau]

So I found the solution and also I want to thank you guys for your suggestions it helped me a lot.

Changes in P9654A --> Deployment Server Revisions screen
Server Share Path should have ' \E810 ' (nothing else) previously I had d:\PeopleSoft\E810

In Foundations --> Tools --> System Administration Tools--> Environments and check the Release Master, Path Code Master and Envionment Master
Release Master should have ' E810 ' for the Release (no drive letter or back slash) previously it was PeopleSoft\E810
Paht Code Master should have ' E810 ' for the Server Share path(no drive letter or back slash).
The deployment server name should be in the Machine Key field.
The Environment Master should have 'E810' for the Release (no drive letter or back slash)



The next thing is the E810\OneWorld Client Install\Install.inf. I
added information for PackageINFs and Current Release Master Path This is what looks like (UOMDEP810 is mine deployment server):


[FileLocations]
PackageInfs=\\UOMDEP810\E810\package_inf
CurrentReleaseMasterPath=\\UOMDEP810\E810
ClientListener=\\UOMDEP810\E810\OneWorld Client Install\Push Install Listener,Setup.exe,/s DefaultInstallPath=c:\e810

[ThirdPartyApps]
MSDE=ThirdParty\MSDE\Setup.exe,

[Attributes]
LocalDS=Local
LocalDB=JDELocal
LocalDBI=JDELocal
DataByPathcode=1

After that modifications I builded the full package and it works fine now.
Only one little thing...
During package build I created the Feature with ODBC datasource but during the installation process on the workstation this feature didn’t work because I have to manually write [DB SYSTEM SETTINGS] section in jde.ini and I have to create also manually ODBC DSN on my workstation. Shouldn’t it be automatic? How to prepare it properly in order to avoid manual work?