160 WLMF-03002 to WLMF-03028
- WLMF-03002: The Quality of Service Management (QoS) user {0} is not authorized to perform this operation {1}.
- 
                     
                     Cause: The Quality of Service Management (QoS) user did not have the persmission to perform this operation. 
- WLMF-03003: The Quality of Service Management (QoS) service user does not have the necessary permission to retrieve the JAVA security Subject associated with the current access control context {0}.
- 
                     
                     Cause: The Quality of Service Management (QoS) user did not have the necessary permissions to retrieve the JAVA security Subject within the current access control context. 
- WLMF-03004: Version check failed or not performed. Operation could not be performed.
- 
                     
                     Cause: The operation to exchange the supported version numbers between the server and the client had not been called or had failed. 
- WLMF-03005: Application .ear file is corrupt.
- 
                     
                     Cause: Quality of Service Management (QoS) .ear file was corrupt. 
- WLMF-03006: Unsupported version. The client supports versions {0} to {1}.
- 
                     
                     Cause: An attempt to start the Quality of Service Management (QoS) failed because the client's version was not supported by the QoS. 
- WLMF-03007: Required policy set does not exist.
- 
                     
                     Cause: There was no policy set in persistent storage. 
- WLMF-03008: Invalid argument. Argument {0} was provided with value {1}.
- 
                     
                     Cause: The specified value of the argument was invalid. 
- WLMF-03009: The policy set is corrupt.
- 
                     
                     Cause: The Quality of Service Management (QoS) policy set retrieved from persistent storage was corrupt. 
- WLMF-03010: There is no policy set in QoS persistent storage.
- 
                     
                     Cause: The policy set was not found in Quality of Service Management (QoS) persistent storage. 
- WLMF-03011: QoS is not enabled.
- 
                     
                     Cause: Quality of Service Management (QoS) was not enabled for this operation. 
- WLMF-03012: The component {0} tried to transition from state {1} to {2}, but the current state is {3}. This is illegal.
- 
                     
                     Cause: This is an internal error. 
- WLMF-03013: QoS implement action ID {0} has expired.
- 
                     
                     Cause: The Quality of Service Management (QoS) implement action ID has expired. 
- WLMF-03014: The What If Analysis could not be performed.
- 
                     
                     Cause: Quality of Service Management (QoS) is unable to perform the What If Analysis because its timestamp is invalid or expired. 
- WLMF-03015: The action {0} is in progress and it will complete at {1}. The current time is {2}.
- 
                     
                     Cause: Unable to execute the action because a previous action has not completed. 
- WLMF-03016: Internal error encountered.
- 
                     
                     Cause: This is an internal error. 
- WLMF-03017: The operating system has reported a failure.
- 
                     
                     Cause: There was a problem in the operating system. 
- WLMF-03018: QoS service is not in the expected state.
- 
                     
                     Cause: Quality of Service Management (QoS) was not in the correct state to perform the requested operation. 
- WLMF-03019: Required library could not be loaded.
- 
                     
                     Cause: A library which Quality of Service Management (QoS) depends upon could not be loaded. 
- WLMF-03020: Requested action was not implemented.
- 
                     
                     Cause: Quality of Service Management (QoS) detected a change in system state that invalidated the performance projections. 
- WLMF-03021: Persistent key {0} had invalid value.
- 
                     
                     Cause: Quality of Service Management (QoS) found a corrupt key value in its attempt to retrieve data from the persistent store when starting or restarting. 
- WLMF-03022: Policy set or policy corruption.
- 
                     
                     Cause: Quality of Service Management could not be restarted because it could not read its configuration data from the cluster registry. 
- WLMF-03023: Persistent storage not found.
- 
                     
                     Cause: Quality of Service Management (QoS) could not find the persistent storage when starting or restarting. 
- WLMF-03024: An unsupported parameter was passed to Quality of Service Management.
- 
                     
                     Cause: An attempt to start Quality of Service Management (QoS) was rejected because the deployment type was specified as GLOBAL rather than LOCAL. 
- WLMF-03025: Invalid argument. Argument {0} was provided with value {1} and it must be less than argument {2} with value {3}.
- 
                     
                     Cause: The specified value of the argument was invalid. 
- WLMF-03027: The Grid Infrastructure Management Repository version is incompatible with Quality of Service Management (QoS).
- 
                     
                     Cause: An attempt to enable Quality of Service Management was rejected because the current version was not supported by the Grid Infrastructure Management Repository (GIMR). 
- WLMF-03028: Data retrieval operation failed. Error {0} {1}, encountered.
- 
                     
                     Cause: Quality of Service Management (QoS) failed to retrieve the requested information.