none
SCOM Linux discovery failed with "The user name or password is incorrect" error RRS feed

  • Question

  • Hi every one .

    In our test environment when I want to discover a new linux computer system , discovery process fails with this error message :

    Unexpected DiscoveryResult.ErrorData type.  Please file bug report.
    ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.TaskInvocationException
    Task invocation failed with error code 1326. Error message was: The user name or password is incorrect.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents)

    But I m sure that this username and password is correct and I can logon to this computer with this credential.

    how do I find root cause of this issue ?


    Tuesday, February 10, 2015 12:19 PM

All replies

  • To install the agent via the Discovery Wizard it needs root access to the UNIX/Linux system. You can either use the root account or give a non-root user root access to the required commands via SUDO. See this link for details.

    You can also enable TRACE logging which might help point to the problem. See this link for details.

    Regards,

    -Steve


    Tuesday, February 10, 2015 1:41 PM
    Moderator
  • Thanks for your quick reply. Yes Of course . We are discovering with root user .
    Tuesday, February 10, 2015 2:30 PM
  • I have been enabled logging before doscovery process .

    in temp directory :

    0: 02/10/15 20:03:22 : Enter SCXNameResolverProbe constructor
    0: 02/10/15 20:03:22 : Leave SCXNameResolverProbe constructor
    1: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoInit
    1: 02/10/15 20:03:22 : XML_INIT_CALL
    1: 02/10/15 20:03:22 : Check WSAStartup
    1: 02/10/15 20:03:22 : Exit SCXNameResolverProbe::DoInit
    2: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoProcess()
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess passed initial arguments checking
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess input: 192.168.7.62
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess - Input is an IP-address
    3: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::GetName(): 192.168.7.62
    3: 02/10/15 20:03:22 : Resolve IPv4 address to host name
    3: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::GetName(): SUSE11
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns name: SUSE11
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns ip: 192.168.7.62
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errorcode: 0
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errortext: 
    2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns xml: <NetworkName>SUSE11</NetworkName><IPAddress>192.168.7.62</IPAddress><StatusCode>0</StatusCode><StatusMessage></StatusMessage>
    2: 02/10/15 20:03:22 :  Enter initDataHolder
    2: 02/10/15 20:03:22 : Enter initDataType
    2: 02/10/15 20:03:22 : initDataType initializing output datatype
    2: 02/10/15 20:03:22 : Leave initDataType
    2: 02/10/15 20:03:22 : Leave initDataHolder
    2: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::DoProcess
    4: 02/10/15 20:03:22 : Enter SCXNameResolverProbe destructor
    4: 02/10/15 20:03:22 : SCXNameResolverProbe destructor - FreeLibrary failed: 0
    4: 02/10/15 20:03:22 : Leave SCXNameResolverProbe destructor

    with debug viewer I have this message after discovery :

    [7448] A management object with display name SUSE11 could not be found.

    Tuesday, February 10, 2015 5:06 PM
  • From the SCOM server does the system SUSE11 resolve to IP address 192.168.7.62 [nslookup SUSE11]?

    -Steve

    Wednesday, February 11, 2015 5:44 PM
    Moderator
  • yes I have two HPUX server in this environment  and they have same problem too.

    every 3 servers nslookup are correct .

    I understand from tmp log that scom can resolve host name without any problem .

    I think there is a mismatched item in the debug viewer message .

    Isn't it ?

    Another Interesting log , which is not generated on the linux host /var/log/message 

    There is no line for ssh request from scom server when discovery return incorrect username and password .

    I this username and password are not problem .

     




    • Edited by MAYAHOO Saturday, February 14, 2015 9:08 AM
    Saturday, February 14, 2015 9:01 AM
  • Are you able to Discover any UNIX/Linux agents with this test environment? Have you updated to the latest MP's/agents?

    http://www.microsoft.com/en-us/download/details.aspx?id=29696

    Regards,

    -Steve

    Saturday, February 14, 2015 3:15 PM
    Moderator
  • Hi Mayahoo,

    Please advise if you have found the solution, even i am receiving error in SCOM 2019 when trying to discover Redhat Linux servers.

    Regards,

    Kiran Kumar Reddy

    Thursday, August 8, 2019 7:33 AM