-199 Errors launching an SSO enabled application

  • 7940097
  • 19-Aug-2009
  • 26-Apr-2012

Environment

SecureLogin
SecureLogin SSO
All Versions
MS AD, LDAP, NT4, Citrix, Terminal Services


Situation

SSO administrator is creating an application definition to SSO enable an application. When they start the application, error -199 appears.

Resolution

The error -199 will provide a pointer to the line of the application definition SecureLogin is having trouble interpreting. It may not be the exact line but it should provide you with a clue. For example, the line may be reporting the ChangePassword command but the issue could be there is restricted a variable to a password policy but haven’t created the password policy.

Make sure the syntax is correct in the application definition.

Also verify the command used applies to the type of application you are enabling. Certain commands only apply to certain application types. For example, GetURL is only applicable to web applications. The application definition includes information on which commands apply to which application types.

Additional Information

Root Cause

When SecureLogin sees an SSO enabled application launch (by the .exe name, the URL for a web script etc.) it parses the application defintion (formerly called scripts) to see which messages, text, prompts, URLs and/or dialog boxes etc. it should ""watch for"" and what it should do when it ""sees"" them.

Error -199 occurs when the script parser is unable to interpret a command in the script, often due to syntax error.

For example, you will receive a -199 error in the following situations:

  • An ""If"" statement does not end with an ""EndIf"";
  • There are spaces between words in a command e.g. use Message Box (incorrect syntax) instead of MessageBox (correct syntax);
  • You use a command for a new version of SecureLogin on an old version of SecureLogin (new versions often include new commands that can only be read by the new client);
  • There is no # in front of a commented line;
  • You have called a sub routine using Call NameofSubRoutine but haven’t created the sub routine or have the name wrong.

In this case, the administrator did not use the correct syntax and typed some commands incorrectly.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.