Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

LIBMFF Messages 1000-1099

1000	ERROR: Application must contain at least two NameManagers.
	Description	If two NameManagers are not configured in the application when a NameManager service is booted, the NameManager quits its startup and writes this error message to the userlog. At least two servers must be configured to run the NameManager service as part of any application. This requirement ensures that a working copy of the name-to-IOR mapping is always available. If the servers are on different machines and one machine crashes, when the machine and application are restarted, the new NameManager obtains the mapping from the other NameManager.
	Action	Configure two NameManagers in the UBBCONFIG file.
1001	ERROR: Application must contain one Master NameManager.
	Description	NameManagers can be designated as either master or slave, the default being slave. If a master NameManager service is not configured in the application and is not running when a slave NameManager service starts, the server terminates itself during boot.
	Action	Configure one of the NameManagers as the master using the -M option in the UBBCONFIG file.
1002	ERROR: Application can only contain one Master NameManager.
	Description	Only one master NameManager can be specified in an application. If more than one NameManager service is designated as a master, the NameManager quits its startup.
	Action	Configure only one NameManager as the master in the UBBCONFIG file.
1004	ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The CannotProceed exception is raised if the FactoryFinder or NameManager encounters an internal error during the search, and the error is written to the userlog. Depending on the severity of the internal error, the server running the FactoryFinder or NameManager services may have terminated.
	Action	If a FactoryFinder service has terminated, start a new FactoryFinder service. If a NameManager service has terminated and another NameManager service is running, start a new NameManager service. If there are no NameManager services running, all server applications must be shut down and restarted to reload the NameManagers.
1005	ERROR: Cannot access TMIB, tperrno = tperrno. [IC=internalcode]
	Description	The NameManager or FactoryFinder service cannot access the TMIB.
	Action	Follow the recovery procedures for the tperrno displayed.
1006	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1007	ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot advertise a network service needed for coordination with other NameManager servers.
	Action	Follow the recovery procedures for the IIOP Server Listener displayed.
1008	WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1009	ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot subscribe to events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1010	WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unsubscribe for events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1011	ERROR: Cannot recover factory mapping.
	Description	A NameManager was not able to obtain a complete factory mapping from another NameManager.
	Action	Shut down and restart the NameManager that generated the message.
1012	ERROR: Application must start TMSYSEVT first.
	Description	The System Event Broker, TMSYSEVT, was not started before the NameManagers were booted.
	Action	Start TMSYSEVT before starting any of the NameManagers.
1013	ERROR: TMSYSEVT must be active.
	Description	The System Event Broker, TMSYSEVT, was not active when the NameManagers were started.
	Action	Ensure that TMSYSEVT has been started before the NameManagers are started.
1014	WARN: Could not advertise administrative service
	Description	A server application is attempting to unregister an application factory during Server::release(). The server detects a problem with the unregister operation at this time. Upon further investigation, the server discovers that the entire application is shutting down. As such, the unregister silently fails because the NameManagers also shut down.
	Action	None.
	See Also	Server::release(), tpsvrdone(3)
1015	ERROR: Invalid class specified
	Description	No NameManagers were specified in the options for the TMFFNAME servers in the UBBCONFIG file.
	Action	Specify at least two TMFFNAME servers as NameManagers, with one being the master NameManager, and an additional TMFFNAME server as the FactoryFinder.
1016	ERROR: Slave NameManager started before Master NameManager.
	Description	In the UBBCONFIG file, a slave NameManager server was started before a master NameManager server. When the slave starts, it tries to communicate with a master and fails.
	Action	In the UBBCONFIG file, start the master NameManager before starting any slave NameManagers.
	See Also	For more information about the TMFFNAME server, see the Administration Guide.
1017	ERROR: Cannot configure both a NameManager and a FactoryFinder together.
	Description	The NameManager and the FactoryFinder were configured using the same server process. This is an invalid combination.
	Action	Separate the NameManager and FactoryFinder into two separate processes.
	See Also	For more information about the TMFFNAME server, see the Administration Guide
1018	WARN: Posting failed; Slave NameManagers may become out of sync.
	Description	The master NameManager failed to post an update message to the System Event Broker, brought about by either a register_factory or an unregister_factory method. The System Event Broker then cannot notify any slave NameManagers. As a result, the slave's factory name mapping may become out of sync with the master.
	Action	First check to ensure that the System Event Broker is running. Second, ensure that there is a communications path between it and the master NameManager. Lastly, shut down and restart the slave NameManagers. On reboot, the slave NameManagers obtain a new copy of the factory name mapping from the master NameManager.
1019	INFO: Detected message loss; resynchronizing name map.
	Description	A slave NameManager, upon receipt of an update message from the master NameManager, has discovered that a previous update message was never received. The slave requests a refresh of the factory name mapping from the master NameManager.
	Action	None.
1020	ERROR: Initialization:unable to open factoryfinder initialization file val, opt_p
	Description	An error has occurred while attempting to open the FactoryFinder initialization file.
	Action	Ensure that the FactoryFinder initialization file is present, is in the correct location, and that the name corresponds to the master Name Manager -f filename command line argument in the ubbconfig file.
1021	ERROR: Initialization:unable to process factoryfinder initialization file val, opt_p
	Description	An error has occurred while attempting to process the FactoryFinder initialization file.
	Action	Examine the initialization file for errors. This message is often displayed with one of the errors in the range of 1022 to 1025 in this catalog.
1022	ERROR: Invalid factory Id: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1023	ERROR: Invalid DomainId: line = val
	Description	A text error has been encountered in the DOMAINID keyword or value while attempting to process the FactoryFinder initialization file.
	Action	Correct the DOMAINID keyword or value in the FactoryFinder initialization file.
1024	ERROR: Invalid RName: line = val
	Description	A text error has been encountered in the RNAME keyword or value while attempting to process the FactoryFinder initialization file.
	Action	Correct the RNAME keyword or value in the FactoryFinder initialization file.
1025	ERROR: File contained no Domain Section Types
	Description	An error has occurred while attempting to process the FactoryFinder initialization file. No Section Types (DM_REMOTE_FACTORIES and DM_LOCAL_FACTORIES) were found in the file.
	Action	Edit the FactoryFinder initialization file to include Section Types.
1026	ERROR: FactoryFinder Invoke to TDomain val failed.
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1027	ERROR: Cannot access TMIB, tperrno = tperrno. [IC=internalcode]
	Description	The NameManager or FactoryFinder service cannot access the TMIB.
	Action	Follow the recovery procedures for the tperrno displayed.
1028	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1029	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1030	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1031	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1032	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1033	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1034	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1035	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1036	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1037	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1038	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1039	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1040	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1041	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1042	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1043	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1044	ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot advertise a network service needed for coordination with other NameManager servers.
	Action	Follow the recovery procedures for the IIOP Server Listener displayed.
1045	ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot advertise a network service needed for coordination with other NameManager servers.
	Action	Follow the recovery procedures for the IIOP Server Listener displayed.
1046	ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot advertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1047	WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1048	WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1049	WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1050	ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot subscribe to events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1051	WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unsubscribe for events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1052	ERROR: Application did not configure any NameManagers.
	Description	No NameManagers were specified in the options for the TMFFNAME servers in the UBBCONFIG file.
	Action	Specify at least two TMFFNAME servers as NameManagers, with one being the master NameManager, and an additional TMFFNAME server as the FactoryFinder.
1053	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1054	ERROR: Invalid factory Id: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1055	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1056	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1057	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1058	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1059	ERROR: Invalid factory Id/Kind: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1060	ERROR: Invalid DomainId: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1061	ERROR: Invalid Domain Keyword: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1062	ERROR: Missing remote entry Kind value: line = val
	Description	A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.
	Action	Correct the factoryID.factoryKind values in the FactoryFinder initialization file.
1063	ERROR: FactoryFinder Invoke to TDomain val failed: val
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1064	ERROR: Cannot access TMIB, tperrno = tperrno.
	Description	The NameManager or FactoryFinder service cannot access the TMIB.
	Action	Follow the recovery procedures for the tperrno displayed.
1065	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1066	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1067	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1068	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1069	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1070	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1071	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1072	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1073	ERROR: Out of memory.
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1074	INFO: Total application factory shutdown assumed.
	Description	A server application is attempting to unregister an application factory during Server::release(). The server detects a problem with the unregister operation at this time. Upon further investigation, the server discovers that the entire application is shutting down. As such, the unregister silently fails because the NameManagers also shut down.
	Action	None.
	See Also	Server::release(), tpsvrdone(3)
1075	ERROR: FactoryFinder Invoke to TDomain val failed.
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1076	ERROR: FactoryFinder Invoke to TDomain val failed:
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1077	ERROR: FactoryFinder Invoke to TDomain val failed.
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1078	ERROR: Invalid RName: line = val
	Description	The FactoryFinder initialization file contains an invalid RName.
	Action	Modify the RName value entered at line val.
	See Also	For more information about the TMFFNAME server, see the Administration Guide.
1079	ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The RegistrarNotAvailable exception is raised if the FactoryFinder service cannot locate the NameManager service. Possible situation that has occurred is that no NameManager servers are running.
	Action	Because there are no NameManagers active that contain the factory name-to-IOR mapping, all server applications must be shut down and restarted to reload the NameManagers.
1080	ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The RegistrarNotAvailable exception is raised if the FactoryFinder service cannot locate the NameManager service. Possible situation that has occurred is that no NameManager servers are running.
	Action	Because there are no NameManagers active that contain the factory name-to-IOR mapping, all server applications must be shut down and restarted to reload the NameManagers.
1081	ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The RegistrarNotAvailable exception is raised if the FactoryFinder service cannot locate the NameManager service. Possible situation that has occurred is that no NameManager servers are running.
	Action	Because there are no NameManagers active that contain the factory name-to-IOR mapping, all server applications must be shut down and restarted to reload the NameManagers.
1082	ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The RegistrarNotAvailable exception is raised if the FactoryFinder service cannot locate the NameManager service. Possible situation that has occurred is that no NameManager servers are running.
	Action	Because there are no NameManagers active that contain the factory name-to-IOR mapping, all server applications must be shut down and restarted to reload the NameManagers.
1083	ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The CannotProceed exception is raised if the FactoryFinder or NameManager encounters an internal error during the search, and the error is written to the userlog. Depending on the severity of the internal error, the server running the FactoryFinder or NameManager services may have terminated.
	Action	If a FactoryFinder service has terminated, start a new FactoryFinder service. If a NameManager service has terminated and another NameManager service is running, start a new NameManager service. If there are no NameManager services running, all server applications must be shut down and restarted to reload the NameManagers.
1084	ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The CannotProceed exception is raised if the FactoryFinder or NameManager encounters an internal error during the search, and the error is written to the userlog. Depending on the severity of the internal error, the server running the FactoryFinder or NameManager services may have terminated.
	Action	If a FactoryFinder service has terminated, start a new FactoryFinder service. If a NameManager service has terminated and another NameManager service is running, start a new NameManager service. If there are no NameManager services running, all server applications must be shut down and restarted to reload the NameManagers.
1085	ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val]
	Description	Accompanying this message is an exception raised to an application object. The CannotProceed exception is raised if the FactoryFinder or NameManager encounters an internal error during the search, and the error is written to the userlog. Depending on the severity of the internal error, the server running the FactoryFinder or NameManager services may have terminated.
	Action	If a FactoryFinder service has terminated, start a new FactoryFinder service. If a NameManager service has terminated and another NameManager service is running, start a new NameManager service. If there are no NameManager services running, all server applications must be shut down and restarted to reload the NameManagers.
1086	ERROR: Out of memory. [IC=internalcode]
	Description	A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.
	Action	The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.
1087	ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot advertise a network service needed for coordination with other NameManager servers.
	Action	Follow the recovery procedures for the IIOP Server Listener displayed.
1088	ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot subscribe to events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1089	WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unsubscribe for events posted by the System Event Broker.
	Action	Follow the recovery procedures for the tperrno displayed.
1090	WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]
	Description	A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.
	Action	Follow the recovery procedures for the tperrno displayed.
1091	ERROR: Local factory and remote factory cannot have the same identifier 'FactoryName'.
	Description	In a multiple domain environment, factories in different domains cannot have the same name.
	Action	Change the name of one of the factories.
1092	ERROR: OBJ_ADAPTER Exception. FactoryFinder Invoke to TDomain val failed:
	Description	An error has occurred while attempting to invoke the FactoryFinder in the specified domain.
	Action	Ensure that the FactoryFinder and domain name information was correctly specified.
1093	ERROR: Couldn't register TransactionFactory. Registrar service not available. Check status of FactoryFinder server(s).
	Description	The TransactionFactory could not be registered because the registration service was unavailable.
	Action	Ensure that your application's FactoryFinder service is fully operational.
1094	ERROR: FFServer::registerTransactionFactory() cannot proceed due to unexpected problem with Registrar. Check status of FactoryFinder server(s).
	Description	The TransactionFactory could not be registered because of unexpected problems with the registration service.
	Action	Ensure that your application's FactoryFinder service is fully operational.