Run a remote *.cmd from PDQ-deploy

Comments

2 comments

  • Shane Corellian

    If an install works when you run it interactively (when you manually run the bat file) but fails when you deploy it then the issue is often permissions and/or access to an interactive desktop.

    The Run As option may need to be changed. Make sure you aren't running as Local System. Using Local System would prevent the deployment from successfully accessing network file shares once the installation begins. You will want to Run As Deploy User or Deploy User (Interactive). The Deploy User must have rights to all the referenced network locations (\\wds\Pakker\Jet 
    Report 2012-2013\setup.iss, \\wds\Pakker\NAV2009R2DK\setup.xml, etc)

    I would recommend finding out what error code 2 means from Symantec. This could mean anything from File Not Found, to Fatal Error, etc. Finding out what their error (return) codes mean will help you in troubleshooting.

    Is xcopy returning error code 4? 

     

    -Shane

     

    0
    Comment actions Permalink
  • Me

    Sorry for the late reply.

    NAV is not Norton Antivirus, but Microsoft Navision.

    It seems as I have managed this thing by this workaround:

    http://support.adminarsenal.com/entries/21529507-Installer-returned-error-code-2-when-deploying-Dynamics-NAV-2009?page=1#post_23012664

    Havn't been looking into the JetReport part yet.

    Regards, Lars.

    0
    Comment actions Permalink

Please sign in to leave a comment.