UNABLE TO SIGN IN ON PY9

[JunkPam]

WIN2KSERVER, SQL2000, ENTERPRISEONE 8.9SP2.

HI
THE LAST FRIDAY I'M STARTING TO GET THE FOLLOWING ERROR, BEFORE THAT EVERYTHING WAS OK

WHEN I'M TRYING TO SIGN IN INTO THE PROTOTYPE ENVIRONMENT I GET THIS

DATABASE PASSWORD ENTRY
DATABASE: ONEWORLD LOCAL
USER:
PASSWORD:

AND THIS IS THE JDE.LOG

12928/3412 Fri Oct 13 11:21:20.281 jdb_ctl.c2803

Starting OneWorld



12928/3412 Fri Oct 13 11:21:30.500 JDBODBC.C1177

ODB0000163 - SQLDriverConnect failure. rc=-1



12928/3412 Fri Oct 13 11:21:30.515 JDBODBC.C1177

ODB0000164 - DBC:00 [IM002][0] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified



12928/3412 Fri Oct 13 11:21:30.531 JDBODBC.C1187

ODB0000010 - SQLDriverConnect failed. ODBC DSN: OneWorld Local.



12928/3412 Fri Oct 13 11:21:32.171 jdb_drvm.c735

JDB9900164 - Failed to connect to OneWorld Local



6908/9728 Fri Oct 13 11:21:32.406 jdekprnt.c1021

KNT0000119 - PRTTable_GetDefaultPrinterInfo failed to find printer: User: GCANTU Host: WinClient



12928/3412 Fri Oct 13 11:21:33.671 JTP_CM.C242

JDB9909003 - Could not init connect.



12928/3412 Fri Oct 13 11:21:33.687 JTP_TM.C1039

JDB9909100 - Get connect info failed: Transaction ID =



12928/3412 Fri Oct 13 11:21:33.703 jdb_rq1.c2111

JDB3100013 - Failed to get connectinfo



12928/3412 Fri Oct 13 11:21:33.718 jdb_cfr.c4091

JDB9900802 - Failed to open table F9861 for CheckF9500001InOMW.



12928/3412 Fri Oct 13 11:21:33.718 jdb_cfr.c4653

JDB9900803 - Failed to check F9500001 information in F9861 for environment PY9.



12928/3412 Fri Oct 13 11:21:33.750 jdb_ctl.c3081

JDB9900811 - Failed to init CFR info



12928/3412 Fri Oct 13 11:21:33.843 jdb_ctl.c828

JDB4100001 - Failed to validate Env handle


I HOPE YOU CAN HELP ME

THANKS

 

[jjojde]

Hello, is there any chance you are trying to login on the Deployment Server? If it is the deployment server, are you trying to login as JDE/PSFT? I ask because the error messages indicate problems authenticating against the local database and normally you only see this type of message on the deployment server.

If this is not on the deployment server, is there any chance you have multifoundation in place AND you installed a new service pack on the other foundations? And the reason I ask this is because somewhere in SP2, or 8.93 a SAR fix was introduced that would encrypt the password in the F98OWSEC. If someone by mistake installed the newer service pack on the enteprise services and started services, the new security kernel would automatically encrypt the passwords in the F98OWSEC rendering all foundations running on previous service packas AND sharing the same security table inacessible.

 

[alch]

Hi,
Are you able to login using other environments?
Are you able to connect to PY using another computer?
Have you checked your ODBC settings?

Alex

 

[JunkPam]

HI ALEX

YES, I CAN LOGING USING THE PRODUCTION ENVIRONMENT.

AND NO I CAN'T CONNECT IN ANOTHER COMPUTER, NO ONE CAN CONNECT TO THE PROTOTYPE ENVIRONMENT.

THE ODBC SETTINGS LOOKS GOOD

 

[SULLY1]

Your getting the local database prompts because OneWorld can not find the primary database. If you go to your ODBC setting and next through them you can test the connection. Also check your data sources in OneWorld to make sure you are pointing to the correct database driver. It's located in the DLL name field. Also look at how your users resolve server names some use WINS, DNS or host files. Good luck with your issue.

Patty

 

[alch]

Do you see the PY tables? Can you use SQL queries against them using the same computer?
Did you check the Data sources and OCM?

Alex

 

[JunkPam]

jjojde

no i'm not trying to log on the deployment server.
and multifundation its not the case

Sully

already checked the odbc for connecction and in peoplesoft i've checked the datasources too.
everything seems to be ok

alch

i've checked the ocm too. and yes i can query the tables and both databases CRP and PY9

 

[alch]

Hello JunkPam,
I think you missed something. There is no magic in JDE; it's just huge buggy software

You have to check everything again. You can use one of two approaches.
1. Completely refresh your PY environment with the Prod or DV.
2. Find a document how to create a new custom environment and using it as a check-list verify each setting if it was done in PY.

And you can always drop your PY and create it from scratch.

Alex

 

[JunkPam]

yep, in fact we are creating a new environment.

thanks for your help