How to Troubleshoot Sage Payroll Runtime Error 372

Sage Payroll Runtime Error 372 can prevent the payroll application from opening or interrupt tasks that depend on its reporting and printing components. In Sage Pastel Payroll, the error may appear with a message such as “Failed to load control ‘VSPrinter’ from VSView6.ocx.” The message may also warn that the control’s version is outdated or that the application must use the version supplied with the software.

This error can be frustrating because restarting the computer or opening the program again may not correct it. The underlying issue can involve a missing, damaged, incorrectly registered, or incompatible program component. It may also appear after a software update, an incomplete installation, a change to the Windows environment, or a problem affecting a particular workstation or remote desktop session.

The correct troubleshooting method depends on the exact message and when the error occurs. If Sage Pastel Payroll fails immediately at startup, focus first on the control-loading error and installation integrity. If the application opens but fails when generating reports, investigate the reporting components and determine whether the issue is limited to a particular operation.

What Is Sage Payroll Runtime Error 372?

Runtime Error 372 is a Windows application error associated with loading a control that the program expects to use. In Sage Pastel Payroll, a common version of this error refers to the VSPrinter control and the VSView6.ocx component. An OCX file is a type of Windows component that can provide functionality to an application. Older Windows desktop programs may rely on such components for tasks such as displaying or printing reports. If a required component cannot be loaded in the expected form, the application may stop with a runtime error. The message can take different forms, including:

• Run-time error 372 when opening Sage Payroll
• Failed to load control VSPrinter from VSView6.ocx
• Sage Pastel Payroll control loading error
• A warning that the VSView6.ocx version may be outdated
• Sage Payroll error when opening reports or printing payroll output

The exact wording matters. Runtime Error 372 does not always indicate the same missing file across every application. The troubleshooting steps in this article focus on Sage Pastel Payroll errors that reference VSView6.ocx, VSPrinter, or related reporting controls.

Important distinction: Sage products have different installation structures. The guidance for Sage Pastel Payroll in this article should not automatically be applied to Sage Payroll products in other regions or to cloud-based payroll services.

Common Causes of Sage Payroll Error 372

1. Missing or Damaged VSView6.ocx Component:

The most direct cause is a problem with the component named in the error message. The file may be missing, damaged, or unavailable where Sage expects to find it. This can happen if an installation or update did not complete correctly, if a repair process did not restore the required files, or if a component was removed or quarantined by another process.

2. VSPrinter Control Is Not Registered Correctly:

A component may exist on the computer but still fail to load if its registration information is missing, incorrect, or associated with an incompatible version. Registering an OCX file can help when the file is valid and the registration is the actual problem. However, registration cannot repair a damaged file or make an incompatible version suitable for the application.

3. Incomplete Sage Payroll Installation or Update:

Runtime Error 372 may appear after installing a software update or upgrading to a newer payroll release. If the installation leaves a required control unavailable or creates a mismatch between application files, the program may fail during startup or report generation. An update that appears to finish successfully does not necessarily prove that every required component is functioning correctly.

4. Incorrect Component Version:

The error message may state that the version of VSView6.ocx is outdated. This can indicate that Sage is loading a component that does not match the version supplied with the installed application. Copying an OCX file from another computer is not a reliable first response. Different Sage releases may require different components, and replacing one file with another version can create additional compatibility problems.

5. Windows or Workstation Configuration Differences:

The error may affect one computer or one Windows user account while other users can open payroll normally. Possible differences include component registration, local permissions, installation state, or the environment used to launch the application. In remote desktop or terminal-server environments, a problem affecting one user session does not necessarily mean the entire payroll installation is damaged.

6. Corrupted Reporting Components:

If payroll opens successfully but the error occurs when generating reports, the issue may be related to the reporting or printing components rather than the entire application startup process. Related components such as VSView and VSPrinter may be involved in the application’s report-generation workflow. The exact component named in the error should guide the investigation.

7. Incomplete Repair or Reinstallation:

Reinstalling a payroll update alone may not restore every required program component. A repair or full installation may be necessary, depending on the specific Sage Pastel Payroll version and the nature of the damage. Before performing these operations, protect the payroll data and confirm the appropriate installation package and procedure for the installed release.

How to Fix Sage Payroll Runtime Error 372

Follow the steps in order, beginning with the least disruptive checks. If you use Sage Pastel Payroll to process live payroll, verify that company data and backups are protected before changing program files or uninstalling components.

Step 1: Record the Exact Error Message

Start by identifying the component Sage is unable to load.

1. Open Sage Payroll and allow the error message to appear.
2. Record the complete message, including the control name and OCX filename.
3. Note whether the error appears immediately at startup, during login, when opening a report, or while printing.
4. Record the installed Sage Pastel Payroll version and update level.
5. Determine whether the error affects every user or only one computer or Windows account.

Pay particular attention to references to VSPrinter, VSView6.ocx, VSView, or VSPrint. The results help determine the next step:

• Error occurs immediately at startup: Focus on component availability, registration, and installation integrity.
• Error occurs only when opening a report: Investigate the reporting controls and related program components.
• Error began after an update: Check whether the installed update and full application installation are consistent.
• Only one workstation is affected: Compare that workstation with a computer where payroll works.
• The error names a different component: Do not assume that the VSView6.ocx procedure will solve it. Troubleshoot the component actually identified in the message.

This initial check reduces the risk of changing unrelated Windows files.

Step 2: Restart Windows and Close Other Sage Sessions

A restart is not a complete fix for a damaged control, but it can help rule out a temporary application or session problem.

1. Close Sage Payroll and any related Sage applications.
2. Confirm that other users are not actively processing payroll on the same computer or server before restarting shared services or the server.
3. Restart the affected workstation if appropriate.
4. Sign in using the usual Windows account.
5. Open Sage Payroll and check whether Runtime Error 372 appears again.

If the error returns immediately, continue to the component checks rather than repeatedly restarting the computer. For shared systems, do not restart a terminal server or interrupt other users’ sessions without following your organization’s procedures.

Step 3: Check Whether VSView6.ocx Exists

Before registering or replacing a component, verify whether the file is present.

1. Close Sage Payroll.
2. Open File Explorer.
3. Search the local computer for VSView6.ocx.
4. If the error references VSPrinter, note any related VSView or VSPrint files found in the Sage installation or Windows folders.
5. Record the file location and, where possible, its version information.
6. Compare the location with the installation and troubleshooting guidance for your specific Sage Pastel Payroll release.

Do not assume that the file must be in the same location on every computer. The correct location can depend on the installed version and Windows configuration.

• If the file is missing: Do not download an OCX file from an unofficial website or copy one from an unknown computer. Obtain the required component through the appropriate Sage installation, repair, or support process.
• If the file exists: Continue by checking whether it is registered correctly and whether its version is compatible with the installed payroll application.

Step 4: Register VSView6.ocx if the File Is Valid

In some Sage Pastel Payroll environments, registering the existing VSView6.ocx component can resolve a control-loading error. Sage Community Hub discussions have documented the following registration command for installations where the component is located in the 32-bit system component directory. Use this step only after confirming that the file exists at the specified path and is the correct version for your installation.

1. Close Sage Payroll.
2. Open the Windows Start menu.
3. Search for Command Prompt.
4. Right-click Command Prompt and choose Run as administrator.
5. If your confirmed component path is C:\Windows\SysWOW64\VSView6.ocx, enter the following command:
   regsvr32 C:\Windows\SysWOW64\VSView6.ocx
6. Press Enter.
7. Review the registration message returned by Windows.
8. Close Command Prompt and reopen Sage Payroll.

The SysWOW64 directory is commonly used for 32-bit components on 64-bit Windows. The command above is not universal: if the OCX file is stored elsewhere, or the application uses a different component, do not run the command with an assumed path.

If Windows reports that the module cannot be found, verify the path and the component’s dependencies. If the registration fails because the module is invalid or incompatible, do not keep repeating the command. Registration will not repair a corrupted OCX file or resolve a version mismatch. If the component is missing or invalid, proceed to the repair or installation steps.

Step 5: Check the Error Message After Registration

After registering the component, reopen Sage Payroll and test the operation that originally failed. If payroll opens normally, try opening a report and, where appropriate, previewing or printing it. Confirm that the original error no longer appears. If the error persists, note whether the message has changed. For example, a different missing control or a new automation error may indicate that more than one component needs attention.

A successful registration message only confirms that Windows accepted the registration operation. It does not prove that Sage Payroll has every component it needs or that the registered version is the correct one. If Runtime Error 372 continues, avoid registering unrelated OCX files at random. Proceed to the installation-integrity checks.

Step 6: Check for a Sage Payroll Update or Installation Problem

If the error started after an update or software change, verify that the installed payroll release is complete and appropriate for the existing installation.

1. Open Windows Settings or Control Panel and navigate to the installed applications list.
2. Locate the Sage Pastel Payroll application and its associated update entries.
3. Record the displayed version and update information.
4. Compare those details with the version intended to be installed.
5. Check whether the update completed without interruption.
6. Obtain the correct installation package through the authorized Sage download or support process for your product and region.

Do not install a newer update over an older release simply because the error appeared after an update. Confirm the supported upgrade path and the correct full-installation package first. If you are using a shared installation, verify whether the application is installed locally, on a server, or through a remote desktop environment. The repair procedure may differ depending on the deployment.

Step 7: Repair the Sage Installation Where Supported

A repair may restore missing or damaged program components without requiring you to manually replace individual files. The exact repair option and behavior depend on the Sage Pastel Payroll version.

1. Close payroll on the affected computer.
2. Confirm that a recent, verified payroll data backup exists.
3. Confirm that the correct installation files are available.
4. Use the repair procedure supported by your installed Sage release.
5. Follow the installer prompts and allow the operation to complete.
6. Restart Windows if requested.
7. Open Sage Payroll and test startup and reporting.

If the installer does not offer a repair option, do not improvise by deleting program files or removing folders from Windows. Use the installation guidance for your version or consult Sage support.

For Sage Pastel Accounting and Payroll installations that share related components, changes to the accounting installation may affect payroll. Do not repair or remove the accounting application as a first step unless the relevant instructions confirm that it is required.

Step 8: Reinstall Sage Pastel Payroll if the Error Persists

Sage’s published guidance for the specific “Error 372 – Failed to load control VSPrinter from VSView6.ocx” issue identifies uninstalling the existing Pastel Payroll application and its associated update entry, then reinstalling the full Payroll installation, as a resolution.

This is a more disruptive procedure than checking or registering an existing component. Use it when the earlier checks have not resolved the error or when the installation is confirmed to be incomplete or damaged. Before starting:

• Verify that payroll data is backed up and recoverable.
• Confirm that you have the correct full installation package and any required update files.
• Record the installed release and relevant configuration details.
• Confirm how the company data and any shared folders are maintained.
• Ensure that no one is actively using payroll on the affected installation.

Then follow the uninstall and reinstall procedure appropriate to the installed version:

1. Close Sage Pastel Payroll.
2. Open Programs and Features or the applicable Windows installed-apps screen.
3. Locate the Sage Pastel Payroll application.
4. Follow the supported procedure to uninstall the application.
5. If a separate Pastel Payroll update entry is listed and the official instructions for your release require its removal, uninstall that entry as directed.
6. Run the correct full Payroll installation package.
7. Apply the required update level using the supported installation sequence.
8. Launch Sage Payroll and verify that it opens without Runtime Error 372.
9. Check that the correct company data is available before processing payroll.

Do not delete company data folders as part of an ordinary program reinstall. A reinstall should restore the application components, while company data must be preserved and handled according to the product’s documented procedure. If the application is hosted on a server or used through remote desktop, coordinate the work with the person responsible for the installation. An uninstall or reinstall on a shared system can affect other users.

Step 9: Troubleshoot Sage Payroll Error 372 in a Remote Desktop Environment

If the error appears only when one employee signs in through Remote Desktop Services, the issue may be specific to that session or user environment.

1. Confirm whether another authorized user can open Sage Payroll on the same host.
2. Determine whether the affected user receives the same error on another approved workstation or session.
3. Compare the application version and available components across the relevant environments.
4. Check the exact OCX path and registration state where the application runs.
5. Confirm that the affected user has the required permissions to access the application and its components.
6. Avoid making server-wide changes until the scope of the problem is understood.

If other users can open payroll normally, a full reinstall may not be the first step. The cause could be limited to a particular session or user environment. If all users on the server encounter the same error, investigate the shared installation and component state. Coordinate any repair or reinstall with all affected users.

Prevention: Reduce the Risk of Sage Payroll Runtime Errors

A few maintenance practices can help prevent component-loading problems from interrupting payroll operations.

1. Use the correct update package. Confirm that an update applies to the installed payroll release and follow the documented installation sequence.
2. Avoid interrupting installations. Allow software updates and repairs to finish before reopening payroll.
3. Keep reliable backups. Maintain verified payroll data backups before repairs, upgrades, or reinstalls.
4. Avoid unverified OCX replacements. Obtain required program components from authorized installation media or Sage support.
5. Document the installed version. Record the payroll release and update level so that future repairs use compatible files.
6. Test reports after maintenance. After an update or repair, open payroll and test relevant reports before normal processing.
7. Check shared environments carefully. Coordinate changes on terminal servers and other shared installations to prevent disruptions.
8. Record recurring errors. Save the exact message and the conditions that trigger it, especially when only one user or workstation is affected.
9. Use supported repair procedures. Avoid deleting program folders or changing Windows component registrations without a verified reason.

These practices help keep payroll installations consistent and make future troubleshooting more straightforward.

Conclusion

Sage Payroll Runtime Error 372 commonly indicates that the application cannot load a required control. In Sage Pastel Payroll, the error may specifically identify VSPrinter and VSView6.ocx. The cause may be a missing or damaged component, incorrect registration, a version mismatch, or an incomplete installation.

Start by recording the full error message, checking whether the component exists, and confirming when the failure occurs. If the correct file is present and the issue is related to registration, registering that component may help. If the installation is incomplete or damaged, use the supported repair process or reinstall the full Sage Pastel Payroll application after protecting your company data. If the error continues after reinstallation, compare the component version, installation state, and affected user environment before repeating the same steps. Following a controlled troubleshooting sequence can help restore payroll access while reducing the risk of unnecessary changes to the application or company data.

FAQs of Sage Payroll Runtime Error 372: