CA Client Automation

 View Only
  • 1.  Patch Manager error connecting to DSM Server

    Posted Oct 15, 2021 11:33 AM
    Client Automation r14.5

    I can log into the Web Console and accept a patch. It fails to register the patch in the DSM.

    I see the following in the PMEngine.log:

    2021-10-15 06:37:22,190 [localhost-startStop-1] ERROR [com.ca.pmengine.infrastructure] - connect(): failed
    2021-10-15 06:37:22,205 [localhost-startStop-1] FATAL [com.ca.pmengine.eventmanager] - Error connecting to DSM Server. Reason: SME_SEC_NEED_CREDS The client must provide explicit credentials to complete authentication as unified logon is not available.
    2021-10-15 06:37:22,205 [localhost-startStop-1] FATAL [com.ca.pmengine.eventmanager] - Missing Resource ID:INF010

    I believe I have the configuration correct and I can verify the credentials. I will attach a screen capture of the Web Console.

    Has anyone experienced this issue before?

    ------------------------------
    Lindsay Estabrooks
    [JobTitle]
    [CompanyName]
    ------------------------------


  • 2.  RE: Patch Manager error connecting to DSM Server

    Broadcom Employee
    Posted Oct 18, 2021 07:03 AM

    Hi Lindsay,

     

    How are you doing?

     

    The only difference between your screen shot and my test system is that I do not have port 80 in the connection address.

     

    Try turning on tracing and then check the web services log to see if that error gives more details?

     

    Rgds,

    Steve.

     






  • 3.  RE: Patch Manager error connecting to DSM Server

    Posted Oct 19, 2021 02:43 AM
    Hi Steve,

    I am doing well. I hope the same for you.

    Where do I set the tracing on?

    Cheers,
    Lindsay

    ------------------------------
    Lindsay Estabrooks
    [JobTitle]
    [CompanyName]
    ------------------------------



  • 4.  RE: Patch Manager error connecting to DSM Server

    Broadcom Employee
    Posted Oct 19, 2021 04:55 AM

    Hi Lindsay,

     

    Yes, doing fine thanks.

     

    Tracing can be enabled with the command "cftrace -c set -l detail -s 20000 -ln 9"

     

    Rgds,

    Steve.

     






  • 5.  RE: Patch Manager error connecting to DSM Server

    Posted Oct 20, 2021 01:11 PM
    I have found the issue.

    I had previously disabled IPv6 on the network interface, but when I pinged the server by name it still used the IPv6 loopback address [::1].

    I re-enabled IPv6 on the network interface but also made a registry entry to prefer IPv4 over IPv6. Here is the registry entry for anyone interested:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
    "DisabledComponents"=dword:00000020
    
    ​


    ------------------------------
    Lindsay Estabrooks
    [JobTitle]
    [CompanyName]
    ------------------------------