This section contains the following topics:
Message |
Function |
Description |
---|---|---|
1) Sending a new PIN to |
SmLoginLogoutMessage::Send-NewPinForValidation1 |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
2) Sending a new PIN to ACE/Server for validation |
SmLoginLogoutMessage::Send-NewPinForValidation2 |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Ace Server --- couldn’t get |
SmLoginLogoutMessage::Sm-AuthAceGetPinPoliciesFail |
The message is given in the SecurID authentication scheme when ACE server backend PIN policy cannot be retrieved using SecurID/ACE API call. |
Ace Server --- couldn't get |
SmLoginLogoutMessage::Sm-AceHtmlPinParamFail |
The message is given in the SecurID authentication scheme when ACE PIN parameters cannot be retrieved using SecurID/ACE API call. |
ACE State not ACM_NEXT_CODE_ |
SmLoginLogoutMessage::Ace-NextTokenCodeState |
The message in given in HTML SecurID authentication scheme when token code value is expired and the user is required to wait for the next code before attempting a new authentication. |
Ace/Server - new PIN is required, AceAPI returned ambiguous value for isselectable PIN attribute. Cannot complete Ace authentication. |
SmLoginLogoutMessage::Sm-AceHtmlPinRequired |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Ace/Server - new PIN is required, can choose or |
SmLoginLogoutMessage::Sm-AceHtmlChooseNewOrSysPin |
The message is given in the SecurID authentication scheme when ACE user is configured to use either self-chosen or system-generated PIN. |
Ace/Server - new PIN is required, Must accept |
SmLoginLogoutMessage::Sm-AceHtmlCannotChoosePin |
The message is given in the SecurID authentication scheme when ACE user is configured to always use system-generated PIN. |
Ace/Server - new PIN is required, must choose PIN, returning Sm_AuthApi_Reject, Sm_Api_Reason_New_User_-PIN_Tokencode. |
SmLoginLogoutMessage::Sm-AceHtmlChooseNewPin |
The message is given in the SecurID authentication scheme when ACE user is configured to always use self-chosen PIN. |
ACE/Server: ACM_NEW_PIN_ACCEPTED failed with aceRetVal %1i |
SmLoginLogoutMessage::Ace-ServerNewPinAcceptedFailed |
Used in HTML SecurID authentication scheme. Given when the new user PIN was not accepted by ACE server. |
ACE/Server: ACM_NEW_PIN_ACCEPTED failed with aceRetVal %1i, |
SmLoginLogoutMessage::Not-WinAceServerNewPinAccepted-Failed |
Used in HTML SecurID authentication scheme. Given when the new user PIN was not accepted by ACE server. |
ACE/Server: ACM_NEW_PIN_ACCEPTED failed. |
SmLoginLogoutMes-sage::NewPinAcceptedFailed |
Used in HTML SecurID authentication scheme. Given when the new user PIN was not accepted by ACE server. |
AceCheck Access denied by ACE/Server. |
SmLoginLogoutMessage::Ace-CheckAccessDenied |
The message is given in the SecurID authentication scheme when authentication request is rejected by ACE server. |
AceCheck not processed aceRetVal = %1i |
SmLoginLogoutMessage::Ace-CheckNotProcessed |
The error message is given in the SecurID authentication scheme if ACE authentication process through the ACE/SecurID API cannot be completed. |
AceCheck returned not ACM_NEW_PIN_REQUIRED but %1i |
SmLoginLogoutMessage::Acm-NewPinRequiredFail |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceCheck returned not ACM_NEW_PIN_REQUIRED but %1i |
SmLoginLogoutMessage::Invalid-ReturnAceCheckNewPin |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceCheck:Denied---aceRetVal = %1i |
SmLoginLogoutMessage::Sm-AuthAceCheck-Denial |
The message is given in the SecurID authentication scheme when authentication request is rejected by ACE server. |
AceGetMaxPinLen failed |
#REF! |
Used in HTML SecurID authentication scheme. Given when the scheme fails to retrieve max length of user PIN allowed by ACE server. |
AceSendPin failed |
SmLoginLogoutMessage::Ace-SendPinFailed |
The error message is given by HTML SecurID authentication scheme when it fails to send user PIN using to the RSA ACE server ACE/SecurID API. The authentication scheme rejects the request. |
AceServer - CANNOT_CHOOSE_PIN |
SmLoginLogoutMessage::Ace-ServerCannotChoosePin |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceServer - MUST_CHOOSE_PIN |
SmLoginLogoutMessage::Ace-ServerMustChoosePin |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceServer :: Sm_Api_Reason_New_PIN_ |
SmLoginLogoutMessage::Sm-ApiNewPinSelectReason |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceServer returning Sm_Api_Reason_New_PIN_ |
SmLoginLogoutMessage::Sm-ApiSuccessReason |
Used in HTML SecurID authentication scheme. Given when the user PIN is successfully changed by the user. |
AceServer:: returning Sm_AuthApi_Reject Sm_Api_Reason_New_PIN_ |
SmLoginLogoutMessage::Sm-ApiRejectReasonMessage |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceSetPasscode = %1s |
SmLoginLogoutMessage::Sm-AuthAceSetPassCode |
The message is given when the SecurID authentication scheme is making attempt to register passcode for ACE authentication with ACE/SecurID API. |
AceSetPasscode failed with aceRetVal = %1i |
SmLoginLogoutMessage::Ace-SetPasscodeFailed |
The error message is given by SecurID authentication schemes when it fails to register passcode for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
AceSetPin failed |
SmLoginLogoutMessage::Ace-SetPinFailed |
The error message is given by HTML SecurID authentication scheme when it fails to set user PIN using ACE/SecurID API. The authentication scheme rejects the request. |
AceSetSelectionCode DECRYPT = %1s |
SmLoginLogoutMessage::-SelectioncodeDecrypt |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
AceSetUsername failed with aceRetVal = %1i |
SmLoginLogoutMessage::Ace-SetUserNameFailed |
The message is given by SecurID authentication schemes when it fails to register username for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
AddCurrentPWToHistory - Can't set password history info. |
SmLoginLogoutMes-sage::ErrorSettingPassword-History |
Failed to add current password to the list of most recent passwords. |
AuthenticateUserDir - Can't update user blob data |
SmLoginLogoutMessage::Blob-UpdateFailed |
Failed to update Password Blob Data during Authentication process. |
Cannot get AceAlphanumeric |
SmLoginLogoutMessage::Get-AceAlphanumericFail |
Failed to find method in ACE client library. |
Cannot get AceCancelPin |
SmLoginLogoutMessage::Get-AceCancelPinFail |
Failed to find method in ACE client library. |
Cannot get AceCheck |
SmLoginLogoutMessage::Get-AceCheckFail |
Failed to find method in ACE client library. |
Cannot get AceClientCheck |
SmLoginLogoutMessage::Get-AceClientCheckFail |
Failed to find method in ACE client library. |
Cannot get AceClose |
SmLoginLogoutMessage::Get-AceCloseFail |
Failed to find method in ACE client library. |
Cannot get AceGetAuthenticationStatus |
SmLoginLogoutMessage::Ace-GetAuthenticationStatusFail |
Failed to find method in ACE client library. |
Cannot get AceGetMaxPinLen |
SmLoginLogoutMessage::Null-AceGetMaxPinLen |
Failed to find method in ACE client library. |
Cannot get AceGetMinPinLen |
SmLoginLogoutMessage::Null-AceGetMinPinLen |
Failed to find method in ACE client library. |
Cannot get AceGetPinParams |
SmLoginLogoutMessage::Get-AcePinParamFail |
Failed to find method in ACE client library. |
Cannot get AceGetShell |
SmLoginLogoutMessage::Ace-GetShellFail |
Failed to find method in ACE client library. |
Cannot get AceGetSystemPin |
SmLoginLogoutMessage::Ace-GetSystemPinFail |
Failed to find method in ACE client library. |
Cannot get AceGetTime |
SmLoginLogoutMessage::Ace-GetTimeFail |
Failed to find method in ACE client library. |
Cannot get AceGetUserData |
SmLoginLogoutMessage::Ace-GetUserDataFail |
Failed to find method in ACE client library. |
Cannot get AceGetUserSelectable |
SmLoginLogoutMessage::Ace-GetUserSelectable-Fail |
Failed to find method in ACE client library. |
Cannot get AceInit |
SmLoginLogoutMessage::Get-AceInitFail |
Failed to find method in ACE client library. |
Cannot get AceInitialize |
SmLoginLogoutMessage::Ace-InitializeFail |
Failed to find method in ACE client library. |
Cannot get AceLock |
SmLoginLogoutMessage::Ace-LockFail |
Failed to find method in ACE client library. |
Cannot get AceSendNextPasscode |
SmLoginLogoutMessage::Ace-SendNextPasscodeFail |
Failed to find method in ACE client library. |
Cannot get AceSendPin |
SmLoginLogoutMessage::Null-AceSendPin |
Failed to find method in ACE client library. |
Cannot get AceSetNextPasscode |
SmLoginLogoutMessage::Ace-SetNextPasscodeFail |
Failed to find method in ACE client library. |
Cannot get AceSetPasscode |
SmLoginLogoutMessage::Ace-SetPasscodeFail |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Cannot get AceSetPin |
SmLoginLogoutMessage::Null-AceSetPin |
Failed to find method in ACE client library. |
Cannot get AceSetUserClientAddress |
SmLoginLogoutMessage::Ace-SetUserClientAddressFail |
Failed to find method in ACE client library. |
Cannot get AceSetUsername |
SmLoginLogoutMessage::Ace-SetUsernameFail |
Failed to find method in ACE client library. |
Cannot load aceclnt.dll |
SmLoginLogoutMessage::Ace-lntDllLoadFail |
Failed to load ACE client library. |
Cannot retrieve new password from password message |
SmLoginLogoutMessage::New-PasswordRetrieveFail |
When processing Login request, and breaking up password for New and Old, failed to retrieve New Password. |
Cannot retrieve old |
SmLoginLogoutMessage::Old-PasswordRetrieveFail |
When processing Login request, and breaking up password for New and Old, failed to retrieve Old Password. |
Cannot retrieve token from password message |
SmLoginLogoutMessage::Token-RetrieveFail |
When processing Login request, and breaking up password for New and Old, failed to retrieve password token. |
ChangePassword - Can't change password via the provider |
SmLoginLogoutMessage::Pwd-ChangeFailViaProvider |
Failed to change password in User Directory during Change Password request. |
ChangePassword - Can't validate the new password |
SmLoginLogout-Message::ChangePwdValidation-Fail |
Failed to validate password in User Directory during Change Password request. |
CheckPasswordPolicies - authentication status changed to failure due to password policy misconfiguration. |
SmLoginLogout-Message::CheckPwdFailCause-Misconfig |
When checking password policies, failed to validate login attempt. Probably because password policy is misconfigured. |
Could not find the Variable |
SmLoginLogout-Message::VariableFindErrorTo-Delete |
Session Variable flag were passed as part of Request before Session Variable name. |
CSmAuthUser - ChangePassword - Can't update user blob data |
SmLoginLogoutMes-sage::ChangePwdBlobUpdateFail |
Failed to update Password Blob Data during Change Password request. |
DelVariable :Internal Error : Could not find the Variable |
SmLoginLogoutMessage::Del-VariableFindError |
Variable name is empty when trying to delete it from Session Store. |
DelVariable Returned Error %1i for Variable %2s |
SmLoginLogoutMessage::Del-VariableReturnError |
Failed to delete this variable from Session Store. |
Did not set AceSetUsername = %1s |
SmLoginLogoutMessage::Sm-AuthNotSetUserId |
The message is given by SecurID authentication schemes when it fails to register username for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
Error finding the name of variable to be deleted %1s:Invalid Index %2i |
SmLoginLogout-Message::VariableNameFind-InvalidIndexError |
Session Variable flag were passed as part of Request for Session Variable with empty name. |
Error in scheme configuration parameter lpszServerParam corrupted. |
SmLoginLogoutMessage::Error-ScemeConfigServerParam |
Used in SecurID authentication schemes. Same as above. |
Error in scheme configuration parameter: Empty String |
SmLoginLogoutMessage::Error-ScemeConfigParam |
Both basic and form based SecurID authentication schemes require "ACE User ID Attribute Name in Directory" parameter. The error is displayed when this parameter is missing or misconfigured. |
Failed to authenticate |
SmLoginLogoutMessage::User-AuthFail |
Failed to authenticate because of old version of authentication provider library. |
Failed to find authentication realm '%1s |
SmLoginLogoutMessage::Auth-RealmFindFail |
When processing Radius Authentication request, failed to find Realm protected by given Agent / Agent Group. |
FindApplicablePassword |
SmLoginLogoutMessage::Error-FetchingApplicablePolicyRoot |
Failed to fetch Root object while validating Logging attempt. |
FindApplicablePassword |
SmLoginLogoutMessage::Error-FindingMatchingPolicies |
Failed to fetch PasswordPolicy object while validating Logging attempt. |
FindApplicablePassword |
SmLoginLogout-Message::PasswordDataAttrib-NotDefined |
User Directory that we are using has not defined the appropriate attributes for the blob. |
FindApplicablePassword |
SmLoginLogoutMessage::Null-ApplicablePwdPolicyDir |
Both User and Directory objects are NULL when looking for Applicable Password Polices while validating Logging attempt. |
GetRandomPassword - Shortest Length greater than Longest Length |
SmLoginLogoutMessage::Long-PwdLength |
Created random password exceeds maximum allowed length. |
GetRedirect - Can't find applicable password policies. |
SmLoginLogoutMessage::Error-FindingPasswordPolicy |
Failed to Find Applicable Policies while looking for the first applicable password policy that contains redirect information. |
GetRedirect - Can't retrieve password policy. |
SmLoginLogoutMessage::Error-RetrievePasswordPolicy |
Failed to fetch PasswordPolicy object while validating New Password. |
GetVariable : Internal Error:DelVar %1s does not match Var: %2s |
SmLoginLogoutMessage::Get-VariableMatchError |
Variable to be deleted when fetched, has different names for fetching and deleting. |
GetVariable(Del) Returned |
SmLoginLogoutMessage::Get-VariableDelReturnError |
Failed to delete this variable from Session Store. |
GetVariable(Fetch) Returned Error %1i for Variable %2s |
SmLoginLogoutMessage::Get-VariableFetchReturnError |
Failed to find this variable in Session Store. |
GetVariable: Internal Error :Could not find variable |
SmLoginLogoutMessage::Get-VariableFindError |
Variable name is empty when trying to get Session Variables. |
Invalid format for SiteMinder generated user attribute |
SmLoginLogoutMessage::Invalid-SmUserAttribFormat |
ApplcationRole User property has wrong format. |
New PIN was accepted = %1s |
SmLoginLogoutMessage::New-PinAccepted |
Used in HTML SecurID authentication scheme. Given when the user PIN is successfully changed by the user. |
Nonstandard SelectionCode = %1s |
SmLoginLogoutMessage::Ace-ServerNonStandard-Selectioncode |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Passcode not allocated. |
SmLoginLogout-Message::PasscodeNot-Allocated |
Used in SecurID authentication scheme. Failure to allocate buffer for user passcode. |
PassCode1 not Allocated |
SmLoginLogoutMessage::Mem-AllocPasscode1Fail |
Used in SecurID authentication scheme. Failure to allocate buffer for user passcode. |
PassCode1 not Allocated |
SmLoginLogout-Message::Passcode1Not-Allocated |
Used in SecurID authentication scheme. Failure to allocate buffer for next user passcode. |
PassCode1 not checked, |
SmLoginLogoutMes-sage::PassCode1NotChecked |
The error message is given in the SecurID authentication scheme if ACE authentication process through the ACE/SecurID API cannot be completed. |
PassCode1 not set, |
SmLoginLogoutMessage::Pass-Code1NotSet |
The message is given when the SecurID authentication scheme is making attempt to register passcode for ACE authentication with ACE/SecurID API. |
PassCode1 not set, |
SmLoginLogoutMessage::Pass-Code2NotSet |
The error message is given by HTML SecurID authentication scheme when it fails to register next passcode for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
PassCode2 not Allocated |
SmLoginLogoutMessage::Mem-AllocPasscode2Fail |
Used in SecurID authentication scheme. Failure to allocate buffer for user passcode. |
PassCode2 not Sent as NextPasscode, Error = %1i |
SmLoginLogoutMessage::Pass-Code2NotSentAsNextPasscode |
The error message is given by HTML SecurID authentication scheme when it fails to send next passcode to ACE server through ACE/SecurID API. The authentication scheme rejects the request. |
Password Message could not be parsed |
SmLoginLogout-Message::PasswordMessage-ParseFail |
When processing Login request, and breaking up password for New and Old, failed to parse password string. |
PIN allocation failed |
SmLoginLogoutMessage::Pin-AllocationFailed |
Used in HTML SecurID authentication scheme. Failure to allocate buffer for user PIN. |
pszBuf allocation failed |
SmLoginLogoutMessage:pszBuf-AllocFail |
Used in SecurID authentication scheme. Failure to allocate buffer for RSA SecurID user ID attribute name in SiteMinder user directory. |
Returning encrypted System PIN in Cookie via UserMsg |
SmLoginLogoutMes-sage::ReturningEncrypted-SystemPin |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
SelectionCode not allocated. |
SmLoginLogout-Message::SelectionCodeNot-Allocated |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Server exception occurred while authenticating user '%1s' |
'SmLoginLogoutMessage::User-AuthException |
Unknown error happened during Authentication process. Most likely in authentication provider library. |
Server exception occurred |
'SmLoginLogoutMessage::Valid-AuthException |
Error occurred in advanced password services shared library when called during Authentication process. |
Set Username Error = %1i |
SmLoginLogoutMessage::Set-UserNameError |
The message is given by SecurID authentication schemes when ti fails to register username for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
SetVariable :Internal |
SmLoginLogoutMessage::Set-VariableFindError |
Variable name is empty when trying to set it into Session Store. |
SetVariable :Internal Error: NULL Value found for |
SmLoginLogoutMessage::Set-VariableNullValueFound |
Variable value is empty when trying to set it into Session Store. |
SetVariable Returned Error |
SmLoginLogoutMessage::Set-VariableReturnError |
Failed to add/update this variable into Session Store. |
SmAuthenticate: AceInitialization failed |
SmLoginLogoutMessage::Sm-AuthAceInitFail |
Failed to Initialize ACE client library. |
SmAuthenticate: Cannot |
SmLoginLogoutMessage::Create-EventFail |
Used in SecurID authentication scheme. Failure to create event object in SecurID authentication scheme. |
SmAuthenticate: Couldn't get allocate memory for PIN |
SmLoginLogoutMessage::Sm-AceHtmlPinMemAllocFail |
Used in SecurID authentication scheme. Failure to allocate buffer for ACE system-generated PIN. |
SmAuthenticate: Did not set AceSetPasscode = %1s |
SmLoginLogoutMessage::Sm-AuthAceDidNotSetPassCode |
The error message is given by SecurID authentication schemes when it fails to register passcode for ACE authentication with ACE/SecurID API. The authentication scheme rejects the request. |
SmAuthenticate: No numeric value found for SM_ACE_FAILOVER_ATTEMPTS environment variable, proceeding with default value. |
SmLoginLogoutMessage::Zero-SmAuthAceFailover |
To support RSA ACE/SecurID failover, SiteMinder Policy Server has an environment variable SM_ACE_FAILOVER_ATTEMPTS. By default, it set to 3. The error message is given when the value of SM_ACE_FAILOVER_ATTEMPTS is 0. In this case RSA ACE/SecurID failover may not work properly with SiteMinder. |
SmAuthenticate:Cannot allocate storage for EventData |
SmLoginLogoutMessage::Event-DataMemAllocFail |
Used in SecurID authentication scheme. Failure to allocate memory for RSA SecurID API structure. |
SmAuthenticate:Cannot proceed to AceInit--NOT ACE_PROCESSING. aceRetVal= %1i |
SmLoginLogoutMessage::Sm-AuthAceInitProcessingFail |
The message is given by SecurID authentication schemes when it fails to initialize ACE/SecurID API. The authentication scheme rejecting the request and the authentication fails. |
SmAuthenticate:Did not continue to AceCheck. aceRetVal= %1i |
SmLoginLogoutMessage::Sm-AuthAceCheckDidNotContinue |
The error message is given in the SecurID authentication scheme if ACE authentication process through the ACE/SecurID API cannot be completed. |
SmAuthenticate:Did not continue to AceInit completion. pEventData->asynchAceRet= %1i |
SmLoginLogoutMessage::Sm-AuthAceInitCompletionFail |
The message is given by SecurID authentication schemes when it fails to initialize ACE/SecurID API. The authentication scheme rejecting the request and the authentication fails. |
SmAuthenticate:Name Lock Request has been denied by ACE/Server communication failure. |
SmLoginLogoutMessage::Sm-AuthNameLockReqDenied |
The message is given by SecurID authentication schemes when it fails to initialize ACE/SecurID API. The authentication scheme rejecting the request and the authentication fails. |
SmAuthenticate:Thread Sync failed. wRet= %1ul |
SmLoginLogoutMessage::Sm-AuthThreadSyncFail |
The message is given on Windows platform by SecurID authentication schemes when the call to asynchronous ACE API call fails. |
SmAuthenticate:Unable to |
SmLoginLogoutMessage::Sm-AuthUserNameLockFail |
The message is given by SecurID authentication schemes when it fails to lock username for ACE server. In this case SiteMinder authentication scheme rejects the authentication requests. The name lock feature is available in RSA ACE product of version 5.0 and above.see RSA ACE product documentation for additional information on name lock feature. |
SmAuthUser - Failed to fetch Az Realm. |
SmLoginLogoutMessage::Fetch-AzRealmFailed |
Failed to find user Realm when getting Application Role User property. |
SmAuthUser - Failed to fetch Domain object. |
SmLoginLogoutMessage::Fetch-DomainObjFailed |
Failed to find user Domain when getting Application Role User property. |
The new PIN can contain |
SmLoginLogoutMessage::Alpha-NumericOnlyNewPin |
The message is used in HTML SecurID authentication scheme when user was required to change a PIN, and user enters a PIN that contains non-alphanumeric characters. |
The new PIN can contain |
SmLoginLogoutMessage::Digit-OnlyNewPin |
The message is used in HTML SecurID authentication scheme when user was required to change a PIN, and user enters a PIN that contains non-digits. |
The new PIN is too long |
SmLoginLogoutMessage::Long-NewPin |
The message is used in HTML SecurID authentication scheme when user was required to change a PIN and a new PIN is too long. |
The new PIN is too short |
SmLoginLogoutMessage::Short-NewPin |
The message is used in HTML SecurID authentication scheme when user was required to change a PIN and a new PIN is too short. |
Unable to proceed PIN change, unknown PIN type. |
SmLoginLogoutMessage::Ace-ServerUnableToProceedPin-Change |
Information only. If you are experiencing problems with your ACE/SecurID authentication scheme(s), please provide this message to Technical Support. |
Unexpected Message ID |
SmLoginLogout-Message::UnexpectedMessage-ID |
When processing Login request, and breaking up password for New and Old, message ID stored in password field is unknown. |
Usage: %1s[:AppName] |
SmLoginLogoutMessage::Usage-SmUserAttribFormat |
Help string for correct Application Role User property formatting. |
UserPIN not allocated. |
SmLoginLogoutMessage::User-PinNotAllocated |
Used in SecurID authentication scheme. Failure to allocate buffer for user PIN. |
ValidateLoginAttempt - Error Applying Password Policy |
SmLoginLogoutMessage::Error-ApplyingPasswordPolicy |
Failed when tried to Apply Password Policy while validating Logging attempt. |
ValidateLoginAttempt - Error Fetching Password Policy |
SmLoginLogoutMessage::Error-FetchingPasswordPolicy |
Failed to fetch PasswordPolicy object while validating Logging attempt. |
ValidateLoginAttempt - Error Finding Applicable Policies |
SmLoginLogoutMessage::Error-FindingApplicablePolicy |
Failed to Find Applicable Policies while validating Logging attempt. |
ValidateNewPassword - Can't set password change info. |
SmLoginLogoutMessage::Error-PasswordChange |
Failed to set password info while trying to Update Password Blob Data. |
ValidateNewPassword - Error fetching Match regular expressions |
SmLoginLogoutMessage::Match-ExprFetchError |
Failed to get the desired regular expressions for the password policy. |
ValidateNewPassword - Error fetching NoMatch regular expressions |
SmLoginLogoutMessage::No-MatchExprFetchError |
Failed to get the desired regular expressions for the password policy. |
ValidateNewPassword - Error fetching password policy |
SmLoginLogoutMessage::Err-FetchingValidPwdPolicy |
Failed to fetch PasswordPolicy object while validating New Password. |
ValidateNewPassword - Error finding applicable password policies. |
SmLoginLogoutMessage::Err-FindingValidPwdPolicy |
Failed to Find Applicable Policies while validating New Password. |
ValidateNewPassword could not load callout '%1s |
'SmLoginLogoutMessage::Load-CalloutFail |
Failed to Load external library to check password. |
ValidateNewPassword |
SmLoginLogoutMessage::Err-ResolveFuncValidPwd |
Failed to find method in external library to check password. |
Error Message |
Function |
Description |
---|---|---|
Bad %1s request detected |
SmIsAuthorizedMessage::Bad-RequestDetected |
The Authorization Request message failed to conform to the proper format. |
Cannot process active |
SmIsAuthorizedMessage::CanNot-ProcessActiveExpr |
The license for the eTelligent Rules feature is not found. The Active Expression will not be processed. |
Caught exception while |
SmIsAuthorizedMessage::Exc-AddingVar |
A software exception was raised while resolving eTelligent Rules variables. |
Exception in IsOk. |
SmIsAuthorizedMessage::Unk-ExcInIsOK |
An unknown exception occurred while performing an Authorization. |
Exception in IsOk. %1s |
SmIsAuthorizedMessage::ExcIn-IsOK |
An exception occurred while performing an Authorization. |
Failed to Fetch Active |
SmIsAuthorizedMessage::Failed-FetchActiveExpr |
Could not fetch the Active Expression object from the object store. |
Failed to Load Active |
SmIsAuthorizedMessage::Failed-LoadActiveExpr |
The Active Expression could not be loaded. |
Failed to Load Domain %1s |
SmIsAuthorizedMessage::Failed-LoadDomain |
Failed to retrieve the Domain object during eTelligent Rules variable processing. |
Failed to Load Variable %1s |
SmIsAuthorizedMessage::Failed-LoadVar |
Failed to get the specified eTelligent Rules variable. |
Failed to Load Variable Type |
SmIsAuthorizedMessage::Failed-LoadVarType |
Failed to get the type of the specified variable. |
Failed to Load Variables for |
SmIsAuthorizedMessage::Failed-LoadVarActiveExpr |
There was a problem resolving Variables, therefore the Active Expression will not be invoked. |
Failed to Load Variables for |
SmIsAuthorizedMessage::Failed-LoadVarsForActiveExpr |
Failed to load eTelligent Rules Variables for an Active Expression |
Failed to resolve attribute |
SmIsAuthorizedMes-sage::FailedToResolveAttr |
Could not fetch the Response Attribute object from the object store. |
Failed to resolve dictionary |
SmIsAuthorizedMes-sage::FailedToResolveDictVendAttr |
Could not find the specified Vendor Attribute in the Vendor Attribute Dictionary. |
Failed to resolve response |
SmIsAuthorizedMes-sage::FailedToResolveResponse |
Could not fetch the Response object from the object store. |
Failed to resolve response group %1s |
SmIsAuthorizedMes-sage::FailedToResolveResponseGp |
Could not fetch the Response Group object from the object store. |
Failed to resolve user policy |
SmIsAuthorizedMes-sage::FailedToResolveUserPolicy |
Could not fetch the User Policy object from the object store. |
Ignoring variable response - no license for eTelligent Options |
SmIsAuthorizedMessage::No-eTelligentLicense |
The license for the eTelligent Rules feature was not found. Variables will not be processed. |
Invalid response attribute |
SmIsAuthorizedMessage::Invalid-ResponseAttr |
An invalid Response Attribute was not included in the Authorization response. |
IsOk failed. %1s |
SmIsAuthorizedMessage::IsOK-Failed |
The Authorization check failed |
Message |
Function |
Description |
---|---|---|
Failed to initialize TCP server socket: Socket error:%1i |
SmServerMessage::TCP-ServerSocketInitFail |
see the operating system documentation for the specifics of the socket error. (The most common errors are attempting to open a socket already in use on the system or not having sufficient privilege for the socket.) |
Failed to initialize UDP |
SmServerMessage::UDP-ServerSocketInitFailOnPort |
see the operating system documentation for the specifics of the socket error. (The most common errors are attempting to open a socket already in use on the system or not having sufficient privilege for the socket.) |
Failed to initialize WinSock library |
SmServerMessage::WinSock-LibInitFail |
(Windows systems.) The Windows Sockets library could not be initialized. Verify the library is installed and that its version is supported. |
Failed to listen on TCP |
SmServerMessage::TCP-ServerSocketListenFail |
see the operating system documentation for the specifics of the socket error. (The most common errors are attempting to open a socket already in use on the system or not having sufficient privilege for the socket.) |
Failed to load event handler |
SmServerMessage::Event-HandlerLoadFail |
An Event Handler library could not be loaded. Verify the pathnames and access permissions of the configured Event Handlers. |
Failed to load library ’%1s’. |
SmServerMessage::FailedTo-LoadLib |
The reported Authentication Scheme library could not be loaded. If the accompanying error text does not explain the problem, verify that the named library exists and that the file system protections allow access. |
Failed to locate required |
SmServerMessage::Req-EntryPointInEventProvider-LocateFail |
The named library is not a valid Event/Audit Log provider. |
Failed to write audit log |
CSmReports::LogAccess |
The Policy Server could not write to the audit log. Verify the status of the audit log store. |
Failed to obtain host name. Socket error %1i |
SmServerMessage::Host-NameObtainError |
The Audit Logger provider could not retrieve the local system's network hostname, probably due to a network error. The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
Failed to obtain host name. Socket error %1i |
SmServerMessage::Host-NameObtainFail |
The local system's network hostname could not be retrieved, probably due to a network error. The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
Failed to open Audit log |
SmServerMessage::Audit-LogFileAppendFail |
The Audit Logger provider could not open the named file for appending entries. Verify that the pathname provided is valid and that file access permissions are correct. |
Failed to open RADIUS log |
SmServerMessage::Radius-LogFileNotDefined |
The registry does not have an entry for the RADIUS log file’s name, or the name was an empty string, |
Failed to open RADIUS log file: %1s |
SmServerMessage::Radius-LogFileOpenFail |
A RADIUS log file with the given name could not be opened for overwriting (if it already exists) or be created (if it does not exist). Check access permissions to the directory and to the file (if it exists). |
Failed to query authentication scheme ’%1s’ |
SmServerMessage::Fail-QueryAuthScheme |
The Policy Server's query of the given Authentication Scheme failed, so the Authentication Scheme could not be initialized. |
Failed to read on UDP socket. Socket error %1i |
SmServerMessage::UDP-SocketReadFail |
The Policy Server detected an unexpected network error while trying to read a UDP packet carrying either an Admin service connection request or a RADIUS message. The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
Failed to receive request on session # %1i : %2s/%3s:%4i. Socket error %5s |
SmServerMessage::Request-ReceiveOnSessionFail |
The Policy Server detected an unexpected network error while trying to read the agent request in the given session, so it closed the connection. The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
Failed to resolve agent key |
SmServerMessage::Unresolved-AgentKey |
The reported Agent Key could not be found in the Policy Store when Agent Keys were being updated. |
Failed to resolve agent keys |
SmServerMessage::FailTo-ResolveAgentKeys |
No Agent keys could be accessed in the Policy Store for Agent Key Update. |
Failed to resolve agent keys |
SmServerMessage::Agent-KeysResolveFail |
No Agent keys could be accessed in the Policy Store for Agent Key Update. |
Failed to resolve agent keys ’%1s’ |
SmServerMessage::Fail-ToResolveAgentKey |
The reported Agent Key could not be found in the Policy Store when Agent Keys were being updated. |
Failed to resolve Agent or AgentGroup %1s |
SmServerMessage::Agent-OrAgentGroupResolveFail |
The given Agent or Agent Group does not exist or its Policy Store record has become corrupted. |
Failed to resolve all domains |
SmServerMessage::Domain-ResolutionFailed |
The Domain root object record in the Policy Store is missing or has become corrupted. |
Failed to resolve all vendors. |
SmServerMessage::Failed-ToResolveVendors |
The Vendors root object record in the Policy Store is missing or has become corrupted. |
Failed to resolve auth-az |
SmServerMessage::Fail-ToResolveAuthAzMap |
The given Auth-Az Map does not exist or its Policy Store record has become corrupted. |
Failed to resolve function |
SmServerMessage::Failed-ToResolveFunc |
The reported entry point in the given Authentication Scheme library could not be resolved (see the accompanying error text), so the library was not loaded. |
Failed to resolve function |
SmServerMessage::Function-ResolveFail |
The reported entry point in the given TransactEMS library could not be resolved (see the accompanying error text), so the library was not loaded. |
Failed to resolve function |
SmServerMessage::Fail-ToResolveFunction |
The reported entry point in the given library which reports system configuration information could not be resolved (see the accompanying error text), so the library was not loaded. |
management object |
SmServerMessage::Key-ManagementObjResolveFail |
The Policy Server detected an error when it attempted to read the Key Management Object from the Policy Store. |
Failed to resolve key management object |
SmServerMessage::Resolve-KeyMgmtObjFail |
The Agent Key Management Object could not be read from the Policy Store. |
Failed to resolve key management object ’%1s’ |
SmServerMessage::Key-ManagementObjResolve-FailwithVal |
The Agent Key Management Thread detected an error when it attempted to read the given Agent Key Management Object from the Policy Store. |
Failed to resolve list of |
SmServerMessage::Fail-ToResolveAuthAzMapList |
The Auth-Az Map root object record in the Policy Store is missing or has become corrupted. |
Failed to resolve log file |
SmServerMessage::Log-FileNameRosolveFail |
The Audit Logger provider could not retrieve the name for the log file from the registry. Verify that a file name has been configured. |
Failed to resolve shared |
SmServerMessage::Shared-SecretResolveFail |
The Shared Secret Rollover Policy object record in the Policy Store is missing or has become corrupted. |
Failed to resolve user |
SmServerMessage::Fail-ToResolveUserDir |
The given User Directory object does not exist or its Policy Store record has become corrupted. |
Failed to resolve user |
SmServerMessage::User-IdentityFail |
Because there was a failure while searching the policies of the applicable realms, the user’s identity could not be resolved and access was denied. |
Failed to resolve Version 6 function ’%1s’ in ’%2s’ . |
SmServerMessage::Failed-ToResolveVer6Func |
The reported entry point in the given Version 6 Authentication Scheme library could not be found (see the accompanying error text), so the library will not be used. Verify that the Auth Scheme is not an older version. |
Failed to retrieve audit log |
SmServerMessage::Audit-LogFlushIntervalRetrieveFail |
The Audit Logger ODBC provider could not retrieve the flush interval from the registry. Verify that an interval has been configured. |
Failed to retrieve audit log provider library for |
SmServerMessage::AuditLog-ProviderLibRetrieveFail |
The registry does not have a library name entry for the given Audit Log Provider namespace. |
Failed to retrieve audit log |
SmServerMessage::Audit-LogRowFlushCountRetrieveFail |
The registry does not have an entry for the ODBC Audit Log Provider’s row flush count for asynchronous logging, so the default of 1000 will be used. |
Failed to retrieve message |
SmServerMessage::Retrieve-FromMessageQueueFail |
(Windows) An error occurred when the Policy Server process attempted to retrieve a message on its Windows Application Queue. |
Failed to rollover trusted |
SmServerMessage::Trusted-HostSharedSecretsRolloverFail |
An error occurred while attempting to roll over trusted host shared secrets. Verify that the rollover policy is valid. |
Failed to save key |
SmServerMessage::Save-NewMgmtKeyObjFail |
The Agent Key Management Object could not be read from the Policy Store when a new Persistent Key was to be saved. |
Failed to save key |
SmServerMessage::Save-NewMgmtKeyObjAfter-KeyUpdateFail |
The Policy Server generated new Agent Keys for roll over but could not record that they are available for use. |
Failed to save key |
SmServerMessage::Save-NewMgmtKeyObjAfter-PersistentKeyUpdateFail |
The new Persistent Key could not be saved in the Agent Key Management Object in the Policy Store. |
Failed to save key |
SmServerMessage::Save-NewMgmtKeyObjAfterSession-KeyUpdateFail |
The new Agent Session Key could not be saved in the Policy Store. |
Failed to save new |
SmServerMessage::Save-NewCurrentAgentKeyFail |
The given Agent Session Key could not be saved as the Agent’s "current" key. |
Failed to save new key management object |
SmServerMessage::Agent-KeyManagementObjSaveFail |
The Agent Key management thread generated new Agent Keys for roll over but could not record that they are available for use. |
Failed to save new ’last’ |
SmServerMessage::Save-NewLastAgentKeyFail |
The given Agent Session Key could not be saved in the Policy Store as the Agent’s "last" key. |
Failed to save new ’next’ |
SmServerMessage::Save-NewNextAgentKeyFail |
The given Agent Session Key could not be saved in the Policy Store as the Agent’s "next" key. |
Failed to save new |
SmServerMessage::Failed-ToSaveNewPersistentAgentKey |
The given Persistent Agent Key could not be saved in the Policy Store. |
Failed to send response on session # %1i : %2s/%3s:%4i. Socket error %5i |
SmServerMessage::Response-SendOnSessionFail |
The response to an agent request in the given session could not be sent due to a network error (or possibly the Agent failing). The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
Failed to start agent |
SmServerMessage::Agent-CommandManagementThread-CreationFail |
The "watchdog" thread which ensures that the Agent Command Management Thread is running failed to start. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start journal management thread |
SmServerMessage::Journal-ThreadCreateFail |
The "watchdog" thread could not [re-]start the Policy Store Journal Cleanup Management Thread. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start journal management watchdog |
SmServerMessage::Journal-ManagementThreadFail |
The "watchdog" thread which ensures that the Policy Store Journal Management Cleanup Thread is running failed to start. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start key |
SmServerMessage::AgentKey-ThreadCreateFail |
The "watchdog" thread could not [re-]start the Agent Key Management Thread. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start key |
SmServerMessage::Key-ManagementThreadCreateFail |
The "watchdog" thread which ensures that the Agent Key Management Thread is running failed to start. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start main reactor thread |
SmServerMessage::Main-ReactorThreadStartFail |
The Network IO Dispatcher Thread failed to start. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start object store |
SmServerMessage::Journal-StartFailed |
The "watchdog" thread could not [re-]start the Policy Store Journal Management Thread. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to start object store watchdog thread |
SmServerMessage::Watchdog-Failed |
The "watchdog" thread which ensures that the Policy Store Journal Management Thread is running failed to start. Check the operating system’s configured per-process limits for maximum number of threads and for maximum open file descriptors. |
Failed to stat management command channel |
SmServerMessage::Stat-MangmCmdChannelFail |
(Unix/Linux) The stat() of an already-existing Server Command Management pipe/file unexpectedly failed. If also the Server Command Management Thread fails to start, verify that another Policy Server process is not running and delete the pipe/file manually. |
Failed to update agent keys |
SmServerMessage::FailTo-UpdateAgentKeys |
The Administrator command that Agents update their keys could not be saved in the Policy Store. |
Failed to update agent keys |
SmServerMessage::Failed-ToUpdateAgentKeys |
An Agent’s new "current" or "next" Session Key could not be saved in the Policy Store. |
Failed to update changes |
SmServerMessage::Fail-ToUpdateChangesToAgentKeys |
The command that Agents update their keys could not be saved in the Policy Store. |
Failed to update persistent key |
SmServerMessage::Failed-ToUpdatePersistentKey |
An Agent’s Persistent Key could not be saved in the Policy Store. |
Failed to write on UDP socket. Socket error %1i |
SmServerMessage::UDP-SocketWriteFail |
An Admin GUI initialization packet or a RADIUS response packet could not be sent due to a network error (or possibly the Agent failing). The accompanying error code (an errno for UNIX systems, a SOCKET_ERROR for Windows systems) may provide more detail. |
file not found |
SmServerMessage::File-NotFound |
(Windows systems.) The service to start the One View Monitor could not read the bin\smmon.bat file. |
Getting processor affinity |
SmServerMessage::Get-ProcessorAffinityFail |
(Windows) The performance tuning parameter for processor affinity could not be processed, so the existing affinity setting will be unchanged. |
Handshake error: Unknown |
SmServerMessage::Handshake-ErrorUnknownClient |
A client provided the reported name when attempting to connect, but an Agent with that name could not be found in the Policy Store. Also caused by the agent using the wrong shared secret. |
Inconsistent agent key |
SmServerMes-sage::InconsistentAgent-KeyMarker |
An Agent Key record in the Policy Store has the given unrecognized key type. |
Inconsistent number of |
SmServerMes-sage::InconsistentNumberOf-AgentKeys |
The Policy Store contains the given incorrect number of keys for an Agent. |
Internal error computing |
SmServerMessage::Realm-Corrupt |
An unexpected Policy Store failure occured while attempting to fetch the realm list to perform access authorization, so access is denied. |
Invalid agent key marker |
SmServerMessage::Invalid-AgentKeyMarker |
An Agent Key record in the Policy Store has the given unrecognized key type. |
IP address resource filter not |
SmServerMessage::IPAddr-ResourceFilterNotSupported |
Action rules matching in realms does not support matching IP addresses or ranges. |
IsInDictionary - Could not |
SmServerMessage::Add-PasswordDictToHolderFailed |
The named password dictionary could not be cached, probably because no more than 100 dictionaries may be cached. Passwords to be matched against entries in the dictionary are assumed to match. |
IsInDictionary - Could not |
SmServerMessage::Create-PasswordDictFailed |
An unexpected error (probably an out-of-memory condition) occurred while preparing to cache the named password dictionary. Passwords to be matched against entries in the dictionary are assumed to match. |
IsInDictionary - Could not set |
SmServerMessage::Set-PasswordDictFailed |
An error occurred while caching the named password dictionary. Passwords to be matched against entries in the dictionary are assumed to match. |
IsInDictionary - Password Dictionary not open %1s |
SmServerMessage::Open-PasswordDictFailed |
The given password dictionary has been loaded but unexpectedly is not open. Passwords to be matched against entries in the dictionary are assumed to not match. |
IsInProfileAttributes - Error fetching property names |
SmServerMessage::Fetching-PropertyNameFail |
While comparing a password to user profile attribute values, the user attribute names could not be retrieved, so the password is assumed to match. |
IsInProfileAttributes - Error fetching property values |
SmServerMessage::Fetching-PropertyValueFail |
While comparing a password to user profile attribute values, an attribute value could not be retrieved, so the password is assumed to match. |
Monitor request for unrecorded data, Null values returned |
SmServerMessage::MonReq-UnrecordedDataNullValue |
The Policy Server did not recognize the name passed it in a request for monitored data. |
No agent encryption keys |
SmServerMessage::Agent-EncryptionKeyNotFound |
When an Agent’s set of keys was fetched from the Policy Store, a complete set was not found. |
No agent keys in key store |
SmServerMessage::AgentKey-NotFoundInKeyStore |
While attempting to update the Agent Keys in the Policy Store, none were found. |
No initial agent keys |
SmServerMessage::Empty-AgentKeys |
The Policy Store holds no Agent Keys and Key Generation has not been enabled. |
No initial key management |
SmServerMessage::Key-ManagementObjNotFound |
The Policy Store does not hold an initial Agent Key Management object and Key Generation has not been enabled. |
No namespace available for |
SmServerMessage::No-NamespaceAvailForAudit-LogProvider |
The registry does not have an entry for the Audit Log Provider namespace. |
No Root Config object found, Please run smobjimport to |
SmServerMessage::Root-ConfigObjNotFound |
The Policy Store has not been successfully initialized. |
No session pointer while processing request %1s |
SmServerMessage::Null-SessionPointer |
The given Agent request was received but the corresponding Agent Session object was not found or valid, so the request packet was returned without processing. |
Please check file permissions |
SmServerMessage::File-PermissionOrPathCheck |
A file could not be opened. An error message giving the file’s path name should precede this message.Verify that the pathname provided is valid and that file access permissions are correct. |
Policy Server caught |
SmServerMessage::Unknown-PolSrvExcpCaught |
The Policy Server had an unexpected exception while processing an Agent request, so an empty response was returned. |
Policy Server caught |
SmServerMessage::PolSrv-ExcpCaught |
The Policy Server had an unexpected exception while processing an Agent request, so an empty response was returned. The accompanying text may recommend corrective action. |
Policy store failed operation |
SmServerMessage::Policy-StoreOperFail |
The Policy Store object layer caught the described exception. |
Processor affinity left at default setting, cannot set affinity to |
SmServerMessage::Processor-AffinitySetZeroFail |
(Windows) Zero is an invalid value for the performance tuning parameter for processor affinity, so the existing affinity setting will be unchanged. |
Reject %1s : Failed to write access log |
SmServerMessage::Write-FailInAccessLog |
Audit logging failed for the given rejected Authentication or Authorization request. |
Saw agent name in DoManagement() command |
SmServerMessage::Agent-NameInDoManagement |
The "Do Management" Agent command was rejected. |
Saw agent name in Logout() command %1s , request %2s |
SmServerMessage::Agent-NameInLogout |
The Logout request was rejected. |
Setting processor affinity |
SmServerMessage::Set-ProcessorAffinityFail |
(Windows) The performance tuning parameter for processor affinity could not be processed, so the existing affinity setting will be unchanged. |
SM exception caught during initialization (%1s) |
SmServerMessage::SMExcp-DuringInit |
During the Policy Server startup "GlobalInit" phase, an exception was caught and startup failed. The accompanying text may provide more detail. |
SM exception caught during server shutdown (%1s) |
SmServerMessage::SMExcp-DuringServerShutdown |
During the Policy Server shutdown "GlobalRelease" phase, an exception was caught. The accompanying text may provide more detail. |
TCP port initialization failure |
SmServerMessage::TCP-PortInitFail |
During Policy Server startup the TCP ports enabled for Access Control or Administration requests could not be initialized, so startup was terminated. |
The service loader failed to |
SmServerMes-sage::SZSERVER_StartFail |
(Windows) The service loader could not be started (see error text), so it could not start the Policy Server or One View Monitor. |
This policy server does not |
SmServerMessage::Session-EncryptKeyNotFound |
The Policy Server does not have an initial Session Key and Key Generation is not enabled. If Access Control Requests or Administration Requests are configured to be served, startup is terminated. |
Thread Pool thread caught exception |
SmServerMessage::ExcpIn-ThreadPool |
A Policy Server Worker Thread terminated due to an unexpected condition. A replacement thread will be added to the Thread Pool. |
UDP port initialization failure |
SmServerMessage::UDPPort-InitFail |
During Policy Server startup the UDP ports enabled for Administration or RADIUS requests could not be initialized, so startup was terminated. |
UDP processing exception. |
SmServerMessage::UDP-ProcessingExcp |
While an Admin GUI initialization packet or a RADIUS response packet was being processed an unexpected error occurred. No response is sent. |
Unable to create console |
SmServerMessage::Trace-NotEnableConsoleOutput-CollecCreateFail |
The Policy Server process could not access the console (or terminal window) as output for the Profiler (trace) log output. Verify that it has appropriate access permission to open the console. |
Unable to create file output collector. Tracing will not be enabled |
SmServerMessage::Trace-NotEnableFileOutput-CollecCreateFail |
A Profiler (trace) log file could not be opened for overwriting (if it already exists) or be created (if it does not exist). Check access permissions to the directory and to the file (if it exists). |
Unable to create shared |
SmServerMessage::Shared-SecretCreateFail |
During Policy Server startup no Shared Secret policy object was found in the Policy Store, then creation of an initial policy object failed so startup was terminated. |
Unable to enable tracing |
SmServerMessage::Trace-NotEnable |
The initial setup of Profiler (trace) logging was successful but the remainder was not. |
Unable to reset logger |
SmServerMessage::Dynamic-LoggerResetFail |
The thread which detects that logger configuration options were changed while the Policy Server is running could not start, so such changes will not be acted upon unil the Policy Server has been restarted. |
Unable to resolve agent for request %1s |
SmServerMessage::Unresolved-AgentIdentity |
The Agent request is required to include the Agent identity but it could not be verified. The request is rejected. |
Unable to resolve agent |
SmServerMessage::AgentName-UnResolved |
The Agent request is required to include the Agent identity but it could not be verified for the named Agent. The request is rejected. |
Unable to update password |
SmServerMessage::Blob-UpdateFailed |
A user’s "Password Blob" data for Password Services could not be updated in the User Store. If it is so configured, the Policy Server rejected the user’s authentication attempt. |
Unexpected exception while publishing AZ Libs |
SmServerMes-sage::UnexpectedException-PublishingAzLibs |
An unexpected exception occurred while querying information about loaded custom authorization modules for diagnostic "Publish" information, so information regarding custom authorization libraries will not be published. |
Unknown agent key type %1i |
SmServerMessage::Agent-KeyTypeUnknown |
While Processing a "Do Management" request, An Agent Key record in the Policy Store was found with the given unrecognized key type, and the request was rejected. |
Unknown Exception caught |
SmServerMessage::Unknown-ExcpPublishAuthLibs |
An unexpected exception occurred while querying custom authentication scheme libraries for diagnostic "Publish" information, so information regarding loaded custom authentication schemes will not be published. |
Unknown exception caught |
SmServerMessage::Unknown-ExcpWhilePublishEventLibInfo |
An unexpected exception occurred while querying a custom event handler library for diagnostic "Publish" information, so information regarding custom event libraries loaded by SiteMinder will not be published. |
Socket Error 104 |
104 - A call to bind() function failed. |
This message is returned due to an error occurring when the message is sent across the TLI layer. |
Error Message |
Function |
Description |
---|---|---|
%1s could not fetch administrator directory |
SmJavaApiMes-sage::AdministratorDirectory-FetchFail |
Unable to fetch the Registration Administrator User Directory. Check Policy Store. |
%1s could not fetch |
SmJavaApiMes-sage::RegistrationDirectory-FetchFail |
Unable to fetch the Registration User Directory. Check Policy Store. |
%1s could not fetch |
SmJavaApiMes-sage::RegistrationDomain-FetchFail |
Unable to fetch the Registration domain. Check Policy Store. |
%1s could not fetch |
SmJavaApiMes-sage::RegistrationRealm-FetchFail |
Unable to fetch the Registration realm. Check Policy Store. |
%1s could not fetch |
SmJavaApiMes-sage::RegistrationScheme-FetchFail |
Unable to fetch the Registration scheme. Check Policy Store. |
%1s invalid realm oid (null) |
SmJavaApiMessage::Invalid-RealmOid |
Unable to get the realm oid. Ensure that the user login was successful and a valid Session ID is available. |
(CSmEmsCommand::Set-ObjectClasses) Could |
SmJavaApiMessage::Csm-EmsSetObjectClasses-RollBackPropertiesFail |
Unable to reset the properties of the user after new values were rejected. Verify that the user store is operating correctly and the Policy Server can establish a connection. |
(CSmEmsCommand::Set-Properties) Could not |
SmJavaApiMessage::CSm-EmsSetPropertiesRollback-PropertiesFail |
Unable to reset the properties of the user after new values were rejected. Verify that the user store is operating correctly and the Policy Server can establish a connection. |
(CSmEmsCommandV2::Set-ObjectClasses) Could not rollback properties of |
SmJavaApiMessage::Set-ObjectClassesDir-UserRollbackFail |
Unable to reset the properties of the user after new values were rejected. Verify the directory connection defined in the policy store. |
(CSmEmsCommandV2::Set-Properties) Could not |
SmJavaApiMessage::Set-PropertiesDirObjRollbackFail |
Unable to reset the properties of the object after new values were rejected. Verify the directory connection defined in the policy store. |
Exception in Transact SessionTimeoutThread. |
SmJavaApiMessage::Unknown-ExcpTransactSessionTimeout-Thread |
An unknown error occurred while trying to process expired sessions. |
Exception in Transact SessionTimeoutThread. |
SmJavaApiMessage::Excp-TransactSessionTimeoutThread |
An error occurred while trying to process expired sessions. |
Failed to create EmsSession Timeout Thread |
SmJavaApiMessage::Ems-SessionTimeoutThread-CreateFail |
There are not enough system resources to create a new thread. |
Failed to resolve all domains |
SmJavaApiMessage::Domain-ResolveFail |
A problem occurred while trying to retrieve all domains associated with the current administrator. Check for Policy Store corruption. |
getUsersDelegatedRoles |
SmJavaApiMessage::IMSget-UsersDelegatedRolesFail |
Unable to retrieve roles for this user. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersDelegatedRolesInApp failed, error = %1s |
SmJavaApiMessage::IMSget-UsersDelegatedRolesInAppFail |
Unable to retrieve user roles for the application. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersDelegatedTasks |
SmJavaApiMessage::IMSget-UsersDelegatedTasksFail |
Unable to retrieve tasks for this user. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersDelegatedTasksInApp failed, error = %1s |
SmJavaApiMessage::IMS-getUsersDelegatedTasksIn-AppFail |
Unable to retrieve user tasks for the application. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersRoles failed, |
SmJavaApiMessage::IMS-getUsersRolesFail |
Unable to retrieve roles for this user. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersRolesInApp failed, |
SmJavaApiMessage::IMS-getUsersRolesInAppFail |
Unable to retrieve user roles for the application. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersTasks failed, |
SmJavaApiMessage::IMS-getUsersTasksFail |
Unable to retrieve tasks for this user. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
getUsersTasksInApp failed, error = %1s |
SmJavaApiMessage::IMS-getUsersTasksInAppFail |
Unable to retrieve user tasks for the application. Make sure the library smobjims.dll (libsmobjims.so) is installed. |
IMSObjectProviderFactory: |
SmJavaApiMessage::getIMSB-aseObjectProvider_getProc-AddressFail |
Make sure the library smobjims.dll (libsmobjims.so) is installed. |
IMSObjectProviderFactory:get-Provider() - error loading |
SmJavaApiMes-sage::IMS_getProviderLib-LoadError |
This message is generated at startup if IdentityMinder not installed, or not installed correctly. |
IMSObjectProviderFactory:get-Provider() - getProcAddress |
SmJavaApiMes-sage::IMS_getProvider_get-ProcAddressFail |
The library is corrupt or the Policy Server could not load the library due to lack of resources. |
ImsRBACProviderFactory:get-Provider() - getProcAddress |
SmJavaApiMessage::Ims-RBACProvider-Factory_getProviderFail |
This message is generated at startup if IdentityMinder not installed, or not installed correctly. |
IsAssociatedWithDirectory failed, error = %1s |
SmJavaApiMessage::IMSIs-AssociatedWithDirectoryFail |
An error occurred while trying to determine if the user directory is valid for the associated IMS Environment. |
IsUserAssignedRole failed, |
SmJavaApiMessage::IMSIs-UserAssignedRoleFail |
An error occurred while trying to determine if the user belongs to a role. |
IsUserDelegatedRole failed, error = %1s |
SmJavaApiMessage::IMSIs-UserDelegatedRoleFail |
An error occurred while trying to determine if the user belongs to a role. |
SmJavaAPI: Error finding |
SmJavaApiMessage::MSG_E_-FINDING_CAEClog |
The JVM was unable to find the Active Expression class during unitization. Make sure the Option Pack is installed on the Policy Server. Check classpath for smjavaapi.jar. |
SmJavaAPI: Error finding |
SmJavaApiMessage::MSG_E_-FINDING_CNCElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding |
SmJavaApiMessage::MSG_E_-FINDING_CAUTHClog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. |
SmJavaAPI: Error finding class Throwable %1p |
SmJavaApiMessage::MSG_E_-FINDING_CTHROWlog |
The JVM/JRE appears to not have been installed properly. Check to see if a valid rt.jar exists. Ensure that SiteMinder is configured to use a supported version of the JVM. |
SmJavaAPI: Error finding |
SmJavaApiMessage::MSG_E_-FINDING_CTSClog |
Make sure the Option Pack is installed on the Policy Server a valid smjavaapi.jar exists and is included in the classpath. |
SmJavaAPI: Error finding |
SmJavaApiMessage::MSG_E_-FINDING_CUAElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding method ActiveExpressionContext. |
SmJavaApiMessage::MSG_E_-FIND_MINVOKElog |
Make sure the Option Pack is installed on the Policy Server a valid smjavaapi.jar exists and is included in the classpath |
SmJavaAPI: Error finding method ActiveExpressionContext. |
SmJavaApiMessage::MSG_E_-FIND_MRELEASElog |
Make sure the Option Pack is installed on the Policy Server a valid smjavaapi.jar exists and is included in the classpath |
SmJavaAPI: Error finding method SmAuthenticationContext. |
SmJavaApiMessage::MSG_E_-FIND_MAUTHENTICATElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding method SmAuthenticationContext. |
SmJavaApiMessage::MSG_E_-FIND_MAUTHINITlog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding method SmAuthenticationContext. |
SmJavaApiMessage::MSG_E_-FIND_MAUTHQUERYlog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding method SmAuthenticationContext. |
SmJavaApiMessage::MSG_E_-FIND_MAUTHRELEASElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error finding method Throwable.getLocalized-Message %1p |
SmJavaApiMessage::MSG_E_-FIND_GLMlog |
The JVM/JRE appears to not have been installed properly. Check to see if a valid rt.jar exists. Ensure that SiteMinder is configured to use a supported version of the JVM. |
SmJavaAPI: Error finding method TunnelServiceContext.tunnel %1p |
SmJavaApiMessage::MSG_E_-FIND_MTUNNELlog |
Make sure a valid smjavaapi.jar exists and is included in the classpath |
SmJavaAPI: Error initializing Java active expressions %1p |
SmJavaApiMessage::MSG_E_-ACTEXPR_INITlog |
Unable to load the Active Expression library. Check to see if smactiveexpr.jar is in the classpath |
SmJavaAPI: Error initilizing |
SmJavaApiMessage::MSG_E_-INIT_JNI_REFSlog |
The JVM encountered an internal error. Check JVM installation. |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CAEClog |
The JVM encountered an internal error establishing the active expression context |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CNCElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CAUTHClog |
The JVM encountered an internal error establishing a authentication context |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CTHROWlog |
The JVM/JRE appears to not have been installed properly. Check to see if a valid rt.jar exists. Ensure that SiteMinder is configured to use a supported version of the JVM. |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CTSClog |
The JVM encountered an internal error establishing a tunnel connection |
SmJavaAPI: Error making |
SmJavaApiMessage::MSG_E_-GLOBAL_CUAElog |
Make sure a valid smjavaapi.jar exists and is included in the classpath. Check to see if the JVM version is supported for this release. |
SmJavaAPI: Error releasing |
SmJavaApiMessage::MSG_E_-ACTEXPR_RELEASElog |
The JVM encountered an internal error. Check JVM installation. |
SmJavaAPI: Error releasing |
SmJavaApiMessage::MSG_E_-REL_JNI_REFSlog |
The JVM encountered an internal error. Check JVM installation. |
SmJavaAPI: Unable to get a JVM environment %1p |
SmJavaApiMessage::MSG_-ERR_GETTING_JVMlog |
The JVM encountered an internal error. Check JVM installation. |
SmJavaAPI: Unable to |
SmJavaApiMessage::MSG_-ERR_INIT_JNI_REFlog |
The JVM encountered an internal error. Check JVM installation. |
SmJavaAPI: Unable to |
SmJavaApiMessage::MSG_-ERR_REL_JNI_REFlog |
Policy Server could not completely release resources either after authorization or during shutdown. |
SmJVMSupport: Error |
SmJavaApiMessage::MSG_E_-ATTACH_TO_THREADlog |
The JVM might not have been properly initialized. Make sure there are no stray java processes running |
SmJVMSupport: Error |
SmJavaApiMessage::MSG_E_-CREATE_JVMlog |
Make sure the JVM is installed correctly and the library jvm.dll (libjvm.so) is valid |
SmJVMSupport: Error destroying JVM %1p |
SmJavaApiMessage::MSG_E_-DESTROYING_JAVA_VMlog |
The Policy Server did not execute a clean shutdown. JVM resources were not released. |
SmJVMSupport: Error |
SmJavaApiMessage::MSG_E_-DETACH_THREADlog |
The Policy Server did not execute a clean shutdown. JVM resources were not released. |
SmJVMSupport: Error finding class System to release resources from JVM %1p |
SmJavaApiMessage::MSG_E_-JVM_RR_FSYSlog |
The Policy Server did not execute a clean shutdown. JVM resources were not released. |
SmJVMSupport: Error getting CLASSPATH environment variable when creating JVM |
SmJavaApiMessage::MSG_E_-GETENV_CPlog |
Ensure that the CLASSPATH variable is correctly defined |
SmJVMSupport: Error getting JVM environment to release resources from JVM %1p |
SmJavaApiMessage::MSG_E_-JVM_RR_ENVlog |
The Policy Server did not execute a clean shutdown. JVM resources were not released. |
SmJVMSupport: Error getting method GC on class System |
SmJavaApiMessage::MSG_E_-JVM_RR_GGClog |
The JVM was unable to run the garbage collection. Ensure the validity of rt.jar |
SmJVMSupport: Error |
SmJavaApiMessage::MSG_E_-OPEN_JVM_OPTION_FILElog |
Ensure that the environment variable NETE_JVM_OPTION_FILE is set and the file is valid |
SmJVMSupport: Error trying |
SmJavaApiMessage::MSG_E_-GET_CREATED_JVM_LOG |
The JVM might not have been properly initialized. Make sure there there are no stray java processes running . |
SmJVMSupport: Unknown |
SmJavaApiMessage::MSG_E_-CAUGHT_CREATE_JVMlog |
Make sure the JVM is installed correctly and the library jvm.dll (libjvm.so) is valid |
Copyright © 2012 CA.
All rights reserved.
|
|