INTERNAL system exception. An application in the client role was able to start a transaction via Current( ), after which it attempted to send a request to a transaction object. The ORB was then unable to find the OTS application runtime component responsible for generating the corresponding service context for the GIOP Request message.
Since the application was at one time successful in using the OTS runtime component, there could be a memory corruption problem in either the application or the ORB. Check your client application for potential memory corruption problems. If none can be found, contact the Compaq support organization.
INTERNAL system exception. One reason for this exception could be a process in the server role received a request targeted for a transactional object, but the ORB was unable to find the OTS runtime component responsible for processing the service context. The client receives the exception returned from the server.
In this case, it could be that the process was not properly linked with the OTS runtime library (nsdots.o) or that there is a memory corruption problem in the application or the ORB.
Insure the Makefile for the application includes nsdots.o by reviewing the set of object files linked with the executable. After this, check the application for memory corruption bugs. If none can be found, contact the Compaq support organization.
In another scenario, a process in the server role received a request targeted for a transactional object. The server processed and returned the request. In this case, the ORB was unable to find the OTS runtime component responsible for generating the service context for the GIOP Reply message. The client receives the exception returned from the server.
In this case, there is probably a memory corruption problem in the application's method implementation. Check the method implementation for memory corruption errors.
INVALID_TRANSACTION system exception. A process in the server role received a GIOP Request message containing a transaction service context that the OTS runtime component could not demarshal. This is normally caused when the service context was improperly formatted. It could also mean that the OTS runtime component responsible for demarshalling the service context encountered a valid but unexpected construct, or that the construct was corrupted during transit.
Contact the support organization that supports the OTS runtime component that is generating the service context. You may also contact the Compaq support organization to report this as a component defect.