Quantcast
Channel: Operations Manager - General forum
Viewing all articles
Browse latest Browse all 11941

Alert "An internal exception has occurred during discovery." related with Lync

$
0
0

Greetings All,

I'm facing this alert in one Lync 2013 agent. The problem is the SCOM agent is trying to execute a Lync 2010 PowerShell script in folder “'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync'” but this server is Lync 2013 so this folder does not exist, due to this error is generated the alert.

 I have recreated the SCOM health state folder in order to force all discoveries process, but the problem continues after. 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Log Name:      Operations Manager
Source:        Health Service Script
Date:          3/13/2014 1:47:48 PM
Event ID:      223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MYSERVER.MYDOMAIN.LOCAL
Description:
DiscoverCluster.ps1 : 
--------------------------------------------------------------------------------
-Script Name:      Lync Server MP Central Topology Discovery
-Run as account:   nt authority\network service
-Execution Policy: Bypass
--------------------------------------------------------------------------------
Value of Source Id is {333B2339-35AA-8115-0B0D-639F319A6333}.
Value of ManagedEntity Id is {4B127CAD-36D6-FCAB-507F-03FF1CF5555}.
Value of Target Computer is MYSERVER.MYDOMAIN.LOCAL.
Failed to load Lync Server Module. Error: The specified module 'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync' was not loaded because no valid module file was found in any module directory..
An exception occured during discovery script, Exception : System.Management.Automation.CommandNotFoundException: The term 'Get-CsManagementStoreReplicationStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame).
--------------------------------------------------------------------------------

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Health Service Script" />
    <EventID Qualifiers="0">223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-13T12:47:48.000000000Z" />
    <EventRecordID>130617</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>MYSERVER.MYDOMAIN.LOCAL</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DiscoverCluster.ps1</Data>
    <Data>

--------------------------------------------------------------------------------
-Script Name:      Lync Server MP Central Topology Discovery
-Run as account:   nt authority\network service
-Execution Policy: Bypass
--------------------------------------------------------------------------------
Value of Source Id is {88BB2339-35AA-8115-0B0D-639F31999999}.
Value of ManagedEntity Id is {4B127CAD-36D6-FCAB-507F-77777777}.
Value of Target Computer is MYSERVER.MYDOMAIN.LOCAL.
Failed to load Lync Server Module. Error: The specified module 'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync' was not loaded because no valid module file was found in any module directory..
An exception occured during discovery script, Exception : System.Management.Automation.CommandNotFoundException: The term 'Get-CsManagementStoreReplicationStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame).
--------------------------------------------------------------------------------
</Data>
  </EventData>
</Event>

Thanks!


Viewing all articles
Browse latest Browse all 11941

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>