CORBA 2.6.1 Programmer's Reference

client role was able to start a transaction by way of Current( ), after which it attempted to
send a request to a transaction object. The ORB was unable to find the OTS application runtime
component responsible for generating the corresponding service context for the GIOP Request
message.
Because the application was at one time successful in using the OTS runtime component, a
memory corruption problem may exist in either the application or the ORB. Check your client
application for potential memory corruption problems. If none can be found, contact your service
provider.
1701 - 1314064037 - MINOR_NO_TS_RECEIVER
This minor code occurs in the context of a 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 that 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.
Ensure 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 your service provider.
In another scenario, a process in the server role received a request targeted for a transactional
object. The server processed and returned the request. The ORB, however, 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 that case, there is probably a memory corruption problem in the application's method
implementation. Check the method implementation for memory corruption errors.
1703 - 1314064039 - MINOR_BAD_TS_CTX
This minor code occurs in the context of a 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 service provider that supports the OTS runtime component generating the service
context (also report it to HP as a component defect).
Interface Repository Minor Code Values (Numbers
1800 - 1899)
1800 - 1314064136 - MINOR_IR_INIT