Status Code
|
Role
|
Category
|
Resolution
|
AECOM-00002
|
<trace_message>
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00003
|
<error_message>
|
errorRole
|
Adapter
|
Check for the previous error messages.
|
AECOM-00004
|
Cannot convert GUID into string.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00005
|
Cannot convert wide character string to multi byte character string.
|
errorRole
|
Adapter
|
There was a problem with the system. Restart the process.
|
AECOM-00006
|
Cannot convert multi byte character string to wide character string.
|
errorRole
|
Adapter
|
There is a problem with the system. Restart the process.
|
AECOM-00007
|
Cannot construct _guid_t object.
|
errorRole
|
Adapter
|
Internal error. Register the COM component again in the system registry.
|
AECOM-00008
|
Cannot generate GUID.
|
errorRole
|
Adapter
|
Unable to get the Ethernet or token-ring hardware address of the system. Check with the manufacturer.
|
AECOM-00009
|
Invalid GUID <GUID> () <HRESULT>.
|
errorRole
|
Adapter
|
Internal error. Restart the process.
|
AECOM-00010
|
Cannot open registry key.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AECOM-00011
|
Cannot query registry value.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AECOM-00012
|
Cannot determine LIBID for CLSID <CLSID>.
|
errorRole
|
Adapter
|
Register the COM component again in the Microsoft Windows registry.
|
AECOM-00013
|
Cannot open LIBID key <LIBID> in registry () <HRESULT>.
|
errorRole
|
Adapter
|
Register the COM component again in the Microsoft Windows registry.
|
AECOM-00014
|
Cannot get latest type library version for LIBID key <LIBID>.
|
errorRole
|
Adapter
|
Register the COM component again in the Microsoft Windows registry.
|
AECOM-00015
|
Cannot load type library for LIBID key <LIBID> () <HRESULT>.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00016
|
Cannot load type library for CLSID <CLSID> () <HRESULT>.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00017
|
Cannot get type information for CLSID <CLSID> () <HRESULT> ()<error_info>.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AECOM-00018
|
Cannot get type information for interface <Interface> on coclass <coClass> () <HRESULT>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00019
|
Invalid number of methods on interface <Interface> () <HRESULT>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00020
|
Simple type encountered where complex type (UDT or SAFEARRAY) is required ()<Type>
|
errorRole
|
Adapter
|
In the repository, use complex type (UDT or SAFEARRAY) instead of simple type.
|
AECOM-00021
|
Cannot get type information attributes for CLSID <CLSID>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00022
|
Call to ITypeInfo::GetRefTypeInfo failed () <HRESULT>.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00023
|
Call to ITypeInfo::GetContainingTypeLib failed () <HRESULT>.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00024
|
Call to ITypeInfo::GetDocumentation failed () <HRESULT>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00025
|
Call to ITypeInfo::GetVarDesc failed () <HRESULT>.
|
errorRole
|
Adapter
|
Internal error while reading the type library. Make sure that the correct DLL is registered.
|
AECOM-00026
|
Call to ITypeLib::FindName failed <HRESULT>, <error_info>.
|
errorRole
|
Adapter
|
Internal error while reading the type library. Make sure that the correct DLL is registered.
|
AECOM-00027
|
Call to ITypeLib::GetDocumentation failed () <HRESULT>.
|
errorRole
|
Adapter
|
Internal error while reading the type library. Make sure that the correct DLL is registered.
|
AECOM-00028
|
Call to ITypeLib::FindName returned <name> ITypeInfo interfaces for name () <name>.
|
errorRole
|
Adapter
|
Internal error while reading the type library. Make sure that the correct DLL is registered.
|
AECOM-00029
|
Invalid VARTYPE () <vartype>.
|
errorRole
|
Adapter
|
Parameter type used is not supported in this version of the adapter. Use only the supported parameter types.
|
AECOM-00030
|
Invalid type name () <type_name>.
|
errorRole
|
Adapter
|
This version of the adapter does not support the type name used. Use only the supported type names.
|
AECOM-00031
|
Cannot create record for UDT <UDTname>.
|
errorRole
|
Adapter
|
Internal error. Restart the process.
|
AECOM-00032
|
Cannot destroy record for UDT <UDTname>.
|
errorRole
|
Adapter
|
Internal error. Restart the process.
|
AECOM-00033
|
The number of member variables in a COM UDT exceeds the number of fields in an AE class () <class>.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00034
|
Cannot get AE class description () <class>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00035
|
Operations mismatch for the class <class>. The following operations are present in the COM type library, but not in the AE repository: <class>. The following operations are present in the AE repository, but not in the COM type library: <type_library>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00036
|
Parameters mismatch for operation <operation>. The following parameters are present in the COM type library, but not in the AE repository: <repository>. The following operations are present in the AE repository, but not in the COM type library: <type_library>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00037
|
Direction mismatch for parameter <parameter> in operation <operation>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00038
|
Return type mismatch for operation <Type>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00039
|
Parameter type mismatch for parameter <parameter> in operation <operation>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00040
|
No AE class associated with endpoint <endpoint> () <HRESULT>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00041
|
The default interface on the COM coclass associated with the AE class <class> (endpoint <endpoint>) has more than one method.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00042
|
Method <method> of the default interface on the COM coclass associated with the AE class <class> (endpoint <endpoint>) has more than one parameter.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00043
|
Param <parameter> of method <method> of the default interface on the COM coclass associated with the AE class <class> (endpoint <endpoint>) has invalid direction.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00044
|
Param <parameter> of method <method> of the default interface on the COM coclass associated with the AE class <class> (endpoint <endpoint>) has invalid type.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00045
|
The MSubscriber <subscriber> received a message containing an unsupported complex type (<Type>).
|
errorRole
|
Adapter
|
This version of the adapter does not support the type used. Use only the supported types.
|
AECOM-00046
|
The MSubscriber <subscriber> received a message containing a non-matching complex type (<Type>).
|
errorRole
|
Adapter
|
This version of the adapter does not support the type used. Use only the supported types.
|
AECOM-00047
|
Operation <operation> is missing the TIBCOCOMADAPTER_EXCEPTION of type "string".
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00048
|
Invalid number of dimensions for SAFEARRAY (<diemension>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00049
|
Invalid element type (<Type>) in SAFEARRAY. Should be <Type>.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00050
|
Call to SafeArrayAccessData failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00051
|
Call to SafeArrayUnaccessData failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00052
|
Call to SafeArrayCreate or SafeArrayCreateEx failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00053
|
Call to SafeArrayDestroy failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00054
|
Call to SafeArrayGetVartype failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00055
|
Call to SafeArrayGetRecordInfo failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00056
|
A SAFEARRAY contains an invalid element type (<Type>).
|
errorRole
|
Adapter
|
Element type used is not supported. Use only the supported element types, details of which can be found in the user’s guide.
|
AECOM-00057
|
A SAFEARRAY cannot be the element type of a SAFEARRAY (<Type>).
|
errorRole
|
Adapter
|
Element type used is not supported. Use only the supported element types, details of which can be found in the user’s guide.
|
AECOM-00058
|
A VARIANT contains an invalid type (<Type>).
|
errorRole
|
Adapter
|
Element type used is not supported. Use only the supported element types, details of which can be found in the user’s guide.
|
AECOM-00059
|
Cannot initialize a type description for a type contained by a VARIANT (<Type>). Potential memory leak.
|
errorRole
|
Adapter
|
Problem with the System. Restart the process.
|
AECOM-00060
|
Call to IRecordInfo::GetName failed (<HRESULT>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00061
|
Call to GetRecordInfoFromTypeInfo failed (<HRESULT>).
|
errorRole
|
Adapter
|
Problem with the System. Restart the process.
|
AECOM-00062
|
Call to IRecordInfo::GetTypeInfo failed (<HRESULT>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00063
|
Cannot create thread initialized event.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00064
|
Cannot create thread.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00065
|
Thread exited for unknown reason.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00066
|
Cannot start dispatching Rendezvous events.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00067
|
Pool of event dispatching threads has not been created.
|
errorRole
|
Adapter
|
Problem with activating the thread(s). Restart the process and system (if possible).
|
AECOM-00068
|
Number of event dispatching threads must be greater than 0.
|
errorRole
|
Adapter
|
Number of event dispatching threads must be greater than 0. Re-configure the repository option in the repository.
|
AECOM-00069
|
Cannot create event dispatching thread.
|
errorRole
|
Adapter
|
Problem with creating the thread. Restart the process and system (if possible).
|
AECOM-00070
|
Wait for event dispatching thread to exit timed out (<HRESULT>).
|
errorRole
|
Adapter
|
Problem in destroying the threads. Kill the process (if it is still running).
|
AECOM-00071
|
MOperationException thrown: <description>.
|
errorRole
|
Adapter
|
Error in getting the data from Subscribersreply.Restarttheprocess.'
|
AECOM-00072
|
MException thrown: <description>.
|
errorRole
|
Adapter
|
Check error description in the event viewer for more information.
|
AECOM-00073
|
Unknown exception thrown.
|
errorRole
|
Adapter
|
Restart the adapter.
|
AECOM-00074
|
<information>
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00075
|
TIBCOCOMService <service_name> starting with Repo URL ""<repoURL> and Config URL ""<configURL>.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00076
|
TIBCOCOMService running.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00077
|
TIBCOCOMService stopping.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00078
|
TIBCOCOMService initializing.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00079
|
TIBCOCOMService done initializing.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00080
|
Cannot initialize MTrace logging.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00081
|
Command line option specified more than once: <option>.
|
errorRole
|
Adapter
|
Remove the duplicate command line parameters while executing TIBCOCOMService.
|
AECOM-00082
|
Invalid command line option: <option>.
|
errorRole
|
Adapter
|
Pass valid command line parameters to TIBCOCOMService.
|
AECOM-00083
|
Missing data for command line option: <option>.
|
errorRole
|
Adapter
|
Pass valid command line parameters to TIBCOCOMService.
|
AECOM-00084
|
Invalid combination of command line options.
|
errorRole
|
Adapter
|
Pass valid command line parameters to TIBCOCOMService.
|
AECOM-00085
|
Repository URL not specified.
|
errorRole
|
Adapter
|
Pass valid repository file name as command line parameter to TIBCOCOMService.
|
AECOM-00086
|
Config URL not specified.
|
errorRole
|
Adapter
|
Pass a valid Config URL as command line parameter.
|
AECOM-00087
|
Programmatic identifier not specified.
|
errorRole
|
Adapter
|
Pass a valid ProgID while creating the object.
|
AECOM-00088
|
Cannot cannot create tibco moniker (<HRESULT>).
|
errorRole
|
Adapter
|
Check TIBCOCOMInterceptorService executable file in the system path.
|
AECOM-00089
|
IUnknown::QueryInterface failed (<Interface> - <HRESULT>).
|
errorRole
|
Adapter
|
Restart adcomInterceptorService.
|
AECOM-00090
|
Error calling StartServiceCtrlDispatcher (<error>).
|
errorRole
|
Adapter
|
Starting Service failed. Make sure that the service is not already running.
|
AECOM-00091
|
Error calling RegisterServiceCtrlHandler.
|
errorRole
|
Adapter
|
Service callback registration failed. Restart the service.
|
AECOM-00092
|
Error calling SetServiceStatus.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AECOM-00093
|
Cannot open service control manager (<error>).
|
errorRole
|
Adapter
|
There can be several possibilities, You may not have access to service control manager.
|
AECOM-00094
|
Cannot create NT Service (<error>).
|
errorRole
|
Adapter
|
There can be several possibilities, either service already exists or you may not have access to this service.
|
AECOM-00095
|
Cannot open NT Service (<error>).
|
errorRole
|
Adapter
|
Either service is not installed or You may not have access to service.
|
AECOM-00096
|
Cannot delete NT Service.
|
errorRole
|
Adapter
|
Deleting the service failed. Try deleting the service again.
|
AECOM-00097
|
Call to CoInitializeEx failed.
|
errorRole
|
Adapter
|
Some Microsoft Windows COM Libraries might be missing. Try to reinstall them on the system.
|
AECOM-00098
|
Cannot create instance of coclass <class>, interface <Interface> (HRESULT: <HRESULT>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00099
|
Unknown exception thrown by implementation of coclass <class> (interface <Interface>, method <method>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00100
|
Cannot convert DATE to RVDATE.
|
errorRole
|
Adapter
|
Error in converting DATE to RVDATE format. Use the date formats supported by RV.
|
AECOM-00101
|
Cannot convert RVDATE to DATE.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00102
|
Cannot convert CY to BSTR.
|
errorRole
|
Adapter
|
Problem in converting the currency value. Check the validity of the currency value.
|
AECOM-00103
|
Cannot convert BSTR to CY.
|
errorRole
|
Adapter
|
Problem in converting the string to currency value. Check the validity of the currency value.
|
AECOM-00104
|
Invalid data type.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00105
|
Cannot access termination subscriber (<subscriber>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00106
|
Cannot add termination event listener.
|
errorRole
|
Adapter
|
Problem with the termination subscriber in the repository. Please reconfigure it correctly.
|
AECOM-00107
|
Cannot create stop event for TIBCOCOMService.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AECOM-00108
|
Wait for TIBCOCOMService stop event failed.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AECOM-00109
|
Call to SetEvent failed (<error>).
|
errorRole
|
Adapter
|
Restart adcomService.
|
AECOM-00110
|
No rv</cm/tx>RpcServers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00111
|
No rv</cm/tx>Subscribers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00112
|
Downcast of MData to MGlobalNameData failed (<endpoint>).
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00113
|
Cannot get extended properties for (<extended_property>).
|
errorRole
|
Adapter
|
Extended properties are missing in the repository. Please add a configuration option "/class/extendedProperties" in the repository along with correct values. See the user’s guide for details.
|
AECOM-00114
|
Cannot get value for property (<property>).
|
errorRole
|
Adapter
|
Set correct value to "progID" property in the repository.
|
AECOM-00115
|
Cannot derive CLSID from Programmatic Identifier (<PROGID>).
|
errorRole
|
Adapter
|
Set correct value to "progID" property in the repository.
|
AECOM-00116
|
Interface not supported for an AE Class (<PROGID> - <Interface>).
|
errorRole
|
Adapter
|
Set correct value to "defaultInterface" property in the repository.
|
AECOM-00117
|
Cannot add listener to MSubscriber (<subscriber>).
|
errorRole
|
Adapter
|
Problem in adding a subscriber listener. Reconfigure the subscriber correctly in the repository using TIBCO Designer.
|
AECOM-00118
|
Call to getComponentByName failed (<endpoint>).
|
errorRole
|
Adapter
|
Endpoint is not configured correctly in the repository. Reconfigure the endpoint in the repository using TIBCO Designer.
|
AECOM-00119
|
Downcast of MComponent to MRPCServer failed (<endpoint>).
|
errorRole
|
Adapter
|
Cannot create RPC server. Reconfigure the RPC Server correctly in the repository.
|
AECOM-00120
|
Downcast of MComponent to MSubscriber failed (<endpoint>).
|
errorRole
|
Adapter
|
Cannot create the Subscriber. Reconfigure the Subscriber correctly in the repository.
|
AECOM-00121
|
Downcast of MComponent to MPublisher failed (<endpoint>).
|
errorRole
|
Adapter
|
Cannot create the publisher. Reconfigure the Publisher correctly in the repository.
|
AECOM-00122
|
Downcast of MData to MInstance failed.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00123
|
Downcast of MData to MSequence failed.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00124
|
The value of the parameter <parameter> in the request is NULL.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00125
|
The value of the parameter <parameter> in the reply is NULL.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00126
|
Event of type other than MDataEvent received by subscriber (<subscriber>).
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00127
|
Cannot create MInstance from event received by MSubscriber <subscriber> (<description>).
|
errorRole
|
Adapter
|
Problem with the Subscriber. Reconfigure the subscriber correctly in the repository.
|
AECOM-00128
|
Cannot serialize MInstance.
|
errorRole
|
Adapter
|
Problem with the Publisher schema. Reconfigure the schema in repository.
|
AECOM-00129
|
TIBCOCOMInterceptor starting with Repo URL "<repoURL>" and Config URL "<configURL>".
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00130
|
No rv</cm/tx>RpcClients specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00131
|
No rv</cm/tx>Publishers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00132
|
Cannot add shutdown notification listener.
|
errorRole
|
Adapter
|
Recheck the Shutdown event listener in the repository.
|
AECOM-00133
|
Cannot enable shutdown notification (<message>).
|
errorRole
|
Adapter
|
Recheck Shutdown event in the repository.
|
AECOM-00134
|
Cannot initialize RV</cm/tx> RPC Clients (<description>).
|
errorRole
|
Adapter
|
Recheck the endpoint of RPC Clients in the repository.
|
AECOM-00135
|
Cannot initialize RV</cm/tx> Publishers (<description>).
|
errorRole
|
Adapter
|
Recheck the Publisher endpoints in the repository.
|
AECOM-00136
|
Cannot enable MTrace logging.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00137
|
Cannot enable Cerr logging.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00138
|
Cannot enable Event Log logging.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AECOM-00139
|
Cannot get repository information for CLSID (<CLSID>).
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00140
|
AE Repository not currently available.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00141
|
coclass (<class>) not registered in AE Repository.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00142
|
Cannot allocate index for thread local storage (<error>).
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00143
|
Cannot set thread local storage value (<error>).
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00144
|
Cannot get thread local storage value (<error>).
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00145
|
Invalid interface pointer.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00146
|
No operations defined for class <class>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00147
|
No parameters defined for operation <class>::<operation>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00148
|
Unsuccessful HRESULT returned by implementation (<HRESULT>).
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00149
|
Error getting string from MData (<class>: <description>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00150
|
Missing IRecordInfo for record in VARIANT.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00151
|
Attributes mismatch for the class <class>. The following attributes are present in the COM type library, but not in the AE repository: <AEAttribute>. The following attributes are present in the AE repository, but not in the COM type library: <COMAttribute>.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00152
|
The type of the attribute <attribute> in the class <class> is not the same in the AE repository and the COM type library.
|
errorRole
|
Adapter
|
Re-import the DLL into the repository using the metadata import utility.
|
AECOM-00153
|
Unsupported ActiveEnterprise type (<AEClass>: <class>).
|
errorRole
|
Adapter
|
AE Class name used in the repository is not supported in this version of the adapter. Use only the supported AE Class names in the repository. See the user’s guide for details.
|
AECOM-00154
|
Successfully created NT Service (<servicename>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00155
|
Successfully deleted NT Service (<servicename>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00156
|
Call to ITypeInfo::GetTypeAttr failed (<HRESULT>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00157
|
Cannot get type info for UDT.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00158
|
Cannot get attribute description <attribute> for AE class <class>.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00159
|
Invalid instance lifetime value (<value>) in property <property>.
|
errorRole
|
Adapter
|
Set the valid value for the "lifetime" in the repository.
|
AECOM-00160
|
Sending request (<request>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00161
|
Received request (<request>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00162
|
Sending reply (<reply>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00163
|
Received reply (<reply>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00164
|
Publishing document (<document>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00165
|
Received document (<document>).
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00166
|
Advisory: <advisory> : <message>.
|
errorRole
|
Adapter
|
Check the actual error message for details.
|
AECOM-00167
|
Advisory: <advisory> : <message>.
|
warnRole
|
Adapter
|
|
AECOM-00168
|
TIBCOCOMInterceptor service starting.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00169
|
TIBCOCOMInterceptor service running.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00170
|
TIBCOCOMInterceptor service stopping.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00171
|
Bad service request.
|
errorRole
|
Adapter
|
Problem with the Interceptor service. Please reinstall it.
|
AECOM-00172
|
<description>.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00173
|
Cannot load resource module.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AECOM-00174
|
Initialized <endpoint>: Name: <name>; Session: <session>; Subject: <subject>; <information>; Associated class: <class>.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00175
|
Initializing <endpoint>.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00176
|
Starting <number> event dispatching thread</s>.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00177
|
Invalid event of type "<Type>" received by subscriber <subscriber>.
|
errorRole
|
Adapter
|
Error message not used.
|
AECOM-00178
|
MExceptionEvent received by subscriber <subscriber>: <exception>.
|
errorRole
|
Adapter
|
Problem in receiving the data. Check for validity of the incoming data from Interceptor or from external source.
|
AECOM-00179
|
Invalid value assigned to messageConfirmBehavior parameter (<messageConfirmBehaviour>).
|
errorRole
|
Adapter
|
Please set the valid values for "/extendedProperties/messageConfirmBehavior" configuration option in the Repository.
|
AECOM-00180
|
Downcast of MComponent to MRPCClient failed (<RPCClient>).
|
errorRole
|
Adapter
|
Reconfigure the RPC client using TIBCO Designer.
|
AECOM-00181
|
Advisory: <advisory> : <description>.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00182
|
Creation of Recordset object failed.
|
errorRole
|
Adapter
|
Verify that the appropriate ADO libraries are present in the system.
|
AECOM-00183
|
Call to SafeArrayPutElement failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00184
|
Adding field to Recordset object failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00185
|
Cannot open the Recordset object created (<HRESULT>).
|
errorRole
|
Adapter
|
Verify that the appropriate ADO libraries are present in the system.
|
AECOM-00186
|
Cannot populate Recordset object with data received (<HRESULT>).
|
errorRole
|
Adapter
|
Verify that the appropriate ADO libraries are present in the system.
|
AECOM-00187
|
Call to Recordset object method AddNew failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00188
|
Call to Recordset object method MoveFirst failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00189
|
Conversion of Recordset pointer failed.
|
errorRole
|
Adapter
|
Verify that the appropriate ADO libraries are present in the system.
|
AECOM-00190
|
Recordset object data access failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00191
|
Call to Recordset object method MoveNext failed (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00192
|
Cannot close the Recordset object (<HRESULT>).
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00193
|
DataTypeEnum (<datatype>) not supported as a Recordset field.
|
errorRole
|
Adapter
|
Element type used is not supported. Use only the supported element types, details of which can be found in the user’s guide.
|
AECOM-00194
|
Unsupported AE data type used as a Recordset field.
|
errorRole
|
Adapter
|
Data type used is not supported. Use only the supported element types, details of which can be found in the user’s guide.
|
AECOM-00195
|
Publication error: Error occurred while trying to publish. The exception is: <exception>.
|
errorRole
|
Adapter
|
Restart the process.
|
AECOM-00197
|
No JMSRpcServers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00198
|
No JMSSubscribers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00199
|
No JMSRpcClients specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00200
|
No JMSPublishers specified in repository.
|
infoRole
|
Adapter
|
Indicates normal adapter information. No action necessary.
|
AECOM-00201
|
Cannot initialize JMS RPC Clients (<message>).
|
errorRole
|
Adapter
|
Recheck the endpoint of JMS RPC Clients in the repository.
|
AECOM-00202
|
Cannot initialize JMS Publishers (<message>).
|
errorRole
|
Adapter
|
Recheck the endpoint of JMS Publishers in the repository.
|
AEADCOM_910003
|
Startup Error. The command-line parameters: <option> has not been specified
|
errorRole
|
Adapter
|
Please specify the command-line parameter. For details, see the User’s Guide.
|
AEADCOM_910004
|
Startup Error. SDK Exception <exception> occurred in the adapter initialization while creating the MAppProperties object. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please refer to SDK documentation for Repository URL and Configuration URL specification.
|
AEADCOM_910005
|
Startup Error. SDK Error <error> received on starting the adapter after initialization. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify your repository settings. For details, see the User’s Guide..
|
AEADCOM_910006
|
Startup Error. SDK Exception <error> occurred while creating a shutdown listener with parameters <paramter>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify your repository settings for validity of configuration for the shut down listener. For details, see the User’s Guide.
|
AEADCOM_910007
|
Startup Error. Unable to create a connection with the target application <application> using connection parameters <parameter> and the target application error is <error>
|
errorRole
|
Adapter
|
Please verify your repository settings for validity of connection parameters. For details, see the User’s Guide.
|
AEADCOM_910008
|
Startup Error. Received target application error <error> while creating the connection object with the target application <application>. The connection parameters are <parameters> and the connection pool size is <size>.
|
errorRole
|
Adapter
|
Please verify your repository settings for validity of connection parameters. For details, see the User’s Guide.
|
AEADCOM_910009
|
Startup Error. Unable to find target application library/libraries <libraries> in the classpath <classpath> for the target application <application>
|
errorRole
|
Adapter
|
Please verify that the client libraries are included in the classpath. For details, see the User’s Guide.
|
AEADCOM_910010
|
Startup Error. Failed to load properties file containing trace messages from path<path> for Adapter Instance <instance>. Error Message <message>
|
errorRole
|
Adapter
|
Please verify that the locale is set to en_US on your machine.
|
AEADCOM_910011
|
Startup Error. Duplicate instance detected with name = <name>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify your repository settings for duplicate adapter instance name. For details, see the User’s Guide.
|
AEADCOM_910012
|
Startup Error. Unable to create a Custom Hawk Micro Agent Named <name> used for <use>.
|
errorRole
|
Adapter
|
|
AE_ADCOM_START_UP_100
|
Startup Error. Error calling StartServiceCtrlDispatcher.
|
errorRole
|
Adapter
|
Starting Service failed. Make sure that the service is not already running.
|
AE_ADCOM_START_UP_101
|
Startup Error. Error calling RegisterServiceCtrlHandler.
|
errorRole
|
Adapter
|
Service callback registration failed. Restart the service.
|
AE_ADCOM_START_UP_102
|
Startup Error. Error calling SetServiceStatus.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AE_ADCOM_START_UP_103
|
Startup Error. Cannot open service control manager.
|
errorRole
|
Adapter
|
There can be several possibilities, You may not have access to service control manager.
|
AE_ADCOM_START_UP_104
|
Startup Error.Cannot open NT Service.
|
errorRole
|
Adapter
|
Either service is not installed or You may not have access to service.
|
AE_ADCOM_START_UP_105
|
Startup Error. Call to CoInitializeEx failed.
|
errorRole
|
Adapter
|
Some Microsoft Windows COM Libraries might be missing. Try to reinstall them on the system.
|
AE_ADCOM_START_UP_106
|
Startup Error. Cannot enable Event Log logging.
|
errorRole
|
Adapter
|
Check the permissions for the current Microsoft Windows user.
|
AE_ADCOM_START_UP_107
|
Number of event dispatching threads must be greater than 0.
|
errorRole
|
Adapter
|
Number of event dispatching threads must be greater than 0. Re-configure the repository option in the repository.
|
AEADCOM_920001
|
Subscription error. Subscription service <subscription service> listening on <port> received an unexpected event of type = <Type>, Expects event <Type>. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920002
|
Subscription error. Subscription service <subscription service> failed to deserialize the event received on subject <subject> and SDK exception thrown is <exception>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920003
|
Subscription error. Subscription service <subscription service> listening on subject <subject> received inbound event with null data. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920004
|
Subscription error. Subscription service <subscription service> listening on subject <subject> could not deserialize the inbound event to MbusinessDocument <document>. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920005
|
Subscription error. Subscription service <subscription service> listening on subject <subject>,could not find the tracking data. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920006
|
Subscription error. Subscription service <subscription service> listening on subject <subject> received error <error> in SDK message level UserExit <userexit>
|
errorRole
|
Adapter
|
Make sure the UserExit parameters are valid and the user exit is invokable from SDK.
|
AEADCOM_920007
|
Subscription error. Subscription service <subscription service> listening on subject <subject> could not get the class description of <class>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please check the repository configuration for this service. For details, see the User’s Guide.
|
AEADCOM_920008
|
Subscription error. Subscription service <servicename> listening on subject <subject> could not find the mandatory property <property> in class <class>. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920009
|
Subscription error. Subscription service <servicename> listening on subject <subject> received event with invalid value <value> for property <property> in class <class>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920010
|
Subscription error. Subscription service <servicename> listening on subject <subject> received event with missing attribute <attribute> in class <class>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920011
|
Subscription error. Subscription service <service name> listening on subject <subject> received event with missing association <association> for class <class>. The Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920012
|
Subscription error. Subscription service <servicename> listening on subject <subject> received MBusinessDocument <document> with NULL value for attribute <attribute>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920013
|
Subscription error. Subscription service <servicename> listening on subject <subject> received MBusinessDocument <document> with invalid value <value> for attribute <attribute>.
|
errorRole
|
Adapter
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. For details, see the User’s Guide.
|
AEADCOM_920014
|
Subscription error. Subscription service <service name> listening on subject <subject> could not process the inbound event due to connection error <error> against target application <application> with parameters <parameters> after <number> connection retries. The connection timeout is <timeout_value>.
|
errorRole
|
Adapter
|
Check the target application and make sure it is up and running. Check the validity of the connection parameters. For details, see the User’s Guide.
|
AEADCOM_920015
|
Subscription error. Subscription service <servicename> listening on subject <subject> failed due to target application invocation error <error>. Target application is <application>. The target application specific commands and parameters are <parameters>
|
errorRole
|
Adapter
|
Check the target application command and the parameters and make sure they are valid.
|
AEADCOM_920016
|
Subscription error. Subscription service <servicename> listening on <port> received error <error> in Post Processing UserExit <userexit>. The user exit parameters are <parameters>
|
errorRole
|
Adapter
|
|
AEADCOM_920017
|
Subscription error. Subscription service <service name> listening on <port> could not send response <response> on reply subject <subject>. The parameters for publisher endpoint for sending the reply are <parameters>. Repository URL is <repoURL> and Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Please check your repository settings for the publish endpoint of this subscription service. For details, see the User’s Guide.
|
AEADCOM_920018
|
Subscription error. Subscription service <service name> listening on <subject>. could not send target application invocation error <error> on error subject <subject>. The parameters for publisher endpoint for sending the reply are <parameters>
|
errorRole
|
Adapter
|
Please check your repository settings for the publish endpoint of this subscription service. For details, see the User’s Guide.
|
AEADCOM_920019
|
Subscription error. Subscription service <service name> listening on <port> could not create reply from target application response <response> for publish on reply subject <subject>. The parameters for publisher endpoint for sending the reply are <parameters>
|
errorRole
|
Adapter
|
Please check your repository settings for the publish endpoint of this subscription service. For details, see the User’s Guide.
|
AE_ADCOM_SUB_100
|
MExceptionEvent received by subscriber <subscriber>: <error>.
|
errorRole
|
Adapter
|
Problem in receiving the data. Check for validity of the incoming data from Interceptor or from external source.
|
AE_ADCOM_SUB_101
|
The MSubscriber <subscriber> received a message containing an unsupported complex type (<Type>).
|
errorRole
|
Adapter
|
This version of the adapter does not support the type used. Use only the supported types.
|
AE_ADCOM_SUB_102
|
The MSubscriber <subscriber> received a message containing a non-matching complex type (<Type>).
|
errorRole
|
Adapter
|
This version of the adapter does not support the type used. Use only the supported types.
|
AE_ADCOM_SUB_103
|
Cannot create MInstance from event received by MSubscriber <subscriber> (<HRESULT>).
|
errorRole
|
Adapter
|
Problem with the Subscriber. Reconfigure the subscriber correctly in the repository.
|
AEADCOM_930001
|
Publication error. Publication service <servicename> publishing on subject <subject> encountered error <error> while trying to connect to target application <application>. Connection parameters are <parameters>, the connection timeout is <timeout> milliseconds, and the number of retry efforts is <number>. Polling timeout is <number> milliseconds.
|
errorRole
|
Adapter
|
Check the target application and make sure it is up and running. Check the connection parameters for right syntax and values. For details, see the User’s Guide..
|
AEADCOM_930002
|
Publication error. Publication service <servicename> with publication subject <subject> encountered error <error> while trying to create publish event with schema <schema>. The Target application details are <application>.
|
errorRole
|
Adapter
|
Make sure that the publication service is configured properly.
|
AEADCOM_930003
|
Publication error. Publication service <servicename> with publishing subject as <subject> received event from target application <application>. It failed while converting event to "Minstance" as it could not get the class description for <class>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema/class definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_930004
|
Publication error. Publication service <servicename> with publishing subject <subject> received the event from target application <application>. It failed while converting event to "Minstance" as it could find property <property> in class <class>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_930005
|
Publication error. Publication service <servicename> with publishing subject <subject> received the event from target application <application>. It failed while converting event to "Minstance" as property <property> of class <class> has invalid value <value>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_930006
|
Publication error. Publication service <servicename> with publishing subject <subject> received the event from target application <application>. It failed while converting event to "Minstance" attribute <attribute> of class <class> is missing. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema definitions are present in the repository. For details, see the User’s Guide..
|
AEADCOM_930007
|
Publication error. Publication service <servicename> with publication subject <subject> received event from target application but could not create the business document <document>. The target application details are <application>, the Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema definition for the MbusinessDocument maps properly to the event received from the target application. For details, see the User’s Guide.
|
AEADCOM_930008
|
Publication error. Publication service <servicename> with publication subject <subject> received SDK Exception <exception> while converting the event received from target application to BusinessDocument. The exception occurred while setting the attribute <attribute> with value of <value> for Business Document <document>. The target application details are <application>, the Repository URL is <repoURL> and Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the publication service and check that the schema definition for the MbusinessDocument maps properly to the event received from the target application. For details, see the User’s Guide.
|
AEADCOM_930009
|
Publication error. Publication service <servicename> with publication subject <subject> received an event from the target application but encountered error <error> in pre-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>. The target application details are <application>.
|
errorRole
|
Adapter
|
Make sure that the parameters passed to UserExit are valid and the User Exit is invokable by the adapter.
|
AEADCOM_930010
|
Publication error. Publication service <servicename> with publication subject <subject> received error <error> in RvRPC user exit 2-way invocation. The User exit is <userexit>, the user exit endpoint details are <userexit> and the user exit parameters are <parameters>. The user exit timeout is <timeout>.
|
errorRole
|
Adapter
|
Please check the validity of User exit endpoint and the parameters passed to the user exit.
|
AEADCOM_930011
|
Publication error. Publication service <servicename> with publication subject <subject>, received timeout error in RvRPC user exit one-way invocation. The User exit is <userexit>, the user exit endpoint details are <endpoint> and the user exit parameters are <parameters>. The user exit timeout is <number> milliseconds.
|
errorRole
|
Adapter
|
Please check the validity of User exit endpoint and the parameters passed to the user exit.
|
AEADCOM_930012
|
Publication error. Publication service ,<servicename> with publication subject <subject> received error <error> in the SDK message level UserExit. The User exit names are <userexit> and the User exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Make sure the UserExit parameters are valid and the user exit is invokable from SDK.
|
AEADCOM_930013
|
Publication error. Publication service <servicename> with publication subject <subject> received error <error> in post-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Make sure that the parameters passed to UserExit are valid and the User Exit is invokable by the adapter.
|
AEADCOM_930014
|
Publication error. Publication service <servicename> with publication subject <subject> received error while sending event over the wire. The Publish endpoint details are <details>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the publish endpoint for this service.For details, see the User’s Guide.
|
AE_ADCOM_PUB_15
|
Publication error: Error occurred while trying to publish. The exception is: <exception>.
|
errorRole
|
Adapter
|
Restart the process.
|
AEADCOM_940001
|
Request Response error. Request Response service <service name> listening on <subject> received unexpected null data in incoming request. Expects event <events>. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above RequestResponse service. For details, see the User’s Guide.
|
AEADCOM_940002
|
Request Response error. RequestResponse service <servicename> with RequestResponse subject <subject> received an event from the target application but encountered error <error> in pre-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>. The target application details are <application>.
|
errorRole
|
Adapter
|
Please make sure that the parameters passed to User Exit are valid and the User Exit is invokable by the adapter.
|
AEADCOM_940003
|
Request Response error. Request Response service <servicename> with publication subject <subject> received error <error> in the SDK message level User Exit. The User exit names are <userexit> and the User exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Please make sure the User Exit parameters are valid and the User Exit is invokable from SDK.
|
AEADCOM_940005
|
Request Response error. Request Response service <service name> failed to deserialize the received MServerRequest to MInstance: Received event on subject <subject>, event = <event>, SDK exception = <exception>. The Repository URL is <repoURL> and the Configuration URL is <configURL>
|
errorRole
|
Adapter
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request Response service. For details, see the User’s Guide.
|
AEADCOM_940006
|
Request Response error. Error in incoming data for RPC service: <servicename> on subject: <subject>. Not able to map incoming data to the business object schema: <schema> configured at design time. Invalid data type: <Type> for attribute: <attribute>
|
errorRole
|
Adapter
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request Response service. For details, see the User’s Guide.
|
AEADCOM_940007
|
Request Response error. Error in incoming data for RPC service: <servicename> on subject: <subject>. Missing mandatory parameter <parameter> for RPC input class <class>
|
errorRole
|
Adapter
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request Response service. For details, see the User’s Guide.
|
AEADCOM_940008
|
Request Response error. Connection error in invocation of RPC service:<servicename> on subject:<subject>. Connection parameters are parameter_name: <name> parameter_value:<value>
|
errorRole
|
Adapter
|
Check if the end application is up and running. Also verify the connection parameters that are specified in the repository.
|
AEADCOM_940009
|
Request Response error. Request Response service <servicename> listening on subject <subject> failed due to target application invocation error <error>. Target application is <application> and inbound event is <event>. <Where applicable add Target application specific commands and parameters are <parameters>
|
errorRole
|
Adapter
|
Please check the target application command and the parameters and make sure they are valid.
|
AEADCOM_940010
|
Request Response error. Request Response service <servicename> listening on subject <subject> failed to create Reply Business Object Error <error>.
|
errorRole
|
Adapter
|
Please check the target application command and the parameters and make sure they are valid.
|
AEADCOM_940011
|
Request Response error. Request Response service <servicename> listening on subject <subject> receive a time out error. Time out period in configuration file is <timeout>.
|
errorRole
|
Adapter
|
Please check the target application command and the parameters and make sure they are valid.
|
AEADCOM_940012
|
Request Response error. Request Response service <service name> listening on subject <subject> receive an error while sending Data on Reply Address <address>. Error Message <message>
|
errorRole
|
Adapter
|
Please check whether the request client is alive.
|
AEADCOM_940013
|
Request Response error. Request Response service <servicename> with subject <subject> received error <error> in post-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Please make sure that the parameters passed to User Exit are valid and the User Exit is invokable by the adapter.
|
AEADCOM_950001
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject as <subject> received event from target application <application>. It failed while converting event to Request, as it could not get the class description for <class>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the Request Response Invocation Service and check that the schema/class definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_950002
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject as <subject> received event from target application <application>. It failed while converting event to Request, as it could not get the Operation description <description> in the class <class>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the Request Response Invocation Service and check that the schema/class definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_950003
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject as <subject> received event from target application <application>. It failed while converting event to Request. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the Request Response Invocation Service and check that the schema/class definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_950004
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject as <subject> received event from target application <application>. It failed while converting event to Request, as it cannot set Operation Parameter % 4 <parameter>. Repository URL is <repoURL> and the Configuration URL is <configURL>.
|
errorRole
|
Adapter
|
Please verify the configuration of the Request Response Invocation Service and check that the schema/class definitions are present in the repository. For details, see the User’s Guide.
|
AEADCOM_950005
|
Request Response Invocation error. Request Response Invocation service <servicename> with Request Response Invocation subject <subject> received an event from the target application but encountered error <error> in pre-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>. The target application details are <application>.
|
errorRole
|
Adapter
|
Please make sure that the parameters passed to User Exit are valid and the User Exit is invokable by the adapter.
|
AEADCOM_950006
|
Request Response Invocation error. Request Response Invocation <servicename> with subject <subject> received error <error> in the SDK message level User Exit. The User exit names are <userexit> and the User exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Make sure the User Exit parameters are valid and the user exit is invokable from SDK.
|
AEADCOM_950007
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received error while sending event over the wire. The Request Response Invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service. For details, see the User’s Guide.
|
AEADCOM_950008
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received error while requesting event over the wire. The Request Response invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service. For details, see the User’s Guide.
|
AEADCOM_950009
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received error while requesting event over the wire. The Request Response Invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service. For details, see the User’s Guide.
|
AEADCOM_950010
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received null reply while requesting event over the wire. The Request Response Invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check the target application, if it is running or not. Please check the configuration of request response Invocation service.
|
AEADCOM_950011
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received timeout error while requesting event over the wire. The Request Response Invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service. For details, see the User’s Guide.
|
AEADCOM_950012
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject> received error while processing reply message. The Request Response Invocation endpoint details are <endpoint>
|
errorRole
|
Adapter
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service. For details, see the User’s Guide.
|
AEADCOM_950013
|
Request Response Invocation error. Request Response Invocation service <servicename> with subject <subject>, received error <error> in post-processing user exit invocation. The User exit is <userexit> and the user exit parameters are <parameters>.
|
errorRole
|
Adapter
|
Please make sure that the parameters passed to User Exit are valid and the User Exit is invokable by the adapter.
|
AE_ADCOM_SYSTEM_100
|
System error. Unknown exception encountered.
|
errorRole
|
Adapter
|
Restart the adapter.
|
AE_ADCOM_SYSTEM_101
|
System error. Invalid interface pointer.
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AE_ADCOM_SYSTEM_102
|
System error. Bad service request.
|
errorRole
|
Adapter
|
Problem with the Interceptor service. Please reinstall it.
|
AE_ADCOM_SYSTEM_103
|
System error. Advisory: <advisory> : <message>.
|
errorRole
|
Adapter
|
Check the actual error message for details.
|
AE_ADCOM_SYSTEM_104
|
System error. Advisory: <advisory> : <message>.
|
errorRole
|
Adapter
|
Check the actual error message for details.
|
AE_ADCOM_SYSTEM_105
|
MException thrown: <exception>.
|
errorRole
|
Adapter
|
Check error description in the event viewer for more information.
|
AE_ADCOM_SYSTEM_106
|
Unknown exception thrown by implementation of coclass <class> (interface <Interface>, method <method>).
|
errorRole
|
Adapter
|
Make sure that the registered DLL is in its physical location.
|
AE_ADCOM_SYSTEM_107
|
Cannot create event dispatching thread.
|
errorRole
|
Adapter
|
Problem with creating the thread. Restart the process and system (if possible).
|
AE_ADCOM_SYSTEM_108
|
<description>
|
errorRole
|
Adapter
|
Check for the previous error messages.
|
AE_ADCOM_SYSTEM_110
|
RPC server Unavailable. Adapter lost COM server Connection.
|
errorRole
|
System
|
RPC server unavailable. Check whether the COM server process is running.
|
AE_ADCOM_SYSTEM_111
|
COM server Reconnection attempts Failed. Suspending Subscriber Service: <servicename> with subject <subject>.
|
infoRole
|
System
|
RPC server unavailable. Check whether the COM server process is running.
|
AE_ADCOM_SYSTEM_112
|
Successfully Reconnected to COM server. Activating Subscriber Service: <servicename> with subject <subject>.
|
infoRole
|
System
|
Indicates normal adapter information. No action necessary
|
AE_ADCOM_SYSTEM_113
|
COM server Reconnection attempts Failed. Suspending RPC Service: <servicename> with subject <subject>.
|
infoRole
|
System
|
RPC server unavailable. Check whether the COM server process is running.
|
AE_ADCOM_SYSTEM_114
|
Successfully Reconnected to COM server. Activating RPC Service: <servicename> with subject <subject>.
|
infoRole
|
System
|
Indicates normal adapter information. No action necessary.
|
AEADCOM_990001
|
Shutdown error. Failed to deactivate the <name> timer. SDK exception = <exception>
|
errorRole
|
Adapter
|
Check for the SDK exception details.
|
AEADCOM_990002
|
Shutdown error. SDK cleanup exception = <exception>
|
errorRole
|
Adapter
|
Check for the SDK exception details.
|
AEADCOM_990003
|
Shutdown error. Failed to cleanup Hawk microagent. SDK exception = <exception>
|
errorRole
|
Adapter
|
Check for the SDK exception details.
|
AEADCOM_990004
|
Shutdown error. Failed to cleanup the threads: <error>
|
errorRole
|
Adapter
|
Restart adcomService.
|
AEADCOM_990005
|
Shutdown error. Error in disconnecting from <name> connection parameters <name>.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AE_ADCOM_SHUT_100
|
Shutdown error. Wait for TIBCOCOMService stop event failed.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AE_ADCOM_SHUT_101
|
Shutdown error. Call to SetEvent failed.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AE_ADCOM_SHUT_102
|
Shutdown error. Can’t deleteNTservice.
|
errorRole
|
Adapter
|
Deleting the service failed. Try deleting the service again.
|
AE_ADCOM_SHUT_103
|
Wait for TIBCOCOMService stop event failed.
|
errorRole
|
Adapter
|
Restart adcomService.
|
AE_ADCOM_SHUT_104
|
Adapter Termination Criteria is set to any service suspended: Terminating adapter service.
|
infoRole
|
Shutdown
|
RPC server Unavailable. Check whether the COM server process is running and restart the adapter.
|
AE_ADCOM_SHUT_105
|
All Adapter Services suspended: Terminating adapter service.
|
infoRole
|
Shutdown
|
RPC server Unavailable. Check whether the COM server process is running and restart the adapter.
|
AE_ADCOM_SHUT_106
|
Adapter reconnection attempt (<attempt number>) failed.
|
infoRole
|
Shutdown
|
RPC server Unavailable. Check whether the COM server process is running.
|
AE_ADCOM_SHUT_107
|
Adapter failed to reconnect. Terminating adapter service.
|
infoRole
|
Shutdown
|
RPC server Unavailable. Check whether the COM server process is running and restart the adapter.
|