Service instance startup failures
Look for service instance hostname and process ID pairs in the SI Startup Failures column for your application. If there are any service instance hostname and process pairs, the service application experienced problems in either the Register or CreateService method on each of the service instances listed in the column.
If none of your service instances can start successfully, no service instance is available to run any of your tasks. If your client is hung waiting for task results, this may be the reason.
Click on your application name to drill into more details about your workload.
Look for service instance hostname and process ID pairs in the Binding Failures column for your session. If there are any service instance hostname and process ID pairs, the service application experienced problems in the SessionEnter method.
Navigate to the Sessions page. You can see whether any tasks ended in the ERROR state. It is possible your service experienced an error, but was unable to rerun and finish successfully.
Click on a session to drill into more details about that session. Look for comments in the Failure Reason column of your Tasks table.
Find out the host and process ID for the service instance on which the task ran. By default, the hostname is displayed in the Tasks table. You can configure the process ID to be displayed by modifying the Instance ID in Preferences at the bottom of the Tasks table.
Make note of one hostname and process ID to troubleshoot a particular service instance to see what happened in the next steps.
In Symphony DE, look at the service instance manager logs for the application on the host for more information. For example:
In Symphony, if you trap SNMP events, you receive event notifications for the service errors that occur.
You can also use log retrieval to retrieve the service instance manager logs on the host where your service failed to start, as follows:
In the text box, type the file pattern to retrieve service logs for your application.
The service instance manager reports something similar to the following example:
2007-11-14 12:30:43.843 Eastern Standard Time ERROR [3100:5188] sim.backend.ServiceBroker - Code[S20070]: e:\symphonyde\de40\4.0\src\soamservicecontainer.cpp : 137 IException Domain <Application>: Unexpected service exception in method onCreateService(). If the additional details attached do not provide enough information, change your code to use SoamException. Additional Details: Unexpected Exception Caught in onCreateService()..2007-11-14 12:30:43.843 Eastern Standard Time ERROR [3100:5188] soam.common.EventAgent - Code[S75052]: Application <ServiceReplayDebuggerCPP>, service <DebugService>: Failure exception thrown on method <createService>, control code <0>. Action on service instance: action <blockHost> taken on service instance process <5672>, host <achin2>, service <DebugService>.2007-11-14 12:30:43.890 Eastern Standard Time WARN [3100:5188] soam.common.EventAgent - Code[S75064]: Application <FailureException with control code 0>: SIM detected <FailureException with control code 0> for method <createService>. Debug action is <writeServiceEventReplayFiles>. Serl file is <E:\SymphonyDE\DE40\work\serl\ServiceReplayDebuggerCPP\DebugService\ServiceReplayDebuggerCPP.DebugService.achin2.5672.2007-11-14.12h.30m.43s.859ms.serl>.