Platform Symphony Error Message Reference

Code Detail Scenario Action
S25003 This message will be triggered when retrieving an application that does not exist in the system. This message will be triggered when retrieving an application that does not exist in the system.
Please check if the application really exists in the system.
S25011 This message will be triggered when the session director process cannot create a new socket. Session director process cannot startup successfully due to the OS failure to create a new socket.
Make sure the session director host has enough resources to run a new process.
S25012 This message will be triggered when session director process cannot allocate memory for a new application. When a new application is registered, session director fails to allocate memory.
Check the memory usage on the session director host.
S25013 This message will be triggered when session director attempts to use a non- existing configuration key. This is an internal problem.
Please provide the complete error message to Platform Support for investigation.
S25014 This message will be triggered when session director attempts to use a non- existing session manager ID. This is an internal problem. It may occur when a session manager ID has already been removed from the system but session director is still trying to use it.
Please provide the complete error message to Platform Support for investigation.
S25015 This message will be triggered when a user is making a request for a non-existent application. The user is making a CLI request for a non-existent application. This could happen due to misspelling the application name in the command line
Please check the command line and make sure the application name provided is registered with Symphony.
The user application is attempting to connect to Symphony using an application name that has not been registered Please check the client application code and make sure the application name used was registered with Symphony.
S25016 This message will be triggered when session director fails to save data on disk. Session director process is running with the same permissions as the user that start-up the Symphony. This user does not have write access on the disk locations session director is trying to save data.
Please check the write permissions of the directory specified in the error message.
S25017 This message will be triggered when the user is trying to register an application profile with an invalid parameter. The application profile used to register an applications contains an invalid parameter
Please check the application profile and correct the parameter name specified in the error.
The application profile used to register an applications is missing a required parameter Please check the application profile and make sure the parameter specified in the error message is properly defined.
S25018 This message will be triggered when the session director receives a session manager resource but there is no session manager command specified in the application profile for this type of resource. In the session manager section of the application profiles there is a mismatch between the type of resources requested (resReq) and the OS types (osType) defined for the session manager command
Please make sure there is one osType section defined for every type of resources defined by resReq .
Session director receives a resource of a different type than the ones requested This is an internal error. Please provide the complete error message to Platform Support for help.
S25020 This message will be triggered when the user is attempting an operation that requires the application to be enabled. Some admin operations are only intended for enabled applications (for example: soamview sessions, soamview tasks).
Please enable the application and then try again.
S25022 This message will be triggered when the user is trying to register an application for a consumer that doesn't exist. When register an application, the consumer associated with the application does not exist.
Please check consumer ID for spelling errors or create a new consumer with the ID specified in the application profile.
S25023 This message will be triggered when the user is trying to register an application for a consumer but the same application is already registered for a different consumer. When re-register an application, the consumer specified in the new application profile is different than the consumer associated with the application already registered.
Please make sure the consumer ID in the application profile is the same with the consumer ID used when the application was initially registered.
S25024 This message will be triggered when the user is trying to unregister an application but the system failed to remove the persisted application profile. When unregistering an application, session director failed to remove the application profile from the persistent storage.
Please check whether the profiles directory is accessible.
S25025 This message will be triggered when session director cannot start a session manager process. Session director cannot start session manager using the parameters specified in the Application Profile (session manager section)
Please check if the session manager binary is properly installed and whether session director is using the right command to start session manager (see the session manager command on the error message).
S25026 This message will be triggered when session director is trying to delete a file. Session director fails to delete one of its working files.
Please check whether the file (specified in the error message) is accessible by the user specified.
S25027 The mandatory application name is missing in the application profile or is empty. Session director cannot register an application profile if the application name is not properly defined in the application profile
Please check the application name attribute in the consumer section of the application profile.
S25028 This message will be triggered when the user is trying to register an application with a name reserved by the system. Session director fails to register an application if the application name is reserved by the system.
Please change the application name and try again. The system reserved names are specified in the error message
S25029 This message will be triggered when the user is trying to register an application with a name that contains a special character. Session director fails to register an application if the application name contains special characters.
Please change the application name and try again. The special characters are specified in the error message
S25030 This message will be triggered when the session director fails to load an application profile from the persistent storage. An application profile has been modified in the persistent storage and has become invalid. Session director will disable the application.
Please correct the application profile and use soamreg CLI to update the application profile
S25032 This message will be triggered when the session director fails to allocate memory for its internal structures. While trying to process a request, session director cannot allocate memory.
Please check the memory usage on the host
S25033 This message will be triggered when session director is trying to move an application profile to a different location. When an application changes its state (from enabled to disabled or vice versa), session director fails to move the application profile from one location to another.
Please check whether the paths (specified in the error message) are accessible by the user specified.
S25034 This message will be triggered when session director cannot start a session manager process. When a Symphony client is requesting a session manager, an EGO operation takes too long.
Please check if there are enough resources available to run session manager.
S25035 This message will be triggered when session director cannot ping an session manager process. When there is a hardware failure session director will not be able to contact session manager.
Please check if the host specified is working and the network cable is properly plugged.
S25036 This message will be triggered when session director cannot ping an session manager process. When there is a hardware failure session director will not be able to contact session manager.
Please check if the host specified is working and the network cable is properly plugged.
S25037 This message will be triggered when the application is disabled, updated or unregistered while clients are connected to SD.

S25039 This message will be triggered when session director cannot ping an session manager process. When there is a hardware failure session director will not be able to contact session manager.
Please check if the host specified is working and the network cable is properly plugged.
S25042 This message will be triggered when the user is trying to register an application for a consumer that doesn't has leading '/'. When register an application, the consumer associated with the application does not has leading '/'.
Please check consumer ID for spelling errors.
S25043 This message will be triggered when the user specifies a value that is too long for a specified attribute. An attempt is being made to associate a value that is too long for a specific attribute.
Specify a shorter value as guided by the specific error message.
S25234 This message will be triggered when performing an administrative operation on an application that has been disabled. Administrative operation cannot proceed with a disabled application.
No action.
S25245 This message will be triggered when the user is trying to access an application while the application is locked by an admin operation (disable, enable, unregister). While an application is being disabled by one user, another user is trying to access the application. The second user will get the error message.
Please check the status of the application and try again when the application is enabled.
S25255 This message will be triggered when an administrative operation requires a running session manager but it is unavailable. An administrative operation cannot proceed since the session manager is unavailable.
Consider restarting the application.
An administrative operation cannot proceed since the session manager is not responsive. The session manager may be very busy with heavy workload. Wait until it is responsive. If it is not responsive for a long time, consider restarting the application.
An administrative operation cannot proceed since the session manager has not started. Restart the application and then try again.
An administrative operation cannot proceed since the session manager is in the process of starting up. Check that the session manager started and try again.
S25298 The repository server is not running. The SD failed to connect to the RS to retrieve package version information.
Restart the RS.
S25299 Could not connect to EGO to locate the RS. The SD failed to connect to the RS to retrieve package version information.
Restart EGO.
S25300 Could not locate the RS. The SD failed to connect to the RS to retrieve package version information.
Restart the RS.
S25301 Could not remove the appended packageVersion section from the application profile. The SD failed to update the packageVersion section.
Reregister the application.
S25302 Did not find the package in the repository. The package version information was not found in the repository.
Deploy the specified package.
S25303 Package update process failed to reregister all dependent application profiles . The dependent application profiles were not reregistered.
Use soamreg to manually register all application profiles dependent on the deployed package.
S25310 The client use the wrong name space to query the information from SOAM. The namespace used by the client SOAP message is invalid.
Query information from SOAM.
S25311 User attempt to set VERSION_NUM environment variable in application profile. User forget to remove VERSION_NUM from application profile when upgrade from Symphony 3.1 to Symphony 3.2.
Since VERSION_NUM is no longer used from Symphony 3.2, please ensure version attribute of SOAM element is set correctly and remove VERSION_NUM from osType section.
S25312 Application profile mismatch is detected when register or update application profile. User wants to use some feature that is only supported in new application profile format, but forgets to update format version in Profile element.
Update format version in Profile element.
User upgraded format version in Profile element, but does not upgrade the content of application profile to match the new format. Upgrade the content of application profile to match the format version declared in Profile element.
S25313 Application profile mismatch is detected when register or update application profile. User wants to use some feature that is only supported in new application profile format, but forgets to update format version in Profile element.
Update format version in Profile element.
User upgraded format version in Profile element, but does not upgrade the content of application profile to match the new format. Upgrade the content of application profile to match the format version declared in Profile element.
S25322 An admin operation is not supported by this version of the application. User wants to use an admin command that is only supported in newer versions of the Symphony application.
No action required.
S25343 An environment variable name is not valid. A valid environment variable name must have at least one character and must not contain '='.
Use a valid name.
S25344 Did not find the package in the repository. The package version information was not found in the repository.
Deploy the specified package.
S31001 This message will be triggered when session manager front end failed to create a new session object. Session manager front end failed to create a new session object. One of the possible reasons is system does not have enough memory.
The system is unhealthy, restart the system.
S31002 This message will be triggered when session manager front end found that session with this ID already exist. Session manager front end found that session with this ID already exists. This situation can be produced when second client connects to session manager with same connection ID. This is internal problem, you cannot fix by yourself.
The system is unhealthy, restart the system.
S31003 This message will be triggered when session manager front end failed to create a Connection Manager object. Session manager front end failed to create a Connection Manager object. Connection Manager object is critical for communication with client. One of the possible reasons is system does not have enough memory. session manager cannot continue to work after this error was happened.
The system is unhealthy, restart the system.
S31004 This message will be triggered when session manager front end failed to bind Session object to Connection. Session manager front end failed to open the Session object for the current Connection because the Session already opened on the same Connection. The client will be notified about the event.
Verify and correct the session ID used by client for session's opening.
S31005 This message currently unused. Reserved for future use.

S31006 This message will be triggered when session manager front end cannot to use communication proxy object. This message will be triggered when session manager front end cannot to use communication proxy object. Proxy object is NULL. This is internal error preventing the session manager from communicating with the client.
Consider restarting the application.
S31007 This message will be triggered when session manager front end cannot to take mutex object. Session manager front end uses some synchronization objects to synchronize the event driven performance. This message will be triggered when session manager front end cannot to take mutex object.
The system is unhealthy, restart the system.
S31008 This message will be triggered when session manager front end failed to create a new create reply call object. Session manager front end failed to create a new create reply call object. One of the possible reasons is system does not have enough memory.
The system is unhealthy, restart the system.
S31009 Session manager front end failed to submit task result call to Symphony client. Session manager front end failed to submit task result call to Symphony client. It can be also result of broken communication.
Restart the system.
S31010 Failed to find connection object for re-connect. Session manager front end failed to find connection object when client tries to reconnect to session manager.
Contact Platform Technical Support.
S31011 Incompatible version between Symphony DE and session manager Session manager front end discovered incompatible version between the Symphony DE and session manager. Session manager cannot work with incompatible version of client and connection will be rejected.
Install a compatible version of the Symphony DE.
S31012 New connection rejected because of insufficient system resources. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31013 New session rejected because of insufficient system resources. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31014 Session manager front end failed to return new session to Symphony client. This message will be triggered when Failed to return new session created notification to Symphony client.
Restart the Symphony client.
S31015 Failed to return task persistence notification to Symphony client. Failed to return task persistence notification to Symphony client.
Contact Platform Technical Support.
S31016 New task rejected because of insufficient system resources. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31017 Communication failure in accepting new client. This message will be triggered when OS communication system return error in accepting new client's connection.
Correct OS communication system configuration and restart SSM.
S31018 New connection rejected because OS failed to allocate requested amount of data. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31019 New session rejected because OS failed to allocate requested amount of data. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31020 New task rejected because OS failed to allocate requested amount of data. This message will be triggered when session manager front end discovered insufficient system resources and rejected to communicate with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31021 Failed to return task submitted notification to Symphony client. Failed to return task submitted notification to Symphony client.
Contact Platform Technical Support.
S31022 Session update rejected because OS failed to allocate requested amount of memory. This message will be triggered when the session manager front end discovered insufficient system resources and rejected communication with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31023 Session update rejected because of insufficient system resources. This message will be triggered when the session manager front end discovered insufficient system resources and rejected communication with client.
Shutdown unnecessary programs running on this host to free up some memory or restart the machine.
S31024 Session manager front end failed to submit session update result call to Symphony client. Session manager front end failed to submit session update result call to Symphony client. This can be also be the result of broken communication.
Restart the system.
S31025 This message will be triggered when session manager front end failed to bind Session object to Connection. Session manager front end failed to open the session object for the current connection because the session is owned by another user. The client will be notified about the event.
Connect to the application with the credentials of the user who created the session and try to open the session again.
S32001 The application name passed to SSM CORE component is empty. This message will be triggered when SSM Core component when empty application profile was passed to it.
Specify the application name.
S32002 Application with specified name does not exist in SSM CORE component. This message will be triggered when SSM Core component cannot find in internal map specified application profile.
Check the application profile name.
S32003 SSM Core cannot read the application profile. This message will be triggered when SSM Core component cannot read or parse the application profile.
Check the application profile file.
S32004 SSM Core component received an empty application profile object. This message will be triggered when SSM Core component received an empty application profile object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32005 Cannot initialize DOM Parser. This message will be triggered when SSM Core component cannot initialize DOM Parser. The message can be result of shortage of system resources.
Restart cluster.
S32006 There is a parsing error in the Application Profile. The syntax of the Application Profile is incorrect.
Correct the Application Profile and re-register it.
S32007 There is a parsing error in the Application Profile. The syntax of Application Profile is incorrect.
Correct the Application Profile and re-register it.
S31008 SSM Core component unable to start Periodic Manager.. This message will be triggered when SSM Core component failed to start Periodic Manager. One of the possible reasons is system does not have enough memory.
The system is unhealthy, restart the system.
S32009 Specified Session ID does not exist in SSM Core component. This message will be triggered when SSM Core component cannot find in internal map specified Session ID.
Check your session ID and try again.
S32010 Specified Session ID already exist in SSM Core component. This message will be triggered when SSM Core component cannot add a new session object into internal map because session with specified Session ID already exist.
Contact Platform technical support.
S32012 Specified Session type is not found for specified application. This message will be triggered when SSM Core component cannot find session type specified application.
Check your application profile file. Use an existing session type or create a new one in the application profile.
S32013 SSM Core component received an empty session input object. This message will be triggered when SSM Core component received a session input object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32014 SSM Core component discovered wrong state transition from one state to another. This message will be triggered when SSM Core component discovered wrong state transition from one state to another. It means that internal state transition protocol is broken.
Check log files for other ERROR messages.
S32017 SSM Core component received invalid task input object. This message will be triggered when SSM Core component received invalid task input object to create task object. It means that internal state transition protocol is broken.
Check log files for other ERROR messages.
S32018 SSM Core component received invalid number of output objects. This message will be triggered when SSM Core component received invalid number of output objects to get done task list.
Use specified range and try again.
S32019 SSM Core component received invalid task ID to search for. This message is triggered when the SSM Core component receives an invalid task ID to search for.
Use specified range and try again.
S32020 SSM Core component received invalid session ID to search for. This message is triggered when the SSM Core component receives an invalid session ID to search for.
Use specified range and try again.
S32021 SSM Core component cannot continue this operation. This message will be triggered when SSM Core component cannot perform this operation on session with specified ID.
Contact Platform technical support with this information.
S32023 SSM Core component received an empty input task object. This message will be triggered when SSM Core component received an input task object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32024 SSM Core component received an empty session object. This message will be triggered when SSM Core component received a session object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32025 SSM Core component received an empty ARM object. This message will be triggered when SSM Core component received an ARM object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32026 SSM Core component received an empty context object. This message will be triggered when SSM Core component received a context object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32027 SSM Core component received an empty resource manager object. This message will be triggered when SSM Core component received a resource manager object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32028 SSM Core component received an empty policy object. This message will be triggered when SSM Core component received a policy object. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32029 SSM Core component received an invalid input parameter. This message will be triggered when SSM Core component (an Application profile object) received an invalid input parameter. It means that internal protocol between components is broken.
Check log files for other ERROR messages.
S32031 The application profile for application does not contain a valid OS type or the OS type does not exist. The data in Application Profile is incorrect.
Specify OS type in the application profile and re-register the application.
S32032 The application profile for application does not contain a valid session type or the session type does not exist. The data in Application Profile is incorrect.
Specify session type in the application profile and re- register the application.
S32035 SSM Core component cannot find task with specified ID. Task does not exist in session with specified ID.
Specify another task ID or check historical setting for task in its application profile.
S32036 SSM Core component received invalid number as a session priority. This message will be triggered when SSM Core component received invalid session {0} priority.
Use specified range and try again.
S32037 This message will be triggered when an invalid Paging type is requested from within the Middleware. An invalid Paging type is requested from within the Middleware.
Please contact Platform Technical Support.
S32040 This message will be triggered when performing an administrative operation on a disabled application. Administrative operation cannot proceed with a disabled application.
No action.
S32041 This message will be triggered when querying sessions without specifying the application name. Session queries require the associated application name to be specified in the query.
Check if the application name is specified in the query.
S32042 Session could not be recovered because it failed to recover all of its associated tasks. There may have been a storage device failure, data corruption, or incomplete data written.
Resubmit your workload. This error may be prevented by setting the flushDataAsap parameter. Refer to the Developer's Guide for more information about the flushDataAsap parameter and recovery configuration options.
S32043 Task cannot be recovered. This message will be triggered when task with specified ID cannot be recovered. Only part of the tasks were recovered.
Please contact Platform Technical Support.
S32044 SSM is shutting down and further operations are not allowed. Administrative operation cannot proceed with a disabled application.
No action.
S32047 SSM Core component cannot continue this operation. This message will be triggered when SSM Core component cannot perform this operation on session with specified ID.
Contact Platform technical support with this information.
S32048 SSM Core component cannot continue this operation. This message will be triggered when SSM Core component cannot perform this operation on session with specified ID.
Contact Platform technical support with this information.
S32049 Resource is reclaimed by EGO.
No action required. Resource is being reclaimed according to the configured resource plan.
S32050 Information when SIM take too long to register to SSM. This message will be triggered when SIM timed out to register with SSM.
No further action is needed, SOAM will request EGO to replace resource and provision SIM again.
S32051 The application profile for application does not contain valid task watermark setting. The task watermarks are not set correctly in Application Profile.
Make corrections to make sure the taskLowWater is no greater than taskHighWaterMark in the application profile and re-register the application.
S32052 A boundary event has been triggered. A configured boundary has been breached for a resource being monitored by the Session Manager. See the actual log entry for more specific details about the event.
Since this is an information level log entry, no action is required.
S32053 the resource low event has been triggered. A configured minServices can't be met being monitored by the Session Manager. See the actual log entry for more specific details about the event.
You can low your minServices or make sure there is enough resource gotten from EGO, if the resource is keep coming from EGO, ignore this events.
S32054 The given session tag could not be found. The given session tag could not be found.
Please provide valid session tag when trying to perform group operations.
S32055 The filter is invalid. The filter is invalid.
Contact Platform technical support.
S32056 The internal application profile object is being destroyed. The SSM is shutting down due to an administrative command. This will cause the destruction of the internal application profile object.
Retry any actions when the new SSM is up and running.
S32057 No package name is defined for a service using deployment. The deployed packageName must be specified.
Correct the application profile and reregister.
S32058 Only one default service can be specified. Remove all but one default service attributes.
Correct the application profile and reregister.
S32059 Service names must be unique. The service name attribute in the service section must be unique.
Correct the application profile and reregister.
S32060 More than one service was specified without a default=true attribute. The default service must be specified.
Correct the application profile and reregister.
S32061 The session's serviceName must exist. The service specified in the session type section must exist.
Correct the application profile and reregister.
S32062 Service Control section is not in the correct format. The Service Control section in the application profile combines the format supported in 3.1 and older versions with the new format in Symphony 3.2.
Use the latest format for the Control section. Refer to the Platform Symphony Reference, or generate a new application profile with the Platform Management Console. Re-register the application profile.
S32063 Invalid element in the Service Control section. The Return... element is not supported for section DestroyService.
Delete this line from the application profile and re-register the application.
S32064 Invalid attribute actionOnWorkload for Return... element. The actionOnWorkload attribute is not supported on method Register, CreateService or SessionLeave.
Delete this attribute from the Return... element in the application profile and re-register the application.
S32065 Invalid element Exception... for method. Element Exception... is not supported in Register and DestroyService.
Remove the Exception... line from the application profile and re-register the application.
S32066 Invalid attribute actionOnWorkload for Exception... element. The actionOnWorkload attribute is not supported on method CreateService and SessionLeave in the Exception... element.
Delete this attribute from the Exception... element in the application profile and re-register the application.
S32067 Invalid value keepAlive for attribute actionOnSI for Exception... element in method CreateService. blockHost and restartService are the only values supported for actionOnSI in the Exception... element for the CreateService method.
Correct this and re-register the application.
S32068 Invalid attribute actionOnWorkload for Timeout... element. The actionOnWorkload attribute is not supported for method Register, CreateService, SessionLeave or DestroyService in the Timeout... element.
Delete this attribute from the Timeout... element in the application profile and re-register the application.
S32069 Invalid attribute actionOnSI for Timeout... element in method DestroyService. The actionOnSI attribute is not supported for the DestroyService method in the Timeout... element.
Delete this attribute from the Timeout... element in the application profile and re-register the application.
S32070 Invalid element Exit... for method DestroyService. Element Exit... is not supported in DestroyService.
Remove the Exit... line from the application profile and re-register the application.
S32071 Invalid attribute actionOnWorkload for in method. The actionOnWorkload attribute is not supported for method Register, CreateService or SessionLeave in the Exit... element.
Delete this attribute from the Exit... element in the application profile and re-register the application.
S32072 The value of the duration attribute cannot be 0 for Timeout... element in method Register. The value of the duration attribute cannot be 0 for Timeout... element in method Register.
Specify a value larger than 0 and re-register the application.
S32073 The given operation requires a particular policy to be used. The given operation requires a particular policy to be used.
Please modify the policy in the application profile.
S32074 Multiple Timeout... elements are defined. There can only be one Timeout... element.
Remove the duplicate element in the application profile and re-register the application.
S32075 Multiple Exit... elements are defined. There can only be one Exit... element.
Remove the duplicate element in the application profile and re-register the application.
S32076 There are multiple Return... elements defined with the same controlCode. There are multiple Return ... elements defined with the same controlCode.
Change the controlCode in the application profile and re-register the application.
S32077 Multiple Exception... elements are defined with the same controlCode. Multiple Exception... elements are defined with the same controlCode.
Change the controlCode in the application profile and re-register the application.
S32078 Task is failed. actionOnWorkload is fail for Return in Invoke
Change the action on workload in the application profile and re-register the application.
S32079 Task execution result is exceeded the task retry limit. actionOnWorkload is retry for Return in Invoke
Change the action on workload in the application profile and re-register the application.
S32080 The fail action is configured on the successful session The fail action is configured on the successful session
Change the controlCode in the application profile and re-register the application.
S32081 The session retry limit has been exceeded. The fail action is configured on the successful session and exceed
Change the controlCode in the application profile and re-register the application.
S32082 Required attribute was not provided. Required attribute was not provided.
Add the specified action in the application profile and re-register the application.
S32083 Invalid session priority. The session priority is invalid.
The user need to use a valid session priority.
S32084 Custom deployment and Symphony deployment can not be defined together. Conflict between custom deployment and Symphony deployment definitions.
Remove the reference to ${SOAM_DEPLOY_DIR} in startCmd or preExecCmd in the service section.
S32085 The size of session common data is greater than the maximum size configured in application profile. The size of common data for the session is larger than the maximum size configured in the application profile.
Configure a higher diskSpace value in PagingCommonData and try again.
S32086 client set an invalid service name An invalid service name was set by client.
Please check your client code and application profile.
S32089 The task you selected to kill cannot be found in the session. The task with specified ID that you selected to kill does not exist or has been persisted in history.
No action necessary.
S32090 The state of the task or session forbids the killing action. The task is in a state that prevents it from being killed. Tasks must be either running or pending to be killed.
No action necessary.
S32091 The service method returned successfully but the host was blocked. The service method returned successfully but the host was blocked due to configuration in the application profile. The value actionOnSI=blockHost was configured in Control | Method | Return.
If blocking the host upon successful return of the method is not the desired behavior, change the value of actionOnSI in Control | Method | Return in the application profile and re-register the application profile.
S32092 No SOAM/SIM section defined for Symphony 3.x The SOAM/SIM section is necessary to start the SIM
Add the SOAM/SIM section to the application profile and re-register the application.
S32093 No SOAM/SIM/OSTypes section defined for Symphony 3.x The SOAM/SIM/OSTypes section is necessary to start the SIM
Add the SOAM/SIM/OSTypes section to the application profile and re-register the application.
S32093 No SOAM version was specified for profile versions greater than 3.1 The SOAM version was not specified
Specify the SOAM version that you want to use for your application.
S32097 Session could not be recovered because it failed to recover all of its associated common data updates. There may have been a storage device failure, data corruption, or incomplete data written.
Resubmit your workload. You may also refer to the Developer's Guide for more information regarding recovery configuration options.
S32098 The application profile has been updated, and all sessions associated with the updated service(s) have been aborted. The application profile has been updated, and all sessions associated with the updated service(s) have been aborted.
Run the aborted sessions again after updating the profile.
S32099 The specified element is not valid for this profile fragment. The specified element is not valid for this profile fragment.
Edit the profile fragment using the samples as a guideline.
S32100 The specified element is not in this profile fragment. The specified element is not in this profile fragment.
Edit the profile fragment using the samples as a guideline.
S32101 There are redundant elements in the fragment profile. There are redundant elements in the fragment profile..
Edit the fragment profile using the samples as a guideline.
S32102 There are invalidate Edit Type in the fragment profile. There are invalidate Edit Type in the fragment profile.
Edit the fragment profile using the samples as a guideline.
S32103 The specified attribute is not in the specified element of this profile fragment. The specified attribute is not in specified element of this profile fragment.
Edit the profile fragment using the samples as a guideline.
S32104 For successful return of the SessionUpdate method, the actionOnWorkload is configured with \"fail\". For successful return of the SessionUpdate method, the actionOnWorkload is configured with "fail".
If you do not want successful return of the SessionUpdate method to cause workload failure, modify the application error handling behavior in your application profile and re-register the application.
S32105 The application profile has been updated, and all sessions associated with the updated session type(s) have been aborted. The application profile has been updated, and all sessions associated with the updated session type(s) have been aborted.
Run the aborted sessions again after updating the profile.
S32106 The service cleanup timeout must not exceed SSM shutdown timeout. The service cleanup timeout must not exceed SSM shutdown timeout.
Modify service cleanup timeout in application profile.
S32107 Service name does not exist. Service name does not exist.
Check service execution sections in application profile.
S32108 Invalid task ID filter. Task ID filter contains a task ID that is out of range. No task has been created with the specified ID.
Specify IDs for tasks that have already been created.
Task ID filter contains an ID for a task that has already been retrieved. Only retrieve tasks that are available.
S32109 The host is unavailable at this moment, so service instance manager will shut down. If any workload is still running when the service instance manager shuts down, it will be automatically re-run by Symphony. Unable to contact host at this moment.
Check whether the host is still available.
EGO processes are down on the host. Restart EGO on the host.
S32110 The session manager does not recognize the specified type of TaskOutputFilter. It is likely that a newer client is being used with an older session manager.
Update the session manager binary with a newer version, or use a TaskOutputFilter that is supported by your existing session manager.
S32111 The values of the attributes in the session type specified conflicts with the Direct Data Transfer feature. This message will be triggered when the Symphony Session Manager attempts to create a session using a session type with values of attributes that conflict with the Direct Data Transfer feature.
Check your application profile file. Set the session type attributes to values that do not conflict with the Direct Data Transfer feature.
S32112 The values of the attributes in the service section specified conflicts with the Direct Data Transfer feature. This message will be triggered when the Symphony Session Manager attempts to create a session using a service with values of attributes that conflict with the Direct Data Transfer feature.
Check your application profile file. Set the service section's attributes to values that do not conflict with the Direct Data Transfer feature.
S32119 The policy is not supported by the version of Session Manager. The policy is not supported by the version of Session Manager.
Configure the policy with the correct version of Session Manager.
S32120 The policy is not supported by the Session Manager. The policy is not supported by the Session Manager.
Configure the correct policy for the Session Manager.
S32121 The service to slot ratio is invalid. This message will be triggered when the user specifies a service to slot ratio that is invalid.
Configure the ratio to be either 1:N or N:1, where N is a positive integer.
S32122 numOfPreloadedServices is deprecated by numOfSlotsForPreloadedServices. The two attributes cannot be configured together numOfPreloadedServices is deprecated by numOfSlotsForPreloadedServices. The two attributes cannot configured together.
Remove one of the two attributes.
S32123 The resource group filter specified is invalid. The resource group filter should be the subset of resource group name specified in consumer section in application profile. The resource group filter specified is invalid. The resource group filter should be the subset of resource group name specified in consumer section in application profile.
Change the resource group filter specified.
S32125 This message will be triggered when SSM is attempting to initialize the data provider to be used with the Resource Preference Feature. The SSM failed to register with the data provider. The Resource Preference feature will not have access to any details published from service instances.
The system is unhealthy, restart the system.
S32126 This message is triggered when a user enables the Resource Preference evaluations but does no have the license to enable service side publishing. The Resource Preference feature will not have access to any details published from service instances.
If your application requires this ability, obtain a license from Platform Computing.
S32127 This message is triggered when the system fails to parse a preference string provided by the application. The system encountered an error while attempting to parse the preference string supplied by the application.
Review the specific details in the error message which will give a more specific course of action.
S32128 This message is triggered when the system receives a resource attribute definition that it cannot apply to the session. The system received a resource attribute definition that cannot be applied to the session because it is trying to redefine an already applied definition.
Specify a definition that does not redefine a previous definition with the same name.
S32129 This message is triggered when the standby service feature is configured in profile in DE mode.

S32130 This message is triggered when numOfPreloadedServices is configured with a value greater than 10000.

S32131 This message is triggered when the specified taskLowWaterMark configuration is not supported by the SOAM version configured for your application. The specified taskLowWaterMark configuration is not supported by the SOAM version configured for your application.
Specify a valid taskLowWaterMark value for the given SOAM version, or revert to an earlier version of SOAM where this taskLowWaterMark value is supported.
S32132 This message is triggered when the specified taskHighWaterMark configuration is not supported by the SOAM version configured for your application. The specified taskHighWaterMark configuration is not supported by the SOAM version configured for your application.
Specify a valid taskHighWaterMark value for the given SOAM version, or revert to an earlier version of SOAM where this taskHighWaterMark value is supported.
S32133 This message will be triggered when the user specifies an invalid serviceToSlotRatio, where the number of services to run per slot exceeds the system limit. User specified an invalid serviceToSlotRatio, where the number of services to run per slot exceeds the system limit.
Specify a serviceToSlotRatio within the system limit.
S32134 This message will be triggered when the user specifies a value that is too long for a specified attribute. An attempt is being made to associate a value that is too long for a specific attribute.
Specify a shorter value as guided by the specific error message.
S32135 This message is triggered when the specified resourceGroupName configuration is not supported by the SOAM version configured for your application. The specified resourceGroupName configuration is not supported by the SOAM version configured for your application.
Specify a valid resourceGroupName value for the given SOAM version.
S33001 This message is triggered when an invalid input parameter is passed into the interface of the resource manager component. Failed to call an interface of resource manager component.
This is an internal error.
S33002 This message will be triggered when call vem_register failed. Call EGO API vem_open failed.
Check if the environment variable EGO_CONFDIR is set. Check the log file for EGO returned error message.
Call EGO API vem_logon failed. Check if EGO security is set up and enabled. Check the log file for EGO returned error message.
Call EGO API vem_register failed. Check the log file for EGO returned error message. Check if EGO is up.
S33003 This message will be triggered when call vem_unregister failed. Call EGO API vem_unregister failed.
Check the log file for EGO returned error message.
S33004 This message will be triggered when call vem_alloc failed. Call EGO API vem_alloc failed.
Check the log file for EGO returned error message.
S33005 This message will be triggered when call vem_allocfree failed. Call EGO API vem_allocfree failed.
Check the log file for EGO returned error message.
S33006 This message will be triggered when call vem_release failed. Call EGO API vem_release failed.
Check the log file for EGO returned error message.
S33007 This message will be triggered when call vem_startcontainer failed. Call EGO API vem_startcontainer failed.
Check the log file for EGO returned error message.
S33008 This message will be triggered when call vem_signalcontainer failed. Call EGO API vem_signalcontainer failed.
Check the log file for EGO returned error message.
S33009 This message will be triggered when call vem_realloc failed. Call EGO API vem_realloc failed.
Check the log file for EGO returned error message.
S33010 This message will be triggered after call registerConsumer() failed and other interfaces of Resource Manager got called. Call interfaces of Resource Manager failed because call registerConsumer() failed.
Check the log file for Symphony returned error message.
S33011 This message will be triggered when vem_open call returned a NULL handle. The handle returned by vem_open is NULL.
Check EGO log files for error messages.
S33012 This message will be triggered when the resource consumer object is NULL. The resource consumer object passed in is NULL.
Check Symphony log files for error messages.
S33013 This message will be triggered when the handle returned from EGO is NULL. The handle returned from EGO is NULL.
Check Symphony log files for error messages.
S33014 This message will be triggered when the logon user has no permission to operate on a given consumer. The user has no permission to operate on a given consumer.
Add this user to EGO.
S33015 This message will be triggered when the system failed to get the roles for a specific user from EGO. Failed to get roles for a specific user in EGO.
Check if EGO is running and add this user to EGO.
S33016 This message will be triggered when call vem_getroles4user failed. Call vem_getroles4user failed in EGO.
Check if EGO is on and add this user to EGO.
S33017 This message will be triggered when call vem_verifyconsumerpath failed. Call vem_verifyconsumerpath failed in EGO.
Check if EGO is on and add this user to EGO.
S33018 This message will be triggered when call vem_verifyresreq failed. Call vem_verifyresreq failed in EGO.
Check if EGO is on and add this user to EGO.
S33019 This message will be triggered when session director fails to authenticate itself with EGO. Session director is using a credential provided by EGO. If this credential become invalid (password changed or expired) session director will fail to connect to EGO Call vem_logon failed in EGO.
No action is required. Session director will exit and restart
S33020 This message will be triggered when container exits with exception. Call vem_startcontainer failed in EGO.
In the application profile, Check start command, env settings, working directory and execution permission
S33021 This message will be triggered when EGO connect is lost. Lost connection to EGO.
Connection will be retried automatically
S33022 This message will be triggered when failed to connect to EGO. Failed to reconnect to EGO.
None.
S33024 This message will be triggered when failed to allocate memory for EGO API. Failed to allocate memory for EGO API.
None.
S33026 This message will be triggered when call vem_startcontainer failed, and the resource should be discarded. Call EGO API vem_startcontainer failed, and the resource should be discarded.
Check the log file for EGO returned error message.
S33027 This message will be triggered when call vem_release failed. Call EGO API vem_release failed.
Check the log file for EGO returned error message.
S33028 This message will be triggered when call vem_release failed. Call EGO API vem_release failed.
Check the log file for EGO returned error message.
S33029 This message will be triggered when EGO has returned an unexpected null pointer. EGO has returned an unexpected null pointer.
Contact Platform technical support.
S33030 Resource is reclaimed from EGO. Borrowed resource is reclaimed by EGO.
No action needed, if this is the resource planning administrator designed.
S33031 Host is unavailable. Host is not available at this moment.
Check whether the host is still healthly.
S33037 This message will be triggered when host information could not be obtained. Failed to obtain host information.
Make sure that EGO is enabled.
S33040 Resource may be reclaimed from EGO with smart reclaim enabled. Borrowed resource may be reclaimed from EGO with smart reclaim enabled.
No action needed. Resource may be reclaimed according to the configured resource plan.
S33041 Could not open VEMResManager working thread.
None.
S34001 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34002 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34003 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34004 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34005 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34006 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34007 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34008 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Contact Platform technical support.
S34009 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34010 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
Consider restarting the application.
S34011 This message will be triggered when communication with SIM is lost. Communication between session manager and SIM is broken. Session manager will restart SIM and redispatch tasks.
Check SIM log file on specified host for errors.
S34012 This message will be triggered when SSM Backend failed to send allocate service message to SIM. SSM Backend failed to send allocate service message to SIM.
Check SIM log file on specified host for errors.
S34013 This message will be triggered when SSM Backend failed to send enqueue task message to SIM. SSM Backend failed to send enqueue task message to SIM. One of the possible reason is that target host is down.
Check SIM log file on specified host for errors. Check the target host is up.
S34014 This message will be triggered when SSM Backend failed to send kill task message to SIM. SSM Backend failed to send kill task message to SIM.
Check SIM log file on specified host for errors.
S34015 This message will be triggered when SSM Backend failed to send bind service message to SIM. SSM Backend failed to bind service task message to SIM.
Check SIM log file on specified host for errors.
S34016 This message will be triggered when SSM Backend failed to send unbind service message to SIM. SSM Backend failed to send unbind service task message to SIM.
Check specified host is up.
S34017 This message will be triggered when SSM Backend failed to send unregister service message to SIM. SSM Backend failed to send unregister service task message to SIM.
The system is unhealthy, restart the system.
S34018 This message will be triggered when SSM Backend failed to find requested task. SSM Backend failed to find requested task.
The system is unhealthy, restart the system.
S34019 This message will be triggered when SSM Backend identifies incompatible version of SIM. SSM Backend failed to find requested task.
Change application profile to use compatible version of SIM.
S34020 This message will be triggered when an invalid input parameter was send by SIM into the interface of SSM Backend component. Failed to call an interface of SSM Backend component. Protocol between SSM Backend and SIM is broken.
The system is unhealthy, restart the system.
S34021 This message will be triggered when an error happened when task executed by SIM. SSM Backend component discovered that received task contained error object.
Check SIM log file on specified host for errors.
S34022 This message will be triggered when SSM Backend failed to send kill task message to SIM. SSM Backend failed to send kill task message to SIM.
Check SIM log file on specified host for errors.
S34023 Initialization error in the admin request server. SSM Backend will not be able to respond to session and task queries.
Restart the application..
S34024 The Service Instance Manager is suspending task, new tasks can not enqueued. Session Manager is trying to send tasks to SIM which is trying to suspend current task.
No action required. The task will be requeued automatically
S34025 This message will be triggered when there is not enough memory to allocate for the result. Session Manager is Low on memory. Failed to allocate memory for the parameter.
Adjust flow control parameters.
S34026 This message will be triggered when an error happened when task executed by SIM. SSM Backend component discovered that received task contained error object.
Check SIM log file on specified host for errors.
S34027 This message will be triggered when the backend SIM object is invalid. The backend SIM object is invalid.
None.
S34028 The Service Instance Manager is suspending a task, the current operation cannot be completed. The Service Instance Manager is suspending a task, the current operation cannot be completed.
No action required.
S34029 This message will be triggered when the backend SIM object does not have tasks enqueued, but tasks are expected. The backend SIM object does not have tasks enqueued, but tasks are expected.
None.
S34030 The Service Instance Manager is suspending a task. The ongoing suspend request cannot be interrupted. Session Manager is trying to suspend task to SIM which had already been trying to suspend the task.
No action required. The new suspend request will be ignored
S34031 Session Manager received a message for a closed/suspended session. Session Manager received a message from SIM for a closed/suspended session.
No action required.
S34032 The Service Instance Manager is preempting a task. The ongoing preemption cannot be interrupted Session Manager is trying to preempt a task that is in the process of being preempted.
No action required. The task is already undergoing preemption.
S34033 The Service Instance Manager is preempting a task. New tasks cannot be dispatched to this Service Instance Manager. Session Manager is trying to send tasks to SIM which is trying to preempt the current task.
No action required. The task will be requeued automatically.
S34034 This message will be triggered when SSM Backend failed to send standby request to SIM. Session Manager failed to send standby request to SIM.
No action required.
S34037 This message will be triggered when SSM Backend failed to send a reply from the Metadata Provider to the SIM. SSM Backend failed to send reply from the Metadata Provider to the SIM. One of the possible reason is that target host is down.
Check SIM log file on specified host for errors. Verify that the target host is up.
S35001 This message will be triggered when the Paging subsystem attempts to access an invalid block from within the Middleware. The Paging subsystem has attempted to access an invalid block from within the Middleware.
Please contact Platform Technical Support.
S35002 This message will be triggered when the Paging subsystem attempts to access an invalid Physical Media Element from within the Middleware. The Paging subsystem has attempted to access an invalid Physical Media Element from within the Middleware.
Please contact Platform Technical Support.
S35003 This message will be triggered when the Paging subsystem has retrieved a corrupted block. The data contained in the give block is lost. A previous process crash has caused the last I/O operation to fail.
No action necessary.
A previous system crash has caused the last I/O operation to fail. No action necessary.
The file or hardware is corrupt/damaged. Contact your IT Administrator to check on the health of your file system.
S35004 This message will be triggered when the Paging subsystem has run out of available storage. The storage space allocated to the Paging subsystem is full.
Please contact a Platform Systems Engineer to help you tune the system.
S35005 This message will be triggered when the Middleware requests the Paging subsystem to write a zero-length block of data. The Middleware has requested that the Paging subsystem to write a zero-length block of data.
Please contact Platform Technical Support.
S35006 This message will be triggered when the Middleware requests the Paging subsystem to read an invalid block of data. The Middleware has requested that the Paging subsystem read an invalid block of data.
Please contact Platform Technical Support.
S35007 This message will be triggered when the Middleware requests the Paging subsystem to read from a non-existent location. The Middleware has requested that the Paging subsystem read from a non-existent location.
Please contact Platform Technical Support.
S35008 This message will be triggered when the Middleware requests the Paging subsystem to remove data from an invalid location. The Middleware has requested that the Paging subsystem remove data from an invalid location.
Please contact Platform Technical Support.
S35009 This message will be triggered when the Middleware requests the Paging subsystem to remove data from a non-existent location. The Middleware has requested that the Paging subsystem remove data from a non-existent location.
Please contact Platform Technical Support.
S35010 This message will be triggered when there is a failure in attempting to seek within a file. Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S35011 This message will be triggered when a file cannot be written. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S35012 This message will be triggered when a file cannot be read. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S35013 This message will be triggered when the Middleware has attempted to read beyond the end of a file. The Middleware has attempted to read beyond the end of a file.
Please contact Platform Technical Support.
S35014 This message will be triggered when a file cannot be closed. Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Disk quota exceeded.
Remove any unnecessary files from the file system to make space for the given file.
Permission denied. The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
S35015 This message will be triggered when a file cannot be removed from the file system. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. File is in use.
The given file is currently in use, and cannot be deleted while in use. Close the file.
S35016 This message will be triggered when a request has been made to write data that is smaller than the requested write amount. A request has been made to write data that is smaller than the requested write amount.
Please contact Platform Technical Support.
S35017 This message will be triggered when a request has been made to write data across subfiles. A request has been made to write data across subfiles.
Please contact Platform Technical Support.
S35018 This message will be triggered when a request has been made to read data across subfiles. A request has been made to read data across subfiles.
Please contact Platform Technical Support.
S35019 This message will be triggered when the Paging Manager cannot join with its worker thread(s). The Paging Manager cannot join with its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S35020 This message will be triggered when the Paging Manager cannot start its worker thread(s). The Paging Manager cannot start its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S35021 This message will be triggered when the Paging Manager attempts to switch to an invalid paging mode. The Paging Manager has attempted to switch to an invalid paging mode.
Please contact Platform Technical Support.
S35022 This message will be triggered when the Middleware expects a null pointer, but does not receive one. The Middleware was expecting a null pointer, but did not receive one.
Please contact Platform Technical Support.
S35023 This message will be triggered when an invalid Physical Media Element (PME) type has been requested. An invalid PME type has been requested. The default type, Rolling File, has been created instead.
If you are satisfied with the default PME, do nothing. Otherwise, please contact your Platform Systems Engineer to configure this feature.
S35024 This message will be triggered when the Paging Manager experiences an unexpected synchronization error. The Paging Manager has experienced an unexpected synchronization error.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S35025 This message will be triggered when an invalid Paging mode is requested from within the Middleware. An invalid Paging mode is requested from within the Middleware.
Please contact Platform Technical Support.
S35026 This message will be triggered when an invalid Paging operation is requested from within the Middleware. An invalid Paging operation is requested from within the Middleware.
Please contact Platform Technical Support.
S35027 This message will be triggered when an invalid Paging type is requested from within the Middleware. An invalid Paging type is requested from within the Middleware.
Please contact Platform Technical Support.
S35028 This message will be triggered when an invalid S.W.I.M type is requested from within the Middleware. An invalid S.W.I.M type is requested from within the Middleware.
Please contact Platform Technical Support.
S35029 This message will be triggered when the path is not correct or is not writable. The user provided wrong path in the application profile.
Correct the application profile and re-register.
S35036 This message will be triggered when a file cannot be created or opened. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S37001 This message will be triggered when the Journaling Manager cannot start its worker thread(s). The Journaling Manager cannot start its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S37002 This message will be triggered when the Journaling Manager cannot join with its worker thread(s). The Journaling Manager cannot join with its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S38005 This message will be triggered when the SSM get unexpected SymException. SSM get unexpected SymException with description provided.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S38006 This message will be triggered when the SSM get unexpected std::exception. SSM get unexpected std::exception with description provided.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S38007 This message will be triggered when the SSM get unexpected exception. SM get unexpected exception with no additional information provided.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S38010 SSM failed to connect to SD, and please read the log file to find the system error. The system error should provide a hint as to how to correct the problem. The following are examples of some common scenarios. SSM fails to contact with SD due to failure to resolve host name.
Please make sure that your SD address is reachable from this SSM host.
S40001 SIM failed to initialize communications with the service instance. SIM is low on memory and unable to complete initialization.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40002 SIM failed to get a socket from the system to communicate with the service instance. The SIM host is low on system resources.
Shutdown unnecessary programs running on this SIM host to free up the resources or restart the machine.
S40003 SIM failed to start the service instance specified in the Application Profile. The startCmd in the Application Profile was not entered correctly.
Verify that the startCmd is correct.
The startCmd in the Application Profile was not found on the SIM host. Ensure the command specified in the Application Profile is located on the SIM host.
The startCmd for the service failed due to missing dynamic libraries. Ensure that the required dynamic libraries are located on the SIM host.
S40004 SIM failed to run the service instance specified in the Application Profile. The service instance started and then stopped immediately.
Check your service code to determine why the service stopped.
S40005 SIM failed to run the service instance specified in the Application Profile. The service instance started and then stopped immediately.
Check your service code to determine why the service stopped.
S40006 SIM failed to start the service instance specified in the Application Profile. The startCmd for the service failed due to missing dynamic libraries.
Ensure that the required dynamic libraries are located on the SIM host.
S40007 The OnCreateService reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40008 The OnCreateEnter reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40009 The OnInvoke reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40010 The OnSessionLeave reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40011 The OnDestroyService reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40012 The Unload service reply was not received by the SIM. The application service stopped running suddenly.
Check the service code to determine why the service didn't unload properly.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40013 The application service interrupt request wasn't sent. There was a socket error between SIM and the Service.
No action required as SIM will stop.
S40014 The application service interrupt request wasn't sent. There was a socket error between SIM and the Service.
No action required as SIM will stop.
S40015 The SIM failed to connect with the session manager. The SIM host is running low on memory or descriptors.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40016 The SIM failed to connect with the session manager. The session manager is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40017 The Application Profile was not parsed. The machine is low on virtual memory.
Try restarting the machine.
S40018 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40019 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40020 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40021 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40022 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40023 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40024 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40025 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40026 A task's output could not be sent back to the session manager. There was insufficient memory to send the task result over the network.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40027 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40028 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40029 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40030 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40031 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40032 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40033 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40034 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40035 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40036 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40037 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40038 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40039 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40040 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40041 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40042 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40043 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40044 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40045 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40046 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40047 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40048 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40049 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40050 The session manager sent a request to SIM that is not supported. The session manager is in an unstable state.
Restart your application.
S40051 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40052 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40053 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40054 The SSM sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40055 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40056 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40057 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40058 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40059 The SIM failed to send an error message to the session manager. The SSM is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40060 Failed to initialize the XML parser. There was insufficient memory to do the initialization.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40061 Failed to parse the Service section of the Application Profile. There was insufficient memory to do the initialization.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40062 The SIM failed to send a reply message to the session manager. The session manager is not running.
Restart your application.
A network error caused the connection to the SSM to fail. No action required, the SIM will stop.
S40063 The SIM did not successfully complete initialization. There was insufficient memory to start the SIM.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40064 The SIM did not successfully complete initialization. There was insufficient memory to start the SIM.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40065 The SIM did not successfully complete initialization. There was insufficient memory to start the SIM.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40066 The SIM did not successfully complete initialization. There was insufficient memory to start the SIM.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40067 The SIM failed to send a reply message to the SSM. The session manager is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40068 The SIM failed to receive a message from the session manager. The session manager is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40069 There is a parsing error in the Service/Control section of the Application Profile. The syntax of the control statement is incorrect.
Correct the Application Profile and re-register it.
S40070 There is a parsing error in the Service/Control section of the Application Profile. The syntax of the control statement is incorrect.
Correct the Application Profile and re-register it.
S40071 There is a parsing error in the Service/Control section of the Application Profile. The syntax of the control statement is incorrect.
Correct the Application Profile and re-register it.
S40072 There is a parsing error in the Service/Control section of the Application Profile. The syntax of the control statement is incorrect.
Correct the Application Profile and re-register it.
S40073 There is a parsing error in the Service/Control section of the Application Profile. The syntax of the control statement is incorrect.
Correct the Application Profile and re-register it.
S40074 A service API call timed out. The application service is not responding.
No action is required, the service will be terminated. If invoke failed, the service will be restarted.
S40075 A service process has exit. The application service failed.
No action is required, the service will be terminate. If invoke failed, the service will be restarted.
S40076 The application service version and SIM version are incompatible. A service created with a newer Symphony DE is being run with older Symphony binaries.
Rebuild the service with the Symphony DE that came with the installed Symphony binaries.
S40077 The pre-exec command specified in the Application Profile Service section could not be found. The command binary was not installed on the SIM host machine.
Install the command on the SIM host machine
The default deploy tool is not installed on the SIM host. Check the Symphony install to ensure that soamdeploy is present and on the path.
S40078 The pre-exec command specified in the Application Profile Service section failed to start. The command failed due to missing dynamic libraries.
Ensure that the required dynamic libraries are located on the SIM host.
S40079 The pre-exec command specified in the Application Profile Service section returned an error. The pre-exec command failed due to an internal error.
Check the pre-exec command to ensure that it can run on the SIM host.
The default pre-exec command failed due to an internal error. Run the soamdeploy -V, command to ensure that it can run on the SIM host.
S40080 The application service was not started. No osType section matched the current SIM host type. The osType in the Service section doesn't match the SIM resource osType.
Add a service section to match the osType of the resource and re-register the Application Profile.
S40081 The pre-exec command specified in the Application Profile Service section could not be found. The command binary was not installed on the SIM host machine.
Install the command on the SIM host machine
The default deploy tool is not installed on the SIM host. Check the Symphony install to ensure that soamdeploy is present and on the path.
S40082 The SSM tried to unbind a session in the SIM that was not active. The SIM failed to unbind a non-active session.
No user action required
S40083 The SSM tried to suspend a session in the SIM that was not active. The SIM failed to suspend a non-active session.
No user action required
S40084 The SSM tried to kill a session in the SIM that was not active. The SIM failed to kill a non-active session.
No user action required
S40094 The SIM failed to connect with the session manager. The session manager is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40095 The SIM failed to register with the session manager. EGO reclaimed the slot the SIM is running under, and the SSM disconnected communications.
No action required, the SIM will stop.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40097 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40098 A request could not be queued internally. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this SIM host to free up some memory or restart the machine.
S40099 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40100 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40101 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40102 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40103 The OnSessionUpdate reply was not received by the SIM. The application service stopped running.
Check the service code to determine why the service failed.
There was a socket error between SIM and the Service. No action required as SIM will stop.
S40104 The specified code is not configured. The specified code is not configured.
Treat the code as code 0.
S40105 The control code 0 is not configured. The control code 0 is not configured.
The default actions will be adopted.
S40106 The specified code is not configured. The specified code is not configured.
Treat the code as code 0.
S40107 The control code 0 is not configured. The control code 0 is not configured.
The default actions will be adopted.
S40108 The common data update sent to this SIM was out of order. The SSM didn't send the update in the correct sequence.
No action required, the service instance will be stopped.
S40109 An invalid value was provided for the customizedDebugAction attribute in the Service | Control | Method section of the Application Profile. An invalid value was provided for the customizedDebugAction attribute in the Service | Control | Method section of the Application Profile.
Correct the Application Profile and re-register it.
S40110 An invalid value was provided for the debugSetting attribute in the Service section of the Application Profile. An invalid value was provided for the debugSetting attribute in the Service section of the Application Profile.
Correct the Application Profile and re-register it.
S40111 The service instance process failed to register with the SIM after it started up. You have implemented service initialization before calling the ServiceContainer run method, which may prevent the service instance from registering back with the SIM within the specified timeout.
Move your service initialization to the CreateService method.
The service instance did not connect to the SIM within the specified timeout after it started up due to computing resource or network speed. Increase the value of the duration attribute in the Service > Control > Method > Timeout section of the Application Profile for the Register method.
S40112 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40113 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40114 The session manager sent a request to the SIM unexpectedly. The service state in the SIM was not correct for the request that was received.
Restart your application.
S40115 The SIM detected a connection broken to the session manager. A network error caused a disconnection from the session manager.
No action required. Symphony will self-recover from this error.
The SSM has failed over or has been restarted. No action required. Symphony will self-recover from this error.
The session manager is not running. The SD will attempt to restart the session manager. If the session manager fails to start, check your environment and, if necessary, restart your application.
S40116 The SIM failed to send an event to the session manager. The SSM is not running.
Restart your application.
A network error caused the connection to the session manager to fail. No action required, the SIM will stop.
S40117 The session manager sent a request with a missing parameter. The session manager is in an unstable state.
Restart your application.
S40118 The SIM failed to kill the Service Instance. Failed to kill Service Instance.
No action required, SIM will log the detail or exit.
Failed to kill Service Instance. No action required, SIM will handle it.
S40119 SIM will exit because it failed to kill the Service Instance. SIM will exit because it failed to kill the Service Instance.
No action required, SIM will exit.
SIM will exit because it failed to kill the Service Instance. No action required, SIM will exit.
S40120 Failed to start timer. Failed to start timer.
Kill SIM.
S40126 SIM recieved a request to accept a connection, but could not complete the operation. It is likely that the SIM host is low on system resources.
Shutdown unnecessary programs running on this SIM host to free up the resources or restart the machine.
S40127 SIM could not complete the accept request because it cannot recognize the connecting entity. Connection will be ignored. SIM was forced to reject a connection from an unknown entity.
No action required.
S40129 SIM could not dispatch a request to the service instance. SIM was unable to communicate with the service instance.
Service instance may have exited unexpectedly while the request was being sent.
S20021 An invalid argument was passed between internal components of the API. An internal error occurred due to an erroneous interaction between some internal components within the API.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20022 An internal component of the API found itself in an unexpected state. This represents a generic assertion being triggered when an internal component of the API is in as unexpected state.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20023 An internal component of the API attempted to use a synchronization object and encountered an error. A generic error for asserting that all internal synchronization objects perform as expected.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20024 Feature not implemented. An internal component of the API is being requested to make available a feature that the API is certain has not been implemented as yet. This may happen when the internal interface to access a feature may exist but no implementation exists as yet.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20025 Feature not available. An internal component of the API is being requested to make available an interface which it has not implemented/wishes to make available to other internal components of the API.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20026 Feature not available in the current client API. This will usually be returned when a client or service built with a more recent version of the Symphony DE is deployed on a host installed with an older version.
Upgrade the Middleware to match a version that contains the feature required. The best solution is to install the same version of the Middleware that the client was built with.
S20027 An internal API component was not initialized correctly. An attempt is being made to access an internal API component without it being initialized correctly. This represents a generic error for asserting that all internal objects get initialized as expected.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20028 An attempt is being made to initialize an internal API component more than once. A generic error for asserting that the internal objects which do not support multiple initializations never are initialized more than once.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20030 *** this error to be removed. no details.
no action.
S20030 An attempt to allocate memory failed. A generic error for asserting that the amount of memory available to the API is sufficient.
Make more memory available and re-submit workload to the Middleware.
S20031 An internal communication stub is unavailable. An internal API component attempted to register or access a communication stub with an unknown name. This represents a generic error for asserting that the internal objects all use communication stubs that are known and supported.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20032 An internal component encountered a communication error that it could not recover from. A generic error for asserting that the communication errors that cannot be recovered from are identified.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20033 The SOAM_HOME environment variable was not defined. Access to the SOAM_HOME environment variable is required for some internal operations within the API.
Define the environment variable and set its value as the root directory in which Symphony DE was installed.
S20034 *** This error code will be removed (no longer required). no description.
no action.
S20035 Unable to write the specified data type to the stream. A request was made to write an unknown or unsupported data type to the stream.
Check the reference guide for the supported types.
S20036 Unable to read the specified data type from the stream. A request was made to read an unknown or un-supported data type from the stream.
Check the reference guide for the supported types.
S20037 An internal API action cannot be located. This will usually be triggered when the requested action has already expired and is no longer available. This is merely a warning level error and has no significant impact.
No action required.
S20038 An internal error occurred while writing to the stream. An unexpected error occurred while writing to the stream.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20039 An internal error occurred while reading from the stream. An unexpected error occurred while reading from the stream.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20040 *** error code to be removed. no detail.
no action.
S20041 An internal error occurred while attempting to convert a configuration value to the required type. An unexpected error occurred while converting a required configuration parameter.
1. Verify that the parameter reported has a value that is of the correct type. See the Symphony API reference guide for the types to be associated with the specified value.
S20042 Unable to add new operation for execution. An internal error occurred while one of the API's internal component attempted to add a new operation to the API's Operation Manager.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20043 An API component initialization failed. An internal API core component failed to initialize.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20044 An API component un-initialization failed. An internal API core component failed to uninitialize.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20045 Callback object missing. This will usually occur when a session is being created or opened with a flag which requires a valid callback object to be passed.
Ensure that a callback object is being passed and ensure that it has a life cycle that is greater than the life of the session.
S20046 Invalid internal stream encountered. An internal API object is attempting to access a stream which is empty or invalid.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20047 *** Unable to load service. The middleware was unable to load the service associated with the application because the call to the "loadService(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20048 *** Unable to unload service. The middleware was unable to unload the service associated with the application because the call to the "unloadService(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20049 Unable to create service. The middleware was unable to create the service associated with the application because the call to the "onCreateService(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20050 Unable to destroy service. The middleware was unable to destroy the service associated with the application because the call to the "onDestroyService(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20051 Unable to completely propagate common data. The middleware was unable to completely propagate the common data to the service associated with the application because the call to the "onSessionEnter(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20052 Unable to completely remove common data. The middleware was unable to completely remove the common data from to the service associated with the application because the call to the "onSessionLeave(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20053 Unable to invoke the service. The middleware was unable to invoke the service associated with the application because the call to the "onInvoke(...)" method failed.
Debug the service and address the issue causing this method to fail.
S20054 *** Unable to load service due to a fatal error. The middleware was unable to load the service associated with the application because the call to the "loadService(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20055 *** Unable to un-load service due to a fatal error. The middleware was unable to un-load the service associated with the application because the call to the "unloadService(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20056 Unable to create service due to a fatal error. The middleware was unable to create the service associated with the application because the call to the "onCreateService(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20057 Unable to destroy service due to a fatal error. The middleware was unable to destroy the service associated with the application because the call to the "onDestroyService(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20058 Unable to completely propagate common data due to a fatal error. The middleware was unable to completely propagate the common data to the service associated with the application because the call to the "onSessionEnter(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20059 Unable to completely remove common data due to a fatal error. The middleware was unable to completely remove the common data from to the service associated with the application because the call to the "onSessionLeave(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20060 Unable to invoke the service due to a fatal error. The middleware was unable to invoke the service associated with the application because the call to the "onInvoke(...)" method failed with a fatal error.
Debug the service and address the issue causing this method to fail.
S20061 *** Unable to load service due to a user-defined error. The middleware was unable to load the service associated with the application because the call to the "loadService(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20062 *** Unable to unload service due to a user-defined error. The middleware was unable to unload the service associated with the application because the call to the "unloadService(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20063 Unable to create service due to a user-defined error. The middleware was unable to create the service associated with the application because the call to the "onCreateService(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20064 Unable to destroy service due to a user-defined error. The middleware was unable to destroy the service associated with the application because the call to the "onDestroyService(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20065 Unable to completely propagate common data due to a user- defined error. The middleware was unable to completely propagate the common data to the service associated with the application because the call to the "onSessionEnter(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20066 Unable to completely remove common data due to a user-defined error. The middleware was unable to completely remove the common data from to the service associated with the application because the call to the "onSessionLeave(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20067 Unable to invoke the service due to a user-defined error. The middleware was unable to invoke the service associated with the application because the call to the "onInvoke(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20061 *** Unable to load service due to an unexpected error. The middleware was unable to load the service associated with the application because the call to the "loadService(...)" method failed with a user-defined error.
Debug the service and address the issue causing this method to fail.
S20069 *** Unable to un-load service due to an unexpected error. The middleware was unable to un-load the service associated with the application because the call to the "unloadService(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20070 Unable to create service due to an unexpected error. The middleware was unable to create the service associated with the application because the call to the "onCreateService(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20071 Unable to destroy service due to an unexpected error. The middleware was unable to destroy the service associated with the application because the call to the "onDestroyService(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20072 Unable to completely propagate common data due to an unexpected error. The middleware was unable to completely propagate the common data to the service associated with the application because the call to the "onSessionEnter(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20073 Unable to completely remove common data due to an unexpected error. The middleware was unable to completely remove the common data from to the service associated with the application because the call to the "onSessionLeave(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20074 Unable to invoke the service due to an unexpected error. The middleware was unable to invoke the service associated with the application because the call to the "onInvoke(...)" method failed with an unexpected error.
Debug the service and address the issue causing this method to fail.
S20075 Unable to connect with the Service Instance Manager. The service was unable to connect with the Service Instance Manager on the specified port.
This is likely an operating system problem. Check if the port is already being used by another application on the host.
S20076 Unable to create the thread required for the service container. An error occurred while attempting to create a thread for the service container.
This is likely an operating system problem. It is possible that the host has ran out of handles.
S20077 Unable to stop the service driver. The request to stop the service driver could not be completed at this time. It is likely that the service driver wasn't put into run mode by the service container.
Ensure that the ServiceDriver's "run()" method was called before attempting to stop it.
S20078 The service failed to register with the Service Instance Manager. An error occurred while the service was attempting to register with the Service Instance Manager.
This is likely an operating system problem. Check the error details returned for a resolution.
S20079 Callback failed. A failure error code was returned from the provided callback handler.
This type of error code will be treated as a warning level within the API itself. The developer must take the necessary actions to resolve the point of failure if this failure is fatal to the application.
S20080 The connection to the system was broken. A permanent disconnection from the middleware was detected by the client API. It is likely that either a network problem or middleware unavailability has caused this error.
Ensure that the middleware is accessible from the client host or that the middleware is running. If the middleware was relocated and recovered, ensure that the session being operated on is recoverable and was recovered. Check the Session Managers logs for any failures during recovery.
A disconnection from the middleware was detected by the service API. It is likely that either a network problem or middleware unavailability has caused this error. No action required. Service will be restarted upon resource and middleware availability.
S20081 The flag specified while creating the session is invalid. A flag which cannot be interpreted or is ambiguous was presented to the API during the creation of a session.
Ensure that flag (or flag combination is valid). See the API reference guide for the flags allowed.
S20082 An internal method on the action not implemented. A generic error for asserting that only methods intended to be exposed on certain actions are actually accessed by other internal components within the API.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20083 The session is invalid. An attempt was made to access a session, which is no longer available. The session either has already been closed by the client, terminated by the middleware or assigned to a different client connection.
Ensure the session is valid. This can be done by using one of the administrative commands.
S20084 Unable to contact the middleware. The client API was unable to contact the middleware. It is likely that either the middleware is unavailable or not accessible via the network.
Ensure the middleware is running and is accessible from the client host.
S20085 The connection to the system was broken. A permanent disconnection was detected by the API from the middleware and was posted on the provided session callback. It is likely that either a network problem or middleware unavailability has caused this error.
Ensure that the middleware is accessible from the client host or that the middleware is running.
S20086 The callback provided was unnecessary. Based on the flags provided during session creation a callback was not required but one was supplied. This error acts as an assertion to ensure that the developer passes the correct parameter combinations.
Ensure that the correct parameter/flag combinations are being used. These can be found in the API reference guide.
S20087 The fetch attempt is invalid. An attempt is being made to fetch output from an session that was created to expect asynchronous delivery of results.
Ensure that the session was created with the correct flags. These can be found in the API reference guide.
S20088 No exception is associated with this handle. An attempt is being made to retrieve an exception from the handle but none is available because the operation associated with this handle was successfully.
If this is a TaskInputHandle, check whether the task was successfully submitted to the Middleware by using the "getSubmissionState(...)" method before attempting to retrieve an associated exception.
S20089 No output available from this result. An attempt is being made to retrieve an output message from the task result but none is available because the task was un-successfully processed.
Check whether the task was successfully completed or not by using the "isSuccessful(...)" method before attempting to retrieve an associated output message.
S20090 The middleware is unavailable. The middleware cannot be accessed because either the grid or the grid simulation component was unavailable. It is likely that there is an error in the configuration of the cluster.
1. Confirm that the client has been configured correctly.
S20091 An invalid pointer encountered. An internal error occurred when an invalid pointer was returned by one of the API's internal components.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20092 Operation timed-out. No response was received from the middleware within the configured timeout. This usually will occur if the configured value "API_CALL_TIMEOUT" is other than the default of "infinite" and the middleware becomes "unresponsive".
Ensure that the timeout specified is applicable to the nature of the application. For more details about this timeout see the API reference guide.
S20093 Parameter too long. This will usually occur when a string parameter supplied to an API call is beyond its expected length.
Ensure that parameter meets the length specified in the error message returned from the API.
S20094 Parameter out of range. This will usually occur when a numeric parameter supplied to an API call has a value that is outside of its intended range.
Ensure that parameter is within the range specified in the API reference guide.
S20095 *** Task ID for reply duplicated. This is a warning type error and is used internally to monitor the occurrence if task ID duplication.
No action required since this error will never be propagated to the developer's code.
S20096 Failed to complete a security call on the security callback. This will be reported at either log level or API call level when the API fails to complete a call from any of the callback methods.
1. If a custom implementation of the security callback is being used, debug the callback code and resolve the failure.
S20097 Security callback invalid. In some operating systems the API may be afforded the opportunity to intercept an invalid access to the security callback object provided. When this is possible this error will be propagated either to the log or to an API call.
The developer must ensure that a valid callback object is provided and that it has a lifetime longer than the connection object being created.
S20098 Grid information invalid. Invalid information was unexpectedly returned from the grid or grid simulation component.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20099 The Session Director is unavailable. The API was unable to retrieve any information about the Session Director from the grid or grid simulation component. It is likely that the Session Director has not been started or is unavailable.
Ensure that the Session Director has been started.
S20100 Application locator failed. The application could not be located because the call to the grid or the grid simulation component failed. This will usually only occur when there is some error in the configuration.
Please validate all configurations and try the client again.
S20101 The specified configuration file will be used. This is used only for info level logging and is simply used to inform the developer which configuration file will be used by the API for the running instance of the client.
No action required since information is logged for information purposes.
S20102 Default configurations will be used. This is used only for info level logging and is simply used to inform the developer when the API will be using default values for configuration. This will happen only when no configuration file can be located.
No action required since information is logged for information purposes.
S20103 Task result indicated a failure but no exception was propagated. An internal error occurred while attempting to retrieve the exception associated with a failed result because it was not found.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20104 The API is unavailable. An attempt is being made to access the API but it is currently not initialized.
Ensure that initialize was called or that uninitialize was not called before trying to access a feature within the API.
S20105 The session is no longer available. An attempt is being made to access a session which has already been closed by the client application.
Ensure that the client code doesn't attempt to use the session object once it has been closed.
S20106 The session can no longer be operated on because of a lack of available memory. An attempt is being made to access a session which cannot continue because an internal operation failed due to the lack of available memory.
Ensure that the client process has enough memory based on the expected data to be passed between the client and the middleware.
S20107 The connection can no longer be used for communicating with the Middleware because of a lack of available memory. An attempt is being made to access a connection which cannot continue communicating with the Middleware because an internal operation failed due to the lack of available memory.
Ensure that the client process has enough memory based on the expected data to be passed between the client and the middleware.
S20108 An allocation for a buffer failed. An attempt is being made to allocate a buffer which cannot be accommodated at this time.
Ensure that the process has not allocated more virtual address space than is allowed or that the system has an adequate amount of memory.
S20109 An invalid value was specified for a configuration parameter. While reading the configuration file a value was found that is invalid for a particular parameter.
Ensure that the parameters to be used are valid. Valid parameter values can be obtained from the Symphony Reference.
S20110 A parsing error occurred. While parsing the configuration file a critical error was encountered which prevented the API from continuing.
Ensure that the configuration file conforms to XML format and take the necessary action proposed in the specific error message returned to the client.
S20111 A pending connection was cancelled. A connection which was pending was cancelled by an internal component.
See specific reason on error log to identy the reason for the cancellation of the connection.
S20112 An operation was rejected because the component is being shutdown. While an internal component was being shutdown a request was made which couldn't be satisfy.
Ensure that the API is not being uninitialized accidentally.
S20113 The number of tasks received by the session. This is an info level log entry which gives a count of the number of tasks received by the client code.
No action required.
S20114 An internal API object is attempting to access a null message. It is likely that you have already discarded Symphony's copy of your message.
Do not discard your message if you intend on subsequently retrieving it from Symphony.
You have not discarded Symphony's copy of your message. If you have not discarded Symphony's copy of your message, this is an unexpected error. Please contact Platform Technical Support.
S20115 Error retrieving empty message. You cannot retrieve an empty message.
If you intend on retrieving your data, you must ensure that you are serializing something. If you are not sending any data, do not retrieve the message.
S20116 A disconnection was sensed from the Middleware. This info level entry gets logged whenever there is an unexpected break in a connection.
No action required.
S20117 A re-connection to the Middleware was successful. This info level entry gets logged whenever the client successfully re-connects to the Middleware.
No action required.
S20118 Connection attempt status. This info level entry gets logged whenever a reconnection attempt fails. It gives an indication of attempts made and retries outstanding.
No action required.
S20119 Connection attempt status. This info level entry gets logged whenever the final reconnection attempt fails.
No action required.
S20120 EGO handle transition status. This info level entry gets logged whenever there is a successful state of transition for any EGO handles used in the client.
No action required.
S20121 An assertion failed within the API. An assumption within the API has been breached and the expected resulting behavior of the API is unknown in this scenario.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20122 A read operation on a stream failed due to data mismatch. This error will occur when the data type requested from the stream is not the data type that is available.
Ensure that the serialization and de-serialization code match for the message object being marshaled.
S20123 A read operation on a stream failed due to data mismatch. This error will occur when a request is made to read binary data and that request is for less bytes than are available in the next binary block.
Ensure that the serialization and de-serialization code match for the message object being marshaled since partial reads are not supported.
S20124 During a read operation the end of the stream has been encountered. This error will occur when a request is made to read data from a stream but no more is available.
Ensure that the serialization and de-serialization code match for the message object being marshaled it is more than likely that extra data is being read from the stream.
S20125 The service environment was not correctly initialized. This error will occur when the service wasn't initialized correctly.
See the details of the error message thrown for a resolution.
S20126 Physical connection timed-out. No response was received from the middleware while attempting to establish a physical connection. It is likely that there is either a network problem or the SOA Middleware may be unavailable at this time.
Ensure that the middleware and application are configured correctly.
S20127 The connection is no longer available. An attempt is being made to access a connection which has already been closed by the client application or has gone out of scope.
Ensure that the client code doesn't attempt to use the connection object once it has been closed or gone out of scope.
S20128 Connection already shutdown. An operation was rejected because the connection object was already notified about the API being shutdown.
Ensure that the API is not being uninitialized accidentally.
S20129 Unsupported session close flag provided. The requested mode of closing the session is unsupported.
Ensure that the correct mode is being pass to the close method. See API reference for details of supported flags for this operation.
S20130 The cluster config file not found. The cluster config file specified in a cluster URL could not be located.
Ensure that the correct filename was passed to the connect(...) call.
S20131 The cluster URL is invalid. An invalid cluster URL was specified during a connect(...) call.
Ensure that the cluster URL is valid. See the API reference for details on how to create a valid cluster URL.
S20132 The session ID is invalid. An invalid Session ID was passed to the API in an attempt to open a session.
Ensure that the Session ID is valid.
S20133 An error occurred in Service during the onSessionUpdate() call. An error occurred in Service during the onSessionUpdate() call.
Debug the service and address the issue causing this method to fail.
S20134 A fatal error occurred in Service during the onSessionUpdate() call. A fatal error occurred in Service during the onSessionUpdate() call.
Debug the service and address the issue causing this method to fail.
S20135 An error occurred in Service during the onSessionUpdate() call. An error occurred in Service during the onSessionUpdate() call.
Debug the service and address the issue causing this method to fail.
S20136 An unexpected error occurred in Service during the onSessionUpdate() call. An unexpected error occurred in Service during the onSessionUpdate() call.
Debug the service and address the issue causing this method to fail.
S20137 An attempt to update common data failed. Common data could not be updated because the session was created without common data.
Please provide common data upon session creation in order to update the common data later on.
S20138 An unknown session update type was provided. An unknown session update type was provided.
Please check your service code.
S20142 The service instance is exiting because it has lost connection with the service instance manager. The service instance manager has unexpectedly terminated.
No action required.
The application is being disabled/unregistered. No action required.
S20143 Client reconnection failed. The client failed to reconnect to Symphony.
Ensure that the client is running on an operating system with adequate resources.
S20144 The specified deprecated configuration parameter will be ignored. An attempt to apply a deprecated parameter value has failed and will be ignored, because the parameter specified conflicts with other defined values.
You cannot mix parameters that have been deprecated with parameters that have replaced them. Valid parameter values can be obtained from the Symphony Reference.
S20145 Data compression failure. An attempt to compresss the application's data has failed.
Review the error message returned by Symphony and ensure your application is using the data compression feature correctly.
S20146 Data decompression failure. An attempt to de-compresss the application's data has failed.
Review the error message returned by Symphony and ensure your application is using the data compression feature correctly.
S20147 Data compression statistics. This debug level entry gets logged whenever data is compressed and the log level is set to DEBUG. It gives details about the compression operation.

S20148 Data decompression statistics. This debug level entry gets logged whenever data is compressed and the log level is set to DEBUG. It gives details about the decompression operation.

S20149 Failed to update session. The application has made an attempt to update the session, but has failed to specify any attributes to update.
Set at least one attribute to be updated on the SessionUpdateAttributes object before attempting to update the session.
S20150 Client cannot fetch output with TaskOutputFilter when the session flag is SF_FETCH_RESULTS_FROM_CLIENT_CACHE. Client cannot fetch output with TaskOutputFilter when the session flag is SF_FETCH_RESULTS_FROM_CLIENT_CACHE.

S20151 The task ID is invalid. An invalid Task ID was passed to the TaskIdFilter.
Ensure that the Task ID is valid.
S20152 The session is invalid. The session has become invalid because the client has attempted to close it, but the connection between Client and Middleware is broken.
No action needed.
S20153 Unsupported usage of a session close flag. The requested mode of closing the session is not supported when the Direct Data Transfer feature is enabled.
Ensure that the correct mode is being pass to the close method when the Direct Data Transfer feature is enabled for the session. See API reference for details of supported flags for this operation.
S20154 The Direct Data Transfer flag specified is invalid when the Direct Data Transfer feature is enabled. A flag that cannot be interpreted or is ambiguous was presented to the API during the creation of a session when the Direct Data Transfer feature was enabled.
Ensure that the flag (or flag combination) is valid. See the API reference guide for the flags allowed.
S20155 The Direct Data Transfer flag specified is ignored when the Direct Data Transfer feature is enabled. A flag that cannot be interpreted or is ambiguous was presented to the API during the creation of a session when the Direct Data Transfer feature was not enabled.
Ensure that the flag (or flag combination) is valid. See the API reference guide for the flags allowed.
S20156 Could not save a data file for a session that has the Direct Data Transfer feature enabled. Could not save a data file for a session.
Free up some disk space on the drive.
S20157 Service event replay disabled. Service events cannot be replayed for sessions which have enabled the Direct Data Transfer feature.
You must disable the Direct Data Transfer feature and re-run your workload to be able to debug service using the replay log.
S20158 Client failed to connect to Symphony. Client failed to connect to Symphony.
Restart your client and try to connect again.
S20159 The service failed to connect with the client that has the Direct Data Transfer feature enabled. The service cannot connect to the client that has the Direct Data Transfer feature enabled due to a network error.
Ensure that the client host is accessible from the service host.
S20160 The service timed out while trying to connect to the client that has the Direct Data Transfer feature enabled. A network error caused the service to time out while trying to connect to the client that has the Direct Data Transfer feature enabled.
Ensure that the client host has enough system resources and is accessible from the service host.
S20161 Client that has the Direct Data Transfer feature enabled failed to start because of an invalid port number. Client that has the Direct Data Transfer feature enabled cannot start because of an invalid port number.
Ensure that the client starts with a valid port.
S20162 Client that has the Direct Data Transfer feature enabled failed to start because the port is already in use. Client that has the Direct Data Transfer feature enabled cannot start because the port is already in use.
Ensure that the client start up with an unused port.
S20163 Client that has the Direct Data Transfer feature enabled failed to start because of an invalid address. Client that has the Direct Data Transfer feature enabled failed to start because of an invalid address.
Ensure that the configure valid client address.
S20164 Failed to start the client that has the Direct Data Transfer feature enabled with an unknown network error. Failed to start the client that has the Direct Data Transfer feature with an unknown network error.
Ensure that the client host has enough system resources and is accessible from the service host.
S20165 Failed to update the session because the specified attributes cannot be updated at the same time. Failed to update the session because the specified attributes cannot be updated at the same time.
Update the attibutes seperately.
S20166 Invalid service to slot ratio specified. Service to slot ratio must be 1:N or N:1, where N is a positive integer.
Specify a valid service to slot ratio where at least one of the two values is 1.
S20167 Unable to connect with the Service Instance Manager. The service was unable to connect with the Service Instance Manager at the specified endpoint.
This is likely an operating system problem. Check if the port in the URL is already being used by another application on the host.
S20168 The service manager is no longer available. An attempt is being made to access the service manager associated with the service instance after disconnection has completed.
No action required. This may happen during normal shutdown of the service instance.
S20169 The attribute is invalid. An attempt is being made to create an object with an empty name or alias.
Specify a name or alias that is not empty or not null.
S20170 The attribute is invalid. An attempt is being made to create an object name or alias that is too long.
Specify a shorter name or alias.
S20171 The value is invalid. An attempt is being made to set the value on an object to an unsupported value.
Specify a value within the supported range.
S20172 The resource attribute scope is invalid. An attempt is being made to set the scope of a resource attribute to an unsupported value.
Specify a supported scope.
S20173 GUID generator generated a duplicate GUID. GUID generator generated a duplicate GUID. Symphony will generate another one.
No action required.
S20521 Unexpected Synchronization Error. An internal error occurred while attempting manipulate an internal synchronization object by the Boundary Manager component.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20522 Boundary Element attribute missing. A require boundary element attribute was missing from the definition of the element.
Ensure that all attributes are present in the Boundary Element definition.
S20523 Boundary Element attribute type invalid. A boundary element attribute was specified with a value that was of an unexpected type.
Ensure that all attributes have values of the correct type.
S20524 Boundary Element configuration value missing. A required Boundary Element configuration value was missing from the definition of the element.
Ensure that all required configuration values are present in the Boundary Element definition.
S20525 Boundary Element event missing. A required Boundary Element event was missing from the definition of the boundary ranges.
Ensure that all required events are present in the Boundary Element event range definition.
S20526 Boundary Event not mapped. An internal error occurred while attempting to arrive at a level to trigger an event based on the current value. This will only occur when somehow there exists a hole in the definition which was not caught by the element definition validation code.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20527 Data provider already registered. An internal error occurred while attempting to complete the registration of a data provider with the Boundary Manager component.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20528 Unregister failed for data provider. An internal error occurred while attempting to un-register a data provider within the Boundary Manager component because no such provider was registered.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20529 Boundary Manager already initialized. An internal error occurred while attempting to initialize the Boundary Manager component because was already initialized.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20530 Boundary Manager not yet initialized. An internal error occurred while an internal component attempted to access functionality within the Boundary Manager component because it has not yet been initialized.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20531 Functionality not implemented within the Boundary Manager as yet. An internal error occurred while an internal component attempted to access functionality within the Boundary Manager component which has not yet been implemented.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20532 No such element defined. An internal error occurred while an internal component attempted to access the definition of a Boundary Element which was not defined.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20533 Invalid Boundary Manager handle. An internal error occurred while an internal component presented an invalid handle to the Boundary Manager.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20534 Data value out of range. An internal error occurred while an internal component presented a data value for a Boundary Element which was outside of the range specified within the definition of the boundary element.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20535 Global configuration item ignored. An internal error occurred because an unknown global configuration parameter was specified within the configuration for the Boundary Manager.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20536 Shutdown in progress. An internal error occurred while an internal component attempted to access certain functionality within the Boundary Manager while it was being shutdown.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20537 Unable to reserve memory. An internal component within the Boundary Manager was unable to reserve enough memory.
Ensure that there is enough memory available on the host to satisfy the configured amount.
S20538 General internal error. A general unexpected internal error occurred within the Boundary Manager. See error message for details.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20539 The middleware has been halted. The middleware has been halted because the resource specified within the error message has been exhausted and no workload can safely processed while the specified resource is at this level.
1. An attempt should be made by the administrator to make more of the exhausted resource available.
S20540 Boundary Data collection failed. An internal error occurred while the Boundary Manager attempted to collect data related to a specific Boundary Element.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20541 Boundary Event trigger failed. An internal error occurred while the Boundary Manager attempted to trigger an event by notifying all registered internal component about a breach of a boundary.
This type of error may be triggered when the Middleware is in different stages. The specific error details provided willl usually give enough context to the message.
S20542 Shutdown signal failed. An internal error occurred while the Boundary Manager attempted dispatch a shutdown signal to all registered internal components.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.
S20543 Boundary Event definition value out of range. The value specified in the configuration for the triggering of a boundary event falls outside of the range of acceptable values as defined within the Boundary Element definition.
Ensure that all values defined for boundary event triggers are within the valid range.
S20544 Boundary Event definition value overlaps. The value specified in the configuration for the triggering of a boundary event overlaps with another value specified for the same Boundary Element.
Ensure that all values defined for boundary event triggers do not overlap.
S20545 The Middleware has resumed. The middleware has resumed operations because the resource specified in the error message has returned to acceptable levels.
No action required.
S20751 This message will be triggered when the specified class cannot be loaded by the JVM. The specified class cannot be loaded by the JVM.
Contact Platform Technical Support.
S20752 This message will be triggered when the specified variable cannot be found by the JVM. The specified variable cannot be found by the JVM.
Contact Platform Technical Support.
S20753 This message will be triggered when the specified method cannot be found by the JVM. The specified method cannot be found by the JVM.
Contact Platform Technical Support.
S20754 This message will be triggered when the Java process cannot allocate the amount of memory needed. The process cannot allocate the amount of memory needed.
Tune the JVM heap space for your process.
S20759 This message will be triggered when an exception occurred on the invocation of a callback method. An exception occurred on the invocation of a callback method.
Review your callback logic.
S20760 This message will be triggered when an exception occurred on the invocation of a user-defined method. An exception occurred on the invocation of a user-defined method.
Review your logic.
S20761 This message will be triggered when the Callback Manager experiences an unexpected synchronization error. The Callback Manager has experienced an unexpected synchronization error.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S20762 This message will be triggered when the Callback Manager tries to consume from an empty event queue. The Callback Manager has tried to consume from an empty event queue.
Please contact Platform Technical Support.
S20763 This message will be triggered when the input parameter for Java API is invalid. The client code has tried to pass an invalid parameter to the Java API.
Please check the parameter passed to Symphony Java API.
S20764 This message will be triggered when the input parameter for Java API is an unexpected null reference. The client code has tried to pass an unexpected null reference to the Java API.
Please check the parameter passed to Symphony Java API.
S20765 This message will be triggered when the user attempts to deserialize their input/output and the middleware has no data. The user has tried to deserialize their input/output and the middleware has no data.
Please contact Platform Technical Support.
S50005 This message will be triggered when an admin CLI cannot connect to Symphony on the port specified in the configuration file. All the admin CLI need to connect to Symphony on the port specified in the configuration file. If there is a network problem or the port number is wrongly defined or Symphony has not been started, CLI will fail with this error.
Please check the Admin port number specified in the vem_resource.conf if running Symphony DE, or sd.xml if running Symphony on EGO. Then try to start the session director again.
S50841 This message will be triggered when CLI cannot connect to Repository Service. Failed to connect to Repository Service.
Please make sure the URL of Repository Service is correct and Repository Service is running.
S50842 This message will be triggered when CLI cannot create file on file system. Failed to create file on the file system.
Please make sure the file system is writeable.
S50843 This message will be triggered when CLI cannot read file from file system. Failed to read file from the file system.
Please make sure the file system is readable.
S50846 This message will be triggered when CLI cannot upload application package to repository service. Failed to upload application package to Repository Service.
Please use soamunreg the application if it is registered successfully.
Failed to read the uploading file from local file system. Please make sure the uploading file is readable.
S50849 This message will be triggered when CLI cannot remove application package from repository service. Failed to remove application package from Repository Service.

S50852 This message will be triggered when CLI cannot get repository information from Repository Service. Failed to get repository information from Repository Service.

S50855 This message will be triggered when CLI cannot download application package from repository service. Failed to download application package from Repository Service.

S50860 This message will be triggered when CLI cannot communicate with Repository Service. Failed to communicate with Repository Service.
Check if Repository Service is still alive.
S60009 This message will be triggered when an invalid filter string was specified. An invalid filter string was specified.
Check the filter string and correct it.
S60022 This message is triggered when a timer to execute the specified function expires and the function pointer is null. A timer to execute the specified function expired and the function pointer is null.
Send the log that contains this message to Platform Support for analysis.
S60023 This message is triggered when a user attempts to use a product feature without a license to use this feature. User has attempted to use a product feature without a license to use this feature.
Obtain a license from Platform Computing to gain access to this feature.
S60025 This message is triggered when the system fails to parse a preference string provided by the application. The system encountered an error while attempting to parse the preference string supplied by the application.
Review the specific details in the error message which will give a more specific course of action.
S60026 This message is triggered when the system fails to load the external plugin module. The system encountered an error while attempting to load the external plugin module specified in the application profile.
Check the plugin module specified in the application profile.
S60027 This message is triggered when the system has a problem interacting with the external module. The system encountered an error while attempting to interact with the external module. This could be caused by a nonresponsive plugin module
Check the plugin module specified in the application profile.
S60028 This message is triggered when the system receives a nonvalid protocol response from the external plugin module. The external plugin module used a nonvalid protocol to communicate with the system.
Check the plugin module specified in the application profile.
S60029 This message is triggered when the external plugin module responded unsuccessfully to a query for an attribute from the system. The system received an unsuccessful response from the external plugin module.
Check the plugin module specified in the application profile.
S60030 This message is triggered when the external plugin module responded unsuccessfully for the initilization response. The system received an unsuccessful response from the external plugin module.
Check the plugin module specified in the application profile.
S60031 This message is triggered when the SSMResPubPluginCmd is specified but the enableResourcePreferenceEvaluations is set to false in the application profile. If SSMResPubPluginCmd is specified but enableResourcePreferenceEvaluations is set to false in the application profile, external plugin module will not be started.
Set enableResourcePreferenceEvaluations to true in the application profile.
S63001 This message will be triggered when a persistent file cannot be closed. Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Disk quota exceeded.
Remove any unnecessary files from the file system to make space for the persist file.
Permission denied. The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
S63002 This message will be triggered when a persistent file cannot be written. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S63003 This message will be triggered when a persistent file cannot be renamed. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. File is in use.
The given file is currently in use, and cannot be renamed while in use. Close the file.
S63004 This message will be triggered when a persistent file cannot be removed from the file system. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. File is in use.
The given file is currently in use, and cannot be deleted while in use. Close the file.
S63005 This message will be triggered when a persistent file cannot be read. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S63006 This message will be triggered when an iterator of the specified invalid type is requested from within the Middleware. The following are examples of some common scenarios. An iterator of the specified invalid type is requested from within the Middleware.
Please contact Platform Technical Support.
S63007 This message will be triggered when a deserialization error occurred while reading back the given persistent file. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
File is corrupt. The data contained within the file is lost. You may want to contact your IT administrator to check on the health of your file system's hardware. If all is well with the hardware, delete the file and continue.
S63008 This message will be triggered when a persistent file cannot be opened for writing. Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S63009 This message will be triggered when a persistent file cannot be opened for reading. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S63010 This message will be triggered when a Middleware object of the specified invalid type is requested. An IPersistable of the specified invalid type is requested from within the Middleware.
Please contact Platform Technical Support.
S63011 This message will be triggered when a persistent file does not exist. The given persistent file does not exist.
No action necessary.
S65001 This message will be triggered when session director or session manager start up. SOAM_HOME environment variable is not defined.
Define the SOAM_HOME environment variable to the Symphony DE installation directory.
S65002 This message will be triggered when session director or session manager start up. vem_resource.conf file is not found.
Check path the file $SOAM_HOME/conf/vem_resource.conf.
Command do not have permissions to read the vem_resource.conf file. Check permissions of the file $SOAM_HOME/conf/vem_resource.conf and command running.
S65003 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check the previous error messages for tag name error generated.
S65004 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the hosttype tag.
S65005 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the resreq tag.
S65006 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the standalone tag.
S65007 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the req tag.
S65008 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the [name] attribute.
S65009 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the hosttypes tag in the vem_resource.conf file.
S65010 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the env tag in the vem_resource.conf file.
S65011 This message will be triggered when session director or session manager start up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the startcmd tag in the vem_resource.conf file.
S65012 This message will be triggered when function call received a NULL handle. The handle received by function is NULL.
Check EGO log files for error messages.
S65013 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_handle structure parameters in VEM API Stub component.
The system is unhealthy, restart the system.
S65014 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_handle structure parameters in VEM API Stub component.
The system is unhealthy, restart the system.
S65015 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_handle structure parameters in VEM API Stub component.
The system is unhealthy, restart the system.
S65016 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_handle structure parameters in VEM API Stub component.
The system is unhealthy, restart the system.
S65017 This message will be triggered when the VEM API Stub component cannot initiate connection with start_agent daemon. VEM API Stub component fails to create a send socket on the port specified in the configuration file.
Release some System Resource.
S65018 This message will be triggered when the VEM API Stub component cannot connect with start_agent daemon. VEM API Stub component fails to create a connection to start_agent daemon.
Check start_agent daemon process is running. Start start_agent on target host.
S65019 This message will be triggered when the VEM API Stub component cannot send command to start_agent daemon. VEM API Stub component fails to send command to start_agent daemon.
Check start_agent daemon process is running. Start start_agent daemon on target host.
S65020 This message will be triggered when the VEM API Stub component cannot receive response from start_agent daemon. VEM API Stub component fails to receive response from start_agent daemon.
Check s agent.hostname.log file on target host.
S65021 This message will be triggered when VEM API Stub received a message from start agent that process on remote host cannot be created. Process was not started on remote host.
Check agent.hostname.log file on the host.
S65022 This message will be triggered when VEM API Stub closes socket. Failed to close socket.
The system is unhealthy, restart the system.
S65023 This message will be triggered when session director or session manager start up. vem_resource.conf file is not found.
Check path the file $SOAM_HOME/conf/vem_resource.conf.
Command do not have permissions to read the vem_resource.conf file. Check permissions of the file $SOAM_HOME/conf/vem_resource.conf and command running.
S65024 This message will be triggered when session director or session manager start up. start_agent daemon failed to get port to listen from vem_resource.conf.
Check spelling of current host name in the $SOAM_HOME/conf/vem_resource.conf file.
S65025 This message will be triggered when VEM API Stub is initiated. Vem Api Stub failed to get port to connect from vem_resource.conf.
Define the port to connect for Vem Api Stub in the $SOAM_HOME/conf/vem_resource.conf file as an integer.
S65026 This message will be triggered when VEM API Stub is initiated. VEM API Stub failed to get hostname from vem_resource.conf.
Define the hostname in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S65028 This message will be triggered when VEM API Stub is initiated.. VEM API Stub failed to get OS type from vem_resource.conf.
Define the OS type in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S65029 This message will be triggered when VEM API Stub is initiated.. VEM API Stub failed to get CPU factor from vem_resource.conf.
Define CPU factor in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S65030 This message will be triggered when VEM API Stub received unregistered client name. VEM API Stub failed to find specified client name registered clients map.
The system is unhealthy, restart the system.
S65031 This message will be triggered when VEM API Stub cannot find specified allocation ID in internal map. VEM API Stub failed to find specified allocation ID in internal map.
Check other errors in the log file.
S65032 This message will be triggered when VEM API Stub cannot find specified container ID in internal map. VEM API Stub failed to find specified container ID in internal map.
The system is unhealthy, restart the system.
S65033 This message will be triggered when VEM API Stub cannot connect to start_agent daemon. VEM API Stub failed to connect to working start_agent daemon to send command.
Check that the start_agent process is running on the host.
S65033 This message will be triggered when VEM API Stub received response from start_agent daemon. VEM API Stub failed to start a new session manager or SIN on specified hosts.
Check Agent log file for more details.
S65035 This message will be triggered when an invalid input parameter passed into the interface of VEM API Stub. Failed to call an interface of VEM API Stub component.
The system is unhealthy, restart the system.
S65036 This message will be triggered when an invalid input parameter passed into the interface of VEM API Stub. Failed to call an interface of VEM API Stub component.
The system is unhealthy, restart the system.
S65038 This message will be triggered when an invalid input parameter passed into the interface of VEM API Stub. Failed to call an interface of VEM API Stub component.
The system is unhealthy, restart the system.
S65039 This message will be triggered when an invalid input parameter parsed from resource file. Failed to load resource information.
Check previous errors in the log file.
S65040 This message will be triggered when an invalid input parameter passed into the interface of VEM API Stub. Failed to call an interface of VEM API Stub component.
Change the client name in application profile.
S65041 This message will be triggered when Thread Pool cannot be created. Out of Thread Resource.
Release some System Resource.
S65042 This message will be triggered when VEM API Stub cannot find client name ID in internal map. VEM API Stub failed to find specified client name in internal map.
Contact Platform technical support.
S65043 This message will be triggered when an invalid input parameter passed into the function of VEM API stab component. Failed to path through a check of input vem_registerreq structure parameters in VEM API stub component.
The system is unhealthy, restart the system.
S65044 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_registerreq structure parameters in VEM API stub component.
The system is unhealthy, restart the system.
S65044 This message will be triggered when an invalid input parameter passed into the function of VEM API Stub component. Failed to path through a check of input vem_registerreq structure parameters in VEM API Stub component.
The system is unhealthy, restart the system.
S65046 This message will be triggered when data cannot be send to thread queue. Out of Thread Resource.
Release some System Resource.
S65047 This message will be triggered when an VEM API Stub look for the specified container ID . Failed to find container ID in the internal map.
The system is unhealthy, restart the system.
S65048 This message will be triggered when VEM API stub starts up. SOAM_HOME environment variable is not defined.
Define the SOAM_HOME environment variable to the Symphony DE installation directory.
S65049 This message will be triggered when the vem_resource.conf is missing "service" element. Agent detected vem_resource.conf is missing "service" element.
Please add "service" element to specify session director.
S65050 This message will be triggered when the vem_resource.conf is missing "rs" element. Agent detected vem_resource.conf is missing "rs" element.
Please add "rs" element to specify Repository Service.
S65051 This message will be triggered when the vem_resource.conf is missing "hostname" element inside "rs" element. Agent detected vem_resource.conf is missing "hostname" element inside "rs" element.
Please add "hostname" tag to specify the host name of Repository Service.
S65052 This message will be triggered when the vem_resource.conf is missing "port" element inside "rs" element. Agent detected vem_resource.conf is missing "port" element inside "rs" element.
Please add "port" element to specify the port number of Repository Service.
S65053 This message will be triggered when the vem_resource.conf is missing "startcmd" element inside "rs" element. Agent detected vem_resource.conf is missing "startcmd" element inside "rs" element.
Please add "port" element to specify the port number of Repository Service.
S65055 This message will be triggered when the VEM API Stub detect the no SIM configured to start in the cluster. SOAM will not start any SIMs on this cluster.
Check the vem_resource.conf file and configure SIM to start.
S65056 This message will be triggered when VEM API Stub is initiated. VEM API Stub is getting an invalid configuration from vem_resource.conf.
Check the configuration in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S70001 This message will be triggered when start_agent daemon starts up. SOAM_HOME environment variable is not defined.
Define the SOAM_HOME environment variable to the Symphony DE installation directory.
S70003 This message will be triggered when start_agent daemon starts up. start_agent daemon failed to get port to listen from vem_resource.conf.
Define the port to listen in the $SOAM_HOME/conf/vem_resource.conf file.
S70004 This message will be triggered when start_agent daemon starts up. start_agent daemon failed to create start session director command object to start session director daemon.
Reboot computer host.
S70005 This message will be triggered when start_agent daemon starts up. At start up start_agent daemon fails to create a listening socket on the port specified in the configuration file.
Please change the start_agent daemon port number specified in the vem_resource.conf if running Symphony. Then try to start start_agent daemon again.
S70006 This message will be triggered when start_agent daemon starts up. start_agent daemon failed to create Command object to shutdown Symphony.
Reboot computer host. Contact Platform technical support.
S70008 This message will be triggered when start_agent daemon starts up. start_agent daemon failed to create Command object.
Check previous errors to find what command was failed to create.
S70009 This message will be triggered when Startup Agent starts up. The vem_resource.conf file is empty.
Define hosts in vem_resource.conf that belong to the cluster.
S70010 This message will be triggered when start_agent daemon starts up. vem_resource.conf file is not found.
Check path the file $SOAM_HOME/conf/vem_resource.conf.
Command do not have permissions to read the vem_resource.conf file. Check permissions of the file $SOAM_HOME/conf/vem_resource.conf and command running.
S70011 This message will be triggered when Startup Agent starts up. start_agent daemon failed to get port to listen from vem_resource.conf.
Define a valid integer for Startup Agent listening port in the $SOAM_HOME/conf/vem_resource.conf file.
S70012 This message will be triggered when Startup Agent starts up. start_agent daemon failed to get hostname from vem_resource.conf.
Define the hostname in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S70014 This message will be triggered when Startup Agent starts up. start_agent daemon failed to get OS type from vem_resource.conf.
Define the OS type in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S70015 This message will be triggered when Startup Agent starts up. start_agent daemon failed to get CPU factor from vem_resource.conf.
Define CPU factor in the $SOAM_HOME/conf/vem_resource.conf file in specified line.
S70016 This message will be triggered when Startup Agent try to start a new process. start_agent daemon failed to spawn a new process, when it receives the command from VEM API Stub.
Check specified command line.
S70017 This message will be triggered when Startup Agent try to start a new process. start_agent daemon failed to spawn a new process, when it receives the command from VEM API Stub. Command line parameters can be wrong.
Check command line options passed to new process. Check executables names in Application profile.
S70018 This message will be triggered when Startup Agent try to send a response to the client (session director or session manager) about result of execution command. It is a socket error. Failed send information from the socket. Client can be down. Communication is broken.
Check that client is up.
S70020 This message will be triggered when start_agent daemon starts up with -s command line option. start_agent daemon failed to connect to working start_agent daemon to send command for shutdown.
Check that the start_agent process is running on the host and use the soamshutdown command again.
S70021 This message will be triggered when start_agent daemon starts up with -s command line option. start_agent daemon failed to send shutdown Symphony command to working start_agent.
Check that the start_agent process is running on the host and use the soamshutdown command again.
S70022 This message will be triggered when start_agent daemon starts up with -s command line option. start_agent daemon failed to shutdown Symphony.
Manually kill the RS, session director, session manager, SIM processes.
S70024 This message will be triggered when start_agent daemon starts up. start_agent daemon failed to set up environment variable.
Check permissions of the user that starts up Symphony.
S70030 This message will be triggered when start_agent daemon tries to start up session director. start_agent daemon failed to start session director daemon.
Check the session director log file for more detail. Check previous error messages.
S70031 This message will be triggered when start_agent daemon tries to spawn a new session director process. start_agent daemon failed to spawn a new session director process.
Check previous error messages.
S70032 This message will be triggered when start_agent daemon tries to kill a spawned process. Failed to find process ID to kill process for the specified container ID.
Check previous error messages. May be process was previously killed.
S70033 This message will be triggered when start_agent daemon tries to kill a spawned process. Failed terminate with internal process. The process could exit already.
Check previous error messages.
S70034 This message will be triggered when start_agent daemon receives command. Error receiving data from socket.
The system is unhealthy, restart the system.
S70035 This message will be triggered when start_agent daemon parses received command. Failed to recognize received command. Internal protocol was broken.
Contact Platform technical support.
S70036 This message will be triggered when start_agent daemon starts up. vem_resource.conf file is not found.
Check path the file $SOAM_HOME/conf/vem_resource.conf.
Command do not have permissions to read the vem_resource.conf file. Check permissions of the file $SOAM_HOME/conf/vem_resource.conf and command running.
S70037 This message will be triggered when START AGENT starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check the previous error messages for tag name error generated.
S70038 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the hosttype tag.
S70039 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the resreq tag.
S70040 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the standalone tag.
S70041 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the req tag.
S70042 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Check, add or fix the [name] attribute.
S70043 This message will be triggered when start_agent daemon starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the hosttypes tag in the vem_resource.conf file.
S70044 This message will be triggered when start_agent starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the env tag in the vem_resource.conf file.
S70045 This message will be triggered when start_agent starts up. File format of vem_resource.conf file is wrong.
Check format of the vem_resource.conf file. Specify the startcmd tag in the vem_resource.conf file.
S70046 This message will be triggered when start_agent starts up. start_agent failed to get port to listen.
Check spelling of current host name in the vem_resource.conf file.
S70047 This message will be triggered when start_agent start a new process. SOAM_SERVERDIR environment variable is not defined.
Define the SOAM_SERVERDIR environment variable to the Symphony DE server directory.
start_agent does not have a permissions to access SOAM_SERVERDIR. Grant permissions to start_agent.
S70048 This message will be triggered when start_agent start a new process. Failed to find the executable to run.
Check Service attribute in startCmd of your application profile.
S70049 This message will be triggered when start_agent execute command. User do not have permissions to access directory defined by SOAM_SERVERDIR environment variable.
Check permissions for directory defined by SOAM_SERVERDIR environment variable.
S70050 This message will be triggered when the vem_resource.conf is missing "service" element. Agent detected vem_resource.conf is missing "service" element.
Please add "service" element to specify session director.
S70051 This message will be triggered when the vem_resource.conf is missing "rs" element. Agent detected vem_resource.conf is missing "rs" element.
Please add "rs" element to specify Repository Service.
S70052 This message will be triggered when the vem_resource.conf is missing "hostname" element inside "rs" element. Agent detected vem_resource.conf is missing "hostname" element inside "rs" element.
Please add "hostname" tag to specify the host name of Repository Service.
S70053 This message will be triggered when the vem_resource.conf is missing "port" element inside "rs" element. Agent detected vem_resource.conf is missing "port" element inside "rs" element.
Please add "port" element to specify the port number of Repository Service.
S70054 This message will be triggered when the vem_resource.conf is missing "port" element inside "rs" element. Agent detected vem_resource.conf is missing "port" element inside "rs" element.
Please add "port" element to specify the port number of Repository Service.
S70063 This message will be triggered when the start_agent starts session director. Failed to get command line to launch Session Director. Information in the $SOAM_HOME/conf/vem_resource.conf is wrong.
Add a valid host type to the hosttype tag.
S70075 This message will be triggered when the start_agent loads cluster configuration from the vem_resource.conf file. Failed to get command valid number of max number of SSMs SD can start.
Add a valid number to the "max number of SSMs SD can start" section of the specified host.
S70076 This message will be triggered when the start_agent loads cluster configuration from the vem_resource.conf file. Failed to get command valid number of max number SIMs SSM can start.
Add a valid valid number to the "max number of SIMs SSM can start" section of the specified host.
S70077 This message will be triggered when start_agent daemon starts up with -s command line option. start_agent daemon failed to shutdown Symphony.
Manually kill the RS, session director, session manager, SIM processes.
S70079 This message will be triggered when start_agent daemon starts up. Parsing error of the vem_resource.conf file.
Check format of the vem_resource.conf file.
S70080 This message will be triggered when start_agent start a new process. BINARY_TYPE environment variable is not defined.
Define the BINARY_TYPE environment variable to the Symphony DE binary directory.
start_agent does not have a permissions to access BINARY_TYPE. Grant permissions to start_agent.
S75001 This message will be triggered when a Symphony detects a daemon died and try to restart it. Session Director detected session manager died, and tried to restart it.
Monitor whether session manager process can be started successfully within expected duration.
Session manager detected SIM died, and try to restart it. Monitor whether SIM process can be started successfully within expected duration.
S75002 This message will be triggered by session manager when its initialization is done successfully.

S75003 This message will be triggered by session director when it detects session manager process is gone. Session manager crashed when exception happened.
1. Monitor the system auto-recovery process. 2. Check Symphony events/logs to find the clue. 3. Call platform support if problem not solved.
Session manager is shutdown by administrator. none
S75004 This message will be triggered when a session manager reaches its high memory water mark. Current workload (sessions and tasks) is overloading system.
1. Check the memory usage of session manager. 2. suspend/kill some sessions if necessary.
Session manager host has less memory than workload requires. Replace session manager host with more memory.
S75005 This message will be triggered when a session manager reach its low memory water mark.

S75006 This message will be triggered by SIM when its initialization is done successfully.

S75007 This message will be triggered by session manager when it detects SIM process is gone. SIM crash when exception happened.
1. Monitor the system auto-recovery process. 2. Check Symphony events/logs to find the clue. 3. Call platform support if problem not solved.
S75008 This message will be triggered when service instance failed to be created. Service program cannot startup successfully due to dependent file missed.
Check the dependency of service program on that host.
Service program timed out to register with SIM. 1. Check service program to make sure ServiceContainer.run() method is called as early as possible. 2. Configure a longer duration for service register if necessary.
Service program failed in method createService(). 1. Check events to get more info about what is wrong. 2. Debug service program to fix the application bug.
S75009 This message will be triggered when service timed out in its method call.

S75010 This message will be triggered when service exit in its method call.

S75011 This message will be triggered when service throw failure exception in its method call.

S75012 This message will be triggered when service throw fatal exception in its method call.

S75013 This message will be triggered when a host is blocked.

S75014 This message will be triggered when SIM take the action based on user's control code.

S75015 This message will be triggered when session manager detected a client connection lost.

S75016 This message will be triggered when session manager policy found the low task water mark has reached.

S75017 This message will be triggered when a session aborted in session manager.

S75018 This message will be triggered when a open session suspended in session manager.

S75019 This message will be triggered when a suspended session resumed in session manager.

S75020 This message will be triggered when the priority of a session changed in session manager.

S75021 This message will be triggered when a task timed out in service invoke.

S75022 This message will be triggered when service exit in invoke.

S75023 This message will be triggered when service throw exception in invoke.

S75024 This message will be triggered when service throw fatal exception in invoke.

S75025 This message will be triggered when a boundary has been breached for any element defined within the Boundary Manager.

S75026 reserved for Boundary Manager.

S75027 reserved for Boundary Manager.

S75028 This message will be triggered when Symphony failed to read common data of session from its persistent storage.

S75029 This message will be triggered when Symphony failed to read input data of task from its persistent storage.

S75030 This message will be triggered when Symphony failed to read output data of task from its persistent storage.

S75031 This message will be triggered when Symphony failed to write common data of session into its persistent storage.

S75032 This message will be triggered when Symphony fails to write input data of task into its persistent storage.

S75033 This message will be triggered when Symphony failed to write output data of task into its persistent storage.

S75034 This message will be triggered when Symphony failed to write the session object itself into its persistent storage.

S75035 This message will be triggered when Symphony failed to write the session object itself into its persistent storage.

S75036 This message will be triggered when session manager process is going to exit. This message logged with an INFO log level. No action required.

S75037 This message will be triggered when sim fails to deploy the service package. See the ssm log for more information.

S75038 This message will be triggered when Symphony failed to write the session metadata object into its persistent storage.

S75039 This message will be triggered when a host is blocked because the session manager receives a resource but there is no osType section specified in the application profile for this type of resource. In the SIM section of the application profiles there is a mismatch between the type of resources requested (resReq) and the OS types (osType) defined.
Please make sure there is one osType section defined for every type of resources matches resReq.
Symphony receives a resource of a different type than the ones requested. This is an internal error. Please provide the complete error message to Platform Support for help.
S75040 This message will be triggered when session director receives a resource but there is no osType section specified in the application profile for this type of resource. In the SSM section of the application profiles there is a mismatch between the type of resources requested (resReq) and the OS types (osType) defined.
Please make sure there is one osType section defined for every type of resources matches resReq.
Symphony receives a resource of a different type than the ones requested. This is an internal error. Please provide the complete error message to Platform Support for help.
S75041 This message is triggered when the onInvoke method successfully returns.

S75042 This message is triggered when the onSessionEnter method successfully returns.

S75043 This message is triggered when the methods onCreateService or onSessionLeave successfully return, and the system takes the configured action on the service instance based on the configured control code.

S75044 This message is triggered on timeout of the onInvoke method.

S75045 This message is triggered on timeout of the onSessionEnter method.

S75046 This message is triggered on timeout of the Register, onCreateService, or onSessionLeave methods.

S75047 This message is triggered when the service exits in the onInvoke method.

S75048 This message is triggered when the service exits in the onSessionEnter method.

S75049 This message is triggered when the service exits in its the Register, onCreateService, or onSessionLeave methods.

S75050 This message is triggered when the service throws a failure exception in the onInvoke method.

S75051 This message is triggered when the service throws a failure exception in the onSessionEnter method.

S75052 This message is triggered when the service throws a failure exception in the onCreateService or onSessionLeave methods.

S75053 This message is triggered when the service throws a fatal exception in the onInvoke method.

S75054 This message is triggered when the service throws a fatal exception in the onSessionEnter method.

S75055 This message is triggered when the service throws a fatal exception in the onCreateService or onSessionLeave methods.

S75056 This message will be triggered when a task killed in session manager.

S75057 This message will be triggered when the session director has exited because it failed to accept client connections on the configured port. Port is in use.
Specify a port that is not in use. For Symphony, modify the value of SD_SDK_PORT in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again. For Symphony DE, modify the value of the SD_SDK port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
Port is invalid. Specify a port that is in the range of 1 - 65535. For Symphony, modify the value of SD_SDK_PORT in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again. For Symphony DE, modify the value of the SD_SDK port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
S75058 This message will be triggered when the session director has exited because it failed to accept administrative requests on the configured port. Port is in use.
Specify a port that is not in use. For Symphony, modify the value of SD_ADMIN_PORT in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again. For Symphony DE, modify the value of the SD_ADMIN port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
Port is invalid. Specify a port that is in the range of 1 - 65535. For Symphony, modify the value of SD_ADMIN_PORT in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again. For Symphony DE, modify the value of the SD_ADMIN port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
S75059 This message will be triggered when session director has exited because it cannot access the application profiles directory upon startup. The session director is running with the same permissions as the user who started Symphony. This user does not have write access for the specified disk locations.
Check the write permissions for the specified user for the directory specified in the error message.
The specified directory is an absolute path, where the root of that directory is not accessible. The file system may not be mounted. Make sure that the file system is mounted and is accessible to the specified user from the SD host.
The specified directory is an absolute path, where the root of that directory is not accessible. The share may not be accessible. Make sure that the share is accessible to the specified user from the SD host.
The specified directory is an absolute path, where the root of that directory does not exist. Check for the existence of the root of the specified directory.
The wrong directory was specified. Modify the value of SD_APP_PROFILE_DIR in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again.
S75061 This message will be triggered when the repository service has exited because it failed to accept requests on the configured port. Port is in use.
Specify a port that is not in use. For Symphony, modify the value of REPOSITORY_SERVICE_PORT in $EGO_TOP/eservice/esc/conf/services/rs.xml, then try to start the repository service again. For Symphony DE, modify the value of the RS_DEPLOY port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
Port is invalid. Specify a port that is in the range of 1 - 65535. For Symphony, modify the value of REPOSITORY_SERVICE_PORT in $EGO_TOP/eservice/esc/conf/services/rs.xml, then try to start the repository service again. For Symphony DE, modify the value of the RS_DEPLOY port number specified in $SOAM_HOME/conf/vem_resource.conf, then try to start Symphony DE cluster again.
S75062 This message will be triggered when repository service has exited because it cannot access its storage directory upon start up. The session director is running with the same permissions as the user who started Symphony. This user does not have write access for the specified disk locations.
Check the write permissions for the specified user for the directory specified in the error message.
The specified directory is an absolute path, where the root of that directory is not accessible. The file system may not be mounted. Make sure that the file system is mounted and is accessible to the specified user from the SD host.
The specified directory is an absolute path, where the root of that directory is not accessible. The share may not be accessible. Make sure that the share is accessible to the specified user from the SD host.
The specified directory is an absolute path, where the root of that directory does not exist. Check for the existence of the root of the specified directory.
The wrong directory was specified. Modify the value of SD_PERSISTENT_DIR in $EGO_TOP/eservice/esc/conf/services/sd.xml, then try to start the session director again.
S75064 This message will be triggered when the debug setting for the service "customize", and the SIM detects an event for which the customizedDebugAction is something other than "none". Debug setting for the service is "customize", and the SIM detects an event for which the customizedDebugAction is "writeServiceEventReplayFiles". Symphony generates an environment script and a service event replay log for the detected event.
Run the environment script on the command line. From the same shell, launch a debugger and run your service in the debugger to try to reproduce the problem.
S75065 This message will be triggered when the service instance manager times out on process startup and attribute blockHostOnTimeout is set to true in application profile

S75066 This message will be triggered when Symphony failed to read a common data update from its persistent storage.

S75067 This message will be triggered when Symphony failed to write a common data update into its persistent storage.

S75068 This message will be triggered when Symphony failed to write a common data update object into its persistent storage.

S75069 This message will be triggered when the application profile is updated

S75070 This message will be triggered when Symphony failed to write the session object itself into its persistent storage.

S75071 This message is triggered when the SessionUpdate method successfully returns.

S75072 This message is triggered when the SessionUpdate method times out.

S75073 This message is triggered when the service exits during an invocation of the SessionUpdate method.

S75074 This message is triggered when the service throws a failure exception in the SessionUpdate method.

S75075 This message is triggered when the service throws a fatal exception in the SessionUpdate method.

S75076 This message will be triggered when Symphony failed to write session journal externsion into its persistent storage.

S75077 This message will be triggered when Symphony failed to read session journal extension from its persistent storage.

S75078 This message will be triggered when Symphony failed to write task journal extension into its persistent storage.

S75079 This message will be triggered when Symphony failed to read task journal extension from its persistent storage.

S80001 This message will be triggered when a string cannot be converted to a valid timestamp. User renamed a file with a previously valid timestamp.
Change the file name back. Please do not alter the files generated by the Middleware.
Internal error. Please contact Platform Technical Support.
S80002 This message will be triggered when a History file cannot be closed. Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Disk quota exceeded.
Remove any unnecessary files from the file system to make space for the persist file.
Permission denied. The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
S80003 This message will be triggered when a History file cannot be renamed. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. File is in use.
The given file is currently in use, and cannot be renamed while in use. Close the file.
S80004 This message will be triggered when a History file cannot be written. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given file. Change the user, or grant appropriate file access to the user.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S80005 This message will be triggered when a History file cannot be read. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S80006 This message will be triggered when a History file was supposed to be read, but no longer exists. The file was automatically deleted by the Middleware because it is older than the specified lasting period.
No action necessary.
The file was deleted by a user. No action necessary.
S80007 This message will be triggered when the History Manager cannot queue a request. The History Manager cannot queue a request.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S80008 This message will be triggered when the History Manager cannot start its worker thread(s). The History Manager cannot start its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S80009 This message will be triggered when the History Manager cannot join with its worker thread(s). The History Manager cannot join with its worker thread(s).
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S80010 This message will be triggered when an invalid History table is requested from within the Middleware. An invalid History table is requested from within the Middleware.
Please contact Platform Technical Support.
S80011 This message will be triggered when a History file cannot be removed from the file system. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. File is in use.
The given file is currently in use, and cannot be deleted while in use. Close the file.
S80012 This message will be triggered when the History Controller cannot register for periodic cleanup within the Middleware. The History Controller cannot register for periodic cleanup within the Middleware.
Please contact Platform Technical Support.
S80012 This message will be triggered when the History Controller cannot unregister from periodic cleanup within the Middleware. The application may have already been unregistered from periodic cleanup.
No action necessary.
S80014 This message will be triggered when a group of History files cannot be removed from the file system. Please read the error log for the failure renamed. The failure reason should provide a hint as to how to correct the problem. The following are examples of some common scenarios. Permission denied.
The current user does not have appropriate permissions on the given directory. Change the user, or grant appropriate file access to the user.
A user removed the directory. No action necessary. Please do not alter or remove the files generated by the Middleware.
Device is unavailable. The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S80016 This message will be triggered when the contents of the History file cannot be flushed to disk. The following are examples of some common scenarios. Device is unavailable.
The file system is down, or there is a hardware failure. Wait for the file system to come back up, or contact your IT administrator.
S90008 This message will be triggered when authentication failed. Authentication failed.
Check that the user name and password are correct.
S90013 This message will be triggered when the security plugin fails to load. Failed to load the security plugin
Check that the security plugin name and the security library are available and properly configured.
S90016 This message will be triggered when the security plugin name is empty. The security plugin name cannot be empty.
Specify a security plugin name that is applicable to the system.
S85002 This message will be triggered when Repository Service instance failed to be created. Please check the log files for more details.

S85003 This message will be triggered when service instance failed to be created. The port number specified is already used by other process.
Check the port number, and restart this service by assigning another port number in -p option.
S85004 This message will be triggered when service instance failed to allocate memory using ACE_NEW. The system is out of memory causing the service instance to fail.
Check the failing host for memory usage and shutdown any unnecessary processes.
S85005 This message will be triggered when error occurred but cannot get the error info. Internal Error.
Contact Platform technical support for patches.
S85006 This message will be triggered when Internal Task Queue is not working properly. Internal Error.
Contact Platform technical support for patches.
S85007 This message will be triggered when Port Number is invalid. Invalid Port Number is given in command line. The port number must be an integer number greater than zero.
Check the command line and re-specify the port number.
S85008 This message will be triggered when Thread Pool cannot be created. Out of Thread Resource.
Release some System Resource.
S85009 This message will be triggered when Directory cannot be created on file systems. Failed to create Directory on the file systems.
Please check the user read/write permission or disk capability on the file System.
S85010 This message will be triggered when File cannot be created on file systems. Failed to create File on the file systems.
Please check the user read/write permission or disk capability on the file System.
S85011 This message will be triggered when at least one of the parameters is NULL. Get at least one NULL parameter, cannot continue the Deployment Service.
Probably internal problems. Contact Platform Technical Support.
S85012 This message will be triggered when Directory cannot be removed on file systems. Failed to remove Directory on the file systems.
Please check the user read/write permission or disk capability on the file System.
S85013 This message will be triggered when package file cannot be found for the package. Failed to find the package file for the package.
Please check the user read/write permission or disk capability on the file System.
S85014 This message will be triggered when package file cannot be read for the package. Failed to read the package file for the package.
Please check the user read/write permission or disk capability on the file System.
The package file is too big to transmit. Wait for patches and contact Platform Support.
S85015 This message will be triggered when repository directory cannot be read. Failed to read the repository directory.
Please check the user read/write permission or disk capability on the file System.
S85016 This message will be triggered when the deploying package is already deployed. Package is already deployed.
Need to unregister the package at first.
S85017 This message will be triggered when downloading a package from the repository. The requested version doesn't match the repository version. Package was updated or removed.
Need to redeploy the package.
S85018 This message will be triggered when the package was not found in the SOAM service repository. Failed to remove the package.
No action necessary.
S85019 This message will be triggered when the default cache size is changed. Repository cache size was changed.
No action necessary.
S85020 This message will be triggered when the default cache timeout is changed. Repository cache timeout was changed.
No action necessary.
S85021 The client failed to send a request to the repository service. The repository service is not running.
Check the repository service (RS).
A network error caused the connection to the repository service to fail. No action required, the client will stop.
The server request timed out in a soamdeploy or rsdeploy operation. Set RS_REQUEST_TIMEOUT environment variable to greater than 300 (seconds).
S85022 The client failed to receive a reply message from the repository service. The repository server (RS) is not running.
Restart the RS.
A network error caused the connection to the repository service to fail. No action required, the client will stop.
S85023 This message will be triggered if applications are still linked to the existing package when removing. Can not remove the package because applications are still linked to it.
Unlink the package from all applications before removing.
S85024 This message will be triggered when unlink a package that has already been removed. File has already been removed.
No action necessary.
S85025 This message will be triggered if user enters the wrong password and username. User is not authorized to access the repository service.
No action is necessary
S85030 This message will be triggered if user is not authorized to perform actions on the repository service. User is not permitted to access the repository service.
Contact system administrator to add user access.
S85031 The code calling the Package API did not pass correct parameters. This is an internal error; invalid parameter passed to API.
Retry the API call.
S85032 Client instance on the session was not found, because wrong session handle was passed This is an internal error; session manager couldn't find any repository service client instance on the current session
Retry the API call, with correct session handle.
S85033 Message block allocation failed due to lack of virtual memory. SymMessageBlock allocation failed.
Shutdown unnecessary programs running on this RS client to free up some memory or restart the machine.
S85034 The system can not deploy packages less than or equal to 1 byte The system transfers files in blocks and must have two blocks
Make the package file larger than 1 byte
S85035 Repository could not add the package Repository could not add the package
Retry the API call.
S85036 Consumer Id can not be found. Consumer Id can not be found.
Check the spelling and the consumer id.
S85040 Package is already being deployed. Package deployment in progress.
Wait until current deployment completes.
S85041 Rsdeploy agent start operation timed out. Failed to start agent on specified host.
Check slot availability and rsdeploy binary location.
S85042 Rsdeploy operation was cancelled. The rsdeploy agent could not update status since the operation was cancelled.
No action required.
S85043 No hosts in the resource group. The package deployment command could not run, as there were no hosts in the resource group.
Specify a different resource group.
S85044 Specified host was not found in the cluster. The package deployment command could not run, as the specified host was not found.
Specify a different host name.
S85045 Application package not found. The package was not added.
Add the package using rsdeploy add.
S85046 The specified consumer or resource group was not found. The consumer or resource group was not defined.
Select an pre-existing consumer and resource group and rerun the command.
S85047 The specified resource group was not found. The resource group was not defined.
Select an pre-existing resource group and rerun the command.
S85048 The specified host name was not found. The host was not added to a resource group.
Select an pre-existing host name and rerun the command.
S85049 The remote rsdeploy agent terminated suddenly. The rsdeploy host went down.
Restart the specified host.
S85050 No deploy agent could be cancelled. The operation completed.
No action required.
S85057 A package for host type not found. No package found for host type.
Use rsdeploy add to add a package for the required host type..
S85058 Rsdeploy agent start operation timed out. Failed to start agent on specified host.
Check slot availability and this host.
S85061 The RS service went down during a package operation. The RS host or RS service shut down.
Restart the deployment operation.
S85062 Deployment package not found. The package was not added.
Add the package using rsdeploy add.
S85065 Package name is the same as an existing one. Package name is case insensitive when stored to the Windows file system.
Rename the package and try again.
S85071 Currently installed version of RS server doesn't support deploying package to a non-leaf consumer node. RS server before Symphony version 4.1 doesn't support deploying package to a non-leaf consumer node.
Upgrade RS server to the latest version.
S85072 The RS could not send a response back to the requestor. The response operation failed due to the request client disconnecting.
If the problem persists, restart the RS.
S85073 The RS server's download request limit has been exceeded. The RS server is temporarily not accepting download requests.
No action should be required. The soamdeploy download client will wait and then retry.
S85074 The soamdeploy command could not download the requested package file. soamdeploy could create the specified file.
Check the file system and directory permissions.
S85075 The soamdeploy command could not download the requested package file. soamdeploy could write to the specified file.
Check the file system and directory permissions.
S85076 The soamdeploy command could not receive a message from the RS server. The RS sent a message that could not be decoded by soamdeploy.
No action should be required. The soamdeploy download client will wait and then retry.
S85088 The soamdeploy command timed out waiting for a request from the RS server. Soamdeploy sent a message and did not get a reply within the request timeout.
No action should be required. The soamdeploy download client will wait and then retry.
S85089 The RS could not send a response back to the requestor. The response operation failed due to the request client disconnecting.
If the problem persists, restart the RS.
S85091 The package was updated too frequently. RS prevents the user from updating a package too frequently.
Allow more time between package updates.
S87003 The application package's deployment.xml has an XML error. The deployment.xml file as a syntax error.
Please check the deployment.xml file and redeploy the application.
S87006 The deploy utility returned a non-specific error. The deploy utility has insufficient permission to deploy the application service.
Check the file permission of the SOAM_HOME/deploy or EGO_HOME/eservice/rs/deploy directory and ensure that full access is given.
The deploy utility has insufficient disk space to deploy the application service. Check the disk space of the SOAM_HOME/deploy or EGO_HOME/eservice/rs/deploy directory and ensure that sufficient space exists.
S87007 Unable to complete the install as the destination directory already exists. Installation was stopped as the application directory exists.
Remove the application directory and restart Symphony
S87009 The application package file could not be uncompressed. The dearchive utility was not on the executable search path of the machine.
Ensure the dearchive utility is available. unzip for .zip, uncompress for .Z, gunzip for .gz, tar for .tar.
The package file is corrupt. Redeploy the package.
S87012 The application package file could not be copied from the download location to the application directory Insufficient space on the hard drive.
Ensure there is sufficient hard drive space to copy the application package to the application directory. Free some disk space if necessary.
S87013 The application directory could not be delete on uninstall. The directory is in use.
Ensure that a shell or other process is using this directory and then delete the directory manually.
The directory of file permissions prevent deletion. Delete the directory manually.
S87014 The application directory does not exist. Could not find the application directory.
Delete the application manually if it was installed on the machine.
S87015 The application install command timed out. The application install took longer than the timeout specified.
Increase the install timeout value.
The application install command failed to exit due to an error. Debug the application installer to ensure that it works on the target machine.
S87016 The application install command did not start. The application installer requires library files, which are not installed on the machine.
Ensure that all dependent files for the installer are pre- installed.
The installer binary does not run on the target operating system. Check the deployment.xml file in the application package to ensure the correct install command is specified.
S87017 This install command returned an error code. The install command failed and returned an error code.
Debug the installer's error code and redeploy the application module.
S87018 The application uninstall command timed out. The application uninstall took longer than the timeout specified.
Increase the uninstall timeout value. Manually uninstall the application.
The application uninstall command failed to exit due to an error. Debug the application uninstaller to ensure that it works on the target machine. Manually uninstall the application.
S87019 The application uninstall command did not start. The application uninstaller requires library files, which are not installed on the machine.
Ensure that all dependent files for the uninstaller are pre- installed. Manually uninstall the application.
The uninstaller binary does not run on the target operating system. Check the deployment.xml file in the application package to ensure the correct install command is specified. Manually uninstall the application.
S87020 This uninstall command returned an error code. The uninstall command failed and returned an error code.
Debug the uninstaller's error code and manually uninstall the application.
S87021 The SOAM_HOME environment variable was not assigned the location of the Symphony installation. The SOAM_HOME environment variable is not set on Windows.
On Windows, check the System settings to ensure SOAM_HOME is set. If set please restart Windows to restore the environment
The SOAM_HOME environment variable is not set on UNIX. On Unix, set the environment with the proper shell rc file.
S87022 A command failed to start. The command syntax was incorrect.
Fix the command syntax in the deployment.xml file.
Command dependent files are missing. Install the dependent files and redeploy the application.
S87023 A command failed to start. The command syntax was incorrect.
Fix the command syntax in the deployment.xml file.
Command dependent files are missing. Install the dependent files and redeploy the application.
S87024 The application package file could not be copied from the download location to the application directory Insufficient space on the hard drive.
Ensure there is sufficient hard drive space to copy the application package to the application directory. Free some disk space if necessary.
S87025 The deploy utility could not create a directory for verification. Could not create a directory under the specified directory.
Add write permission for the execution user to the specified directory.
S87026 The deploy utility could not save a temp file Could not create a temp file.
Free up some disk space on the drive.
S87027 Failed to locate local EGO_TOP EGO_LOCAL_CONFFIR is not defined
Set EGO_LOCAL_CONFDIR in the environment
S87028 Failed to create a directory Disk maybe full
Check destination directory
S87029 The deploy utility could not create the deployed destination directory. Could not create a directory under the deploy directory.
Add write permission for the execution user to the specified directory.
S87030 The specified file could not be created when caching it to the file system.
Verify the user permissions for the temporary directory and check whether there is sufficient space on the drive.
S87031 The package which containing the '.nfs' file is invalid. Remove the '.nfs' file from the package, then deploy it again. The package that containing the '.nfs' file is invalid.
Remove the '.nfs' file from the package, then deploy it again.
S87051 The application install command timed out. The application install took longer than the timeout specified.
Increase the install timeout value.
The application install command failed to exit due to an error. Debug the application installer to ensure that it works on the target machine.
S87052 This install command returned an error code. The install command failed and returned an error code.
Debug the installer's error code and redeploy the application module.
S87053 The SOAM_HOME environment variable was not assigned the location of the Symphony installation. The SOAM_HOME environment variable is not set on Windows.
On Windows, check the System settings to ensure SOAM_HOME is set. If set please restart Windows to restore the environment
The SOAM_HOME environment variable is not set on UNIX. On Unix, set the environment with the proper shell rc file.
S87054 The application package file could not be uncompressed. The dearchive utility was not on the executable search path of the machine.
Ensure the dearchive utility is available. unzip for .zip, uncompress for .Z, gunzip for .gz, tar for .tar.
The package file is corrupt. Redeploy the package.
S87055 The application package's deployment.xml has an XML error. The deployment.xml file as a syntax error.
Please check the deployment.xml file and redeploy the application.
S87056 The deploy utility could not contact the repository server. The RS is not running.
Restart the RS service.
A network error caused the connection to the RS to fail. No action required, the SIM will stop.
The RS is overloaded and can not respond to connection requests within 300 seconds. Set the RS_CONNECTION_TIMEOUT environment variable to a value greater than 300 in the service section.
S87057 The application package file could not be copied from the repository server The package was not added to the repository server.
Use soamdeploy add to add the package to the repository server.
Insufficient space on the hard drive. Ensure there is sufficient hard drive space to copy the application package to the application directory. Free some disk space if necessary.
The RS is overloaded and can not respond to requests within 300 seconds. Set the RS_REQUEST_TIMEOUT environment variable to a value greater than 300 in the service section.
S87058 Unable to complete the install as the destination directory already exists. Installation was stopped as the application directory exists.
Remove the application directory and restart Symphony
S87059 The application install command failed to run. The command was not found on the disk.
Specify the full path of the command.
The application install command failed run due to incorrect syntax. Debug the application installer to ensure that it works on the target machine.
S87060 The application package file was not found on the repository server. The requested package was not added to the application consumer leaf node.
Use soamdeploy add to redeploy the application package.
S87061 The deploy utility could not create the deployed destination directory. Could not create a directory under the deploy directory.
Add write permission for the execution user to the SOAM_HOME/deploy directory.
S87062 The deploy utility could not connect to ego services. Connection to the EGO master failed.
Check the EGO master host machine and EGO services using egosh.
S87063 The deploy utility could not connect to ego services. Connection to the EGO master host timed out.
Increase the EGO_CONNECT_TIMEOUT value in the local /kernel/conf/ego.conf file.
S87064 The deploy utility could not connect to ego services. Connection to the EGO master failed.
Check the EGO master host machine and EGO services using egosh.
The RS server is not running. Check that the EGO service RS is running using egosh service list.
S87065 The deploy utility failed to cache the package to the file system. The specified package could not be cached.
Verify the user permissions for the temporary directory and check whether there is sufficient space on the drive.
S95004 The FAM failed to connect with the request client. The FAM host is running low on memory or descriptors.
Shutdown unnecessary programs running on this FAM host to free up some memory or restart the machine.
S95005 The FAM failed to connect with the request client. The client is not running.
Restart your application.
A network error caused the connection to the request client to fail. No action required, the FAM will stop.
S95006 The FAM did not successfully complete initialization. There was insufficient memory to start the FAM.
Shutdown unnecessary programs running on this FAM host to free up some memory or restart the machine.
S95007 The FAM did not successfully complete initialization. There was insufficient memory to start the FAM.
Shutdown unnecessary programs running on this FAM host to free up some memory or restart the machine.
S95008 The FAM did not successfully complete initialization. There was insufficient memory to start the FAM.
Shutdown unnecessary programs running on this FAM host to free up some memory or restart the machine.
S95009 The FAM failed to send a reply message to the client. The request client is not running.
Restart your application.
A network error caused the connection to the request client to fail. No action required, the FAM will stop.
S95010 The FAM failed to connect with the request client. The request client is not running.
Restart your application.
A network error caused the connection to the request client to fail. No action required, the FAM will stop.
S95011 The FAM failed to receive a message from the request client. The request client is not running.
Restart your application.
A network error caused the connection to the request client to fail. No action required, the FAM will stop.
S95012 The FAM remote server received a request with a missing argument. The FAM server may not be able to allocate sufficient memory.
Retry your request.
S95013 The FAM remote server could not perform the specified copy operation. The copy operation failed due to a missing source file.
Verify the source path and drive.
S95014 The FAM remote server could not perform the specified write operation. The write operation failed due to a file system error.
Verify the destination path and drive.
S95015 The FAM remote server could not perform the specified read operation. The read operation failed due to a file system error.
Verify the source path and drive.
S95016 The FAM remote server could not send a response back to the requestor. The response operation failed due to the request client disconnecting.
Retry your request.
S95017 The FAM remote server could not allocate memory to service the request. The server is running short of virtual memory.
Retry your request.
S95018 The FAM remote server could not open the specified file. The file doesn't exist or the FAM agent doesn't have sufficient rights.
Retry your request.
S95019 The FAM remote server could not perform the specified read operation. The read operation failed due to a file system error.
Verify the source path and drive.
S95020 The FAM remote server could not perform the specified copy operation. The copy operation failed due to a missing source file.
Verify the source path and drive.
S95021 The FAM remote server could not perform the specified remove operation. The remove operation failed due to a missing source file.
Verify the source path and drive.
S95022 The FAM remote server could not perform the specified remove operation. The remove operation failed due to a missing source directory.
Verify the source path and drive.
S95023 The FAM remote server could not perform the specified open operation. The remove operation failed due to a missing source directory.
Verify the source path and drive.
S95024 The FAM remote server could not perform the specified read operation. The remove operation failed due to a missing source directory.
Verify the source path and drive.
S95025 The FAM remote server could not process the specified pattern. The pattern specified is not a valid regular expression pattern.
Correct the pattern.
S95026 The FAM remote server can not replace the specified file on the file system. The request to overwrite an existing file is not allowed.
Remove the existing file.
S95027 The FAM remote server can not write the specified file on the file system. Write to a file did not succeed.
Check disk space.
S95028 PEM has asked fam to shutdown (via SIGTERM or CTRL_BREAK_EVENT). rfa disappeared or slot reclaimed so pem is nicely asking fam to exit.
Clean-up and exit.
S95029 Client submit a non-absolute path. The operation on a non-absolute path is not allowed.
Clean-up and exit.
S95501 The client failed to connect with the FAM remote agent. The FAM agent is not running.
Retry the file request.
S95502 The client failed to receive a reply message from the FAM agent. The remote FAM agent is not running.
Retry the file request.
S95503 The client failed to send a message to the FAM agent. The remote FAM agent is not running.
Retry the file request.
S95504 A memory buffer could not be allocated. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this client host to free up some memory or restart the machine.
S95505 Failed to create a file. The specified file couldn't be created.
Verify the user permissions for the specified directory and check whether there is sufficient space on the drive.
S95506 The FAM agent did not respond within the time specified. The FAM agent did not respond within the specified timeout interval.
Retry your request.
S95507 Error submitting a request to the remote agent. There was a communications error submitting a request.
Retry your request.
S95508 Error uncompressing the specified file. The requested file could not be uncompressed.
Retry your request.
S95509 Failed to open the specified file for reading. Failed to open a file for reading.
Check the file and retry your request.
S95510 Failed to read the specified file. Failed to open a file for reading.
Check the file and retry your request.
S95511 Error compressing the specified file. The requested file could not be compressed.
Retry your request.
S95512 A required parameter was not specified. The required parameters for the current operation were not specified.
No action required.
S95513 The FAM failed to connect with the request client. The FAM agent is not running.
Retry your request.
A network error caused the connection to the request client to fail. Retry your request.
S95514 A required parameter was not specified. The system may be running low on virtual memory.
Stop any unnecessary processes or restart the client system.
S95515 The EGO container could not be started on the remote system. The specified host is not running.
Restart the specified host.
S95516 A memory buffer could not be allocated. There was insufficient memory to process the request.
Shutdown unnecessary programs running on this client host to free up some memory or restart the machine.
S95517 Failed to write the file. The file doesn't have write permissions.
Set write permissions on the file.
S95518 Cant read the file. The file doesn't have read permissions.
Set read permissions on the file.
S95519 EGO could not allocate. The allocation request is incorrect.
Verify the allocation parameters.
S95520 This message will be triggered when RAManager fails to authenticate itself with EGO. It is using a credential provided by library client. If this credential is or becomes invalid RFA will fail to connect to EGO Call vem_logon failed in EGO.
Provide a different credential.
S96001 This message will be triggered when the Excel Runner Service get unexpected exception. Excel Runner Service got unexpected exception with no additional information provided.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S96002 This message will be triggered when the Excel Runner Service gets an unexpected SymException. Unexpected SymException for the Excel Runner service.
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem.
S96003 This message will be triggered when the Excel Runner Service found pattern popup dialog. Excel Runner Service found specified in application profile pattern in pop up dialog .
Please read the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. Check your Excel spreadsheet.
S96004 This message will be triggered when the Excel Runner Service get FailureException. Excel Runner Service got a FailureException.
Check the error log for the failure reason. The reason should provide a hint as to how to correct the problem. The failed task will be rescheduled to rerun with other service instances.
S96005 This message will be triggered when the Excel Runner Service gets a FatalException. Excel Runner Service gets a FatalException.
Check the error log for the failure reason. The reason should provide a hint as to how to correct the problem. The failed task will NOT be rescheduled to be rerun with other service instances.
S96006 This message will be triggered when the Excel Runner Service gets standard template library FatalException. Excel Runner Service gets a FatalException.
Check the error log for the failure reason. The failure reason should provide a hint as to how to correct the problem. The failed task will NOT be rescheduled to be rerun with other service instances.
S96007 This message will be triggered when Excel Runner Service failed to create a new directory for common data. Excel Runner Service failed to create a new directory for common data. Excel Runner service tried to create the new directory under $SOAM_HOME\work directory.
Please check the write permissions of the $SOAM_HOME\work directory.
S96008 This message will be triggered when Excel Runner Service is trying to delete a file. Excel Runner Service fails to delete one of its working files.
Check whether the file (specified in the error message) is accessible by the specified user. Kill the Excel process, and manually remove the file.
S96009 This message will be triggered when Excel Runner Service is trying to delete a temporary directory. Excel Runner Service fails to delete temporary directory for working files.
Please check whether the directory (specified in the error message) is accessible by the user specified. Kill the Excel process, and manually remove the directory.
S96010 This message will be triggered when Excel Runner Service is trying to write a dialog pattern into the registry. Excel Runner Service fails to write into the registry.
Check whether the registry key (specified in the error message) is accessible by the specified user.
S96011 This message will be triggered when Excel Runner Service is trying to write a dialog pattern into the registry. Excel Runner Service fails to create named mutex.
Check that the Excel Runner service has enough system resources to run.
S96012 This message will be triggered when the Excel Runner service is attempting to start Dialog Sniffer. Excel Runner Service fails to start Dialog Sniffer.
Please check if there are enough resources available to run Dialog Sniffer or check command line in the application profile.
S96013 This message will be triggered when Dialog Sniffer attempts to start up and open a log file. Dialog Sniffer does not have permissions to open the log file.
Check permissions for the file in $SOAM_HOME/logs/ directory.
S96014 This message will be triggered when the Excel Runner service found a fatal pattern in the Dialog Sniffer log file. Dialog Sniffer logged the pattern from the Excel popup dialog into the log file.
Fix the application to avoid pop up dialogs. The dialog information from log file should provide a hint as to how to correct the problem.
S96016 This message will be triggered when the Excel Runner service found a non fatal pattern in the Dialog Sniffer log file. Dialog Sniffer logged the pattern from the Excel popup dialog into the log file.
Fix the application to avoid pop up dialogs. The dialog information from log file should provide a hint as to how to correct the problem.
S97255 This message will be triggered when Symexec Service failed to open log file for appending. Symexec Service failed to open log file for appending under the log directory configured in service section of application profile.
Please check the existence and write permissions of the log directory.
S97256 This message will be triggered when Symexec Service failed to write log. Symexec Service failed to write log into the log file under the log directory configured in service section of application profile.
Please check the existence and write permissions of the log directory.
S97612 This message will be triggered when the Symphony Activation Console could not add the specified consumer to the ConsumerTrees.xml file. The Symphony Activation Console could not add the specified consumer to the ConsumerTrees.xml file.
First add the specified consumer to the consumer tree using the Platform Management Console. Next, locate the application profiles for the new Symphony applications. These will be located in the installation directory, on any host with the upgrade activated, under "EGO_TOP/soam/activation/VERSION_NUM/profiles/disablednotsaveworkload" or "EGO_TOP/soam/activation/VERSION_NUM/profiles/enabled". Replace all instances of "@VERSION_NUM@" with the version of Symphony you are activating. For example, if you are upgrading to Symphony version 4.1.0, specify "4.1". Finally, register the updated application profile with Symphony using the Platform Management Console.
S98001 This message will be triggered when an unknown operation/condition is found in a configuration file. An unknown operation/condition is found in a configuration file.
Contact Platform Support.
S98002 This message will be triggered when fewer arguments than expected have been specified for an operation/condition in a configuration file. Fewer arguments than expected have been specified for an operation/condition in a configuration file.
Contact Platform Support.
S98003 This message will be triggered when an error occurred during the specified operation. An error occurred during the specified operation.
Read the error reason to determine how to resolve the problem.
S98004 This message will be triggered when an error occurred while attempting to undo the specified operation. An error occurred while attempting to undo the specified operation.
Read the error reason to determine how to resolve the problem.
S98005 This message will be triggered when an unknown variable type is found in a configuration file. An unknown variable type is found in a configuration file.
Contact Platform Support.
S98006 This message will be triggered when fewer arguments than expected have been specified for a variable definition in a configuration file. Fewer arguments than expected have been specified for a variable definition in a configuration file.
Contact Platform Support.
S98007 This message will be triggered when an environment variable is not defined. An environment variable is not defined.
Check your environment.
S98008 This message will be triggered when an environment variable is not found in operation/condition variable configuration. An environment variable is not found in operation/condition variable configuration.
Contact Platform Support.
S98009 This message will be triggered when more arguments than expected have been specified for an operation/condition in a configuration file. More arguments than expected have been specified for an operation/condition in a configuration file.
Contact Platform Support.
S98010 This message will be triggered when an invalid value has been specified for an operation/condition argument in a configuration file. An invalid value has been specified for an operation/condition argument in a configuration file.
Contact Platform Support.
S98011 This message will be triggered when an argument has been specified for an operation/condition in a configuration file, but a required dependent argument has not been specified. An argument has been specified for an operation/condition in a configuration file, but a required dependent argument has not been specified.
Contact Platform Support.
S98012 This message will be triggered when a value was parsed from a file, but the value does not match the expected data type. A value was parsed from a file, but the value does not match the expected data type.
Contact Platform Support.
S98013 This message will be triggered when an error occurred while trying to evaluate the specified condition. An error occurred while trying to evaluate the specified condition.
Read the error reason to determine how to resolve the problem.
S98014 This message will be triggered when an error occurred during the specified custom operation. An error occurred during the specified custom operation.
Read the error reason to determine how to resolve the problem.
S98015 This message will be triggered when an error occurred while attempting to undo the specified custom operation. An error occurred while attempting to undo the specified custom operation.
Read the error reason to determine how to resolve the problem.
S98252 Invalid client ID. An internal error occurred while an internal component presented an invalid client ID to the Data Provider.
This type of error is unexpected and can only be resolved by contacting Platform Technical Support.