Explanation | A key was passed into the AppProfileMessages class to resolve to a string, but a properties file for the locale could not be found, and the appropriate message could not be retrieved. |
Action | Determine why the message catalog could not be found. |
Explanation | An application was configured with attributes that are not valid. or not allowed. |
Action | Use the provided key to determine in what way the application was not configured correctly. The key is defined in the user documentation. Assemble the application again with appropriate application profile attributes. |
Explanation | An application was configured with attributes that are not valid or not allowed. |
Action | Use the reason that is provided to determine in what way the application was not configured correctly. Assemble the application again with appropriate application profile attributes, and reinstall the application. |
Explanation | The profile service for the application encountered an error that was not expected. |
Action | Verify that the application is properly configured and installed. |
Explanation | The Application Profiling service has been disabled in the configuration, and it will not be accessible on the server. |
Action | Disabling this service might cause other services on the server to fail. If you wish to enable the service, use the Administrative Console to configure services on this application server. |
Explanation | The Application Profiling service has been disabled in the configuration, but disabling this service could cause other services on the server to fail. |
Action | There is no user action required. |
Explanation | The Application Profiling service experienced an error during initialization. The service will not be accessible on the given server. The root error should have been logged previously. |
Action | Try to resolve the errors that were previously logged. If you are not able to do so, visit the IBM support website for information on problem determination. |
Explanation | The Application Profiling service started successfully. |
Action | There is no user action required. |
Explanation | The Application Profiling service is stopping. |
Action | There is no user action required. |
Explanation | The Application Profiling service could not resolve the specified service, which is required for the Application Profiling service. Look through the log to see if the specified service started successfully. |
Action | If you wish to use the Application Profiling service, correct the problem with the specified service. If you are not able to correct the problem, visit the IBM support website for information on problem determination. |
Explanation | The specified application is configured to require the Application Profiling service, but the Application Profiling service is not enabled. |
Action | Enable the Application Profiling service before starting the specified application that is configured for application profiling. |
Explanation | The specified application will run in V5.x compatibility mode. The V5.x compatibility mode is deprecated. |
Action | Verify that all Java 2 Enterprise Enterprise Edition (J2EE) V1.3 applications on this server that use application profiling can execute properly with Application Profiling V5.x Compatibility Mode disabled, then configure the Application Profiling service to not use V5.x Compatibility Mode. |