High CPU usage with Novell SecureLogin

  • 7011260
  • 25-Oct-2012
  • 25-Oct-2012


NetIQ SecureLogin 7.0.x
Windows 2008 R2 Terminal Servers
Windows 7 workstations
Windows XP workstations
Web based Application


High CPU usage when using SecureLogin for a web based application with Internet Explorer.
Task manger shows hig CPU usage for iExplore.exe, SLBroker.exe, or SLBroker64.exe


In this case the problem was caused by a mis-configured script for one of the web applications. Recreating the script with the NSL7 Wizard resolved the problem.

Additional Information

 There could also have been several other causes for this problem. Troubleshooting Ideas:
1. Check the registry setting for IESSOBHO.  If it is set to 0, make sure that IESSOObjClass and/ or IESSOObj64Class have been disabled in IE Tools, Manage add ons. If IESSOBHO is currently set to 1, try setting it to 0 and then disable the IESSOObjClass add on. Restart IE and SecureLogin after making changes.
       HKLM\SOFTWARE\Protocom\SecureLogin  DWORD  IESSOBHO 

      1 Default value: SecureLogin works through the BHO interface
             0 Integrate with the IE process instead.

Note that if IESSOBHO is set to 0 AND the IESSOObjClass add on is active SecureLogin will attempt to do both of the above, which could cause performance or utilization problems.

2. Disable dotnetsso and flash sso per TID 7008895.
  If this helps, test to see if other applications are affected.  If you are not using SecureLogin for .net or flash applications this may be a viable solution.   Again, restart IE and SecureLogin after making any changes.

3. Set IESSO_NOTONEXIT to 1. This may particularly be helpful if the web app has multiple pages.  This setting disables the on page exit processing.

               0 runs on exit
               1 stops running the user mode wizard

 As always, restart IE and SecureLogin after making any changes in the registry.

 4. Determine if the problem is only present when one specific sso enabled app is invoked, or if it happens with with all sso enabled web apps.

5. If the problem only occurs for one (or a few) app(s), disable SecureLogin for this app by unchecking the "enabled" box on the details tab for the application in Manage Logins.  If the problem goes a way with the  application disabled, the problem is most likely with the script for that application.  Determine what kind of script is being used, and try recreating it with the NSL7 Wizard.

The "details" tab of the application will show the type script in parentheses after the name of the application definition, for example, advanced web, generic wizard, or web wizard.  Application definitions created with the NSL7 Wizard will show as type “Generic Wizard.” In this particular case the type showed as “Web Wizard Script” meaning the application definition was created with the NSL6.1 Wizard.