Application fabric messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 1000 |
Service Started |
<service name> Service started on port <port>. |
Informational |
|
| 1001 |
Service Failed |
<service name> Service failed to start. |
Error |
|
Application messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 2000 |
File Not Exist |
Failed to open <file name> file: <task name>. |
Error |
- Verify that the file exists and identifies the task.
- Verify the file is stored in the appropriate application directory.
|
| 2001 |
Var Not Set |
Application <application name> not set. |
Error |
- Open the application XML file in a text editor, enter a value for the application name, increase the version number, repackage the application, and redeploy the package.
|
| 2002 |
Task Reference Not Exist |
Process Flow: <process flow name> references task <task name> that does not exist. |
Error |
- Verify the task name specified in the process flow and the task file name in the application definition file match exactly.
- Verify the task exists.
|
| 2003 |
Process Reference Not Exist |
Process Flow: <process flow name> references sub-process <subprocess name> that does not exist. |
Error |
- Verify the specified sub-process flow name and the desired process flow name match exactly.
- Verify the specified sub-process flow exists. Verify the specified sub-process flow is located in the appropriate application directory
|
| 2004 |
Duplicate App Name |
Duplicate application name found: <application name>. |
Error |
- Open the second application XML file in a text editor, change the application name and increase the version number, repackage the application, and redeploy the package.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 2005 |
App Failed to Load |
App <application name> failed to load: <port>. |
Error |
- Verify that the correct application is specified.
- Verify the application exists.
|
| 2006 |
App Loaded |
App <application name> loaded. |
Informational |
|
| 2007 |
Duplicate Process Flow Definition |
Duplicate process flow definition <process flow name> found in <file name>. |
Error |
- Open one of the process flows in a text editor and change the process flow name. Open the application definition file in a text editor, add the process flow name, and increase the version number. Repackage the application and redeploy the package.
|
| 2008 |
Duplicate Task Definition |
Duplicate task definition <task name> found in <file name>. |
Error |
- Open one of the tasks in a text editor and change the task name. Open the task definition file in a text editor and add the task name. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 2009 |
Duplicate Component Task Definition |
Duplicate component/task definition <component/task name> found in <file name>. |
Error |
- Open one of the components or tasks in a text editor and change the task name. Open the task definition file in a text editor and add the task name. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 2010 |
Invalid Task |
Error |
<task name> <task or compoment> failed validation <file name> <reason> |
Refer to reason for the error and take appropriate steps. |
| 2012 |
Unsupported File Type In Support Files |
Inclusion of the <file type> in <file name> in the support-files list is deprecated. Use instead. |
Warning |
- Generate a supported file type. Open the application definition file in a text editor, change the unsupported file type to the supported file type, and increase the version number. Repackage the application and redeploy the package.
|
| 2013 |
Fabric Keeper Restart Error |
Error on fabric keeper Restart:fabric keeper is not installed,
Error on fabric keeper Restart:service is not installed, or
Error on fabric keeper Restart:<OS specific service startup errors> |
Error |
- If fabric keeper is not installed, reinstall fabric keeper.
- If the service is not installed, reinstall fabric keeper. For operating system specific service startup errors, refer to your operating system documentation.
For all other fabric keeper startup errors, contact Customer Support.
|
| 2014 |
Fabric Keeper Restart Status |
Status of fabric keeper restart: Stopping fabric keeper
Status of fabric keeper restart:fabric keeper not installed,
Status of fabric keeper restart:fabric keeper continue pending,
Status of fabric keeper restart:fabric keeper pause pending,
Status of fabric keeper restart:fabric keeper paused,
Status of fabric keeper restart:fabric keeper running,
Status of fabric keeper restart:fabric keeper start pending,
Status of fabric keeper restart:fabric keeper stop pending,
Status of fabric keeper restart:fabric keeper stopped,
Status of fabric keeper restart:fabric keeper in unknown state, or
Status of fabric keeper restart:Starting fabric keeper. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 2023 |
Fabric Keeper Upgrade Error |
Error on fabric keeper upgrade: <IP address> |
Error |
|
| 2100 |
Fabric App Extraction Failed |
Failed to extract fabric application: <application name>. |
Error |
- Repackage the application with fabric_pkg and redeploy.
- Contact Customer Support if the problem persists.
|
Process flow messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 3005 |
No State Named Start |
Process Flow: <process flow name> does not have a start state. |
Error |
- Open the process flow in a text editor and add a start state. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3006 |
State Named Finish |
Process Flow: <process flow name> includes a state named finish (illegal). |
Error |
- Open the process flow in a text editor and rename the finish state. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3007 |
Noncomplete Arc With Task Result |
Process Flow: <process flow name> has a transition <arc identifier> that includes a task-result where none is allowed. |
Error |
- Open the process flow in a text editor and correct the error. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3008 |
Process Failed to Load |
Process Flow: <process flow name> failed to load. |
Error |
- Verify that the correct process flow is specified.
- Verify the process flow exists.
|
| 3009 |
Process Already Loaded |
Process Flow: <process flow name> already loaded. |
Warning |
- Open one of the process flows in a text editor and change the process flow name. Open the application definition file in a text editor, add the process flow name, and increase the version number. Repackage the application, and redeploy the package.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 3010 |
Process Loaded |
Process Flow: <process flow name> loaded. |
Informational |
|
| 3011 |
Could Not Execute Nonexistent Process |
Could not execute process flow <process flow name> because it does not exist. |
Error |
- Verify that the correct process flow is specified.
- Verify the process flow exists. Verify the process flow is stored in the appropriate application directory.
|
| 3013 |
Process Name With Illegal Characters |
Process Flow: <process flow name> has illegal characters in a process name or state name <illegal field name>. |
Error |
- Open the process flow in a text editor and change the process flow name or the state name. Use only alphanumeric characters (upper or lower case), hyphens (-), and underscores (_). Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 3015 |
Cannot Resume Process Flow No Service |
Process Flow: Cannot resume process flow because no request services are available. |
Error |
- Verify your network connections.
|
| 3016 |
Cannot Resume Process Flow Cannot Update Service |
Process Flow: Cannot resume process flow because cannot synchronize state with request. |
Error |
- Verify your network connections.
|
| 3017 |
State Not Exist |
Process Flow: <process flow name> State: <state name> has an arc that references an undeclared state: <state name>. |
Error |
- Verify the state name specified in the arc and the desired state name are identical.
- Verify the state exists.
|
| 3018 |
Process Service Busy |
The Process Service is busy. |
Warning |
- Consider increasing the number of workers in your fabric. Refer to the Installation instructions for more information.
|
| 3019 |
Invalid Request |
Invalid request received: <data>. |
Error |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 3020 |
Access Denied to Process Flow |
Access denied to <user name> for <application name.process flow name> |
Error |
- Verify that the user should not have access to the process flow. If the user should have access to the process flow, use fabric_user to update the user.cfg file and update the group.cfg file.
|
| 3021 |
Process and or State Does Not Exist |
Process and or state <process name and or state name> does not exist |
Error |
- Verify that the process flow and/or state name is correct.
- Verify that the process flow and/or state is stored in the appropriate application directory.
|
| 3022 |
Failed to Get Task Service |
Could not get task service for <task name>. |
Error |
- Verify the process flow and/or state name is correct.
- Verify the workers are operating properly.
|
| 3023 |
Unexpected Request Service Data |
Received unexpected request service data: <data>. |
Error |
|
| 3024 |
Startup Failure |
<module> failed to start. |
Error |
- Verify that the TCP stack on the worker is operating properly.
- Contact Customer Support for assistance.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 3025 |
Unexpected Request Service Disconnect |
Received unexpected request service disconnect. |
Error |
- Verify your network connections.
- Verify hardware functionality.
- Verify client functionality.
|
| 3026 |
Duplicate State |
Process Flow: <process flow name> State: <state name> has a duplicate definition. |
Error |
- Open the process flow in a text editor, change one of the state names, and save the file. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3027 |
Client Disconnected During Phase |
Client disconnected during request <setup, waiting-for-start, or processing> phase. |
Error |
- Verify your network connections.
- Verify hardware functionality.
- Verify client functionality.
|
| 3028 |
Unexpected Task Service Data |
Received unexpected task service data: <data>. |
Error |
|
| 3029 |
Task Service Disconnect During Commit |
Received unexpected task service disconnect during FAM commit. |
Error |
- Verify your network connections.
- Verify hardware functionality.
- Verify client functionality.
|
| 3030 |
Task Service Commit Error |
Received FAM commit failure from task service. |
Error |
- Verify your network connections.
- Verify hardware functionality.
- Verify client functionality.
|
| 3031 |
Duplicate Arc |
Process Flow: <process flow name> State: <state name> has a arc that is already defined for status: <status> and result: <result>. |
Error |
- Open the process flow in a text editor, change one of the arcs, and save the file. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3032 |
Unset Status And Result In Arc |
Process Flow: <process flow name> State: <state name> has an arc with result and status not set. |
Error |
- Open the process flow in a text editor, add a result and status to the arc, and save the file. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 3033 |
Affinity Task Reference Not Exist |
Process Flow: <process flow name> references affinity-task (<task name>) that does not exist. |
Error |
- Verify the affinity-task exists.
- Verify the affinity-task name in the process flow is correct.
|
| 3034 |
Component Reference Not Exist |
Process Flow: <process flow name> references component (<component name>) that does not exist. |
Error |
- Verify the component exists.
- Verify the component name in the process flow is correct.
|
| 3035 |
Method Reference Not Exist |
Process Flow: <process flow name> references method (<method name>) that does not exist. |
Error |
- Verify the method exists.
- Verify the method name in the process flow is correct.
|
| 3036 |
Both Affinity and Sub-process Flow Defined In State |
Process Flow: <process flow name> State: <state name> can not contain both affinity-task(<affinity task name>) and subflow(<sub-process flow name>) |
Error |
- Affinity tasks can only be defined for process flow states that call a task.
|
Task messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4000 |
Task Loaded |
<IP address> Task loaded: FileMethod <method name>. |
Informational |
|
| 4001 |
Task Failed to Load |
<IP address> Task failed to load: File <file name> Method <method name> because: <reason>. |
Error |
- Verify that the task files are stored in the appropriate application directory.
- Verify the *.dll, *.so, *.class, or *.jar file compiled correctly.
|
| 4002 |
Task Already Loaded |
<IP address> Task failed to load because task name already loaded: File <file name> Method <method name>. |
Warning |
- Open one of the tasks in a text editor and change the task name. Open the task definition file in a text editor and add the task name. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 4003 |
JVM Not Loaded |
Java Virtual Machine failed to load <reason>. |
Error |
- Verify that the Java Virtual Machine is installed and functioning correctly.
|
| 4004 |
Failed to Get JVN Environment |
JNI: Failed to get JVM environment: <reason> |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4005 |
Task Failed to Execute |
Task <task name> failed to execute: <reason>. |
Error |
- Verify the worker has enough memory to complete the task.
|
| 4010 |
Limited Task Without Parameters |
<IP address> Task failed to load due to missing limited task parameters. |
Error |
- Open the task definition file in a text editor and add the missing limited task parameters. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 4011 |
Invalid Limited Task Parameters |
<IP address> Task failed to load due to invalid limited task parameters. |
Error |
- Open the task definition file in a text editor and correct the limited task parameters. The min and max parameters must be greater than zero. The percentage parameter must be between 1 and 100. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 4012 |
Limited Task Validated |
<IP address> Limited Task validated: FileMethod <method name>. |
Informational |
|
| 4013 |
Limited Task Started |
<IP address> Limited Task started: File <file name> Method <method name>. |
Informational |
|
| 4014 |
Limited Task Stopped |
<IP address> Limited Task stopped: File <file name> Method <method name>. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4015 |
Limited Task Failed to Start |
<IP address> Limited Task failed to start: File <file name> Method<method name> because: <reason>. |
Error |
- Verify the task files are stored in the appropriate application directory.
|
| 4016 |
Limited Task Failed to Stop |
<IP address> Limited Task failed to stop: File <file name> Method <method name> because: <reason>. |
Error |
- Verify that the limited task code does not contain blocking forloop structures preventing shutdown. To shutdown the limited task you must send an administrative shutdown command or reboot the worker.
|
| 4017 |
Task Implementation Not Supported |
Implementation type: <implementation> is not supported. |
Error |
- Recompile the task in .NET, Java, or 'C' (CentOS, RHEL, SUSE, or Windows). Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package
|
| 4018 |
Task Module Not Exist |
Task Module: <file name> failed to load. |
Error |
- Verify that the task files are stored in the appropriate application directory.
- Verify the *.dll, *.so, *.class, or *.jar file compiled correctly.
|
| 4019 |
Task Method Not Exist |
Task Module: <file name> does not contain referenced method <method name>. |
Error |
- Verify specified task is listed in the application XML file.
- Verify the specified method exists.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4020 |
Failed Getting Java Request Handle |
Task Service: failed to get Java-based request handle. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| 4021 |
Failed Marshalling Java Request |
Task Service: failed to marshall Java-based task request. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| 4022 |
Failed Setting Java Request |
Task Service: failed to set Java-based request into JVM. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| 4023 |
Failed Unmarshalling Java Request |
Task Service: Failed to unmarshall Java-based task. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| 4024 |
Failed to Free Java Request Memory |
Task Service: failed to free Java-based task request memory in JVM. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4025 |
Task Not in Pool |
<task name> Task not in pool: File: <module> Method: <method name>. |
Informational |
|
| 4026 |
Active Java Classpath |
Java Virtual Machine Classpath: <classpath>. |
Informational |
|
| 4027 |
Task Service Busy |
Task Service is busy. |
Warning |
- Consider increasing the number of workers in your fabric. Refer to the Installation instructions for more information.
|
| 4028 |
Startup Failure |
<task name> failed to start. |
Error |
- Verify that the TCP stack on the worker is operating properly.
- Contact Customer Support if this message continues.
|
| 4029 |
Background Task Without Parameters |
<IP address> Task failed to load due to missing background task parameters. |
Error |
- Open the task definition file in a text editor and add the missing background task parameters. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4030 |
Background Task Too Many Parameters |
<IP address> Task failed to load due to too many background task parameters. |
Error |
- Open the task definition file in a text editor and remove the duplicate parameters. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 4031 |
Invalid Background Task Parameters |
<IP address> Task failed to load due to invalid background task parameters. |
Error |
- Open the task definition file in a text editor and correct the background task parameters. Open the application definition file in a text editor, increase the version number, repackage the application, and redeploy the package.
|
| 4032 |
Background Task Started |
<IP address> Background task started: File <file name> Method: <method name>. |
Informational |
|
| 4033 |
Background Task Stopped |
<IP address> Background Task stopped: File: <file name> Method: <method name>. |
Informational |
|
| 4034 |
Background Task Failed to Start |
<IP address> Background task failed to start: File <file name> Method: <method name> because: <reason>. |
Error |
- Verify the task files are stored in the appropriate application directory.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4035 |
Background Task Failed to Stop |
<IP address> Background task failed to stop: File: <file name> Method: <method name> because: <reason>. |
Error |
- Verify that the background task code does not contain blocking or loop structures preventing shutdown. To shutdown the background task you must send an administrative shutdown command or reboot the worker.
|
| 4036 |
Background Task Execute Failed |
<IP address> Background task failed to execute: File <file name> Method: <method name> because: <reason>. |
Error |
- Verify the worker has enough memory to complete the task.
|
| 4037 |
Exclusive Task Loaded |
<IP address> Exclusive task loaded: File <file name> Method: <method name>. |
Informational |
|
| 4038 |
Exclusive Task Failed to Load |
<IP address> Exclusive task failed to load: File: <file name> Method: <method name> because: <reason>. |
Error |
- Verify that the task files are stored in the appropriate application directory.
- Verify the *.dll, *.so, *.class, or *.jar file compiled correctly.
|
| 4039 |
Task Service LD_LIBRARY_PATH |
<task service name> has LD_LIBRARY_PATH: <path> |
Informational |
|
| 4040 |
Duplicate Methods Defined |
Duplicate method definition: File: <module name> Component: <component name> Method/Alias: <method or alias name>. |
Error |
- Open of the task definition file in a text editor and change the component name. Open the application definition file in a text editor, add the component name, and increase the version number. Repackage the application and redeploy the package.
|
| 4041 |
Affinity Task Not In Pool |
<task name> Affinity-Task no in pool. |
Informational |
|
Task manager messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4500 |
Submitted Start |
Submitted start command to <service name>. |
Informational |
|
| 4501 |
Submitted Stop |
Submitted stop command to <service name>. |
Informational |
|
| 4502 |
Failed to Submit Start |
Error received while submitting start command to <service name> : <error message>. |
Error |
- Verify the service is installed in the application directory.
- Contact Customer Support if this message continues.
|
| 4503 |
Failed to Submit Stop |
Error received while submitting stop command to <service name> : <error message>. |
Error |
- Verify that the application does not contain a blocking or looping structure preventing shutdown.
- Use the fabric_ctl kill command to force the application fabric services on this worker to shutdown.
|
| 4504 |
Done Submitting Start Commands |
Done submitting start commands to application services. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4505 |
Done Subnitting Stop Commnads |
Done submitting stop commands to application services. |
Informational |
|
| 4506 |
Failed to Copy Task Service |
Failed to copy <service name> to <path>. |
Error |
- Verify the user running the service has permission to copy files from FABRIC_HOME to a directory under FABRICHOME/apps.
|
| 4507 |
Service Down |
Service <service name> unexpectedly down. |
Error |
|
| 4508 |
Region Publisher Failed to Start |
Region publisher failed to start. |
Error |
|
| 4509 |
Failed to Load App Catalog |
Failed to load app catalog. |
Error |
- Verify the apps directory permissions.
|
JNI messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 4900 |
Java Exception Thrown |
Java exception thrown: <exception>. |
Error |
- Verify the task code functionality.
|
| 4901 |
Java Method Not Exist |
Class: <file name> does not contain referenced method <method name> Exception: <exception description>. |
Error |
- Verify the specified method exists.
|
| 4902 |
Java Class Not Found |
Class: <file name> not found in class path: Exception: <exception description>. |
Error |
- Verify the file is included in the Java class path.
|
| 4903 |
Failed to Get JVM Environment |
JNI: failed to get JVM environment: <reason>. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
| 4904 |
Failed to Get Method |
Failed to get java method <method name>. |
Error |
- Verify your Java environment settings.
- Contact Customer Support if the problem persists.
|
Request messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 5000 |
Request Returned Failure Before Execution |
Request returned failure before execution. |
Error |
- Verify network connections.
- Verify fabric TPS.
|
| 5001 |
Missing SSL Certificate File |
Request service is configured to enable SSL, but the SSL certificate file is missing. |
Error |
|
| 5002 |
Request Saved for Recovery |
Unable to return request ID <request identifier> to client for <application name> <process flow name>. Saved to recovery service. |
Warning |
- Use the recover process function to retrieve the process state.
|
| 5003 |
Request Could Not be Saved to Recovery |
Unable to return request to client and save to recover service may not have succeeded. |
Error |
- Verify network connections.
|
| 5004 |
Request Service Busy |
Request service is busy. |
Warning |
- Consider increasing the number of request handlers in your fabric. Refer to the configuration files and worker services for more information.
- Consider increasing the number of workers in your fabric. Refer to the Installation instructions for more information.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 5005 |
Invalid Request |
Invalid request received: <data>. |
Error |
|
| 5006 |
Access Denied |
<request service>: invalid <user name/password>. |
Error |
- Verify the user name and password are valid.
- Verify the user name and password are included in the request.
- Verify the user is a member of an authorized security group.
|
| 5007 |
Unexpected Client Data |
Received unexpected client data:<data>. |
Error |
|
| 5008 |
Failed to Get Process Service |
Could not get the process service connection during <setup, start, or processing> phase for <application name.process flow name>. |
Error |
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 5010 |
Failed to Get Process Service ACK |
Failed to receive an ack from the process service. |
Error |
- Verify network connections.
|
| 5011 |
Failed to Get Final Client ACK |
Failed to receive final ack from the client. |
Error |
- Verify network connections.
|
| 5012 |
Lost Process Service Connection |
Lost the connection to the process service. |
Error |
- Verify network connections.
|
| 5013 |
Startup Failure |
<service, process, or thread> failed to start. |
Error |
|
| 5014 |
Failed to Get New Process Service |
Could not get new process service to continue <process flow name>. |
Error |
- Verify network connections.
- Verify fabric TPS.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 5015 |
Error Waiting for Process Service Setup |
Error waiting for the process service setup for <process flow name>. Reason: <reason>. |
Error |
- Verify network connections.
- Verify application fabric TPS.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| 5016 |
Waiting for Client Start |
Error waiting for client start for <process flow name>. Reason: <reason>. |
Error |
- Verify network connections.
- Verify fabric TPS.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| 5017 |
Error Waiting for Process Start ACK |
Error waiting for process service start ack for <process flow name>. Reason: <reason>. |
Error |
- Verify network connections.
- Verify fabric TPS.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| 5018 |
Error During Request Processing |
Error during processing for <process flow name>. Reason: <reason>. |
Error |
- Verify network connections.
- Verify fabric TPS.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
Restart system service messages
| Code |
Message |
Definition |
Type |
Suggest Solution |
| 6013 |
Fabric System Service Restart Error |
Error on fabric_system_service restart: <IP address>. |
Error |
|
| 6014 |
Fabric System Service Restart Status |
Status of fabric_system_service restart: <IP address>. |
Informational |
|
| 6015 |
Fabric System Service Upgrade Error |
Error on fabric_system_service upgrade: <IP address>. |
Error |
|
Service messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 7000 |
Service Started |
<service name> Service started on port <port>. |
Informational |
|
| 7001 |
Service Failed |
<service name> Service failed to start. |
Error |
|
| 7002 |
App Failed to Load |
App <application name> failed to load: <port>. |
Error |
- Verify the correct application is specified.
- Verify the application exists.
|
| 7003 |
App Loaded |
App <application name> loaded. |
Informational |
|
| 7004 |
Fabric Keeper Not Running |
Fabric keeper is down. Fabric attempting fabric keeper restart and shutting self down. |
Error |
- If you manually started the fabric worker manager before starting fabric keeper, the fabric worker manager automatically starts fabric keeper.
- If you did not manually start the fabric worker manager before starting fabric keeper, contact Customer Support.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 7005 |
Fabric Keeper Failed to Restart |
The fabric failed to restart fabric keeper. |
Error |
|
| 7006 |
Invalid Request |
Invalid request received: <data>. |
Error |
|
| 7100 |
Restart Timeout |
Restart timeout occurred:<IP address>. |
Error |
- Verify hardware functionality.
- Verify software functionality.
|
| 7101 |
Reboot Timeout |
Reboot timeout occurred:<IP address>. |
Error |
- Verify hardware functionality.
- Verify software functionality.
|
| 7102 |
Deploy Failed |
Failed to deploy file <file name>. |
Error |
- Verify network connections.
|
| 7103 |
Copy to Upload Failed |
Failed to copy file <application name> to upload directory for deployment. |
Error |
- Verify the correct file is specified for deployment.
- Verify network connections.
|
| 7104 |
License Error |
License Key Error: license key is expired,
License Key Error: failed to load license file,
License Key Error: license key is invalid, or
License Key Error: Number of workers (number of workers) exceeds license (number allowed), shutting down now. |
Error |
- If the license key expired, contact your Appistry Sales representative for a new license key.
- If the license key failed to load, redeploy the license key. If the problem persists, contact Customer Support.
- If the license key is invalid, verify the correct license key was deployed. If the problem persists, contact Customer Support.
- If the number of workers in the application fabric exceeds the number of workers allowed, contact your Appistry Sales representative.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 7105 |
Fabric Keeper Restart |
Restarting fabric keeper. |
Informational |
|
| 7106 |
Erasing Master Boot Record |
Erasing the master boot record. |
Informational |
|
| 7107 |
Rebooting Worker Machine |
Rebooting worker machine. |
Informational |
|
| 7108 |
Spreading File |
Spreading file: |
Informational |
|
| 7109 |
Spreading File Error |
Error spreading file: |
Error |
- Verify network connections.
- Redeploy the fabric file.
- Contact Customer Support if the problem persists.
|
| 7110 |
Fabric Keeper Operations |
Fabric keeper services shutdown,
Fabric keeper starting,
Exchanging manifests with leader:<IP address> <port>,
Promoted to leader,
Demoted from leader,
Conceding election for leader,
Nominating self for leader, or
Decided to promote. |
Informational |
|
| 7111 |
File Deployment Error |
Failed to copy file from download directory,
Failed to remove file from download directory. |
Error |
|
| 7112 |
MFTP File Spreading |
MFTP File Spread:failed to copy file from download directory,
MFTP File Spread:Subscribe failed:transfer aborted due to timeout, or
MFTP File Spread:Subscribe failed:transfer cancelled. |
Error |
|
| 7113 |
Manifest Exchange |
Manifest exchange:responding to <IP address> <port>. |
Informational |
|
| 7114 |
No System Service Available |
No system service available. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 7115 |
Fabric System Service Restart |
Restarting Fabric System Service. |
Informational |
|
| 7116 |
Fabric Members OS Out of Sync |
WorkerOS <operating system> is out of sync with worker
<IP address> OS <operating system>. |
Informational |
|
| 7117 |
Erase Master Boot Record Failed |
Failed to erase master boot record. |
Error |
- Verify network connections.
- Verify the master boot record exists.
|
| 7118 |
Reboot Worker Machine Failed |
Failed to reboot worker machine. |
Error |
- Verify network connections.
|
| 7119 |
Unknown System Command |
Invalid system command received <message>. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 7120 |
Shutdown Worker Manager |
Shutting down worker manager for <reason>. |
Informational |
|
| 7121 |
IP Address Invalid |
Failed to bind to an adapter with a valid IP address, received: <IP address>. |
Error |
- The worker automatically attempts to obtain a valid IP address. If this continues, reboot the worker.
|
| 7122 |
IP Address Valid |
Bound to adapter with MAC Address <MAC address> using IP Address <IP address>. |
Informational |
|
| 7123 |
Fabric File Extraction Failed |
Failed to extract : <file name>. Error: <reason>. |
Error |
- Repackage the file, and redeploy.
- Contact Customer Support if the problem persists.
|
| 7124 |
Transferring File |
Transfering file: <file name>, version <file version>. |
Informational |
|
| 7125 |
File Transfer Error |
Transfer failed for file: <file name>, error: <reason>. |
Error |
- Verify network connections.
- Redeploy the fabric file.
- Contact Customer Support if the problem persists.
|
Region services messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 8000 |
Region Services Starting |
Location: <member IP address> Region: <region ID> Services starting. |
Informational |
|
| 8001 |
Region Services Shutting Down |
Location: <member IP address> Region: <region ID> Services shutting down. |
Informationsl |
|
| 8002 |
Region Services Shut Down |
Location: <member IP address> Region: <region ID> Services now shut down. |
Informational |
|
| 8003 |
Member Leaving Region |
Location: <member IP address> Region: <region ID> Member leaving region. |
Informational |
|
| 8004 |
Disbanding Region Member |
Location: <member IP address> Region: <region ID> Disbanding region member. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 8005 |
Promoting to Region Leader |
Location: <member IP address> Region: <region ID> Promoting To region leader. |
Informational |
|
| 8006 |
Demoting Region Leader |
Location: <member IP address> Region: <region ID> Demoting region leader. |
Informational |
|
| 8007 |
Demoting From Senior Region Leader |
Location: <member IP address> Region Leader Region: Demoting from senior region leader. |
Informational |
|
| 8008 |
Creating Senior Region Leader |
Location: <member IP address> Region Leader Region: Creating Senior Region Leader for leader region. |
Informational |
|
| 8009 |
Promoting to Senior Region Leader |
Location: <member IP address> Region Leader Region: Promoting To Senior Region Leader. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 8010 |
Creating Region Leader |
Location: <member IP address> Region: Creating Region Leader for region. |
Informational |
|
| 8011 |
Region Heartbeat Size |
Location: <member IP address> <region ID>: <region location> Heartbeat size: <number of regions>. |
Informational |
|
| 8012 |
Splitting on Size |
Location: <member IP address> <region ID>: <region location> Splitting on size: <region member count>. |
Informational |
|
| 8013 |
Disbanding on Size |
Location: <member IP address> <region ID>: <region location> Disbanding on size: <region member count>. |
Informational |
|
| 8014 |
Region Leader Startup Failed |
Location: <member IP address> <region ID>: <region location> Region Leader Startup Failed: <region member count>. |
Error |
- Verify hardware functionality.
- Verify Appistry EAF installation.
|
Volunteer services messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 9000 |
TCP Connection Manager Failed to Start |
TCP Connection Manager failed to start. |
Error |
- Verify software functionality.
|
| 9001 |
Fabric Connection Manager Failed to Start |
Fabric Connection Manager failed to start. |
Error |
|
Fabric worker manager messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 10000 |
Fabric Worker Manager Initialized |
Location: <Application Fabric member IP address> fabric worker manager: <region IP address> fabric worker manager initialized. |
Informational |
|
| 10001 |
Fabric Worker Manager OS Path |
Fabric worker manager OS path: <path>. |
Informational |
|
| 10002 |
Fabric Worker Manager OS LD Library Path |
Fabric worker manager OS ld_library_path: <path>. |
Informational |
|
| 10003 |
Fabric Worker Manager Home |
Fabric worker manager Home:<directory>. |
Informational |
|
| 10004 |
IPC Startup Failure |
IPC Server Failed to start: <reason>. |
Error |
- Re-send the fabric_ctl command.
- Contact Customer Support if this message continues.
|
| 10100 |
Pipe Creation Error |
Fabric System Service failed to start. Could not open named pipe. |
Error |
- Verify the user account fabricuser exists on the worker's operating system.
- Verify the directory /tmp exists.
|
Worker monitor messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 13000 |
Worker Lost |
Worker: <worker IP address> failed to respond. |
Error |
|
| 13001 |
Worker Found |
Worker: <worker IP address> now responding. |
Warning |
- Verify the worker should be connected to the fabric.
|
| 13002 |
Worker Monitor Failed to Start |
Worker monitor <worker IP address> failed to start. |
Error |
|
| 13003 |
Worker Monitor Scheduler Failed to Start |
Worker monitor (<worker IP address>) scheduler failed to start. |
Error |
|
FAM messages
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 14000 |
Service Started |
<service name> service started on ports <port> <port>. |
Informational |
|
| 14001 |
Startup Failure |
<service name> failed to start. |
Error |
|
| 14005 |
Service Stopped |
<service name> service stopped on port <port> <port>. |
Informational |
|
| 14006 |
Lost Quorum |
FAM was unable to acquire quorum: <space name>. |
Error |
- Verify network connections.
- Verify hardware functionality.
|
| 14007 |
Heal Leader Failure |
Leader failed to heal space <space name> message:Leader was unable to appoint a new peer
Leader failed to heal space <space name> message: Leader was unable to appoint a new buddy. |
Error |
- Verify network connections.
- Consider increasing the storage capacity of the workers in the fabric.
- Consider increasing the number of workers in the fabric. Refer to the Installation instructions for more information.
|
| 14008 |
Heal No Quorum |
Worker has no quorum to heal: mark space <space identifier> offline. |
Error |
- Verify network connections.
- Verify hardware functionality.
|
| 14009 |
Lost Peer |
Peer not found on heal for space: <space identifier>. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 14010 |
Heal Detected |
Heal condition detected by <IP address> for space: <space identifier>. |
Informational |
|
| 14011 |
No Leader |
Leader not found on heal for space: <space identifier>. |
Error |
- Verify network connections.
- Verify hardware functionality.
|
| 14012 |
Heal Leader Success |
Leader reported success in healing space: <space identifier>. |
Informational |
|
| 14013 |
Sync Complete |
Sync complete for space: <space identifier>. |
Informational |
|
| 14014 |
Shutdown Immediate |
service shutdown immediate on port <port>. |
Informational |
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 14015 |
Missed Ping |
Space monitor missed a ping from FAM member <IP address> for space: <space identifier>. |
Informational |
|
| 14016 |
Worker Found |
Space monitor detected a missing FAM member <IP address> for space: <space identifier>. |
Informational |
|
| 14017 |
Success |
FAM operation completed successfully. |
Informational |
|
| 14018 |
Generic FAM Error |
The FAM operation failed. |
Error |
- Use the get error code and get error message functions for more information.
|
| 14019 |
Library Init Failure |
The FAM API failed to initialize. |
Error |
- Verify software functionality.
- Verify hardware functionality.
|
| Code |
Message |
Definition |
Type |
Suggested Solution |
| 14020 |
No Service Response |
The FAM API did not receive a response from the FAM service. |
Error |
| |
