Article ID: 114509, created on Aug 3, 2012, last review on Jun 20, 2016

Symptoms

Task to import APS application fails with the error message in case of OA on Windows Management Node:

Destination host_id #1 : Internal error: Error on command execution - "C:\Program Files\SWsoft\PEM\APS\tools\tar.exe -c scripts -f scripts.tar", Error: %1 is not a valid Win32 application.

The following HCL request may be found in OA debug log:

Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]: Thread (3212) Process: (<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]: <!DOCTYPE HCL PUBLIC "HCL" "HCL 1.0">
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]: <HCL>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:   <DECLARE/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:   <PERFORM>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:     <SET value="root" var="defuser"/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:     <SET value="root" var="defgrp"/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:     <RM path="C:\Program Files\SWsoft\PEM/APS/tmp/package29"/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:     <MKDIR group="${defgrp}" hier="yes" owner="${defuser}" path="C:\Program Files\SWsoft\PEM/APS/tmp/package29" perm="0755" uniq="no"/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:     <EXTRACT filename="C:\Program Files\SWsoft\PEM/APS/packages/BackupAgent-1.0-26.app.zip" rootpath="C:\Program Files\SWsoft\PEM/APS/tmp/package29"/>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]:   </PERFORM>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]: </HCL>
Jul 15 19:36:10 PEMCORE001 : DBG [1:2880:b98:25232 1:1864:c8c pleskd]: )

The similar problem may appear during OA Agent installation/upgrade or other operations on managed Windows server. The server ID may be found in the failed task properties: Destination host_id #1. In the example above host ID is 1, it is OA Management Node always. In case of problem with slave host you will see its ID in the failed task.

Cause

The file C:\Program exists on OA Management Node or managed Windows server.

Resolution

The file C:\Program is not a part of OA distribution, it must have been created manually or by 3rd-party software. Remove (or at least rename) the file C:\Program on OA Management Node or managed Windows server and re-run the failed OA task.

Search Words

Error: %1 is not a valid Win32 application

Internal error: Error on command execution

Email subscription for changes to this article
Save as PDF