SPB install failing in AIX

(imported topic written by SystemAdmin)

I am pretty green when it comes to the AIX OS, and I am working on a .spb installer that will install an monitoring agent on my AIX devices.

Belowis the failed action script. I am hoping someone out there has more experience than I in trying to determine the hang up of this. Thank you to those who can assist!

Action Script Execution Detail

Completed // Download all specified files

Completed begin prefetch block

Completed add prefetch item name=C19CCEA8358B94C30C7DEEA93A94C92D9740E6E8 sha1=c19ccea8358b94c30c7deea93a94c92d9740e6e8 size=141913317 url=SWDProtocol://127.0.0.1:52311/uploads/C19CCEA8358B94C30C7DEEA93A94C92D9740E6E8/uxaix526.spb.bfswd

Completed end prefetch block

Completed // All SWD Files will go into a folder in the clients __BESData folder. This folder get cleared on every restart.

Completed parameter “baseFolder” = “__Download”

Completed // Make Relative Folders

Completed delete __createfile

Completed delete makeDirs.bat

Completed createfile until

end

Completed @ECHO OFF

Completed mkdir “{parameter “baseFolder”}”

Completed

end

Completed move __createfile makeDirs.bat

Failed waithidden makeDirs.bat

// Move files into subfolders and unescape file names

move “__Download\C19CCEA8358B94C30C7DEEA93A94C92D9740E6E8” “{parameter “baseFolder”}uxaix526.spb”

// Run setup process

delete __createfile

delete run.bat

// Use .bat to set working directy to packages root, for setup command.

createfile until

end

@ECHO OFF

cd “{parameter “baseFolder”}”

call “{pathname of parent folder of client & “\SIE”}\swd_env.bat”

wdinstsp.exe -f “uxaix526.spb”

wdlssp.exe > “{pathname of parent folder of client & “\SIE”}\software.cfg”

end

move __createfile run.bat

// You will not be able to stop or take action on an applicable BES Client until your installer completes,

// so ensure no user input is required.

// If your package absolutely must interact with the user, replace waithidden with run.

waithidden run.bat

(imported comment written by SystemAdmin)

The .bat files are what are holding you back here. The current version of software distribution only supports windows (though we will be expanding this in the next release)

(imported comment written by SystemAdmin)

That would explain it. Thanks Zak.