Environment
Novell SecureLogin
NSL7.0.1
NSL7.0.1
Situation
Lotus Notes becomes unresponsive when mail attachment is opened.
Task Manager shows SLWinsso takes 50% of CPU utilization.
Lotus Notes hangs when SLDotNetsso is active.
Task Manager shows SLWinsso takes 50% of CPU utilization.
Lotus Notes hangs when SLDotNetsso is active.
Resolution
Bug report has been entered.
Workaround:
Disable sldotnetsso.exe
The problem is caused by operations performed by sldotnet.sso. To disable sldotnetsso.exe do the following:
1. Install NSL7.0.1 HotFix4 or later. (Note: with HF3 this workaround was made available for 32 bit Windows systems. With HF4 it also works with 64 bit Windows operating systems.)
2. Create a DWORD value 'DisableDotNetSSO' under the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Protocom\SecureLogin'. (Note: On 64 bit workstations this must be a 32 Bit DWORD.)
3. Set this value to "1".
Bug report has been entered.
Workaround:
Disable sldotnetsso.exe
The problem is caused by operations performed by sldotnet.sso. To disable sldotnetsso.exe do the following:
1. Install NSL7.0.1 HotFix4 or later. (Note: with HF3 this workaround was made available for 32 bit Windows systems. With HF4 it also works with 64 bit Windows operating systems.)
2. Create a DWORD value 'DisableDotNetSSO' under the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Protocom\SecureLogin'. (Note: On 64 bit workstations this must be a 32 Bit DWORD.)
If the registry entry 'DisableDotNetSSO' is not present or set to '0' then sldotnetsso will be enabled. If registry entry 'DisableDotNetSSO' is set to '1' then sldotnetsso will be disabled and will not start as part of NSL. Workstations so modified will not have single sign on for .net applications.
Workaround:
Disable sldotnetsso.exe
The problem is caused by operations performed by sldotnet.sso. To disable sldotnetsso.exe do the following:
1. Install NSL7.0.1 HotFix4 or later. (Note: with HF3 this workaround was made available for 32 bit Windows systems. With HF4 it also works with 64 bit Windows operating systems.)
2. Create a DWORD value 'DisableDotNetSSO' under the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Protocom\SecureLogin'. (Note: On 64 bit workstations this must be a 32 Bit DWORD.)
3. Set this value to "1".
Bug report has been entered.
Workaround:
Disable sldotnetsso.exe
The problem is caused by operations performed by sldotnet.sso. To disable sldotnetsso.exe do the following:
1. Install NSL7.0.1 HotFix4 or later. (Note: with HF3 this workaround was made available for 32 bit Windows systems. With HF4 it also works with 64 bit Windows operating systems.)
2. Create a DWORD value 'DisableDotNetSSO' under the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Protocom\SecureLogin'. (Note: On 64 bit workstations this must be a 32 Bit DWORD.)
If the registry entry 'DisableDotNetSSO' is not present or set to '0' then sldotnetsso will be enabled. If registry entry 'DisableDotNetSSO' is set to '1' then sldotnetsso will be disabled and will not start as part of NSL. Workstations so modified will not have single sign on for .net applications.