AutoSys Workload Automation

 View Only
Expand all | Collapse all

The local security is bypassed error

  • 1.  The local security is bypassed error

    Posted Nov 11, 2019 05:57 PM

    I'm trying to open an app through a Windows job in CA Workload Automation Desktop Client R12 I have tried this variations, I tried executing a Bat file a powershell file and giving the location of the exe file directly in CAWA but with no luck
    When I run any job I get this log 

    Mon Nov 11 16:33:24 2019 CAWA_I_20005 AFM: 20191111 16332278+0600 MXVADM_MX02689 JavaAgent#tcpip@CENTRAL_MANAGER 1313262448_HEBER_BAT/01_PRUEBA_RUBEN.37/MAIN RUN . Data(Command="D:\Prueba.bat") TargetSubsystem(WIN) MFUser(MX02689) InteractiveJob WOBRequestID(541949BCCAE0C3CBFA6F8712F0CFE4EB4A24AC5315735116046750)
    Mon Nov 11 16:33:24 2019 CAWA_I_20008 Agent version: CA Workload Automation Agent for Microsoft Windows R11.3 Build 738
    Mon Nov 11 16:33:24 2019 CAWA_I_20006 --- Environment ---
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ALLUSERSPROFILE=C:\ProgramData
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: APPDATA=C:\WINDOWS\system32\config\systemprofile\AppData\Roaming
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: AUTOPID=15160
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: CommonProgramFiles=C:\Program Files\Common Files
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: CommonProgramW6432=C:\Program Files\Common Files
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: COMPUTERNAME=MXVADM_MX02689
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ComSpec=C:\WINDOWS\system32\cmd.exe
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: DriverData=C:\Windows\System32\Drivers\DriverData
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENT=MXVADM_MX02689
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENTDIR=C:\CA\WA_Agent_R11_3_4
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENTHASH=AA22A2797DF81F492535E550C9D6799C2F307512
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENTPORT=7520
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENTSPOOL=C:/CA/WA_Agent_R11_3_4/spool
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAGENTTOKEN=4D583032363839
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAPGEN=37
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAPPL=01_PRUEBA_RUBEN
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPAPPLMGR=JavaAgent#tcpip@CENTRAL_MANAGER
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPOBJECT=1313262448_HEBER_BAT/01_PRUEBA_RUBEN.37/MAIN
    Mon Nov 11 16:33:24 2019 CAWA_I_20007 Environment variable: ESPWOB=1313262448_HEBER_BAT
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: LOCALAPPDATA=C:\WINDOWS\system32\config\systemprofile\AppData\Local
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: NUMBER_OF_PROCESSORS=4
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: OS=Windows_NT
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: Path=C:\CA\WA_Agent_R11_3_4\jre\bin\;C:\CA\WA_Agent_R11_3_4\jre\bin\server;C:\CA\WA_Agent_R11_3_4\addons;C:\CA\WA_Agent_R11_3_4\addons;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files (x86)\RSA SecurID Token Common;C:\Program Files\RSA SecurID Token Common;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\SecureCRT\;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PROCESSOR_ARCHITECTURE=AMD64
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 142 Stepping 9, GenuineIntel
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PROCESSOR_LEVEL=6
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PROCESSOR_REVISION=8e09
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: ProgramData=C:\ProgramData
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: ProgramFiles=C:\Program Files
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: ProgramFiles(x86)=C:\Program Files (x86)
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: ProgramW6432=C:\Program Files
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: PUBLIC=C:\Users\Public
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: SystemDrive=C:
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: SystemRoot=C:\WINDOWS
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: TEMP=C:\WINDOWS\TEMP
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: TMP=C:\WINDOWS\TEMP
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: UATDATA=C:\WINDOWS\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: USERDOMAIN=HEBMTY
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: USERNAME=MXVADM_MX02689$
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: USERPROFILE=C:\WINDOWS\system32\config\systemprofile
    Mon Nov 11 16:33:25 2019 CAWA_I_20007 Environment variable: windir=C:\WINDOWS
    Mon Nov 11 16:33:25 2019 CAWA_I_20013 Command to be executed: "C:\WINDOWS\SYSTEM32\cmd.exe" /c D:\Prueba.bat >>"C:\CA\WA_Agent_R11_3_4\spool\CENTRAL_MANAGER\MAIN\01_PRUEBA_RUBEN.37\1313262448_HEBER_BAT" 2>>&1
    Mon Nov 11 16:33:25 2019 CAWA_I_20010 The local security is bypassed
    Mon Nov 11 16:33:25 2019 CAWA_I_20022 Process created with pid: 16432
    Mon Nov 11 16:33:25 2019 CAWA_I_20017 Job completed successfully. Exit code 0


    this is the agentparm.txt file with all the configurations

    #
    # Agent settings for nt-x86-64
    #

    #
    # Log
    #
    # log.archive settings:
    # 0 - archive with time extension
    # 1 - append ".archive.log"
    # 2 - delete previous log
    # 3 - keep writing to the same log file
    log.level=5
    log.archive=1
    log.maxsize=1M
    #

    #
    # Agent name
    #
    agentname=MXVADM_MX02689

    #
    # Communications
    #
    communication.inputport=7520

    communication.managerid_1=CENTRAL_MANAGER
    communication.manageraddress_1=SCA2011145
    communication.managerport_1=7507
    communication.monitorobject_1=MXVADM_MX02689/AGENTMON1.0/MAIN

    #
    # Security
    #
    security.filename=C:/CA/WA_Agent_R11_3_4/security.txt
    security.level=off
    security.cryptkey=C:/CA/WA_Agent_R11_3_4/cryptkey.txt

    #
    # Initiators
    # There will be separate line for each pair of <class, number of initiators>
    # initiators.class_N, where N is number running from 1 to ...
    # Class is user definable, (should be the same here and in AFM)
    # Soft shutdown mode waits for all jobs to be completed
    #
    initiators.class_1=Default,1000

    #
    # Core parameters
    #
    core.health.monitor.enable=true

    #
    # General characteristics
    #
    spooldir=C:/CA/WA_Agent_R11_3_4/spool
    # Java parameters
    oscomponent.javapath=C:/CA/WA_Agent_R11_3_4/jre/bin
    oscomponent.jvm=server

    # What plugins we want to start by the core Java agent
    plugins.start_internal_1=runner
    plugins.start_internal_2=router
    plugins.start_internal_3=filemon
    plugins.start_internal_4=objmon
    plugins.start_internal_5=filebrowser

    # Jars classpath
    oscomponent.classpath=jars/*.jar;jars/ext/*
    management.snmp.mibfile=C:/CA/WA_Agent_R11_3_4/cybermation.mib

    #
    # What management connectors we want to start by the core Java agent
    #


    #
    # Windows Service name
    #
    oscomponent.servicename=CA Workload Automation Agent 11.3.4
    oscomponent.servicedisplayname=CA Workload Automation Agent 11.3.4

    # Windows Settings
    oscomponent.lookupcommand=true
    oscomponent.noforceprofile=false
    oscomponent.dumpenvironment=false
    oscomponent.initialworkingdirectory=SCRIPT
    oscomponent.cmdprefix.force=true

    runnerplugin.spool.clean.enable=true
    runnerplugin.spool.expire=10D
    runnerplugin.spool.sleep=36H
    oscomponent.joblog=true
    oscomponent.cmdprefix.force=true
    oscomponent.interactive=true
    oscomponent.cmdprefix.force.redir.inline=true
    oscomponent.interactive.session.ignoreinactive=true
    oscomponent.interactive.sessionzero=true
    oscomponent.logon.elevated=true
    oscomponent.su.newconsole=true
    oscomponent.shell=true
    #oscomponent.default.user=MXVADM_MX02689
    oscomponent.default.password=2390hasG

    #
    # Installer setting. Do not modify the setting below
    #
    installer.version=R11.3.4


    #
    # Added by Manager
    #
    communication.managerhealthmon_1=false
    communication.socket_1=plain


    ------------------------------
    Heber Solis
    ------------------------------


  • 2.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 12, 2019 02:17 AM
    Hi,

    Looking at the log , looks like the batch command file ran without any errors. The two statements - security and exit code are not errors as far as i know. 
    The job seems to be an interactive job going by the log. But it runs without any user input.

    Do you expect any inputs that the user should give.

    For further analysis , I would suggest if you can raise a ticket for this.

    Ravi Kiran


  • 3.  RE: The local security is bypassed error

    Posted Nov 12, 2019 07:35 AM
    Hi thank you for your help, how can I raise a ticket im new around here and no, i just need to run the bat file because it has all the parameters and even with no parameter I just want it to open the app it doesn't do it it says no errors and so on but it doesn't do anything


  • 4.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 13, 2019 01:32 AM
    Hi,

    You can raise a case in support.broadcom.com site.


  • 5.  RE: The local security is bypassed error

    Posted Nov 14, 2019 10:32 AM
    I can´t open a ticket the url you provided leads to nowhere, I poke around the site and got to here https://www.broadcom.com/support/services-support/ca-support/contact-support?intcmp=footernav where I click open a case and it redirects me to https://casupport.broadcom.com/ where it asks me to sign in again and I do and redirects me to https://www.broadcom.com/mybroadcom so I don't know what to do, could you help me please? I have like around 2 months striggling with this error and i don't know what it is causing it


  • 6.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 14, 2019 10:37 AM
    Hi, 
    I suggest that you call the support center.  The number is below. At the very least they can open a case for you.  They can also resolve the issue of opening a case. 
    Support Center (ESP HELPDESK) 800-225-5224

    Don


  • 7.  RE: The local security is bypassed error

    Posted Nov 14, 2019 10:40 AM
    Hi, I'm from México, I can still call there?


  • 8.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 14, 2019 10:57 AM
    Hi, 
    You may also want to look at this post. 
    I think the format you need is similar to the one below. I don't support dSeries but it should be similar to this. 

    cmdname C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

    args & D:\cyb_agent_R7\helloworld.ps1


    https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?GroupId=1537&MessageKey=33139563-adce-4ed1-92ce-d6c94a88d0c1&CommunityKey=45e0ea8b-1184-409f-80eb-26bf98cd2e61&tab=digestviewer&ReturnUrl=%2fenterprisesoftware%2fcommunities%2fcommunity-home%2fdigestviewer%3ftab%3ddigestviewer%26CommunityKey%3d45e0ea8b-1184-409f-80eb-26bf98cd2e61

    Don



  • 9.  RE: The local security is bypassed error

    Posted Nov 14, 2019 12:42 PM
    thank you, I implemented the solution and nothing :(


  • 10.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 14, 2019 06:01 PM
    Hi, 
    I think you need to open a case so we can get the details. 

    My job definition only has 3 items in it. From the output at the beginning of this post it looks like the powershell is working correctly.  
    Agent Name DPW01
    Command to run C:\WINDOWS\SYSTEM32\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE
    Arguments to pass C:/Users/Administrator/Documents/Scripts/TEST1.ps1

    don



  • 11.  RE: The local security is bypassed error

    Posted Nov 14, 2019 06:06 PM
    Hi, Thank you, Do you have the url to do that? I can't find where and where I think the ticket is made i'm being redirected to somewhere else :(


  • 12.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 14, 2019 06:23 PM
    I would call the help desk directly.  They can get it worked out.... 
    Support Center (ESP HELPDESK) 800-225-5224


  • 13.  RE: The local security is bypassed error

    Broadcom Employee
    Posted Nov 19, 2019 03:53 PM
    Hi Heber,

    For the message local security is bypassed.  That is a result of your agentparm.txt settings.  It is just an informational message and has no impact on the running of the job.

    Check out this link for more details on what it does if your interested:
    https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/11-5/configuring/set-up-security/setting-up-local-security-on-the-agent.html

    Regards,
    Mike


  • 14.  RE: The local security is bypassed error

    Posted Nov 19, 2019 04:25 PM

    thank you but, then, what's the issue? :( it's so frustrating look 

    1 I can't open a case in here because the page doesn't let me 

    2 I can't call support center because I'm only an automation tester in my organization and I don't have the information they are asking for 

    3 I've done everything it says in several pages here and in documentation and nothing seems to work 

    I've been struggling with this issue for over a month and I'm clueless of what could be wrong 
    Thanks for the help




  • 15.  RE: The local security is bypassed error
    Best Answer

    Broadcom Employee
    Posted Nov 19, 2019 11:11 PM
    Hi,

    I will request you to contact your Product administrator  in your organization to open a ticket for you with the required information.

    Ravi Kiran