Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

Sage 50 Error 1920: Troubleshooting Service Startup Failures

Installing or upgrading Sage 50 can become frustrating when the setup process stops with Error 1920. Instead of completing the installation, Windows displays a message saying that a Sage service failed to start and that sufficient privileges may be required to start system services. The affected service may be the Sage 50 Accounts Data Service, Sage 50 Control Service, or Sage AutoUpdate Manager Service. Restarting the computer or running the installer again may not resolve the problem if the underlying service configuration is still preventing startup.

Sage 50 Error 1920 is a Windows Installer service-start failure. It does not identify one single cause. The problem may involve Windows permissions, temporary installation files, antivirus interference, an existing Sage service, damaged service-related files, or a Windows component required by the service. The exact error message matters because the Data Service, Control Service, and AutoUpdate Manager have different functions and may require different troubleshooting procedures.

This guide explains how to troubleshoot Sage 50 Error 1920 using Sage’s documented procedures for the affected services. It covers installation permissions, temporary files, antivirus interference, service processes, Control Service folders, Data Service startup, and version-specific considerations. One important distinction: the exact service names in this error are used in Sage 50 Accounts documentation in certain regions. Sage 50 U.S. Edition has different components and installation procedures, so do not apply UK-specific folder paths or service instructions to a U.S. installation without confirming that they match your product.

Why Does Sage 50 Error 1920 Occur?

Error 1920 appears when the Windows Installer cannot start a service required by the Sage installation. The message often includes wording such as:

  • Error 1920: Service Sage 50 Accounts Data Service failed to start.
  • Error 1920: Service Sage 50 Control Service failed to start.
  • Error 1920: Service Sage AutoUpdate Manager Service failed to start.
  • Verify that you have sufficient privileges to start system services.

Sage’s official installation guidance identifies these as separate Error 1920 scenarios. It provides different troubleshooting procedures depending on which service fails. For example, the Control Service issue can involve service-related temporary folders and .NET components, while the AutoUpdate Manager issue has its own steps involving temporary files, antivirus software, and running Sage processes.

The wording about insufficient privileges should not automatically be interpreted as proof that the Windows account lacks administrator rights. Permissions are one possible cause, but the service may also be blocked by security software or unable to initialize because of an existing installation problem.

Common causes of Sage 50 installation Error 1920:

Possible causeWhat may happenWhat to check
Insufficient Windows permissionsInstaller cannot start or configure a Sage serviceWindows account privileges and folder permissions
Antivirus interferenceSecurity software blocks a Sage service or installation processAntivirus alerts, exclusions, and product-specific guidance
Existing Sage processesAn earlier service or update process remains activeRunning Sage processes and services
Damaged temporary filesInstallation cannot reuse or create required temporary componentsWindows temporary folders
Control Service folder problemSage Control Service fails to initializeVersion-specific Sage Control Service temporary folder
Damaged service-related filesData Service fails during installation or startupSage service files and installation state
Missing or damaged .NET componentsA service that depends on .NET cannot start correctlyRequired .NET Framework version and Windows updates
Incorrect service installationService registration or configuration is incompleteSage installation and service status
Server system requirementsData Service cannot install on the computer hosting company dataSage version requirements and Windows compatibility

Before changing anything, identify the exact service named in the error. This prevents you from applying a fix designed for the AutoUpdate Manager to a Data Service problem, or deleting files that are unrelated to the failed component.

How to Fix Sage 50 Error 1920

The safest troubleshooting approach is to follow the procedure for the service named in the error message. Start with a Windows restart and basic permission checks. If those do not help, use the relevant Sage procedure for the Data Service, Control Service, or AutoUpdate Manager.

Before beginning, close Sage 50 and any open installer windows. In a network installation, ask other users to exit Sage 50 before restarting or modifying services on the computer that hosts the company data. Make sure you have a current company data backup before carrying out advanced repair or reinstallation work.

1. Restart Windows and Run the Sage Installer with Administrator Rights

A pending Windows operation or an installation process that did not close properly can interfere with a service installation. Restarting Windows clears many temporary process conflicts and gives the installer a clean opportunity to configure the required service.

Follow these steps:

  1. Save your work and close Sage 50.
  2. Close any Sage installation or update windows.
  3. Restart the computer.
  4. Sign in to Windows using an account with administrator privileges.
  5. Locate the original Sage installation file.
  6. Right-click the installer and select Run as administrator, if that option is available.
  7. Approve the Windows security prompt when appropriate.
  8. Follow the installation instructions and check whether Error 1920 appears again.

Running the installer as administrator can address some permission-related installation failures, but it will not necessarily resolve a service blocked by antivirus software, damaged files, or missing Windows components. If the error persists, note the exact service name and continue with its corresponding troubleshooting section.

2. Clear the Windows Temporary Folder

Sage’s official troubleshooting procedure for the AutoUpdate Manager service includes clearing the Windows temporary folder. Temporary installation files can sometimes interfere with a new installation attempt. To clear the temporary folder:

  1. Close Sage 50 and the installer.
  2. Press Windows + R on your keyboard.
  3. Enter %temp% and select OK.
  4. When File Explorer opens, press Ctrl + A to select the contents.
  5. Press Delete.
  6. If Windows reports that some files are currently in use, skip those files rather than forcing their removal.
  7. Restart Windows.
  8. Run the Sage installer again using the appropriate administrator account.

Important precaution

The %temp% folder may contain temporary files used by other applications, not just Sage 50. Sage cautions that deleting its contents can affect other software. If you are unsure which files can safely be removed, ask your IT support team to perform the cleanup. If clearing temporary files does not resolve the error, do not repeat the same cleanup indefinitely. Move to the service-specific checks.

3. Resolve Sage 50 Accounts Data Service Error 1920

When the message identifies Sage 50 Accounts Data Service, the installation has failed to start the service responsible for supporting access to Sage 50 company data. Sage’s official Data Service Error 1920 guidance describes a sequence of checks involving Control Service temporary folders, service-related SQLite files, temporary files, Windows permissions, and antivirus software. The applicable steps depend on the installed Sage Accounts version.

First, check the installed version. The service folder names include a version identifier, commonly represented as VXX in Sage instructions. Do not substitute a different version number or modify files belonging to another Sage installation. For the documented Control Service folder check:

  1. Confirm whether your Sage Accounts version is v27.1 or earlier.
  2. Close Sage 50 and make sure the relevant Sage services are not running.
  3. Open File Explorer.
  4. Navigate to C:\Windows\Temp\.Net.
  5. Look for a folder referring to the Sage Control Service, such as Sage.UK.Accounts50.Data.Service.Control_v27.
  6. If the folder applies to your version and the Sage procedure instructs you to remove it, delete that specific folder.
  7. Retry the installation.

Sage states that this Control Service folder deletion is not required for version v27.2 and later as part of this particular Data Service Error 1920 procedure. Do not delete unrelated folders. Rename the service-related SQLite files when the procedure applies: Sage’s instructions also identify service-related SQLite files in the Sage Accounts service installation folder. The location depends on whether Windows is 32-bit or 64-bit:

  • 32-bit Windows: C:\Program Files\Sage\AccountsServiceVXX
  • 64-bit Windows: C:\Program Files (x86)\Sage\AccountsServiceVXX

The files named in the procedure are:

  • Sg50Svc_vXX.sqlite3
  • Sg50Svc_vXX.sqlite3-Shm
  • Sg50Svc_vXX.sqlite3-wal

If these files exist and the official procedure applies to your installation, rename them as instructed rather than deleting them. For example, an administrator may append an identifying suffix such as old to the filenames. Then close File Explorer and retry the Sage installation. These are service-related files, so do not rename similarly named files in another folder or another version’s installation. If you cannot identify the correct files, stop and ask your IT support team.

4. Fix Sage 50 Control Service Error 1920

The Sage 50 Control Service helps manage the relevant Sage Accounts service components. If it fails to start during installation, Sage’s documented troubleshooting includes checking the Control Service temporary folder, stopping the relevant Sage services, and verifying the required .NET components.

For newer Sage Accounts releases, service names can include the installed version number. For example, a service may appear as Sage 50 Accounts Service v33 or Sage 50 Accounts Control v33. The actual names depend on the installed release. Stop the relevant Sage services:

  1. Press Windows + R.
  2. Enter services.msc and select OK.
  3. Locate the Sage 50 Accounts service for your installed version.
  4. Right-click it and select Stop, if it is running.
  5. Locate the corresponding Sage 50 Accounts Control service.
  6. Stop that service as well, if it is running.

If the computer hosts company data, make sure all users have closed Sage 50 before stopping services. Stopping a data service while other users are working can interrupt access to company data.

Check the Control Service temporary folder:

  1. Open File Explorer.
  2. Navigate to C:\Windows\Temp\.Net.
  3. Locate the folder associated with your installed Sage Control Service version.
  4. Follow Sage’s version-specific instructions for removing the affected folder.
  5. Return to the Services window.
  6. Start the relevant Sage services again if the procedure requires it.
  7. Retry the installation.

Sage’s newer Control Service guidance also identifies antivirus interference and .NET configuration as possible causes. The exact folder and service names must match the installed release. Do not use an example folder name from another version as a replacement for your own.

5. Fix Sage AutoUpdate Manager Service Error 1920

If the error specifically states that the Sage AutoUpdate Manager Service failed to start, follow the AutoUpdate Manager troubleshooting procedure rather than the Data Service procedure. Sage’s official instructions include clearing temporary files, restarting Windows, checking antivirus interference, ending remaining Sage processes, and reviewing permissions when the problem continues. Start with the temporary-file and restart checks:

  1. Close the Sage installer.
  2. Press Windows + R.
  3. Enter %temp%.
  4. Select the temporary files and remove the files Windows allows you to delete.
  5. Restart Windows.
  6. Sign in as a Windows administrator.
  7. Run the Sage installation again.

If the error remains, Sage’s guidance recommends checking whether antivirus software is interfering with the installation. Follow the security-software instructions in the next section.

Check for a running AutoUpdate Manager process:

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Open the Processes tab or the appropriate process view in your Windows version.
  3. Look for Sage.Central.AutoUpdateManager.Service.exe.
  4. Confirm that no Sage update or installation is actively running.
  5. If the process is left over from a failed attempt, follow Sage’s instructions to end it.
  6. Check for other remaining Sage processes only when it is safe to do so.
  7. Run the installer again.

Do not end processes blindly. A running Sage process may belong to another user or an active operation. On a shared computer or server, coordinate with the administrator before stopping processes. If the AutoUpdate Manager still fails, have your IT support team review the permissions on the relevant Sage installation folders and the service’s ability to start.

6. Check Antivirus Software That May Block Sage Services

Antivirus and endpoint-protection software can sometimes interfere with Sage service installation or startup. Sage specifically identifies antivirus interference in its Error 1920 guidance for the Control Service and AutoUpdate Manager.

Sage has also documented a Control Service issue affecting certain Sage Accounts v33.1 installations in connection with security products including Webroot SecureAnywhere and OpenText Core Endpoint Protection. This is a version- and product-specific example, not evidence that every antivirus application causes Error 1920. How to investigate antivirus interference:

  1. Identify the antivirus or endpoint-protection product installed on the affected computer.
  2. Check its security history, quarantine, and blocked-application notifications for Sage installation components.
  3. Confirm whether the product has pending updates.
  4. Ask your IT administrator or antivirus provider whether a Sage process or service has been blocked.
  5. If Sage’s specific instructions require a temporary test or an exclusion, have an authorized administrator apply it.
  6. Retry the installation according to the documented procedure.
  7. Restore normal protection and confirm that the appropriate security controls remain active.

Do not permanently disable antivirus software to complete an installation. If a temporary test is required, keep it limited to the necessary time and scope, and follow your organization’s security policy. If the antivirus product reports no blocked Sage components, continue investigating Windows permissions, .NET, and service configuration rather than assuming security software is responsible.

7. Check Windows Permissions for Sage Installation Folders

Error 1920 may appear when the installer cannot access a folder or create or start a Windows service. Sage’s troubleshooting procedures include checking permissions on shared Windows folders when the basic installation steps do not resolve the problem. A Windows administrator account does not necessarily guarantee that every folder has the correct permissions. Folder ownership, inherited permissions, and security policies can also affect installation. Before changing permissions:

  • Confirm which Sage service is failing.
  • Identify the folder named in the error or the relevant folder in Sage’s official procedure.
  • Check whether the computer is managed by a domain or organization.
  • Ask your IT administrator to review the permissions if you do not manage Windows security settings.

Sage’s Data Service Error 1920 instructions include an advanced permissions procedure involving the Common Files folder under Program Files. The exact location depends on Windows architecture:

  • 64-bit Windows: C:\Program Files (x86)\Common Files
  • 32-bit Windows: C:\Program Files\Common Files

The documented procedure involves reviewing folder security and ownership. Because changing ownership or permissions on a shared Windows folder can affect other applications, do not apply broad permission changes without following Sage’s exact instructions for your version. Avoid granting the Everyone group full control or changing permissions across the entire Program Files directory. These changes can weaken Windows security and create problems unrelated to Sage 50.

8. Verify the Required Microsoft .NET Framework Components

Some Sage Accounts service-start failures can be associated with .NET Framework components. Sage’s Control Service troubleshooting guidance specifically includes checking for Microsoft .NET Framework 4.7.2 or later in the applicable version-specific procedure.

A missing, disabled, or damaged .NET component can prevent a service from initializing correctly. Check the installed .NET components:

  1. Press Windows + R.
  2. Enter appwiz.cpl and select OK.
  3. Open the Windows features area using the available Windows interface.
  4. Review the Microsoft .NET Framework features.
  5. Check whether the .NET version required by your Sage release is installed and enabled.
  6. If the required component is missing or disabled, ask your IT administrator to install or enable the supported component.
  7. Restart Windows and retry the Sage installation.

Do not assume that the newest .NET release automatically replaces every older framework component. Some applications require particular .NET Framework versions or features. Follow the system requirements for your exact Sage release and Windows version. If the required .NET component is already installed, do not repeatedly enable and disable Windows features. Continue with the remaining checks or ask IT support to investigate whether the framework installation is damaged.

9. Check Whether the Windows System Information Tool Works

Sage’s newer Control Service troubleshooting procedure includes checking the Windows System Information application. If this Windows component opens as a blank window or displays an error, Sage identifies it as a possible sign of a Windows management problem that may need attention. To check the application:

  1. Select the Windows Search box.
  2. Type System Information.
  3. Open the System Information application.
  4. Wait for the system details to appear.

If the application displays the computer’s information normally, continue with the other Sage troubleshooting checks. If it opens blank or displays an error, do not immediately reset Windows management components. Sage’s documented procedure includes advanced Windows Management Instrumentation (WMI) troubleshooting using an elevated Command Prompt. This should be performed by an IT professional because WMI supports multiple Windows applications and services.

The procedure may involve stopping and restarting the Windows Management Instrumentation service. Sage also documents a repository-reset command for cases where the service cannot be stopped normally. These operations can affect Windows management functionality, so do not run them simply because Error 1920 appeared. If the System Information application remains unavailable after the appropriate repair, have your IT administrator investigate Windows before reinstalling Sage 50.

How to Prevent Sage 50 Error 1920

Although Error 1920 can have several causes, good installation and maintenance practices can reduce the likelihood of service-start failures.

1. Keep Windows and required components updated

Install supported Windows updates and maintain the .NET components required by your Sage release. Before upgrading Sage 50, check the product’s system requirements to confirm that the computer meets the requirements for the application and its services.

2. Use the correct Windows administrator account

Make sure the person installing or upgrading Sage 50 has the necessary Windows privileges. If your organization controls software installation through IT policies, arrange for an authorized administrator to perform the installation.

3. Review antivirus and endpoint-protection settings

Keep antivirus software updated and monitor its security notifications for blocked Sage processes. If a documented compatibility issue exists, follow the instructions from Sage and the security-software provider. Avoid leaving protection disabled after troubleshooting.

4. Close Sage processes before installation

Make sure Sage 50 and its related installation or update processes are closed before starting a new installation. In a network environment, coordinate maintenance with users before stopping services on the computer hosting company data.

5. Verify the server configuration

Check that the computer hosting company data meets the system requirements for the Sage release. Maintain the correct Data Service version and ensure that workstations connect to the intended server.

6. Maintain company data backups

Create and verify backups before major upgrades, service repairs, or reinstallation. Keep backups in an appropriate location separate from the working company data so that a problem with the installation does not also affect the available recovery copy.

7. Follow version-specific installation instructions

Service names, temporary folders, and installation procedures can change between Sage releases. Use the instructions for your exact version rather than copying commands or folder paths from an older installation guide.

Conclusion

Sage 50 Error 1920 occurs when Windows cannot start a service required by the Sage installation. The failed component may be the Data Service, Control Service, or AutoUpdate Manager, and each can require a different troubleshooting approach.

Start by restarting Windows and running the installer with the appropriate administrator permissions. If the error continues, follow the documented procedure for the affected service. This may involve clearing temporary files, checking antivirus interference, closing remaining Sage processes, reviewing service-related folders, verifying .NET components, or investigating Windows permissions.

Pay particular attention to the installed Sage edition and release. Service names and troubleshooting paths differ across versions and regions, so applying an unrelated procedure can create additional problems. If the service still cannot start, consult your IT administrator or Sage support before making advanced Windows changes or reinstalling the application.

FAQs of Sage 50 Error 1920:

How do I fix Sage 50 Error 1920 during installation?

First, identify the service named in the error message. Restart Windows, sign in using an administrator account, and run the Sage installer with the required permissions. If the problem continues, follow the specific Sage troubleshooting procedure for the Data Service, Control Service, or AutoUpdate Manager. Check temporary files, antivirus interference, and Windows components as applicable.

What does Sage 50 Error 1920: Service failed to start mean?

It means Windows Installer could not start a service required by the Sage installation. The message may identify the Sage 50 Accounts Data Service, Sage 50 Control Service, or Sage AutoUpdate Manager Service. The error does not automatically mean that your Windows account lacks administrator privileges; other installation or service problems may be responsible.

How do I fix Sage 50 Accounts Data Service failed to start Error 1920?

Check that the computer meets the system requirements for your Sage release. Then follow Sage’s Data Service Error 1920 procedure, which may involve checking the version-specific Control Service temporary folder, renaming specified service-related SQLite files, clearing temporary files, and reviewing permissions. Ask IT support to assist with advanced file or permission changes.

Why does Sage 50 Control Service fail to start?

The Control Service may fail because of antivirus interference, damaged service-related temporary files, missing or damaged .NET components, or Windows configuration problems. Check the relevant service status and follow the official troubleshooting procedure for your installed Sage version. Do not delete Control Service folders from another version’s installation.

How do I fix Sage 50 AutoUpdate Manager Service Error 1920?

Start by clearing the Windows temporary folder using Sage’s documented procedure and restarting the computer. If the error remains, check whether antivirus software is blocking the installation and whether the Sage.Central.AutoUpdateManager.Service.exe process remains active after a failed attempt. Follow the permissions guidance if the service still cannot start.

Can antivirus software cause Sage 50 Error 1920?

Yes. Sage documents antivirus interference as a possible cause of certain Control Service and AutoUpdate Manager startup failures. Some endpoint-protection products have also been associated with specific release-related installation problems. Check security notifications and follow the relevant Sage and antivirus-provider instructions rather than permanently disabling protection.

What should I do if Sage 50 Error 1920 continues after restarting Windows?

If restarting does not help, investigate the exact service named in the message. Review the relevant permissions, temporary files, antivirus settings, .NET requirements, and server configuration. If the service still fails, contact Sage support or your IT administrator with the error message, installed release, affected service name, and troubleshooting steps already completed.

Related Articles