Unable to open UBE of different ENV from WSJ after Tools Upgrade

[Soumen]

We recently did a Tools Upgrade on our DV910 environment from TR9.1.4.7 to TR9.1.5.5. The tools upgrade completed successfully with no major issues. However we noticed that when trying to open a PDF from the work with submitted jobs on a different environment we get the below message. This happens for any PDF from PD or PY environment. The PDF's from DV910 are opening fine though.
The behavior is different for PY910 and PD910. It is important to mention here that the DV910 is on the same LPAR as the PY910 on a V7R1 iSeries box. The PD910 is on a different LPAR.

Error Message received for PD910 PDF's:

Error message received: UBE: Error creating input or output stream for socket: Connection refused: connect

Here is what the e1root log says...

21 Aug 2015 11:01:48,629[SEVERE][NET]*ERROR* JdeConnectionPool SSSERV02:8016 Error creating input or output stream for socket: Connection refused: connect
21 Aug 2015 11:01:48,629[SEVERE][KERNEL]*ERRROR* LaunchUBE: *ERRROR* LaunchUBE: Error creating input or output stream for socket: Connection refused: connect user:AICHS Env:JDV910
21 Aug 2015 11:01:48,629[SEVERE][JAS]ube.myService() : UBE exception:Error creating input or output stream for socket: Connection refused: connect com.jdedwards.system.kernel.LaunchUBEException: Error creating input or output stream for socket: Connection refused: connect


Error Message received for PY910 PDF's:

"UBE: Retrieve of UBE file failed. The file may not exist on Enterprise Server."

Here is what the e1root log says..

20 Aug 2015 14:53:14,348[SEVERE][JAS]ube.myService() : UBE exception:Retrieve of UBE file failed. The file may not exist on Enterprise Server. com.jdedwards.system.kernel.LaunchUBEException: Retrieve of UBE file failed. The file may not exist on Enterprise Server.
20 Aug 2015 14:53:21,368[SEVERE][KERNEL]*ERRROR* LaunchUBE: *ERRROR* LaunchUBE: Retrieve of UBE file failed. The file may not exist on Enterprise Server. user:AICHS Env:JDV910
20 Aug 2015 14:53:21,368[SEVERE][JAS]ube.myService() : UBE exception:Retrieve of UBE file failed. The file may not exist on Enterprise Server. com.jdedwards.system.kernel.LaunchUBEException: Retrieve of UBE file failed. The file may not exist on Enterprise Server.
20 Aug 2015 14:53:28,638[SEVERE][KERNEL]*ERRROR* LaunchUBE: *ERRROR* LaunchUBE: Retrieve of UBE file failed. The file may not exist on Enterprise Server. user:AICHS Env:JDV910
20 Aug 2015 14:53:28,638[SEVERE][JAS]ube.myService() : UBE exception:Retrieve of UBE file failed. The file may not exist on Enterprise Server. com.jdedwards.system.kernel.LaunchUBEException: Retrieve of UBE file failed. The file may not exist on Enterprise Server.
20 Aug 2015 14:54:25,361[SEVERE][KERNEL]*ERRROR* LaunchUBE: *ERRROR* LaunchUBE: Retrieve of UBE file failed. The file may not exist on Enterprise Server. user:AICHS Env:JDV910
20 Aug 2015 14:54:25,361[SEVERE][JAS]ube.myService() : UBE exception:Retrieve of UBE file failed. The file may not exist on Enterprise Server. com.jdedwards.system.kernel.LaunchUBEException: Retrieve of UBE file failed. The file may not exist on Enterprise Server.


I did an initial assessment of the jde.ini, jas.ini and jdbj.ini files between DV and PY environments but could not notice anything which could result in this issue.
Is there some setup I am missing?

Thanks,
Soumen

 

[Soumen]

Could a multifoundation setup be the reason for this behaviour?
The DV is set on a different port than PY and PD which are set on same port. So the setup is something like.
DV:8016
PY:7016 ; both on same iSeries Server
PD:7016 on a different iSeries Server.

Could that be the reason?

The behavior from FAT client is similar for PY jobs "Failed to Retrieve UBE".
For PD jobs it just keep spinning and returns nothing.
jde.log reports just this error: JDENET_SendMsg failed

Thanks,
Soumen

 

[craig_welton]

For the foundations on the same machine each foundation has it's own printqueue location. When connecting to 7016 and requesting a DV report, it's not finding it in the printqueue that PY (7016) is serving.

Craig

 

[Soumen]

Right! I have this resolved now.