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

    Question

  • 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!

    Friday, March 14, 2014 8:41 AM

Answers

All replies

  • Did you try executing remove-scomdisabledclassinstance command in OpsMgr Shell?

    To verify open your Discovered inventory and scope it to 2010 Lync Server, you will find the entity existing in the group. Then run the powershell command, and once it is completed check the discovered inventory again. hope it disappear.

    Regards,

    Saravanan

    Friday, March 14, 2014 10:18 AM
  • Hi Saravanan, thanks for your reply.

    The server doesn't appear discovered in "LS Server Role "of Lync 2010 MP, however It is correctly discovered in LS Server Role of Lync 2013.

    The value of the "source ID" is the name of the discovery, so for identify:

    get-scdiscovery | ? {$_.id -match "GUID_SOURCE_ID"} | select displayname

    The result is:

    DisplayName: LS Central Topology Discovery


    I have applied a disable override over this discovery for the agent affected.

    Regards, 


    Friday, March 14, 2014 10:35 AM
  • Not just LS Server Role. Does this server show up in any of the views within the Lync Server 2010 folder in your monitoring pane. Was the command executed?

    Friday, March 14, 2014 10:58 AM
  • Try adding the NETWORK SERVICE account to the following local groups on the Edge server:

    RTC Component Local

    RTC Local Administrators

    Then restart the System Center Management service.

    This fixed it for me. If you look at the membership of the equivalent local groups on a Lync Server 2013 Front End you'll see that these groups contain the NETWORK SERVICE account. Looks to be an oversight by MSFT.

    Also you can refer below link, Same issue here

    http://social.technet.microsoft.com/Forums/systemcenter/en-US/f164f5a4-8dab-4f28-8cef-5d83d98d78a7/lync-2013-mp-lync-application-discovery-issue-for-the-dmz-servers?forum=operationsmanagermgmtpacks


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

    Friday, March 14, 2014 2:20 PM
  • Hi Mai, thanks for your reply. 

    all things mentioned were in place already.


    Friday, March 14, 2014 2:35 PM
  • To configure Lync 2013 MP, You can refer below link

    http://www.oiboran.com/?p=2020

    And verify that you configure as above link


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"


    Friday, March 14, 2014 4:51 PM