Clarity Client Automation

OSIM with NLS SD agent - caf connection problems with following plugin installations

  • 1.  OSIM with NLS SD agent - caf connection problems with following plugin installations

    Posted 12-09-2019 04:34 AM
    14.0.3 Domain Manager fresh installation with OSIM.
    I have deleted the ENU SD agent packages from the SD library to enable the NLS agent for OSIM (as described in article 111683 "OSIM: How to switch between ENU and NLS variant of the SD Agent).
    OSIM installation of Windows 10 1903 german runs as expected and the NLS SD agent (german) is installed and shows up as "CA DSM Agent + Software Delivery plugin 14.0.3000.725" in the list of installed packages. PC is then rebooted to complete the AD domain registration.
    Now the NLS AM agent plugin " "CA DSM Agent + Asset Management plugin 14.0.3000.725" is delivered through SD to the PC.
    In DSM explorer the job doesn't finish.
    Looking at the PC as local administrator:
    the caf service is running (services control panel) and the AM agent plugin is installed, but "caf status" returns "failed to connect local caf service".
    Trace messages: "CreateMutex: Global\cafCLIrunning: (5) access denied"; "CreateOSMutex failed"; "can't connect pipe to caf service"

    After a reboot caf status is running fine and the AM installation job is marked as success.
    Now doing the installation of the RC plugin the same (error) behaviour can be seen.

    Doing the same OSIM installation with ENU packages only does not reveal any problems.
    Does anyone have seen similar problems with the use of the NLS agents - and found a solution ?
    Regards
    Claus