These are the error codes returned by SecureLogin.
-102 BROKER NO SUCH ENTRY
Source:
SecureLogin
Possible Cause:
You tried to load a script or variable that doesn't exist. For example, you set up Terminal Launcher to run from a shortcut or to run a particular script, but the script doesn't exist.
Action:
Check that the name of the script is actually defined is SecureLogin. Verify that the name is the same as specified in the script editor.
-103 BROKER INVALID CLASS CREATED
Source:
SecureLogin
Possible Cause:
You are running an earlier version. SecureLogin is trying to create a new version of the script data format that was stored in eDirectory or NDS.
Action:
Upgrade the older SecureLogin client to the new client. Install the latest SecureLogin software.
-104 BROKER CREATE CLASS FAILED
Source:
SecureLogin
Possible Cause:
The SecureLogin client has run out of memory.
Action:
Free up some memory. Try again later.
-107 BROKER ENTRY NOT FOUND
Source:
SecureLogin
Possible Cause:
You tried to load a script or variable that doesn't exist.
Action:
Check that the name of the script is actually defined is SecureLogin. Verify that the name is the same as specified in the script editor.
-109 BROKER SCRIPT BUFFER ALLOC FAILED
Source:
SecureLogin
Possible Cause:
The SecureLogin client has run out of memory.
Action:
Free up some memory. Try again later.
-112 BROKER NO SUCH VARIABLE
Source:
SecureLogin
Possible Cause:
You are trying to use an undefined variable. Because SecureLogin isn't prompting you for the variable, data has become unusable, or some other situation is preventing the software from working as expected.
Action:
Call Novell Technical Services.
-114 BROKER PRIMARY NOT AVAILABLE
Source:
SecureLogin
Possible Cause:
You are not logged in to the Directory. You are using the offline cache. Therefore, some Directory functions can't be performed. (For example, you can't change your passphrase.)
Action:
Log in to the Directory.
-116 BROKER HEADER DATA CORRUPT
Source:
SecureLogin
Possible Cause:
Data isn't available. You might have had 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.
Action:
Call Novell Technical Services.
-123 BROKER CACHE PASSWORD INCORRECT
Source:
SecureLogin
Possible Cause:
You have tried to log in 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. However, if you have installed the NMAS module, the passphrase can be the passphrase answer or your current eDirectory or NDS password.
Action:
Enter the correct passphrase answer or Directory password.
-129 BROKER ENTRY LIST NOT NULL
Source:
SecureLogin
Possible Cause:
The software is not working as intended.
Action:
Delete the local cache file and try again.
Action:
Call Novell Technical Services.
-131 BROKER SYM LIST NOT NULL
Source:
SecureLogin
Possible Cause:
Memory is not being handled as expected.
Action:
Call Novell Technical Services.
-138 BROKER SYMBOL DATA CORRUPT
Source:
SecureLogin
Possible Cause:
SecureLogin is unable to use the data in the local cache file or in the Directory.
Action:
Delete the local cache file and try again.
Action:
Call Novell Technical Services.
-140 BROKER SCRIPT DATA CORRUPT
Source:
SecureLogin
Possible Cause:
SecureLogin is unable to use data in scripts.
Action:
Delete the local cache file and try again.
Action:
Call Novell Technical Services.
-166 BROKER INVALID DES KEY
Source:
SecureLogin
Possible Cause:
Hex strings are invalid. The DESKEY variable requires hexadecimal (0-9, A-F) numbers.
Action:
Make sure that the DESKEY variable contains only hexadecimal numbers.
-167 BROKER INVALID DES OFFSET
Source:
SecureLogin
Possible Cause:
Hex strings are invalid. The DESOFFSET variable requires hexadecimal (0-9, A-F) numbers.
Action:
Make sure that the DESOFFSET variable contains only hexadecimal numbers.
-168 BROKER DESKEY NOT FOUND
Source:
SecureLogin
Possible Cause:
You tried to generate a one-time password for a platform. However, you haven't defined the DESKEY variable.
Action:
Create the DESKEY variable.
-169 BROKER DESOFFSET NOT FOUND
Source:
SecureLogin
Possible Cause:
You tried to generate a one-time password for a platform. However, you haven't defined the DESOFFSET variable.
Action:
Create the DESOFFSET variable.
-171 BROKER CACHE FILE OPEN FAIL
Source:
SecureLogin
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 has rights to the cache directory.
-174 BROKER CACHE SAVE FAILED
Source:
SecureLogin
Possible Cause:
SecureLogin tried to save data to the offline cache but is unable to.
Action:
Assign rights so that the specified user has rights to the cache directory.
-175 BROKER CACHE SECRETS INCORRECT
Source:
SecureLogin
Possible Cause:
The offline cache password is incorrect. The key that is being used to decrypt the cache file is not the key that the cache file was encrypted with.
Possible Cause:
After logging in as a user and creating a cache file, you went to another workstation, reset your passphrase, and logged in. You receive this error when you return to the original workstation.
Action:
Delete the cache file.
-176 BROKER PUBLIC KEY READ FAILED
Source:
SecureLogin
Possible Cause:
SecureLogin is unable to read the public key from eDirectory or NDS.
Action:
Troubleshoot eDirectory or NDS.
-179 BROKER RTVALUE DOES NOT EXIST
Source:
SecureLogin
Possible Cause:
You tried to read a runtime variable that has not been defined.
Action:
Check the script. Make sure that the variable has been set before it is read or used as a command.
-180 BROKER DS VARIABLE NOT READ
Source:
SecureLogin
Possible Cause:
You used one of the % variables to read a Directory attribute, but SecureLogin can't read the variable.
Action:
Make sure that you have spelled the attribute name correctly.
Action:
Troubleshoot eDirectory or NDS.
-181 BROKER WRONG PASS PHRASE
Source:
SecureLogin
Possible Cause:
You entered the wrong passphrase.
Possible Cause:
You tried to change your passphrase but typed it incorrectly.
Possible Cause:
You enabled a preference relating to SecureLogin's hand icon. You double-clicked the hand icon but typed the passphrase incorrectly.
Action:
Enter the passphrase correctly.
-190 BROKER NO AUTH DATA FOUND
Source:
SecureLogin
Possible Cause:
Although the Prot:SSO Entry attribute has data, the Prot:SSO Auth attribute was blank. Someone deleted the Prot:SSO Auth attribute.
Action:
Delete the Prot:SSO Entry attribute. SecureLogin creates these attributes the next time that you run SecureLogin.
-192 BROKER UNABLE TO INSTANTIATE
Source:
SecureLogin
Possible Cause:
A module (for example, WinSSO) has tried to connect to the Combroker but is unable to.
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.
-199 BROKER ERROR COMMAND NOT HANDLED
Source:
SecureLogin
Possible Cause:
A script parser encountered an unrecognizable command.
Action:
Make sure that you have spelled the command correctly.
Action:
Make sure that the If/EndIf blocks match.
-201 BROKER UNEXPECTED END OF SCRIPT
Source:
SecureLogin
Possible Cause:
If/EndIf or Repeat/EndRepeat blocks don't match. SecureLogin reached the end of the script without finding an expected EndIf or EndRepeat command.
Action:
Check the script. Make sure that If/EndIf and Repeat/EndRepeat blocks match.
-211 BROKER ENTRY ALREADY IN LIST
Source:
SecureLogin
Possible Cause:
You tried to add a script or variable, but a script or variable with that name already exists.
Action:
Use a different name for the script or variable, or use the script editor to rename the existing script or variable.
Source:
SecureLogin
Possible Cause:
In script language, each command expects a certain number of arguments. You have used either too few or too many arguments for a given command.
Action:
Check the documentation for that command. Make sure that you are passing to the command the correct number of arguments.
Source:
SecureLogin
Possible Cause:
The script language was expecting a decimal number, but characters other than 0-9 appeared.
Action:
Remove incorrect characters.
-220 BROKER HLLAPI FUNCTION NOT FOUND
Source:
SecureLogin
Possible Cause:
In the Terminal Launcher configuration, you specified a hllapi.dll and the name of the function in that DLL. The name of the function cannot be found in the DLL.
-222 BROKER HLLAPI DLL LOAD FAILED
Source:
SecureLogin
Possible Cause:
Terminal Launcher was unable to load the hllapi.dll that you specified.
Action:
Make sure that the path and file that you entered for the DLL are correct.
Possible Cause:
The hllapi.dll for that emulator is looking for other DLL files that don't exist or haven't been installed for that emulator.
Action:
Check the vendor's documentation for information about that emulator.
-224 BROKER ERROR DURING WINHLLAPICLEANUP
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
In the Terminal Launcher configuration, you incorrectly specified that the emulator is a WinHLLAPI emulator.
-226 BROKER ERROR DURING WINHLLAPISTARTUP
Source:
SecureLogin
Action:
Check the vendor's documentation for information about that emulator.
-227 BROKER CANNOT FIND WINHLLAPICLEANUP FUNCTION IN DLL
Source:
SecureLogin
Possible Cause:
In the Terminal Launcher configuration, you incorrectly specified that the emulator is a WinHLLAPI emulator.
-228 BROKER BUTTON NOT FOUND
Source:
SecureLogin
Possible Cause:
For a Windows single sign-on application, no button exists for the control ID that you specified. For example, if you specified Click #3, no button exists for control ID 3.
Action:
Specify the correct control ID number for the button.
-230 BROKER SETPLAT FAILED
Source:
SecureLogin
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.
Source:
SecureLogin
Possible Cause:
The software is not working as intended.
Action:
Call Novell Technical Services.
-232 BROKER UNABLE TO START PROGRAM
Source:
SecureLogin
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.
-236 BROKER CHANGEPASSWORD INVALID VARIABLE SYNTAX
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
A password is unable to satisfy a password policy 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
Source:
SecureLogin
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, making sure that one restriction doesn't contradict another restriction in the policy.
-242 BROKER EXCEPTION CHARACTER FOUND
Source:
SecureLogin
Possible Cause:
You entered a password that contains a character that isn't allowed.
Action:
Use allowable characters in your password.
-243 BROKER PASSWORD TOO SHORT
Source:
SecureLogin
Possible Cause:
You entered a password that doesn't have enough characters.
Action:
Provide enough characters in your password.
-244 BROKER PASSWORD TOO LONG
Source:
SecureLogin
Possible Cause:
You entered a password that has too many characters.
Action:
Type the correct number of characters.
-245 BROKER INSUFFICIENT UPPERCASE CHARS
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
The software is not working as intended.
Action:
Call Novell Technical Services.
-256 BROKER UNABLE TO GET NT CACHE DIR
Source:
SecureLogin
Possible Cause:
You are using NT 4 Domains mode, but you haven't defined or mapped a Homedrive.
Action:
Log in as the user to determine whether the Homedrive and Homepath variables are set. If the variables are not set, use the NT domain administrative tools to set them.
-257 BROKER UNABLE TO CREATE NT CACHE DIR
Source:
SecureLogin
Possible Cause:
The user didn't have rights to create a directory on the user's Homedrive.
Action:
Grant the user rights to the directory.
-259 BROKER MUST BEGIN WITH UPPERCASE
Source:
SecureLogin
Possible Cause:
You entered a password that didn't begin with an uppercase character.
Action:
Type an uppercase character at the beginning of the password.
-261 BROKER ENTRY SRC OBJECT MISMATCH
Source:
SecureLogin
Possible Cause:
You are using a platform other than eDirectory or NDS 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
Source:
SecureLogin
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.
Action:
Install the latest version of SecureLogin.
-264 BROKER DDE CONNECT FAILED
Source:
SecureLogin
Possible Cause:
Terminal Launcher couldn't 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
Source:
SecureLogin
Action:
Refer to the vendor's documentation.
-266 BROKER NT FILE STORAGE SAVE FAILED
Source:
SecureLogin
Possible Cause:
Using NT 4 Domains mode, the user was unable to save to the equivalent of a cache file in the Home directory.
Action:
Grant the user rights so that the user can write files to the Home directory.
-269 BROKER NOT A PASSWORD POLICY COMMAND
Source:
SecureLogin
Possible Cause:
An invalid command was used in a password policy.
Action:
Make sure that the command is spelled correctly.
-271 BROKER PASSWORD UNACCEPTABLE
Source:
SecureLogin
Possible Cause:
The password didn't meet requirements as specified in password policies.
Action:
Enter the password correctly.
-273 BROKER MSTELNET OPERATION NOT SUPPORTED
Source:
SecureLogin
Possible Cause:
The generic emulator can't support a particular operation (for example, SetCursor).
Action:
For generic emulators, don't use the command.
-279 BROKER EMULATOR LAUNCH FAILED
Source:
SecureLogin
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 that the path to the emulator is correct.
-280 BROKER UNABLE TO CREATE EMULATOR
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
A comma doesn't separate decimal numbers for input and output control IDs.
Action:
For generic emulators, you must specify a set of input and output control IDs. Use a comma to separate decimal numbers.
-282 BROKER INVALID CHARACTER FOUND IN COPY ID LIST
Source:
SecureLogin
Possible Cause:
A comma doesn't 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 TLAUNCH INI
Source:
SecureLogin
Possible Cause:
SecureLogin is unable to read the tlaunch.ini file because the file has been deleted.
Action:
Create a blank tlaunch.ini file.
Action:
Create a default tlaunch.ini file by reinstalling SecureLogin.
-284 BROKER NO TERMINAL TYPE DEFINED
Source:
SecureLogin
Possible Cause:
The tlaunch.ini file contains an error. The terminal type for the emulator has not been defined.
Action:
Using Terminal Launcher, specify a terminal type for the emulator.
-290 BROKER FILE LOAD FAILED
Source:
SecureLogin
Possible Cause:
You don't have enough rights to convert an earlier tlaunch.ini file to a later format, read an earlier tlaunch.ini file, or create a new tlaunch.ini file.
Action:
The network administrator must assign necessary rights.
-293 BROKER NO EXTENDED TREES FOUND
Source:
SecureLogin
Possible Cause:
The SecureLogin schema extensions to eDirectory or NDS haven't been installed on any of the eDirectory or NDS trees that you are connected to.
Action:
Extend the schema by running schema.exe.
Action:
Connect to an eDirectory or NDS tree that has the SecureLogin schema extensions.
-294 BROKER SETPLAT VARIABLE MUST BE RUN TIME
Source:
SecureLogin
Possible Cause:
The first argument to a SetPlat argument can be a variable. If it is a variable, it must be a runtime variable. The variable used is not a runtime variable.
Action:
Make the first argument a runtime variable.
-295 BROKER ERROR CONDITIONAL COMMAND NOT HANDLED
Source:
SecureLogin
Possible Cause:
SecureLogin doesn't handle text in the second part of an If command.
Action:
Make sure that the command is one listed and documented in the Novell SecureLogin Administration Guide.
-298 BROKER RAW MODE MUST BE SECOND ARG
Source:
SecureLogin
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 EXIST
Source:
SecureLogin
Possible Cause:
You have tried to use repeated characters in a password, but a password policy doesn't allow them.
Action:
Avoid repeated characters.
-300 BROKER DISALLOWED SEQUENTIALS EXIST
Source:
SecureLogin
Possible Cause:
You have tried to use sequential characters in a password, but a password policy doesn't allow them.
Action:
Avoid sequential characters.
-301 BROKER DISALLOWED KEYBOARD ADJACENTS EXIST
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
You entered a password that doesn't have a character in a required position.
Action:
Enter the password correctly.
-308 BROKER BAD POSITION ARGUMENT
Source:
SecureLogin
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
Source:
SecureLogin
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 WRITEABLE VARIABLE
Source:
SecureLogin
Possible Cause:
You tried to save a new value to type of variable that can't be written to.
Action:
Use a runtime or normal variable.
-314 BROKER COPY BACKUP FAILED
Source:
SecureLogin
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.
Action:
Close the process and try again.
Possible Cause:
You don't 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
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
You have used a GoTo command, but the label that you directed it to hasn't been defined.
Action:
Define the label.
-317 BROKER INCORRECT DATABASE VERSION
Source:
SecureLogin
Possible Cause:
The version of SecureLogin that you are using doesn't handle the version of SecureLogin that is stored in eDirectory or NDS.
Action:
Upgrade to the latest version of SecureLogin.
-318 BROKER DIRECTORY CRC DOES NOT MATCH
Source:
SecureLogin
Possible Cause:
Whenever SecureLogin stores an entry in eDirectory or NDS, SecureLogin employs a redundancy check. If the redundancy check doesn't match when SecureLogin reloads the entry, the data in eDirectory or NDS is unusable.
Action:
Troubleshoot eDirectory or NDS.
-319 BROKER DISALLOWED DUPLICATES EXIST
Source:
SecureLogin
Possible Cause:
You entered a password that has unacceptable duplicate characters.
Action:
Enter the password correctly.
-320 BROKER GOTO LIST ASSERTION
Source:
SecureLogin
Possible Cause:
The software is not working as intended.
Action:
Call Novell Technical Services.
-321 BROKER SUBROUTINE NOT DEFINED
Source:
SecureLogin
Possible Cause:
A Call command is calling a subroutine that hasn't yet been defined.
Action:
Define the subroutine.
-325 BROKER ENTRY MUST HAVE NON NULL KEY
Source:
SecureLogin
Possible Cause:
You tried to add a script or variable that is a blank string.
Action:
Provide a name for the script or variable.
-326 BROKER VARIABLE REQUIRED
Source:
SecureLogin
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 but isn't.
Action:
Change the argument to a variable.
-327 BROKER OBJECT NOT FOUND
Source:
SecureLogin
Possible Cause:
LDAP or Active Directory* can't locate the User object in eDirectory or NDS.
Action:
Troubleshoot eDirectory or NDS.
-328 BROKER ADS MEMORY FAILURE
Source:
SecureLogin
Possible Cause:
The Active Directory library was unable to allocate memory.
Action:
Close one or more applications and try again.
-329 BROKER ADS ERROR GETTING ATTRIBUTE
Source:
SecureLogin
Possible Cause:
Although data exists in Active Directory, SecureLogin is unable to read the data.
Action:
Troubleshoot Active Directory.
-330 BROKER ADS INSUFFICIENT RIGHTS TO DELETE
Source:
SecureLogin
Possible Cause:
When you removed a script, SecureLogin tried to delete part of an attribute from Active Directory. However, you are unable to delete the attribute because you don't have sufficient rights to Active Directory.
Action:
The administrator must assign sufficient Active Directory rights for each user so that the user can modify SecureLogin attributes.
-331 BROKER ADS ERROR DELETING VALUE
Source:
SecureLogin
Possible Cause:
Active Directory was unable to delete a value.
Action:
Troubleshoot Active Directory.
-332 BROKER NO PASSWORD FIELD VARIABLE IN SCRIPT
Source:
SecureLogin
Possible Cause:
A Web script must have at least one Type command that has “password” as the second argument. The following lines illustrate a typical script:
Type $Username
Type $Password Password
However, the script 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
Source:
SecureLogin
Possible Cause:
On the RegSplit command, the string that you are running through the regular expression didn't match.
Action:
Change the regular expression.
-335 BROKER REGEX COMPILE FAILED
Source:
SecureLogin
Possible Cause:
The syntax of the regular expression was incorrect.
Action:
Revise the syntax of the regular expression.
-336 BROKER DIRECTORY AUTH DATA CORRUPT
Source:
SecureLogin
Possible Cause:
There is a problem with the Prot:SSOAuth data attribute.
Action:
Call Novell Technical Services.
-340 BROKER UNKNOWN DATABASE VERSION
Source:
SecureLogin
Possible Cause:
You are using an earlier version of SecureLogin.
Action:
Upgrade to the latest version of SecureLogin.
-349 BROKER UNABLE TO FIND SESSION FILE
Source:
SecureLogin
Possible Cause:
Terminal Launcher couldn't find a session file for an emulator.
Action:
Configure Terminal Launcher to have the correct path to the file for the emulator session.
-350 BROKER ERROR NO INDEX
Source:
SecureLogin
Possible Cause:
You started using indexes in a Web script. For example, on the first line you typed the following:
Type $Username #1
Later in the script, you used a Type command without #2 (or another number). You have mixed index mode and non-index mode.
Action:
Either use index mode or non-index mode. Don't mix the two modes.
-353 BROKER RECURSIVE SCRIPT INCLUDE DETECTED
Source:
SecureLogin
Possible Cause:
While using the Include command, you included a script twice.
Action:
Only include a script once.
-354 BROKER NETWORK PASSWORD INCORRECT
Source:
SecureLogin
Possible Cause:
You have turned on the option to prompt the user of the network password before the user can access options on the system tray. The user entered an incorrect password.
Action:
Enter the correct password.
-356 BROKER INVALID CHARACTER FOUND IN STARTUP ID LIST
Source:
SecureLogin
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.
-361 BROKER NMAS DLL NOT AVAILABLE
Source:
SecureLogin
Possible Cause:
SecureLogin can't load 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
Source:
SecureLogin
Possible Cause:
SecureLogin couldn't find the NMAS relogin function in the DLL for NMAS.
Action:
Install the latest version of NMAS.
-363 BROKER STANDARD VARIABLE REQUIRED
Source:
SecureLogin
Possible Cause:
The command requires a $ variable. However, you provided a ? variable.
Action:
Provide a $ variable.
-365 BROKER LDAP INIT FAILED
Source:
SecureLogin
Possible Cause:
The initialization of the LDAP SSL layer failed.
-372 BROKER ACCESS IS DENIED
Source:
SecureLogin
Possible Cause:
For LDAP, you don't have rights to the part of the Directory that you are trying to access.
Action:
Grant users the correct rights.
-373 BROKER HLLAPI CONNECT FAILED
Source:
SecureLogin
Possible Cause:
Terminal Launcher was unable to connect to the emulator
Action:
Make sure that the emulator has HLLAPI enabled.
-375 BROKER NOT RUNNING NT
Source:
SecureLogin
Possible Cause:
Although you aren't running NT, you tried to use a feature that is only available through NT.
Action:
Don't use that feature unless you are running NT.
-380 BROKER HLLAPI NOT CONNECTED TO PS
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
Incorrect parameters were given to a command that uses a HLLAPI function.
Action:
Contact Novell Technical Services.
-382 BROKER HLLAPI INVALID PS POSITION
Source:
SecureLogin
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 script.
-383 BROKER HLLAPI SYSTEM ERROR
Source:
SecureLogin
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
Source:
SecureLogin
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 other HLLAPI applications.
-385 BROKER HLLAPI INPUT REJECTED
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
SecureLogin is unable to query available HLLAPI sessions.
Action:
Make sure that Terminal Launcher is set up correctly with the emulator.
-387 BROKER LAST NDS USER NOT FOUND
Source:
SecureLogin
Possible Cause:
The last eDirectory or NDS user, as stored in the registry, could not be read for use in an NMAS login.
Action:
Make sure that the last eDirectory or NDS user is stored correctly in the registry.
-388 BROKER LAST NDS USER UNWORTHY
Source:
SecureLogin
Possible Cause:
The last eDirectory or NDS user, as stored in the registry, was not in the correct format. An NMAS login was unable to use the format.
Action:
Make sure that the last eDirectory or NDS user is stored correctly in the registry.
-389 BROKER NMAS DISCONNECTED LOGIN NOT FOUND
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
SecureLogin could not initialize the LDAP SSL libraries.
-391 BROKER LDAP SSL ADD CERT FAILED
Source:
SecureLogin
Possible Cause:
SecureLogin could not open the certificate you supplied for LDAP over SSL. Either the file doesn't exist or it is in the incorrect format.
If the certificate file specified ends in .der, SecureLogin uses Distinguished Encoding Rules (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
Source:
SecureLogin
Possible Cause:
A built-in variable such as ?sysversion was not found.
Action:
Make sure that the variable name is correct.
-393 BROKER SCRIPT NOT PURELY INDEXED
Source:
SecureLogin
Possible Cause:
While working with Web modules, you mix indexed and non-indexed commands. For example, you typed the following:
type $username #1
type $password
-394 BROKER LDAP PASSWORD INCORRECT
Source:
SecureLogin
Possible Cause:
The password supplied to login to LDAP was incorrect.
Action:
Check the password.
-395 BROKER LDAP USER NON EXISTENT
Source:
SecureLogin
Possible Cause:
The username that you used to log in to LDAP does not exist.
Action:
Make sure that the username exists in the Directory and that the LDAP context is correct.
-396 BROKER LDAP SERVER DETAILS INCORRECT
Source:
SecureLogin
Possible Cause:
One or more of the LDAP server parameters supplied was incorrect.
Action:
Check the LDAP server address and port number.
Action:
Make sure that the LDAP server you are connected to is running.
-399 BROKER DIVIDE BY ZERO IS BAD
Source:
SecureLogin
Possible Cause:
Using the Divide command, you attempted division by zero.
-400 BROKER WRONG SECTION NAME
Source:
SecureLogin
Possible Cause:
You manually edited a wizard-generated script.
Action:
When editing a script, don't 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 script.
-401 BROKER INVALID GLOBAL WIZARD CONFIG
Source:
SecureLogin
Possible Cause:
You manually edited a wizard-generated script.
Action:
When editing a script, don't 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 script.
-402 BROKER LDAP ATTRIBUTE DOES NOT EXIST IN SCHEMA
Source:
SecureLogin
Possible Cause:
You are running LDAP on eDirectory, but you have not correctly mapped the LDAP attributes.
Action:
Check your LDAP attribute mappings.
Possible Cause:
You are running LDAP on a platform other than eDirectory. However, the schema is not extended for that platform.
Action:
Extend the LDAP schema.
-403 BROKER AAVERIFY DLL NOT AVAILABLE
Source:
SecureLogin
Possible Cause:
SecureLogin was unable to load slaaverify.dll.
Action:
Make sure that you have the correct DLLs installed for Aaverify.
-404 BROKER AAVERIFY FUNCTION NOT FOUND
Source:
SecureLogin
Possible Cause:
You are using the incorrect version of slaaverify.dll.
Action:
Check the version of slaaverify.dll.
-405 BROKER AAVERIFY CONSISTENCY FAILURE
Source:
SecureLogin
Possible Cause:
You are using the incorrect version of slaaverify.dll.
Action:
Check the version of slaaverify.dll.
-406 BROKER AAVERIFY ERROR
Source:
SecureLogin
Possible Cause:
You are using the incorrect version of slaaverify.dll.
Action:
Check the version of slaaverify.dll.
-410 BROKER NOT A STRING ATTRIBUTE
Source:
SecureLogin
Possible Cause:
You are using % variables, but the attribute you are reading is not a plain string attribute (syncestring or syncistring on eDirectory).
Action:
Check the schema a definition of the attribute to confirm that the syntax is syncestring or syncistring.
-411 BROKER LDAP INVALID DN SYNTAX
Source:
SecureLogin
Possible Cause:
The format of your LDAP username was invalid.
Action:
Check the format of the username that you entered.
-412 BROKER INVALID OPTION COMBINATION
Source:
SecureLogin
Possible Cause:
An invalid combination of options was passed to a script command. For example, you passed -right and -raw to the Click command.
Action:
Review the documentation for the script command.
-413 BROKER AAVERIFY SLOGIN DOES NOT EXIST
Source:
SecureLogin
Possible Cause:
Slaaverify.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
Source:
SecureLogin
Possible Cause:
Slaaverify.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
Source:
SecureLogin
Possible Cause:
Slaaverify.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
Source:
SecureLogin
Possible Cause:
The wizard was unable to retrieve the executable name for the window you selected.
Action:
For this application, don't use the wizard.
-417 BROKER ADS PUT OCTET INSUFFICIENT RIGHTS
Source:
SecureLogin
Possible Cause:
You do not have sufficient rights to ADS to perform the current operation.
Action:
Ask the ADS administrator to assign you additional ADS rights.
-418 BROKER ADS CLR OCTET INSUFFICIENT RIGHTS
Source:
SecureLogin
Possible Cause:
You do not have sufficient rights to ADS to perform the current operation.
Action:
Ask the ADS administrator to assign you additional ADS rights.
-423 BROKER ERROR INITIALIZING DATA STORES
Source:
SecureLogin
Possible Cause:
SecureLogin was unable to initialize either the primary or secondary datastore.
-424 BROKER UNABLE TO LOAD SLOTP DLL
Source:
SecureLogin
Possible Cause:
Slotp.dll could not be loaded. This DLL is required for synchronizing one-time passwords to LDAP directories.
Action:
Review documentation for one-time passwords.
-425 BROKER LDAP NO SUCH ATTRIBUTE
Source:
SecureLogin
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
Source:
SecureLogin
Possible Cause:
A system variable (for example, ?syspassword) was requested but was not available. Slina.dll or slnmas.dll must be correctly installed for these variables to function.
Action:
Make sure that either slina.dll or slnmas.dll is installed.
-430 BROKER MUST BE CALL OR GOTO
Source:
SecureLogin
Possible Cause:
When using the OnException command, the second parameter must be either Call or GoTo.