Subscribe

OCPM failed powershell scripts

Hello everyone,

 

I'm running OCPM 4.0.1 together with SCOM 2012 R2 UR7 for Clustered DataONTAP monitoring and have been doing so for a while now. OCPM is set up according to the deployment manual and most things seems to be working fine except a couple of ever returning errors of failed Powershell- scripts. Any ideas on how to solve these? Thank you in advance!

 

StorageEfficiency.ps1

System.Management.Automation.MethodInvocationException: Exception calling "InvokeMethod" with "6" argument(s): "Execution of OC.Cluster.OM.Server.Monitoring.StorageEfficiency.GetStorageEfficiency method resulted in exception being thrown. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> NetApp.Ontapi.ErrnoException+EAPIERROR: No cards in the system
at NetApp.Ontapi.NaApi`1.Invoke(INaServer server)
at OC.Common.ClusterLibrary.ZAPI.Flash.FlashDevice.GetFlashDevices(NcController vserverConnection, FlashDeviceInfo queryAttributes, FlashDeviceInfo desiredAttributes)
at OC.Cluster.OM.Server.Monitoring.StorageEfficiency.getAdminVserverStorageEfficiency(ClusterAdminVserver adminVserver)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.InvokeMethod(Assembly assembly, String typeName, Object[] contructorParameters, String methodName, Object[] parameters)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.AppDomainCallback()"At line:64 char:5
+ $result = [OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker]::InvokeMethod($a ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo)
at CallSite.Target(Closure , CallSite , RuntimeType , AppDomain , String , String , Array , String , Array )
at System.Dynamic.UpdateDelegates.UpdateAndExecute7[T0,T1,T2,T3,T4,T5,T6,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
at System.Management.Automation.Interpreter.DynamicInstruction`8.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Script Name: StorageEfficiency.ps1
One or more workflows were affected by this.
Workflow name: DataONTAP.Cluster.Monitoring.StorageEfficiency.Rule

 

Discovery.ps1

System.Management.Automation.MethodInvocationException: Exception calling "InvokeMethod" with "6" argument(s): "Execution of OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage method resulted in exception being thrown. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception:
The following error(s) were encountered while performing discovery:
Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipTargetException: Det relationsmål som angetts för identifieringsdataobjektet är inte giltig.
ID för relationsmål: ce3bebef-c861-35a0-e78b-e1f1017e2cce
Regel-ID: bd92d3b9-7f88-469d-af1c-f87ce05c2723
Instans:
<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{138c0a98-23f2-e49a-69aa-b24fecc14551}" SourceTypeId="{a7539302-3b3e-37d0-7497-614f50e0b5f3}" TargetTypeId="{e95c2fd7-0b62-7399-e337-66808f592eb3}"><Settings /><SourceRole><Settings><Setting><Name>ed5c5f5b-13eb-9426-2d64-3f440729d0b7</Name><Value>e1a</Value></Setting><Setting><Name>a97314bb-cde3-5370-20a8-7bb5824011cd</Name><Value>9f917a79-5664-11e3-af0c-95bb2f2d7e11</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>f4a2981a-259c-bd73-79db-fdd41f5df9c7</Name><Value>068fe991-f4e8-11e4-8048-00a0984f7596</Value></Setting></Settings></TargetRole></RelationshipInstance>
at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
at Microsoft.EnterpriseManagement.Common.Internal.ConnectorFrameworkConfigurationServiceProxy.ProcessDiscoveryDataWithBinarySupport(Int32 operation, Guid discoverySourceId, IList`1 entityInstances, IList`1 relationshipInstances, IDictionary`2 streams, Boolean useOptimisticConcurrency)
at Microsoft.EnterpriseManagement.ConnectorFramework.SnapshotDiscoveryData.Commit(EnterpriseManagementGroup managementGroup, Guid discoverySourceId, Boolean useOptimisticConcurrency)
at Microsoft.EnterpriseManagement.ConnectorFramework.SnapshotDiscoveryData.Overwrite(EnterpriseManagementConnector monitoringConnector)
at OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage(Boolean startVirtualizationDiscoveryTask)

at OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage(Boolean startVirtualizationDiscoveryTask)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.InvokeMethod(Assembly assembly, String typeName, Object[] contructorParameters, String methodName, Object[] parameters)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.AppDomainCallback()"At line:64 char:5
+ $result = [OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker]::InvokeMethod($a ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo)
at CallSite.Target(Closure , CallSite , RuntimeType , AppDomain , String , String , Array , String , Array )
at System.Dynamic.UpdateDelegates.UpdateAndExecute7[T0,T1,T2,T3,T4,T5,T6,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
at System.Management.Automation.Interpreter.DynamicInstruction`8.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Script Name: Discovery.ps1
One or more workflows were affected by this.

Workflow name: DataONTAP.Cluster.Discovery.Rule
Instance name: Clustered Data ONTAP: Management Server Resource Pool

 

Monitoring.ps1

System.Management.Automation.MethodInvocationException: Exception calling "InvokeMethod" with "6" argument(s): "Execution of OC.Cluster.OM.Server.Monitoring.StorageMonitoring.InsertNodeVserverPerformanceStatistics method resulted in exception being thrown. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> NetApp.Ontapi.ErrnoException+EAPIERROR: For system object, no instances were found to match the given query.
at NetApp.Ontapi.NaApi`1.Invoke(INaServer server)
at OC.Common.ClusterLibrary.ZAPI.Performance.Performance.GetPerformanceInstanceData(NcController controller, String[] counters, String filterData, String[] instanceUUIDs, String[] instances, String objectName, String privilegeLevel)
at OC.Cluster.OM.Server.Monitoring.StorageMonitoring.InsertNodeVserverPerformanceStatistics(String nodeVserverUuid)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.InvokeMethod(Assembly assembly, String typeName, Object[] contructorParameters, String methodName, Object[] parameters)
at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.AppDomainCallback()"At line:64 char:5
+ $result = [OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker]::InvokeMethod($a ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo)
at CallSite.Target(Closure , CallSite , RuntimeType , AppDomain , String , String , Array , String , Array )
at System.Dynamic.UpdateDelegates.UpdateAndExecute7[T0,T1,T2,T3,T4,T5,T6,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
at System.Management.Automation.Interpreter.DynamicInstruction`8.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Script name: Monitoring.ps1
One or more workflows were affected by this.
Workflow name: DataONTAP.Cluster.Monitoring.InsertNodeVserverPerformanceStatistics.Rule

 

Re: OCPM failed powershell scripts

Re: OCPM failed powershell scripts

Hello mcgue,

 

Thank you for the reply! I checked the KB and took the recommended steps. I already had a local windows profile for my action account but figured it might be worth trying anyway. Restarted the services and booted up the console. Sadly, though, I'm still getting an exception thrown at me when I try to run a manual discover using the default action account. Double checked the account/credentials under "Manage Storage System" and that checks out to be ok. Digged a bit deeper and discovered the following errors when running a manual discovery. These all appear within seconds in the Operations Manager event log.

 

First;

Data Access Layer rejected retry on SqlError:

Request: ProcessRelationshipStagingForUpsert -- (TransactionId=3486828), (DiscoverySourceId=bd92d3b9-7f88-469d-af1c-f87ce05c2723), (TimeGenerated=2015-09-08 13:10:13), (PerformHealthServiceCheck=False), (HealthServiceId=), (RETURN_VALUE=1)

Class: 16

Number: 777980003

Message: The specified relationship doesn't have a valid target.

 

Second;

An exception was thrown while processing ProcessDiscoveryDataWithBinarySupport for session ID uuid:2873cb56-dbd0-463d-806c-1f7cd3fc8567;id=178.

Exception message: Det relationsmål som angetts för identifieringsdataobjektet är inte giltig.

ID för relationsmål: ce3bebef-c861-35a0-e78b-e1f1017e2cce

Regel-ID: bd92d3b9-7f88-469d-af1c-f87ce05c2723

Instans:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{138c0a98-23f2-e49a-69aa-b24fecc14551}" SourceTypeId="{a7539302-3b3e-37d0-7497-614f50e0b5f3}" TargetTypeId="{e95c2fd7-0b62-7399-e337-66808f592eb3}"><Settings /><SourceRole><Settings><Setting><Name>ed5c5f5b-13eb-9426-2d64-3f440729d0b7</Name><Value>e1a</Value></Setting><Setting><Name>a97314bb-cde3-5370-20a8-7bb5824011cd</Name><Value>9f917a79-5664-11e3-af0c-95bb2f2d7e11</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>f4a2981a-259c-bd73-79db-fdd41f5df9c7</Name><Value>068fe991-f4e8-11e4-8048-00a0984f7596</Value></Setting></Settings></TargetRole></RelationshipInstance>

Full Exception: Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipTargetException: The relationship target specified in the discovery data item is not valid.

Relationship target ID: ce3bebef-c861-35a0-e78b-e1f1017e2cce

Rule ID: bd92d3b9-7f88-469d-af1c-f87ce05c2723

Instans:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{138c0a98-23f2-e49a-69aa-b24fecc14551}" SourceTypeId="{a7539302-3b3e-37d0-7497-614f50e0b5f3}" TargetTypeId="{e95c2fd7-0b62-7399-e337-66808f592eb3}"><Settings /><SourceRole><Settings><Setting><Name>ed5c5f5b-13eb-9426-2d64-3f440729d0b7</Name><Value>e1a</Value></Setting><Setting><Name>a97314bb-cde3-5370-20a8-7bb5824011cd</Name><Value>9f917a79-5664-11e3-af0c-95bb2f2d7e11</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>f4a2981a-259c-bd73-79db-fdd41f5df9c7</Name><Value>068fe991-f4e8-11e4-8048-00a0984f7596</Value></Setting></Settings></TargetRole></RelationshipInstance>

at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkUpsertRelationshipInstances(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)

at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkSnapshot(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)

at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)

at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryAuthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext, WindowsIdentity identity)

at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageSnapshotProcessingHandler.Process()

at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)

at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithBinarySupport(DatabaseConnection dbconnection, Int32 operation, Guid discoverySourceId, IList`1 sdkEntityInstances, IList`1 sdkRelationshipInstances, IDictionary`2 streams, Boolean useOptimisicConcurrency, IContext context)

at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryDataWithBinarySupport(DatabaseConnection dbconnection, Int32 operation, Guid discoverySourceId, IList`1 entityInstances, IList`1 relationshipInstances, IDictionary`2 streams, Boolean useOptimisticConcurrency)

at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryDataWithBinarySupport(Int32 operation, Guid discoverySourceId, IList`1 entityInstances, IList`1 relationshipInstances, IDictionary`2 streams, Boolean useOptimisticConcurrency)

 

 

Third and final;

Discovery.ps1 : Clustered Data ONTAP discovery failed.

Exception calling "InvokeMethod" with "6" argument(s): "Execution of OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage method resulted in exception being thrown. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception:

The following error(s) were encountered while performing discovery:

Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipTargetException: The relationship target specified in the discovery data item is not valid.

Relationship target ID: ce3bebef-c861-35a0-e78b-e1f1017e2cce

Rule ID: bd92d3b9-7f88-469d-af1c-f87ce05c2723

Instans:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{138c0a98-23f2-e49a-69aa-b24fecc14551}" SourceTypeId="{a7539302-3b3e-37d0-7497-614f50e0b5f3}" TargetTypeId="{e95c2fd7-0b62-7399-e337-66808f592eb3}"><Settings /><SourceRole><Settings><Setting><Name>ed5c5f5b-13eb-9426-2d64-3f440729d0b7</Name><Value>e1a</Value></Setting><Setting><Name>a97314bb-cde3-5370-20a8-7bb5824011cd</Name><Value>9f917a79-5664-11e3-af0c-95bb2f2d7e11</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>f4a2981a-259c-bd73-79db-fdd41f5df9c7</Name><Value>068fe991-f4e8-11e4-8048-00a0984f7596</Value></Setting></Settings></TargetRole></RelationshipInstance>

at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)

at Microsoft.EnterpriseManagement.Common.Internal.ConnectorFrameworkConfigurationServiceProxy.ProcessDiscoveryDataWithBinarySupport(Int32 operation, Guid discoverySourceId, IList`1 entityInstances, IList`1 relationshipInstances, IDictionary`2 streams, Boolean useOptimisticConcurrency)

at Microsoft.EnterpriseManagement.ConnectorFramework.SnapshotDiscoveryData.Commit(EnterpriseManagementGroup managementGroup, Guid discoverySourceId, Boolean useOptimisticConcurrency)

at Microsoft.EnterpriseManagement.ConnectorFramework.SnapshotDiscoveryData.Overwrite(EnterpriseManagementConnector monitoringConnector)

at OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage(Boolean startVirtualizationDiscoveryTask)

at OC.Cluster.OM.Server.Discovery.StorageDiscovery.DiscoverStorage(Boolean startVirtualizationDiscoveryTask)

--- End of inner exception stack trace ---

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.InvokeMethod(Assembly assembly, String typeName, Object[] contructorParameters, String methodName, Object[] parameters)

at OC.Cluster.OM.AppDomainInvoker.AppDomainInvoker.AppDomainCallback()"

 

 

I underlined some parts that I suspect could be the source of the problem. Any ideas?

 

Thanks!

 

 

Re: OCPM failed powershell scripts

Hello,

 

I have the same kind of problem and I'm looking for an answer, but the link you posted is broken.

Do you have a working one ?

 

greetings Matt