Skip to main content
NetApp Knowledge Base

SnapCenter Plug-in for Microsoft Windows raises harmless errors in Windows Application Event log

Views:
817
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-In for Microsoft Windows (SCW) 4.3 or earlier

Issue

  • SCW reports a critical error similar to the following example in the Windows Application Event log.

Example 1:

Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist 
  at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
  at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
  at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Example 2:

Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist 
 at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
 at SnapDrive.Nsf.Common.PowerShell.PSHelper.RunCommand(Command command,
IEnumerable input)

Example 3:

Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable ""ErrorActionPreference"" or common parameter is set to Stop: 
===================================================================================
| This cmdlet must be directed to a data vserver.  You are currently connected    |
| to the cluster admin vserver.  See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing    |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP.         |
===================================================================================

   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at SnapDrive.Nsf.Common.PowerShell.PSHelper.RunCommand(Command command, IEnumerable input)

 

  • Outputs similar to the following example can be seen in the SCWDebug.log.

Example 1:

Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Verbose SDW PID=[<PID>] TID=[<TID>] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist
Verbose SDW PID=[<PID>] TID=[<TID>] No retry condition match found or max retry reached. Throwing error The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist
Verbose SDW PID=[<PID>] TID=[<TID>] --PSHelper::RunCommand
Error SDW PID=[<PID>] TID=[<TID>] Failed to get FCP target node name for StorageSystem: svm1.demo.netapp.com
 entry doesn't exist
Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageConnectionPool::CleanUpIfStale
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCacheHelper::GetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] ++TargetInfoCache::ShouldGetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCache::ShouldGetTargetInfo
Error SDW PID=[<PID>] TID=[<TID>] FCP target information is null/empty

Example 2:

Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist 
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at SnapDrive.Nsf.Common.PowerShell.PSHelper.RunCommand(Command command, IEnumerable input)

Verbose SDW PID=[<PID>] TID=[<TID>] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist 
Verbose SDW PID=[<PID>] TID=[<TID>] No retry condition match found or max retry reached. Throwing error The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist 
Verbose SDW PID=[<PID>] TID=[<TID>] --PSHelper::RunCommand
Error SDW PID=[<PID>] TID=[<TID>] Failed to get FCP target node name for StorageSystem: <STORAGESYSTEM>
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: entry doesn't exist
Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageConnectionPool::CleanUpIfStale
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCacheHelper::GetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] ++TargetInfoCache::ShouldGetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCache::ShouldGetTargetInfo
Error SDW PID=[<PID>] TID=[<TID>] FCP target information is null/empty
Error SDW PID=[<PID>] TID=[<TID>] iSCSI target information is null/empty

Example 3:

Verbose SDW PID=[<PID>] TID=[<TID>] Getting iSCSI target info
Verbose SDW PID=[<PID>] TID=[<TID>] ++PSHelper::RunCommand
Verbose SDW PID=[<PID>] TID=[<TID>] ++ConfigManager::GetConfigSettingMaxRetryFileExist
Verbose SDW PID=[<PID>] TID=[<TID>] --ConfigManager::GetConfigSettingMaxRetryFileExist
Verbose SDW PID=[<PID>] TID=[<TID>] ++ConfigManager::GetConfigSettingRetryInterval
Verbose SDW PID=[<PID>] TID=[<TID>] --ConfigManager::GetConfigSettingRetryInterval
Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 
===================================================================================
| This cmdlet must be directed to a data vserver.  You are currently connected    |
| to the cluster admin vserver.  See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing    |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP.         |
===================================================================================

   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at SnapDrive.Nsf.Common.PowerShell.PSHelper.RunCommand(Command command, IEnumerable input)

..

Verbose SDW PID=[<PID>] TID=[<TID>] --PSHelper::RunCommand
Verbose SDW PID=[<PID>] TID=[<TID>] Failed to get iSCSI target node name for StorageSystem: <STORAGESYSTEM>
 
===================================================================================
| This cmdlet must be directed to a data vserver.  You are currently connected    |
| to the cluster admin vserver.  See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing    |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP.         |
===================================================================================


Verbose SDW PID=[<PID>] TID=[<TID>] Getting FC target info
Verbose SDW PID=[<PID>] TID=[<TID>] ++PSHelper::RunCommand
Verbose SDW PID=[<PID>] TID=[<TID>] ++ConfigManager::GetConfigSettingMaxRetryFileExist
Verbose SDW PID=[<PID>] TID=[<TID>] --ConfigManager::GetConfigSettingMaxRetryFileExist
Verbose SDW PID=[<PID>] TID=[<TID>] ++ConfigManager::GetConfigSettingRetryInterval
Verbose SDW PID=[<PID>] TID=[<TID>] --ConfigManager::GetConfigSettingRetryInterval
Critical SDW PID=[<PID>] TID=[<TID>] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 
===================================================================================
| This cmdlet must be directed to a data vserver.  You are currently connected    |
| to the cluster admin vserver.  See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing    |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP.         |
===================================================================================

   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at SnapDrive.Nsf.Common.PowerShell.PSHelper.RunCommand(Command command, IEnumerable input)

..

Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageConnectionPool::CleanUpIfStale
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCacheHelper::GetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] ++TargetInfoCache::ShouldGetTargetInfo
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCache::ShouldGetTargetInfo
Error SDW PID=[<PID>] TID=[<TID>] FCP target information is null/empty
Error SDW PID=[<PID>] TID=[<TID>] iSCSI target information is null/empty
Verbose SDW PID=[<PID>] TID=[<TID>] --TargetInfoCache::AddTargetInfoForStorageSystem

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.