Over the past few weeks, some users have reported error 1923. For some users, my error might be Error 1923: Make sure you have sufficient permissions to install system items and / or Error 1939 when trying to modify or install Intel® Control Center Killer.
Uniwares_AS
Posts: 8
Joined: Thursday October 4, 2009 01:03 am
Error 1923 While Installing Service
Hello, the package I created installs the service as a component, but the installation still fails under the following conditions:
Product: PRODUCTNAME- Error 1923. The PRODUCTNAME (PRODUCTNAME may be servicing) service is not installed. Make sure you have valid permissions to install system services.
Hardly a matter of privileges, as far as I know, the user is an administrator, awesome bug under W2k and WXP and W2003 server.
Please note that the name associated with the service cannot contain properties that cannot be formatted (for example, “[PRODUCTNAME]” instead of most “PRODUCTNAME”), and it cannot ignore spaces.
We have a guide on how to create an operation, install it, take a look: http://www.advancedinstaller.com/user-g … rvice.html
If the underlying problem persists, send our staff an AIP (if it does not contain classified information) or a small drop test repeating this behavior to AdvancedInstaller support. transport com so that we can investigate each of our problems.
Uniwares_AS
Posts: 8
Registration: 4 okThursday, October 2007 01:03
PRODUCTNAME does not refer to the building, but to the actual service name that appears in the event log (so replace PRODUCTNAME with MYDUMMYSERVICE on the other side).
All stages of learning – if applicable – can be read.
And sorry for posting on the wrong forum, I don’t know why it ended here.
Uniwares_AS
Posts: 8
Joined: Thursday October 4, 2008 01:03 am
Resolved And Feature Request
If a service needs to be installed under an important restricted account such as the NetworkService privilege, the installer should follow these steps 1) Create a custom action for each operating system that requires a different account name 2) Set SERVICEACCOUNT to an account name for the operating system in the CostFinalize custom action these names are: NT AUTHORITY SYSTEM for Windows 2000, NT AUTHORITY NETWORK SERVICE for Windows XP / 2003 3) If the service requires the flag “Allow to interact with the desktop”, it MUST run under the LocalSystem account (therefore webpage name should be left blank and even set to AUTHORITY SYSTEM) 4) do not add [SERVICEACCOUNT] to display the account name field under services 5) In any case, the password subject is ignored for integrated service clients like NetworkService, LocalService, LocalSystem, and can be left blank
Any other setting will result in error 1923 (or sequence 1920) if installed without warning. Invalid account name is an error during installation, allowing you to wait for a new account to be created and try again.
Okay, not forgetting, now a feature request comes in: perhaps the AI can automatically disable the account name / password fields every time you enable “Allow service to interact with the desktop.” Some can save people time.
We will be looking into adding this type of functionality in a future version of the Adva installer.nced. Thanks for your feedback.
bjk68
Posts: 55
Joined: Tuesday December 2009 01 12:45 pm
Subject: Error 1923 While Installing Service
Today I received this error from 1923, which said that I did not have permission to install services. I followed each of the steps in the help column http://www.advancedinstaller.com/user-g … rvice.html to add the login right for the user user. But this installation also failed with error 1923. I confirmed that the “Allow operations to interact with the desktop” checkbox was unchecked. But still unsuccessfully.
I eventually found the exact problem: the installer was trying to install a service that was already present on the system. You do not expect to see the severe error 1923 “Insufficient Permissions” if part of the service already exists.
The previous version of this service was installed manually, and now we are creating an installer directly for this update service. This first version linked to the installer of this service certainly does not have any update functionality because o You actually do not know the previously installed service. Therefore, we should have manually uninstalled the previous translation of the service before hoping to install the next version of type s.
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
Run gpedit. Undoubtedly, in the tree structure, expand Computer Configuration> Windows Settings> Security Settings> Local Policies> User Rights Assignment. In the details pane, find and double-click Service Connection.
Start Windows Explorer as administrator. Press Ctrl + Shift + Esc to open the Task Manager.Use the command line. Press the Windows key + R keys.Convert your account to admin credit.Disable User Account Control.
Navigate to Computer Configuration> Windows Settings> Security Settings> Local Policies> User Rights Assignment. In the main details pane, double-click Connect as Critical Service. Click Add User or Group … and / or add the account to the account listrecords that have the right to connect during the service. Click OK to close the policy editor.
