Thank you Dale and David for your help. I essentially copied the VMs under our EAS 5.5 to EAS 6.3. I believe I have the same version as the PB environment. I will check.
It feels like a proxy name issue. I remember from the java world about having a different name for proxy to avoid collision. I don't know if the new version is renaming it to do this.
I also constantly see the below message in the jaguar.log. Have you seen anything like this?
2013-05-16 09:48:49.156 ERROR Thread-60 [ManagementImpl] Refresh Failed. The current server is an EJB proxy server. Please refresh the parent server.
2013-05-16 09:48:49.156 INFO Thread-60 [ConsoleOutput] ERROR: Refresh Failed. The current server is an EJB proxy server. Please refresh the parent server.
2013-05-16 09:48:49.156 INFO Thread-60 [SystemException] org.omg.CORBA.BAD_OPERATION was thrown by method com.sybase.jaguar.server.JaguarServer.iiopHandler
2013-05-16 09:48:49.156 INFO Thread-60 org.omg.CORBA.BAD_OPERATION: Refresh Failed. The current server is an EJB proxy server. Please refresh the parent server. vmcid: 0x0 minor code: 0 completed: No
Sam