CA Client Automation

  • Private Community

  • 1.  Exit Code 3010

    Posted Sep 17, 2018 09:23 AM

    Hi,

    trying to create software package for .Net Framework 4.7.2.

    Although I have set in procedure the parameter "setup.exe /q /norestart $#ec:0,3010", the jobs fail with error code 3010.

    I thought $#ec will filter the listed codes? Which log-File should I check to see what is going wrong?

     

    Thanks in advance



  • 2.  Re: Exit Code 3010

    Broadcom Employee
    Posted Sep 17, 2018 10:13 AM

    For testing purposes change your command line to "setup.exe /q /norestart /debuglog %temp%\netframeset.log $#ec:0,3010",

     

    Then check window\temp for the log.

     

    Richard Lechner

    Principal Engineering Services Architect

     

    CA Technologies

    Mobile: +1 703 655 7161 | Richard.Lechner@ca.com

     

    <mailto:Richard.Lechner@ca.com>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>



  • 3.  Re: Exit Code 3010
    Best Answer

    Posted Sep 17, 2018 10:16 AM

    Code a separate $#ec: parameter for each code:

     

    $#ec:0 $#ec:3010

     

    Comma separated codes is not supported.

     

    On Mon, Sep 17, 2018, 08:23 NoIdea999 <



  • 4.  Re: Exit Code 3010

    Posted Sep 18, 2018 03:13 AM

    Thanks for the replies Richard and Steve! Separation of the $#ec parameter seems to have solved my problem!