DRezanka
Reputable Poster
Help,
Pre-SP22, we have had our Enterprise Server named LPI400 and out Relational Database (Directory Entry) named LPI401. Why they were different goes way back before I came to work here. SP22 changed all that. After the upgrade, I was suddenly getting errors in both the JDE Services and JAS stating that "Connection to relational database LPI401 does not exist". JDE said that with SP22, a change was made that the ES machine name and RDB name had to match. Okay, so I made the change. The messages disappeared from the JDE Services, but now my JAS is giving me ""Connection to relational database LPI400 does not exist". Same sort of message, different RDB name.
I have a call open to JDE, but they have been 'reviewing my logs' for two days now. I have a critical deadline fast approaching. Does anyone have any idea what might be wrong or how I might troubleshoot it?
Thanx much,
Doug
Pre-SP22, we have had our Enterprise Server named LPI400 and out Relational Database (Directory Entry) named LPI401. Why they were different goes way back before I came to work here. SP22 changed all that. After the upgrade, I was suddenly getting errors in both the JDE Services and JAS stating that "Connection to relational database LPI401 does not exist". JDE said that with SP22, a change was made that the ES machine name and RDB name had to match. Okay, so I made the change. The messages disappeared from the JDE Services, but now my JAS is giving me ""Connection to relational database LPI400 does not exist". Same sort of message, different RDB name.
I have a call open to JDE, but they have been 'reviewing my logs' for two days now. I have a critical deadline fast approaching. Does anyone have any idea what might be wrong or how I might troubleshoot it?
Thanx much,
Doug
