Tag Archives: Symantec

Veritas Backup Exec Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status.

Having experienced a number of intermittent failures related to 0xE000FED1 we looked into increasing the retires and timeouts and found that the following values resolved the issue.

Browse to or create the following registry structure HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Besc

Under Besc create the following DWORD values:

Create a 32bit DWORD with name “UseSnapshotEngineRetry” and value (decimal) 1

Create a 32bit DWORD with name “SnapshotEngineRetries” and value (decimal) 5

Create a 32bit DWORD with name “SnapshotEngineWaitTime” and value (decimal) 360000 (that is 6 minutes in milliseconds)

You can find further information on the registry settings in this Veritas article:

https://www.veritas.com/content/support/en_US/article.100015593.html

Volsnap.sys – Pre Service Pack 3 Revision History for Windows Server 2003 SP2 and Windows Small Business Server 2003 SP2 (SBS 2003)

Volsnap.sys – Pre Service Pack 3 Revision History for Windows Server 2003 SP2 and Windows Small Business Server 2003 SP2 (SBS 2003)

15-Jan-2010 – 5.2.3790.4650 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/979457 – Some snapshots are not mounted in Windows Server 2003 SP2 after computer restarts if there are many snapshots

13-Jan-2010 – 5.2.3790.4649 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/979407 – A node of a cluster may stop responding in Windows Server 2003 SP2

18-May-2009 – 5.2.3790.4516 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/967551 – Rollup update for the volsnap.sys driver in Windows Server 2003

23-Feb-2009 – 5.2.3790.4465 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/967327 – Shadow copies that you create in Windows Server 2008 cannot be detected in Windows Server 2003

31-Aug-2007 – 5.2.3790.4143 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/940349 – Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues

06-Aug-2007 – 5.2.3790.4127 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/940041 – Volume Shadow Copy Service snapshots may be unexpectedly deleted after you restart a Windows Server 2003-based computer

03-Aug-2007 – 5.2.3790.4126 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/940239 – VSS cannot create a volume snapshot even when VSS has sufficient memory space in Windows Server 2003

19-Jul-2007 – 5.2.3790.4120 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/940252 – The Volume Shadow Copy Service may leak private bytes and virtual memory when you use the service to take frequent snapshots in Windows Server 2003 or in Windows XP

23-May-2007 – 5.2.3790.4087 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/933653 – A memory leak occurs when an application performs a snapshot on a computer that is running Windows Server 2003

12-Feb-2007 – 5.2.3790.4021 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/931312 – Windows Server 2003 may not start when the Volume Shadow Copy Service is enabled

[RESOLVED] Your computer may stop responding when you run an application, Software Firewall or anti-virus package that uses the Windows Filtering Platform API

Your computer may stop responding when you run an application, Software Firewall or anti-virus package that uses the Windows Filtering Platform API

This issue affects the following operating systems:

  • Windows 7 – Service Pack 1
  • Windows Small Business Server 2011 – Service Pack 1
  • Windows SBS 2011 – Service Pack 1
  • Windows Server 2008 R2 – Service Pack 1
  • Windows Small Business Server 2008 – Service Pack 2
  • Windows SBS 2008 – Service Pack 2
  • Windows Server 2008 – Service Pack 2
  • Windows Vista – Service Pack 2

In this situation, the computer may perform slowly or stop responding and network activity may be affected.  You find that a system restart may resolve this issue in some instances.

This issue occurs because the FwpsStreamInjectAsync0 function causes the interrupt request level (IRQL) to leak.  You can resolve the issue by updating to the latest Netio.sys driver.  The download link can be found within Microsoft KB 2664888 http://support.microsoft.com/kb/2664888

 

Windows Filtering Platform (WFP) General Description

Windows Filtering Platform (WFP) is a set of API and system services that provide a platform for creating network filtering applications. The WFP API allows developers to write code that interacts with the packet processing that takes place at several layers in the networking stack of the operating system. Network data can be filtered and also modified before it reaches its destination.

By providing a simpler development platform, WFP is designed to replace  previous packet filtering technologies such as Transport Driver Interface (TDI)  filters, Network Driver Interface Specification (NDIS) filters, and Winsock Layered Service Providers (LSP). Starting in Windows Server 2008 and Windows Vista, the firewall hook and the filter hook drivers  are not available; applications that were using these drivers should use WFP instead.

With the WFP API, developers can implement firewalls, intrusion detection systems, antivirus programs, network monitoring tools, and parental controls. WFP integrates with and provides support for firewall features such as authenticated communication and dynamic firewall configuration based on applications’ use of sockets API (application-based policy). WFP also provides infrastructure for  IPsec policy management, change notifications, network diagnostics, and stateful filtering.

More info can be found here http://msdn.microsoft.com/en-us/library/windows/desktop/aa366510(v=vs.85).aspx

 

Windows 7, Windows Server 2008 R2 or SBS 2011 with Service Pack 1 – Randomly Stops Responding after you use the VSS Software Provider in Windows

If you are using the Volume Shadow Copy Service (VSS) software provider on a system running Windows 7 – Service Pack 1, Windows Server 2008 R2 – Service Pack 1 or Small Business Server 2011 – Service Pack 1 then you may find the computer randomly stops responding.

 

This occurs because volsnap.sys tries to obtain a lock again on a file even if it is already holding a lock.

A hotfix can be requested to resolve the issue using KB 2627052 http://support.microsoft.com/kb/2627052