Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Historian
  • AVEVA Historian Tech Notes

TN - HIST - 25022302 Resolving VSS (Volume Shadow Copy Service) Errors in Windows Event Viewer

Last updated: May 18th, 2026

Description

  • Author: Zach Burns
  • Published: May 18th, 2026

Details:

Description

This article provides guidance on resolving Volume Shadow Copy Service (VSS) errors that may occur after a new installation of System Platform. 

Solution Details

You may encounter Event ID 8193 and Event ID 8213 in the Windows Event Viewer. These errors are typically caused by missing permissions and registry entries for the virtual service account NT SERVICE\InSQLConfiguration. The steps outlined below will help you correct the registry configuration and permissions to eliminate these errors.

Solution Steps:

The following errors are observed in windows event viewer on the Historian node:

Event Error 8193

Event Error 8213

The problem is present because the virtual service account NT SERVICE\InSQLConfiguration user registry is not present in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl

This user will also need to be present in the permission of the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Diag.

This issue can be resolved and these errors can be removed by adding a DWORD value for NT SERVICE\InSQLConfiguration and setting it to 1 under the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl Key

Additionally, grant the NT SERVICE\InSQLConfiguration account Full Control permissions on the registry key by right-clicking the key, selecting “permissions” and assigning “Full Control”

eventerrors shadowcopy
Give feedback about this article

Recommended articles

[ISS Support Case] Unable to launch Intouch after Windows Updates

Intouch 2017u2 Error when launching WV - Failed to open application Update installed was an Insider Preview for Windows 11 Update does not have a KB, not listed in Security Central Also found that Windows 11 not supported for program version - client advised OS updated on its own

Read More

[ISS Support Case] InTouch License Acquisition Failure

Client reached out due to receiving failure to acquire license when attempting to start WindowViewer.

Read More

[ISS Support Case] License Activation Failure

Client reached out due to failure to activate license after fresh license manager installation.

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2026 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand