SecureLogin error messages display a number code that generally includes a text description of the error. SecureLogin error numbers currently range between -101 and -914. Following is a list of these error message, their cause, and the appropriate action to take.
Some of the codes displayed in SecureLogin error messages are not native SecureLogin codes. Refer to the relevant application’s Help for assistance with the following:
NetIQ eDirectory: Numbers between -1 and -813
Microsoft Active Directory; Error codes such as, 0x80070002
For more information about Active Directory error codes, go to the Microsoft website.
-102: BROKER_NO_SUCH_ENTRY
Possible Cause:
You tried to load an application definition or variable that does not exist. For example, you set up Terminal Launcher to run from a shortcut or to run a particular application definition, but the application definition does not exist.
Action:
Check that the name of the application definition is actually defined in SecureLogin. Verify that the name is the same as the name specified in the application definition.
-103: BROKER_INVALID_CLASS_CREATED
Possible Cause:
Data has become corrupted, or you are running an earlier version.
SecureLogin is trying to create a new version of the application definition data format that was stored in ANDS.
Action:
Upgrade the older SecureLogin client to the new client. Install the latest SecureLogin software.
-104: BROKER_CREATE_CLASS_FAILED
Possible Cause:
The SecureLogin client has run out of memory.
Action:
Free up some memory. Try again later.
-105: BROKER_REMOVE_ENTRY_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-106: BROKER_UPDATE_GET_ENTRY_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-107: BROKER_ENTRY_NOT_FOUND
Possible Cause:
An attempt to load an application definition or variable that does not exist.
Action:
Check that the name of the application definition is actually defined in SecureLogin. Verify that the name is the same as the name specified in the application definition editor.
-109: BROKER_SCRIPT_BUFFER_ALLOC_FAILED
Possible Cause:
The SecureLogin client has run out of memory.
Action:
Free up some memory. Try again later.
-110: BROKER_NO_MORE_PLATFORMS
Possible Cause:
Data is corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-111: BROKER_NO_MORE_VARIABLES
Possible Cause:
Data is corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-112: BROKER_NO_SUCH_VARIABLE
Possible Cause:
You are trying to use an undefined variable. Because SecureLogin is not prompting you for the variable, data has become corrupted, or some other situation is preventing the software from working as expected.
Action:
Contact NetIQ Support.
-114: BROKER_PRIMARY_NOT_AVAILABLE
Possible Cause:
You are not logged on to the directory. You are using the offline cache. Therefore, you cannot perform some directory functions. For example, you cannot change your passphrase.
Action:
Log in to the directory.
-116: BROKER_HEADER_DATA_CORRUPT
Possible Cause:
Data is corrupted. You might have a customized build for your site, but have installed a standard version of SecureLogin, or have gone from a standard version to a customized build for your site.
Action:
Delete the local cache file and try again. If unsuccessful, contact NetIQ Support.
-120: BROKER_INVALID_PREF_DATA_TYPE
Possible Cause:
Data is corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-121: BROKER_PREFERENCE_DATA_CORRUPT
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-122: BROKER_TARGET_ENTRY_LIST_NOT_LOADED
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-123: BROKER_CACHE_PASSWORD_INCORRECT
Possible Cause:
You have tried to log on from offline mode, but the password you entered does not match the expected password from the local cache. Typically, the offline password is the passphrase answer.
Action:
Enter the correct passphrase answer or directory password.
-129: BROKER_ENTRY_LIST_NOT_NULL
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Delete the local cache file and try again. If unsuccessful, contact NetIQ Support.
-130: BROKER_ENTRY_LIST_NULL
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Delete the local cache file and try again. If unsuccessful, contact NetIQ Support.
-131: BROKER_YSM_LIST_NOT_NULL
Possible Cause:
Memory is not handled as expected.
Action:
Contact NetIQ Support.
-132: BROKER_SYM_LIST_NULL
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-138: BROKER_SYMBOL_DATA_CORRUPT
Possible Cause:
Data has become corrupted in the local cache file or in the directory.
Action:
Delete the local cache file and try again. If unsuccessful, contact NetIQ Support.
-140: BROKER_SCRIPT_DATA_CORRUPT
Possible Cause:
Data has become corrupted in application definitions.
Action:
Delete the local cache file and try again.
-141: BROKER_PREF_INVALID
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-142: BROKER_SET_PREF_INVALID
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-145: BROKER_SECURITY_ALERT
Possible Cause:
Unable to locate security keys (AuthData), but security data appears to exist. It is possible that someone has attempted to gain access to your security data.
Action:
Contact your system administrator.
-166: BROKER_INVALID_DES_KEY
Possible Cause:
Hex strings are invalid. The DES_KEY variable requires hexadecimal (0-9, A-F) numbers.
Action:
Make sure that the DES_KEY variable contains only hexadecimal numbers.
-167: BROKER_INVALID_DES_OFFSET
Possible Cause:
Hex strings are invalid. The DES_OFFSET variable requires hexadecimal (0-9, A-F) numbers.
Action:
Make sure the DES_OFFSET variable contains only hexadecimal numbers.
-168: BROKER_DESKEY_NOT_FOUND
Possible Cause:
You tried to generate a one-time password for a platform. However, you have not defined the DES_KEY variable.
Action:
Create the DES_KEY variable.
-169: BROKER_DESOFFSET_NOT_FOUND
Possible Cause:
You tried to generate a one-time password for a platform. However, you have not defined the DES_OFFSET variable.
Action:
Create the DES_OFFSET variable.
-171: BROKER_CACHE_FILE_OPEN_FAIL
Possible Cause:
SecureLogin tried to read or write to the offline cache. However, SecureLogin is unable to open the cache file.
Action:
Assign rights so that the specified user object has rights to the cache directory.
-173: BROKER_NO_MORE_CACHE_FILE_DATA
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-174: BROKER_CACHE_SAVE_FAILED
Possible Cause:
SecureLogin is unable to save data to the offline cache.
Action:
Assign rights so that the specified user object has rights to the cache directory.
-175: BROKER_CACHE_SECRETS_INCORRECT
Possible Cause:
The offline cache password is incorrect for either of the following reasons:
-
The key used to decrypt the cache file is not the key that the cache file was encrypted with.
-
If you log on as a user to a workstation and create a cache file, and then you go to another workstation, reset your passphrase and log on, then when you return to the original workstation this error message appears.
Action:
Delete the cache file.
-176: BROKER_PUBLIC_KEY_READ_FAILED
Possible Cause:
SecureLogin is unable to read the public key from Active Directory System.
Action:
Troubleshoot Microsoft Active Directory System and Microsoft ADAM.
-177: BROKER_PUBLIC_KEY_HAS_CHANGED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-179: BROKER_RTVALUE_DOES_NOT_EXIST
Possible Cause:
You tried to read a runtime variable that is not defined.
Action:
Check the application definition. Make sure that the variable is set before it is read or used as a command.
-180: BROKER_DS_VARIABLE_NOT_READ
Possible Cause:
You used one of the % variables to read a directory attribute, but SecureLogin cannot read the variable.
Action:
Make sure that you have spelled the attribute name correctly. Troubleshoot Microsoft Active Directory System or Microsoft ADAM.
-181: BROKER_WRONG_PASS_PHRASE
Possible Cause:
The passphrase or password is incorrect. The reason could be:
-
You entered the wrong passphrase.
-
You tried to change your passphrase, but entered it incorrectly.
-
You password protected the SecureLogin notification area (system tray) icon and entered the incorrect password.
Action:
Enter the passphrase or password correctly.
-190: BROKER_NO_AUTH_DATA_FOUND
Possible Cause:
Although the SecureLogin Entry attribute has data, the SecureLogin Auth attribute was blank.
Someone deleted the SecureLogin Auth attribute.
Action:
Delete the Prot:SSO Entry attribute.
SecureLogin creates these attributes the next time you run SecureLogin.
-192: BROKER_UNABLE_TO_INSTANTIATE
Possible Cause:
A module, for example, WinSSO, is unable to connect to the Combroker.
Action:
If you are using Windows 95, make sure that you have the latest DCOM update, or reinstall Internet Explorer.
For other platforms, reinstall SecureLogin.
-195: BROKER_FILE_TRAITS_OP_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-196: BROKER_DUMMY_OP_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-199: BROKER_ERROR_COMMAND_NOT_HANDLED
Possible Cause:
An application definition parser encountered an unrecognizable command.
-200: BROKER_END_OF_SCRIPT
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-201: BROKER_UNEXPECTED_END_OF_SCRIPT
Possible Cause:
If/EndIf or Repeat/EndRepeat blocks do not match. SecureLogin reached the end of the application definition without finding an expected EndIf or EndRepeat command.
Action:
Check the application definition. Make sure that the If/EndIg and Repeat/EndRepeat blocks match.
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-207: BROKER_END_SCRIPT_NOW
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-210: BROKER_CORPORATE_MOD_ABORTED
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-211: BROKER_ENTRY_ALREADY_ON_LIST
Possible Cause:
You tried to add an application definition or variable, but an application definition or variable with that name already exists.
Action:
Do one of the following
-213: BROKER_NDS_OP_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
-214: BROKER_UNABLE_TO_GET_CURRENT_OU
Possible Cause:
Data has become corrupted or the software is not working as intended.
Action:
Contact NetIQ Support.
Possible Cause:
In application definition language, each command expects a certain number of arguments. You have used either too few or too many arguments for a given command.
Action:
Make sure you are passing the correct number of arguments to the command.
-219: BROKER_NOT_A_NUMBER
Possible Cause:
The application definition language was expecting a decimal number, but characters other the 0-9 appeared.
Action:
Remove incorrect characters.
-220: BROKER_HLLAPI_FUNCTION_NOT_FOUND
Possible Cause:
In the Terminal Launcher configuration, you specified a HLLAPI.DLL and the name of the function in the DLL. The name of the function cannot be found in the DLL.
Action:
Check you have specified the correct terminal emulator type. Make sure that you entered the HLLAPI function correctly.
-221: BROKER_HLLAPI_OBJECT_UNINITIALISED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-222: BROKER_HLLAPI_DLL_LOAD_FAILED
Possible Cause:
Terminal Launcher was unable to load the HLLAPI.DLL that you specified. The HLLAPI.DLL for that emulator is looking for other DLL files that do not exist or are not installed for that emulator.
Action:
Make sure that the path and file that you are entered for the DLL are correct.
Check the vendor’s documentation for information about that emulator.
-223: BROKER_HLLAPI_OBJECT_ALREADY_INITIALISED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-224: BROKER_ERROR_DURING_WINHLLAPICLEANUP
Possible Cause:
Terminal Launcher has called the WinHLLAPI cleanup function for a WinHLLAPI emulator.
Action:
Check the vendor’s documentation for information about that emulator.
-225: BROKER_CANNOT_FIND_WINHLLAPISTARTUP_FUNCTION_IN_DLL
Possible Cause:
In the Terminal Launcher configuration, you incorrectly specified that the emulator is a WinHLLAPI emulator.
Action:
Make sure that you have specified the correct emulator type.
-226: BROKER_ERROR_DURING_WINHLLAPISTARTUP
Possible Causes:
The reason can be the following:
Action:
Check the vendor’s documentation for information about that emulator.
-227: BROKER_CANNOT_FINDWINHLLAPICLEANUP_FUNCTION_IN_DLL
Possible Cause:
In the Terminal Launcher configuration, you incorrectly specified that the emulator is a WinHLLAPI emulator.
Action:
Make sure you have specified the correct emulator type.
See the NetIQ Web site for information about configuring specific terminal emulators.
-228: BROKER_BUTTON_NOT_FOUND
Possible Cause:
For a Windows single sign-on application, no button exists for the control ID you specified. For example, if you specified Click #3, no button exists for control ID #3.
Action:
Specify the correct emulator type.
-230: BROKER_SETPLAT_FAILED
Possible Cause:
The regular expression that you supplied in the SetPlat command is invalid.
Action:
Check the syntax of the regular expression that you provided.
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-232: BROKER_UNABLE_TO_START_PROGRAM
Possible Cause:
The Run command was unable to find and start the requested program.
Action:
Make sure that the executable program exists and that the path is correct.
-234: BROKER_FREE_PLATFORM_SCRIPT_NULL_PTR
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-235: BROKER_VBA_LOGIN_INTERFACE_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-236: BROKER_CHANGEPASSWORD_INVALID_VARIABLE_SYNTAX
Possible Cause:
One of the parameters that you pass to the ChangePassword command must be a variable. The parameter that you provided is not a variable.
Action:
Specify a variable.
-237: BROKER_MAD_COMMAND_SET_INVALID_VARIABLE_SYNTAX
Possible Cause:
The first parameter that you pass to the Set command must be a variable. The parameter that you provided is not a variable.
Action:
Specify a variable.
-239: BROKER_POLICY_SCRIPT_ARG_NUM
Possible Cause:
One of the commands in a password policy script has too few or too many arguments.
Action:
Include the correct number of arguments.
-240: BROKER_VALID_CHARS_OUTNUMBERED
Possible Cause:
A password is unable to satisfy a password policy. This is because the maximum number of allowable characters is less than the minimum number of allowable characters.
Action:
Set the maximum number of a particular class of characters to a greater number than the minimum number of specified allowable characters.
-241: BROKER_PASSWORD_LOGIC_ERROR
Possible Cause:
You have incorrectly set up a password policy. No password can satisfy all the settings.
Action:
Work through each restriction in the password policy, and make sure that one restriction does not contradict another restriction in the policy.
-242: BROKER_EXECEPTION_CHARACHER_FOUND
Possible Cause:
You entered a password that contains a character that is not allowed.
Action:
Use allowable characters in your password.
-243: BROKER_PASSWORD_TOO_SHORT
Possible Cause:
You entered a password that does not have enough characters.
Action:
Provide enough characters in your password.
-244: BROKER_PASSWORD_TOO_LONG
Possible Cause:
You entered a password that has too many characters.
Action:
Enter the correct number of characters.
-245: BROKER_INSUFFICIENT_UPPERCASE_CHARS
Possible Cause:
You entered a password that has too few uppercase characters.
Action:
Use the specified number of uppercase characters in your password.
-246: BROKER_TOO_MANY_UPPERCASE_CHARS
Possible Cause:
You entered a password that has too many uppercase characters.
Action:
Use the specified number of uppercase characters in your password.
-247: BROKER_INSUFFICIENT_LOWERCASE_CHARS
Possible Cause:
You entered a password that has too few lowercase characters.
Action:
Use the specified number of lowercase characters in your password.
-248: BROKER_TOO_MANY_LOWERCASE_CHARS
Possible Cause:
You entered a password that has too many lowercase characters.
Action:
Use the specified number of lowercase characters in your password.
-249: BROKER_INSUFFICIENT_PUNCTUATION_CHARS
Possible Cause:
You entered a password that has too few punctuation characters.
Action:
Use the specified number of punctuation characters in your password.
-250: BROKER_TOO_MANY_PUNCTUATION_CHARS
Possible Cause:
You entered a password that has too many punctuation characters.
Action:
Use the specified number of punctuation characters in your password.
-251: BROKER_INSUFFICIENT_NUMERALS
Possible Cause:
You entered a password that has too few numerals.
Action:
Use the specified number of numerals in your password.
-252: BROKER_TOO_MANY_NUMERALS
Possible Cause:
You entered a password that has too many numerals.
Action:
Use the specified number of numerals in your password.
-253: BROKER_NT_FILE_TRAITS_OP_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-256: BROKER_UNABLE_TO_GET_NT_CHACE_DIR
Possible Cause:
You are using Windows NT 4 Domains mode, but you have not defined or mapped a Home drive.
Action:
Log in as the user to determine whether the Home drive and Home path variables are set. If the variables are not set, use the Windows NT domain administrative tools to set them.
NOTE:Version 3.6 and above do not support Windows NT.
-257: BROKER_UNABLE_TO_CREATE_NT_CACHE_DIR
Possible Cause:
The user object did not have rights to create a directory on the user’s local drive.
Action:
Grant the user object rights to the directory.
-259: BROKER_MUST_BEGIN_WITH_UPPERCASE
Possible Cause:
You entered a password that did not begin with an uppercase character.
Action:
Enter an uppercase character at the beginning of the password.
-260: BROKER_NO_DATA_STORES_LOADED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-261: BROKER_ENTRY_SRC_OBJECT_MISMATCH
Possible Cause:
You are using a platform other than NDS or eDirectory and have moved an object. The directory object that you are reading entries from is not the directory object that the entries were saved to.
Action:
Manually copy and paste the scripts between the objects.
-262: BROKER_CACHE_FILE_INCORRECT_VERSION
Possible Cause:
The cache file that you are trying to load was created by a later version of SecureLogin.
Action:
Use the version of SecureLogin that created the cache file.
Install the latest version of SecureLogin.
-263: BROKER_DDE_LOGIN_INTERFACE_NOT_IMPLEMENTED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-264: BROKER_DDE_CONNECT_FAILED
Possible Cause:
Terminal Launcher could not connect to a specified DDE emulator.
Action:
Make sure that the emulator launched correctly and the emulator’s DDE support is turned on.
-265: BROKER_DDE_DISCONNECT_FAILED
Possible Cause:
Failed attempt to disconnect from a DDE-supporting terminal emulator.
Action:
See the vendor’s documentation.
-266: BROKER_NT_FILE__SAVE_FAILED
Possible Cause:
The user object was unable to save to the equivalent of a cache file in the Home directory using Windows NT 4 Domains.
Action:
Grant the user object rights so that the user can write files to the Home directory.
NOTE:Version 3.6 and above do not support Windows NT.
-269: BROKER_NOT_A_PASSWORD_POLICY_COMMMAND
Possible Cause:
An invalid command was used in a password policy.
Action:
Make sure that the command is spelled correctly.
-271: BROKER_PASSWORD_UNACCEPTABLE
Possible Cause:
The password did not meet the requirements as specified in password policies.
Action:
Enter the password correctly.
-273: BROKER_MSTELNET_OPERATION_NOT_SUPPORTED
Possible Cause:
The generic emulator cannot support a particular operation, for example, SetCursor.
Action:
Do not use the command for generic emulators.
-279: BROKER_EMULATOR_LAUNCH_FAILED
Possible Cause:
In Terminal Launcher, you can configure the path to the executable that will run. However, the specified executable is unable to run.
Action:
Make sure the path to the emulator is correct.
-280: BROKER_UNABLE_TO_CREATE_EMULATOR
Possible Cause:
You have specified an invalid terminal type in TLAUNCH.INI (or the Terminal Launcher configuration).
Action:
Specify the correct terminal type.
-281: BROKER_INVALID_CHARACTER_FOUND_IN_PASTE_ID_LIST
Possible Cause:
A comma does not separate decimal numbers for copy IDs.
Action:
For generic emulators, you must specify a set of copy control IDs. Use a comma to separate decimal numbers.
-282: BROKER_INVALID_CHARACTER_FOUND_IN_COPY_ID_LIST
Possible Cause:
A comma does not separate decimal numbers for copy IDs.
Action:
For generic emulators, you must specify a set of copy control IDs. Use a comma to separate decimal numbers.
-283: BROKER_UNABLE_TO_READ_TLAUCH_INI
Possible Cause:
SecureLogin is unable to read the TLAUNCH.INI file because the file has been deleted.
Action:
Do one of the following:
-284: BROKER_NO_TERMINAL_TYPE_DEFINED
Possible Cause:
The TLAUNCH.INI file contains an error. The terminal type for the emulator is not defined.
Action:
Use Terminal Launcher to specify a terminal type for the emulator.
-285: BROKER_EMULATOR_INFO_NOT_FOUND
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-286: BROKER_RELOAD_NOT_ENABLED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-287: BROKER_TERMINAL-CONNECT-TRY-AGAIN
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-289: BROKER_WRONG_OBJECT_TYPE
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-290: BROKER_FILE_LOAD_FAILED
Possible Cause:
You do not have enough rights to convert an earlier TLAUNCH.INI file to a later format.
Action:
Do one of the following:
NOTE:Ask the administrator to assign you necessary rights.
-292: BROKER_DLL_NOT_INITIALISED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-294: BROKER_SETPLAT_VARIABLE_MUST_BE_RUN_TIME
Possible Cause:
The first argument to a SetPlat argument can be a variable. The variable used is not a runtime variable.
Action:
Make the first argument a runtime variable.
-295: BROKER_ERROR_CONDITIONAL_COMMAND_NOT_HANDLED
Possible Cause:
SecureLogin does not handle text in the second part of an If command.
Action:
Make sure that the command is the one listed and documented correctly.
-297: BROKER_PARSER_ELSE_STATEMENT_FOUND
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-298: BROKER_RAW_MODE_MUST_BE_SECOND_ARG
Possible Cause:
For the Click command, you have placed the –X and –Y arguments before –Raw.
Action:
If you use –Raw, place it as the first argument.
-299: BROKER_DISALLOWED_REPEATS_EXIT
Possible Cause:
You have tried to use repeated characters in a Password Policy that does not allow them.
Action:
Avoid repeated characters.
-300: BROKER_DISALLOWED_SEQUENTIALS_EXIST
Possible Cause:
You have tried to use sequential characters in a password, but a Password policy does not allow them.
Action:
Avoid sequential characters.
-301: BROKER_DISALLOWED_KEYBOARD_ADJACENTS_EXIST
Possible Cause:
You entered a password that has an unacceptable sequence of characters.
Action:
Enter an approved sequence of characters.
-303: BROKER_CHARACTER-NOT-IN-REQUIRED-POSITION
Possible Cause:
You entered a password that does not have a character in a required position.
Action:
Enter the password correctly.
-308: BROKER_BAD_POSITION_ARGUMENT
Possible Cause:
While calling a SetCursor command, you tried to move the cursor to an invalid position. For example, out of the terminal session’s boundary.
Action:
Specify a valid position.
-309: BROKER_ERROR_CONVERTING_POSITION
Possible Cause:
The conversion from –X and –Y coordinates for the SetCursor command has failed.
Action:
Specify the –X and –Y coordinates for one offset from the top left-hand corner of the screen.
-310: BROKER_NOT_A_WRITABLE_VARIABLE
Possible Cause:
You tried to save a new value to a type of variable that cannot be written to.
Action:
Use a runtime or normal variable.
-311: BROKER_RUN_SCRIPT_AGAIN
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-312: BROKER_NO_OU_PERIOD_FOUND
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-314: BROKER_COPY_BACKUP_FAILED
Possible Cause:
When SecureLogin begins to update the cache file, SecureLogin first copies the current cache file to a file with the same name, but uses the extension .GOOD.
SecureLogin was unable to copy the file. The .GOOD file is already open because another process is using it.
Possible Cause:
You do not have rights to create files in the directory.
Action:
Ask the administrator to assign you rights to the directory.
-315: BROKER_GOTO_LABEL_ALREADY_DEFINED
Possible Cause:
You have used a GoTo command, but the label that you directed it to has already been used.
Action:
Remove the second label command.
-316: BROKER_GOTO_LABEL_NOT_DEFINED
Possible Cause:
You have used a GoTo command, but the label that you directed it to has not been defined.
Action:
Define the label.
-317: BROKER_INCORRECT_DATABASE_VERSION
Possible Cause:
The version of SecureLogin that you are using does not handle the version of SecureLogin that is stored in the directory.
Action:
Upgrade to the latest version of SecureLogin.
-318: BROKER_DIRECTORY_CRC_DOES_NOT_MATCH
Possible Cause:
Whenever SecureLogin stores an entry in Microsoft Active Directory, SecureLogin employs a redundancy check. If the redundancy check does not match when SecureLogin reloads the entry, then the data in Microsoft Active Directory has been corrupted.
Action:
Troubleshoot Microsoft Active Directory or Microsoft ADAM.
-319: BROKER_DISALLOWED_DUPLICATE_EXIST
Possible Cause:
You entered a password that has unacceptable duplicate characters.
Action:
Enter the password correctly.
-320: BROKER_GOTO_LIST_ASSERTION
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-321: BROKER_SUBROUTINE_NOT_DEFINED
Possible Cause:
A Call command is calling a subroutine that has not yet been defined.
Action:
Define the subroutine.
-322: BROKER_UNABLE_TO_FIND_PASSWORD_FIELD
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-323: BROKER_PASSWORD_FIELD_STYLE_NOT_SET
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-324: BROKER_WEB_ACTION_NOT_SUPPORTED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-325: BROKER_ENTRY_MUST_HAVE_NON_NULL_KEY
Possible Cause:
You tried to add an application definition or variable that is a blank string.
Action:
Provide a name for the application definition or variable.
-326: BROKER_VARIABLE_REQUIRED
Possible Cause:
Some commands, for example, ReadText, require a variable to copy the data that they are returning to. The argument must be a variable.
Action:
Change the argument to a variable.
-327: BROKER_OBJECT_NOT_FOUND
Possible Cause:
Microsoft Active Directory/ADAM library was unable to allocate memory.
Action:
Troubleshoot Microsoft Active Directory or Microsoft ADAM.
-328: BROKER_ADS_MEMORY_FAILURE
Possible Cause:
The Microsoft Active Directory/ADAM library was unable to allocate memory.
Action:
Close one or more applications and try again.
-329: BROKER_ADS_ERROR_GETTING_ATTRIBUTE
Possible Cause:
Although data exists in Microsoft Active Directory/ADAM, SecureLogin is unable to read the data.
Action:
Troubleshoot Microsoft Active Directory or Microsoft ADAM.
-330: BROKER_ADS_INSUFFICIENT_RIGHTS_TO_DELETE
Possible Cause:
When you removed an application definition, SecureLogin tried to delete part of an attribute from Microsoft Active Directory/ADAM. However, you are unable to delete the attribute because you do not have sufficient rights.
Action:
The administrator must assign sufficient directory rights for each user object so that the user can modify SecureLogin attributes.
-331: BROKER_ADS_ERROR_DELETING_VALUE
Possible Cause:
Microsoft Active Directory/ADAM was unable to delete a value.
Action:
Troubleshoot Microsoft Active Directory or Microsoft ADAM.
-332: BROKER_NO_PASSWORD_FIELD_VARIABLE_IN_SCRIPT
Possible Cause:
A Web application definition must have at least one Type command that has “password” as the second argument. The following lines illustrate a typical application definition:
-
Type $Username
-
Type $Password Password
However, the application definition has no Type command followed by the Password attribute.
Action:
Add a Type command followed by the Password attribute.
-333: BROKER_REGEX_GET_REPLACE_STRING_FAILED
Possible Cause:
On the RegSplit command, the string that you are running through the regular expression did not match.
Action:
Change the regular expression.
-335: BROKER_REGEX_COMPILE_FAILED
Possible Cause:
The syntax of the regular expression was incorrect.
Action:
Revise the syntax of the regular expression.
-336: BROKER_DIRECTORY_AUTH_DATA_CORRUPT
Possible Cause:
The SecureLogin:SSOAuth data attribute has become corrupt.
Action:
Contact NetIQ Support.
-337: BROKER_DES_KEY_NOT_SET
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-338: BROKER_DES_INVALID_BLOCK_LEN
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-339: BROKER_INVALID_ENCRYPTION_TYPE
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-340: BROKER_UNKNOWN_DATABASE_VERSION
Possible Cause:
You are using an earlier version of SecureLogin.
Action:
Upgrade to the latest version of SecureLogin.
-341: BROKER_USER_KEY_NOT_SET
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-343: BROKER_PRIMARY_KEY-DECRYPT_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-344: BROKER_SECONDARY_KEY_DECRYPT_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-345: BROKER_MERGE_WRONG_ENTRY_TYPE
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-348: BROKER_PASSWORD_RESET_DETECTED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-349: BROKER_UNABLE_TO_FIND_SESSION_FILE
Possible Cause:
Terminal Launcher could not find a session file for an emulator.
Action:
Configure Terminal Launcher with the correct path to the file for the emulator session.
-352: BROKER_AUTH_DATA_INCORRECT
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-353: BROKER_RECURSIVE_SCRIPT_INCLUDE_DETECTED
Possible Cause:
While using the Include command, you included an application definition twice.
Action:
Only include an application definition once.
-354: BROKER_NETWORK_PASSWORD_INCORRECT
Possible Cause:
You have turned on the option to prompt the user for the network password before the user can access options on the taskbar, and the user entered an incorrect password.
Action:
Enter the correct password.
-355: BROKER_USER_ABORTED_LOAD_PROCESS
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-356: BROKER_INVALID_CHARACTER_FOUND_IN_STARTUP_ID_LIST
Possible Cause:
For generic emulators, you specify the startup control ID.
A comma must separate a list of numbers. You have used a character other than a comma.
Action:
Remove unacceptable characters.
-357: BROKER_ERRO_REG_CACHE_NO_DETAILS
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-358: BROKER_ERROR_REG_CHACE_SAVE_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-359: BROKER_ERROR_REG_CACHE_SPLIT
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-360: BROKER_PASSWORD_VARIABLE_NOT_ALLOWED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-361: BROKER_NMAS_DLL_NOT_AVAILABLE
Possible Cause:
SecureLogin cannot pad the DLL file for NMAS for use with the AAVerify command.
Action:
To use features for AAVerify, install NMAS.
-362: BROKER_NMAS_LEGACY_RELOGIN_NOT_FOUND
Possible Cause:
SecureLogin could not find the NMAS relogin function in the DLL for NMAS.
Action:
Install the latest version of NMAS.
-363: BROKER_STANDARD_VARIABLE_REQURED
Possible Cause:
A ? variable has been used and this command requires a $ variable.
Action:
Provide a $ variable.
-364: BROKER_LDAP_LOGIN_CANCELLED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-365: BROKER_LDAP_INIT_FAILED
Possible Cause:
The initialization of the LDAP SSL layer failed.
Action:
Contact NetIQ Support.
-367: BROKER_REG_AUTH_CACHE_MISMATCH
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-368: BROKER_LDAP_TOKEN_DELETED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-369: BROKER_CRED_LIST_NOT_NULL
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-370: BROKER_CRED_LIST_NULL
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-371: BROKER_NO_MORE_CRED_SETS
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-372: BROKER_ACCESS_IS_DENIED
Possible Cause:
For LDAP, you do not have rights to the area of the directory that you are trying to access.
Action:
Grant user objects the correct rights.
-373: BROKER_HLLAPI-CONNECT_FAILED
Possible Cause:
Terminal Launcher was unable to connect to the emulator.
Action:
Make sure that the emulator has HLLAPI enabled.
-374: BROKER_DUPLICATE_ENTRIES_EXIST
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-375: BROKER_NOT_RUNNING_NT
Possible Cause:
Although you are not running Windows NT, you tried to use a feature that is available only through Windows NT.
Action:
Do not use that feature unless you are running Windows NT.
-376: BROKER_WINNT_CACHE_AUTH_REG_FAILED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-377: BROKER_WINNT_CACHE_AUTH_REG_WRONG_USER
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-378: BROKER_INVALID_PIPE_STRING_FOUND
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-379: BROKER_HEX_LENGTH_INCORRECT
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-380: BROKER_HLLAPI_NOT_CONNECTED_TO_PS
Possible Cause:
Terminal Launcher tried to use a HLLAPI function. However, the HLLAPI DLL is not connected to the emulator presentation space.
Action:
Make sure that Terminal Launcher is set up correctly with the emulator.
-381: BROKER_HLLAPI_SPECIFYING_PARAMETERS_ERROR
Possible Cause:
Incorrect parameters were given to a command that uses a HLLAPI function.
Action:
Contact NetIQ Support.
-382: BROKER_HLLAPI_INVALID_PS_POSITION
Possible Cause:
An attempt was made to move the cursor or read text from an invalid (out of bounds) position on the emulator presentation space.
Action:
Correct the positioning parameter in the application definition.
-383: BROKER_HLLAPI_SYSTEM_ERROR
Possible Cause:
Terminal Launcher is not configured correctly for the emulator.
Action:
Make sure that Terminal Launcher is set up correctly with the emulator and that the emulator correctly supports HLLAPI.
-384: BROKER_HLLAPI_PS_BUSY_ERROR
Possible Cause:
A HLLAPI function is being called while the emulator presentation space is unavailable.
Action:
Make sure that the emulator is not being used by another HLLAPI application.
-385: BROKER_HLLAPI_INPUT_REJECTED
Possible Cause:
The emulator rejected an attempt to input data into the emulator presentation space.
Action:
Make sure that the emulator presentation space is not locked.
-386: BROKER_HLLAPI_ERROR_QUERYING_SESSIONS
Possible Cause:
SecureLogin is unable to query available HLLAPI sessions.
Action:
Make sure that the Terminal Launcher is set up correctly with the emulator.
-387: BROKER_LAST_NDS_USER_NOT_FOUND
Possible Cause:
The last NDS or eDirectory user object, as stored in the registry, could not be read for use in an NMAS login.
Action:
Make sure the last NDS or eDirectory user object is stored correctly in the registry.
-388: BROKER_LAST_NDS_USER_UNWORTHY
Possible Cause:
The last NDS or eDirectory user object, as stored in the registry, was not in the correct format. An NMAS login was unable to use the format.
Action:
Make sure the last NDS or eDirectory user object is stored correctly in the registry.
-389: BROKER_NMAS_DISCONNECTED_LOGIN_NOT_FOUND
Possible Cause:
NMAS disconnected login function not found in NMAS.DLL.
Action:
Make sure that the correct NMAS.DLL is installed.
-390: BROKER_LDAP_SSL_INIT_FAILED
Possible Cause:
SecureLogin could not initialize the LDAP SSL libraries.
Action:
Contact NetIQ Support.
-391: BROKER_LDAP_SSL_ADD_CERT_FAILED
Possible Cause:
SecureLogin could not open the certificate you supplied for LDAP over SSL. Either the file does not exist or it is in the incorrect format. If the certificate file specified ends in .DER, then SecureLogin uses Distinguished Encoding Rule (DER) format. Otherwise SecureLogin uses B64 format.
Action:
Make sure that the path to the certificate is correct and that it is in DER format.
-392: BROKER_BUILTIN_VARIABLE_NOT_FOUND
Possible Cause:
A built-in variable such as ?sysversion was not found.
Action:
Check that the format of the variable name is ?SysVersion(system).
-393: BROKER_SCRIPT_NOT_PURELY_INDEXED
Possible Cause:
While working with Web modules, you mix indexed and nonindexed commands.
For example, you entered the following:
Type $Username #1
Type $Password
Action:
Make sure that all commands use indexes, or remove all indexes.
-394: BROKER_LDAP_PASSWORD_INCORRECT
Possible Cause:
The password supplied to log in to LDAP was incorrect.
Action:
Check the password.
-395: BROKER_LDAP_USER_NON_EXISTANT
Possible Cause:
The user name that you used to log on to LDAP does not exist.
Action:
Make sure that the user name exists in the directory and that the LDAP context is correct.
-396: BROKER_LDAP_SERVER_DETAILS_INCORRECT
Possible Cause:
One or more of the LDAP server parameters supplied was incorrect.
Action:
Check the LDAP server address and port number.
Make sure that the LDAP server you are connected to is running.
-398: BROKER_WIZ_CP_WRONG_SCRIPT_TYPE
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-399: BROKER_DIVIDE_BY_ZERO_IS_BAD
Possible Cause:
Using the Divide command, you attempted division by zero.
Action:
Do not attempt division by zero.
-400: BROKER_WRONG_SECTION_NAME
Possible Cause:
You manually edited a wizard-generated application definition.
Action:
When editing an application definition, do not edit the specially generated comments. Only edit the actual commands. If this error occurs, you will no longer be able to use the wizard for that application definition.
-401: BROKER_INVALID_GLOBAL_WIZARD_CONFIG
Possible Cause:
You manually edited a wizard-generated application definition.
Action:
Do not edit the specially generated comments in an application definition. Only edit the actual commands. If this error occurs, you will no longer be able to use the wizard for that application definition.
-402: BROKER_LDAP_ATTRIBUTE_DOES_NOT_EXIST_IN_SCHEMA
Possible Cause:
Either of the following:
-
You are running LDAP on eDirectory, but have not correctly mapped the LDAP attributes.
-
You are running LDAP on a platform other than eDirectory. However, the schema is not extended for that platform.
Action:
Check your LDAP attribute mappings. Extend the LDAP schema.
-403: BROKER_AAVERIFY_DLL_NOT_AVAILABLE
Possible Cause:
SecureLogin was unable to load SL_AAVERIFY.DLL.
Action:
Make sure that you have the correct DLLs installed for AAVERIFY.
-404: BROKER_AAVERIFY_FUNCTION_NOT_FOUND
Possible Cause:
You are using the incorrect version of SL_AAVERIFY.DLL.
Action:
Check the version of SL_AAVERIFY.DLL.
-405: BROKER_AAVERIFY_CONSISTENCY_FAILURE
Possible Cause:
You are using the incorrect version of SL_AAVERIFY.DLL.
Action:
Check the version of SL_AAVERIFY.DLL.
-406: BROKER_AAVERIFY_ERROR
Possible Cause:
You are using the incorrect version of SL_AAVERIFY.DLL.
Action:
Check the version of SL_AAVERIFY.DLL.
-408: BROKER_DES_KEY_DATA_CORRUPT
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-409: BROKER_OPERATION_ABORTED_BY_USER
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-410: BROKER_NOT_A_STRING_ATTRIBUTE
Possible Cause:
You are using % variables, but the attribute you are reading is not a plain string attribute (SYN_CE_STRING or SYN_CI_STRING on eDirectory).
Action:
Check the schema definition of the attribute to confirm that the syntax is SYN_CE_STRING or SYN_CI_STRING.
-411: BROKER_LDAP_INVALID_DN_SYNTAX
Possible Cause:
The format of your LDAP user name was invalid.
Action:
Check the format of the user name that you entered.
-412: BROKER_INVALID_OPTION_COMBINATION
Possible Cause:
An invalid combination of options was passed to an application definition command.
For example, you passed –Right and –Raw to the Click command.
Action:
See the appropriate application definition command.
-413: BROKER_AAVERIFY_SLOGIN_DOES_NOT_EXIST
Possible Cause:
SL_AAVERIFY.DLL generates these errors. There is a problem connecting to the SecureLogin server.
Action:
Troubleshoot service location problems by reviewing documentation on SecureLogin Advanced Authentication.
-414: BROKER_AAVERIFY_ERR_SLOGIN_NOT_RUNNING
Possible Cause:
SL_AAVERIFY.DLL generates these errors. There is a problem connecting to the SecureLogin server.
Action:
Troubleshoot service location problems by reviewing documentation on SecureLogin Advanced Authentication.
-415: BROKER_AAVERIFY_ERR_LOAD_LIB_SLPAM
Possible Cause:
SL_AAVERIFY.DLL generates these errors. There is a problem connecting to the SecureLogin server.
Action:
Troubleshoot service location problems by reviewing documentation on SecureLogin Advanced Authentication.
-416: BROKER_WI_GETEXENAME_ERR
Possible Cause:
The wizard was unable to retrieve the executable name for the window you selected.
Action:
Do not use the wizard for this application.
-417: BROKER_ADS_PUT_OCTET_INSUFFICIENT_RIGHTS
Possible Cause:
You do not have sufficient rights to Microsoft Active Directory/ADAM to perform the current operation.
Action:
Ask the directory administrator to assign you additional Microsoft Active Directory/ADAM system rights.
-418: BROKER_ADS_CLR_OCTET_INSUFFICIENT_RIGHTS
Possible Cause:
You do not have sufficient rights to Microsoft Active Directory/ADAM to perform the current operation.
Action:
Ask the directory administrator to assign you additional Microsoft Active Directory/ADAM system rights.
-420: BROKER-_SLAASSO_ERR_CRYPTO_KEY_NOT_SET
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-421: BROKER_SLASSO_ERR_UNKNOWN_DATA
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-422: BROKER_SLASSO_OUT_OF_MEMORY
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-423: BROKER_ERROR_INITIALISING_DATA_STORES
Possible Cause:
SecureLogin was unable to initialize either the primary or secondary datastore.
Action:
Contact NetIQ Support.
-424: BROKER_UNABLE_TO_LOAD_SLOTP_DLL
Possible Cause:
SLOTP.DLL could not be loaded. This DLL is required for synchronizing one-time password to LDAP directories.
Action:
Review documentation for one-time passwords.
-425: BROKER_LDAP_NO_SUCH_ATTRIBUTE
Possible Cause:
You have used a % variable on LDAP. However, the requested attribute does not exist.
Action:
Check the spelling of the attribute name against the LDAP schema.
-426: BROKER_SYS_VARIABLE_NOT_AVAILABLE
Possible Cause:
A system variable, for example, ?syspassword, was requested but was not available. SLINA.DLL, SLNMAS.DLL or SLCREDMAN.DLL must be correctly installed for these variables to function.
Action:
Make sure that either SLINA.DLL, SLNMAS.DLL or SLCREDMAN.DLL is installed.
-427: BROKER_USERNAME_UNSUITABLE_FOR_READING_SLINA_CREDS
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-428: BROKER_NO_EXCEPTION_HANDLER_DEFINED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-429: BROKER_EXCEPTOPN_RAISED
Possible Cause:
Data has become corrupted, or the software is not working as intended.
Action:
Contact NetIQ Support.
-430: BROKER_MUST_BE_CALL_OR_GOTO
Possible Cause:
When using the OnException command, the second parameter must be Call or GoTo.
Action:
Make sure that Call is used with the OnException command.
-442: BROKER_CHAR_UCASE_NOT_IN_REQUIRED_POSITION
Possible Cause:
There is not an uppercase character in a position where one is required.
Action:
Check the password for compliance with the Password Policy.
-443: BROKER_CHAR_LCASE_NOT_IN_REQURED_POSITION
Possible Cause:
Raised by the Password Policy code if there is not a lower case character in a position where one is required.
Action:
Check the password for compliance with Password Policy.
-444: BROKER_PUNCTUATION_NOT_IN_REQUIRED_POSITION
Possible Cause:
There is not a punctuation character in a position where one is required.
Action:
Check password for compliance with Password Policy.
-477: BROKER_UNABLE_TO_GET_REGISTRY_DATA
Possible Cause:
The SecureLogin application definition GetReg command could not read the required registry information.
Action:
Contact NetIQ Support.
-478: BROKER_ERROR_PARSING_PARAMETER
Possible Cause:
The registry entry name passed to the SecureLogin application definition GetReg command was incorrect.
Action:
Make sure that the name begins {HKCR, HKCC, HKCU, HKLM, or HKU} and corresponds to one of the Windows registry hives. Also, it must contain the path to the desired registry entry within the node.
-481: BROKER_AUTH_QUERY_ON_WRONG_OBJECT_TYPE
Possible Cause:
SecureLogin has attempted to load data from a directory object of an incorrect type.
Action:
Contact NetIQ Support.
-482: BROKER_VERSION_NO_ROLL_BACK
Possible Cause:
The SecureLogin datastore version cannot be returned to an older datastore version after it has been set to version 6.0.
Action:
Contact NetIQ Support.
-483: BROKER_SECURE_CONNECTION_REQUIRED
Possible Cause:
SecureLogin cannot load sensitive data from the server over insecure connections.
Action:
Contact NetIQ Support.
-500: BROKER_ERROR-ACCOUNT-EXPIRED
Possible Cause:
SecureLogin was unable to authenticate your Active Directory account because your user account has expired.
Action:
Contact your system administrator.
-501: BROKER_ERROR_ACCOUNT_DISABLED
Possible Cause:
SecureLogin was unable to authenticate your Active Directory account because your user account has been disabled.
Action:
Contact your system administrator.
-502: BROKER_ERROR_ACCOUNT_LOCKED
Possible Cause:
SecureLogin was unable to authenticate your Active Directory account because your user account has been locked.
Action:
Contact your system administrator.
-503: BROKER_ERROR_PASSWORD_EXPIRED
Possible Cause:
SecureLogin was unable to authenticate your Active Directory account because your password has expired.
Action:
Change your Active Directory password or contact your system administrator.
-600: BROKER_NONFIR_INVALID_TARGET
Possible Cause:
A non-directory datastore is unable to load the local rule that contains the required data for an object. This could be because of the following:
Action:
Contact your system administrator.
-2147016656: Error opening specified object
Possible Cause:
Microsoft Active Directory code error message (value 0x80072031): There is no such object on the server.
Action:
You have entered an incorrect object or container definition when assigning user rights. Reenter the correct object or container definition.