Single Logon - Common Problems
Credential Storage Error
Description
Single Logon stores certain module credentials in the Windows User Account to enable other programs to seamlessly log the user on to the system without the need to enter credentials.
Symptoms
When you attempt to load up Single Logon you will be met by the following error a specified logon session does not exist
Solution
This error is caused by the WriteWinCredentials call failing when storing or updating credentials within Windows..
The Windows store credential facility can be disabled by group policy via the Network access: Do not allow storage of credentials or .NET Passports for network authentication setting in security options. This must be enabled for this Single Logon functionality to work correctly.
Auto Start
Description
Single Logon can start automatically when a user logs on, this feature is called Auto Start. If enabled Auto Start allows the user can select a list of modules that they would like Single Logon to automatically start when they log on to Windows.
Symptoms
Receive errors from modules which are being auto-started by Single Logon. These modules will however work when manually activated by user in Single Logon. The most typical error of the sort is produced by the EMIS module when error Cannot find splash form is shown on auto-start but not when activated manually via Single Logon. Another example is error Timeout waiting for window, which again occurs on auto-start but not through manual activation.
Solution
When Windows initially logs on a lot of CPU time will be allocated to the various tasks that must be performed when a new logon session is initialised. This will means they program sometimes take longer to load than normal and can cause problems for Single Logon to function correctly
SingleLogon has inbuilt time limits for certain events, e.g. it will wait X seconds for a program window to appear. If these are exceeded then an error will occur.
Attempting to auto-start too soon after Windows logon can result in modules failing due to the programs running too slowly and these time limits being exceeded.
Single Logon has an auto-start delay setting (Settings --> Auto Start) which CSS recommends is set at a minimum of 30s for a standard GP practice. If errors continue to occur when auto-starting but not when activating the program manually through Single Logon then this time limit should be increased until the error no longer occurs.
If 90s is reached and the error is not resolved then this should be passed to Campbell Software Solutions for investigation.
See handy hints ans tips for details on how to set or change this settingTrustee Rapport Software Conflict
Description
Single Logon requires access to browser interfaces to function. If the Rapport software is running, Single Logon will be unable to access the interfaces required for authentication.
Symptoms
Attempting to activate any web based module gives error Not implemented
Solution
The Rapport software should be disabled or removed on computers where Single Logon is required. It is also unlikely that the Rapport software is approved for use by organisation IT departments due to the non-standard browser behaviour that is exhibited by design when the software is installed.