When Laserfiche Directory Server and Microsoft SQL Server are on the same machine, the SQL server service has to start before the Directory Server. If not, users may see a variety of symptoms, a few of which are described below:
- While making changes in the Laserfiche Directory Server (such as creating a new user or group, or processing Active Directory group synchronization rules), users receive the following error: "Group 'Test' not registered successfully: The given key was not present in the dictionary."
- When users restart their computer and launch Laserfiche Directory Server 10.4, they receive the following error: "Reactivation was not successful: The given key was not present in the dictionary. (LFDS10)(LMO0)" This behavior also occurs when creating a new license, adding new users, or trying to register/un-register a new instance of the product.
- After shutting down and restarting the computer, users have to restart Laserfiche Directory Server and re-license the products again.
- Users are unable to save changes, such as taking away a user's license, without receiving the following error: "The given key was not present in the dictionary." Upon refreshing the page, however, the license is shown to be removed.
You may see the issues described above when Laserfiche Directory Server and Microsoft SQL Server are installed on the same machine. In order for Laserfiche Directory Server to function, Microsoft SQL Server must start before it. When the server is rebooted, Laserfiche Directory Server may start before SQL, causing an error.
Change the Laserfiche Directory Server startup type to Automatic (Delayed Start). This will allow Microsoft SQL Server to start before Laserfiche Directory Server.
- Open the Services MMC Snap-in.
- Locate the Laserfiche Directory Server 10.4 service and view its properties.
- Under the General tab in the Laserfiche Directory Server 10.4 Properties (Local Computer) dialog box, change the Startup type to Automatic (Delayed Start).
- Click OK to save the changes.