Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.
Customer with SecureLogin installed in a Microsoft Active Directory environment wants to administer SecureLogin using the MMC snapin.
They started MMC and navigated to the CN=Administrator user object. They then navigated to the SecureLogin tab and the following errors displayed;
Please load SecureLogin before using the script editor
SecureLogin was unable to load the script editor. Err=1114 Path=c:\Program Files\Protocom\SecureLogin\scptedit2.dll
Unable to load the SecureLogin script editor in MMC
Before you can administer SecureLogin data (including applications, usernames and passwords, settings etc.) the SecureLogin client must verify you have the appropriate access required and communicate with the Directory.
The SecureLogin security keys and communications broker are only loaded when the SecureLogin client is running. If SecureLogin didnât apply security checks on the data in this way, people with rights to the Directory could potentially view data and administer the product (for example).
You must start the SecureLogin client before attempting to administer it using MMC. In newer versions of SecureLogin, a more friendly message is displayed advising the user to load SecureLogin.