The significance of Windows user rights when activating 1C:Drive
According to the feedback received from 1Ci partners, some settings specified during the installation of 1C:Enterprise are of great importance for the successful activation of 1C:Drive and the proper exchange of server-client licenses. In a nutshell, these settings allow the creation of a new user under which the 1C:Enterprise product runs. If they are not set properly, they may cause problems during the activation of 1C:Drive.
Problem Description
As shown in the 1C:Enterprise server instructional video, users may choose to install 1C:Enterprise as a Windows service that an exclusive user (“USR1CV8” by default) runs. If this new user doesn't have "Administrator" or "Performance log user" rights, some components like CodeCompletionAddIn required for 1C:Drive activation cannot be attached properly. In this case, two main problems related to activation may occur:
- When a 1C:Drive license is activated on the server side, the “Type is not defined (AddIn.CodeCompletionAddIn.libepf)” error is received.
- Occasionally, the server cannot exchange user license data with the connected clients causing them to receive the “No free licenses are available at the moment” warning.
Solution
- Close the 1C:Enterprise application.
- Run the 1C:Enterprise application as administrator and activate the license.
- If the error persists, close the 1C:Enterprise application once again and make sure that the user account running the 1C server is of “Performance log user” or “Administrator” type. If the account has any other rights, change it to either of the above.
- Restart the 1C:Enterprise server service (1C:Enterprise 8.3 Server Agent).
- Run the 1C:Enterprise application and activate the license.
- If the license is already activated but clients are unable to connect successfully, close the 1C:Enterprise application on the client side and then connect to the server again after completing previous steps on the server.
- If the license is already activated but clients are unable to connect successfully, close the 1C:Enterprise application on the client side and then connect to the server again after completing previous steps on the server.