Software distribution wizard installing Symantec NetBack Client - using silentinstall.cmd

Content Authoring
1

Deploying Windows Symantec NetBackup Client using the Software Distribution
Wizard with the command, silentclient.cmd, is failing Command failed (Thread execution failed (2)) wait __Download\silentclient.cmd. Log file:

   Command succeeded (Prefetch download manager collected file) prefetch 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 sha1:6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 size:321503353 http://itemserver.training.tivoli.edu:52311/Uploads/6b315ebbd5172fa48c5e32e285ca9b3b7c73df29/x64.tmp sha256:c7db1e4e865037c39db65a660723f9bd9917e74f3636123765f97a5ef2ca30f0 (action:3990)
At 15:17:05 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command succeeded extract 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 (action:3990)
   Command started - wait  __Download\silentclient.cmd (action:3990)
   Command failed (Thread execution failed (2)) wait  __Download\silentclient.cmd (action:3990)

The software is currently copied to Bigfix Server in the following path C:\x64\x64. and I can run the command from there with success.

I have tried adding: Command succeeded (Exit Code=9009) wait cmd /c __Download"\silentclient.cmd" (action:3989) with no success.

2

When you run this on a client you should be able to find the script and files in the client folder on the system __BESData\ActionSite\__Download

Go ahead and action this against a client and look in that folder and see if you can find the script and files – and try running it from there

3

The file is located here

C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\__Global\__Cache\Downloads\6b315ebbd5172fa48c5e32e285ca9b3b7c73df29
4

So files are located in that path during download but are moved to the __BESData\ActionSite\__Download folder before running – you should find it in that path when it attempts to actually run the .bat file

5

I am looking at this path and the extracted folder is there with the files

C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\CustomSite_PPW_SA\__Download\x64
6

In __Download is there a silentclient.cmd file?

7

I am running the fixlet out of the customsitePPW_SA. The files are located at . The sha1 file is located
C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\__Global\__Cache\Downloads and appears that it is extracted to

C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\CustomSite_PPW_SA\__Download\x64

and the silentclient.cmd is in that folder.

8

Is the silentclient.cmd in __Download or in __Download\x64?

9

silentclient.cmd is located in

__Download\x64

10

The action script of your command is doing this:

Command started - wait __Download\silentclient.cmd (action:3990)

It is calling silentclient.cmd thinking it’s in the __Download folder but it’s actually in the __Download\x64 folder.

You’ll need to change the line (in your actionscript):

wait __Download\silentclient.cmd

to:

wait __Download\x64\silentclient.cmd
1 Like
11

I am still getting the following as I have tried that before. (Exit Code=9009)

   Command succeeded (Prefetch download manager collected file) prefetch 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 sha1:6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 size:321503353 http://itemserver.training.tivoli.edu:52311/Uploads/6b315ebbd5172fa48c5e32e285ca9b3b7c73df29/x64.tmp sha256:c7db1e4e865037c39db65a660723f9bd9917e74f3636123765f97a5ef2ca30f0 (action:3992)
At 17:09:24 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command succeeded extract 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 (action:3992)
   Command started - wait __Download\x64\silentclient.cmd (action:3992)
   Command succeeded (Exit Code=9009) wait __Download\x64\silentclient.cmd (action:3992)
12

That’s a very different error message than before. This implies that some part of your script is returning code 9009 and thus your script is running but not working. The old message was that the script wasn’t even running – we are one step closer :slight_smile:

I’ve seen 9009 before using xcopy, can you post the contents of silentclient.cmd?

13

So I can run the command __Download\x64\silentclient.cmd from the directory and it installed the software. Rename file from .bes to .txt silentclient.bes (5.6 KB)

When I look up the code I see the following in one article.

Program is not recognized as an internal or external command, operable program or batch file. Usually indicates that command, application name or path has been misspelled when configuring the Action.

14

Are you navigating to: CustomSite\__Download\x64 and running silentclient.cmd

Or are you navigating to: CustomSite and running __Download\x64\silentclient.cmd

15

navigating to: CustomSite\__Download\x64 and running silentclient.cmd

16

Your issue is that the working directory when BigFix runs the script is:

__BESData\Customsite

and then it calls:

__Download\x64\silentclient.cmd

with a working directory of: __BESData\Customsite

The issue with this is that when it gets to your “setup.exe” line in the script it is looking for setup.exe in the working directory and not in the x64 folder.

To fix this you either need to have your script change directory into the x64 folder:

cd __Download\x64
setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%'

or you need to call setup.exe in the __Download\x64 folder:

__Download\x64\setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%'
1 Like
17

I am not following. The silentclient.cmd provides options values for the install process. So I am not certain I am following above.

18

The working directory is your root – all other paths are relative to the working directory.

Reproducing the issue
The reason it works when you run it manually is because your command prompt is sitting here:

__BESData\Customsite\__Download\x64

If you “CD” up two directories so your command prompt is sitting at:
__BESData\Customsite and you run __Download\x64\silentclient.cmd

You will get the same error that BigFix is getting.

The Issue
When BigFix runs the batch file its working directory is:

__BESData\Customsite

All paths from here on out are relative to that path so when we call:

wait __Download\x64\silentclient.cmd

We are telling BigFix to take the working directory, add that, and run it:

__BESData\Customsite + \ + __Download\x64\silentclient.cmd

Your script, silentclient.cmd now inherits the working directory of the BigFix client:

__BESData\Customsite

So when your silentclient.cmd script calls “setup.exe” the command prompt interprets that to be:

__BESData\Customsite + \ + setup.exe

This obviously doesn’t exist as the setup.exe is in the x64 folder next to the batch script. So what we need to do is we change the script so that when it calls setup.exe it’s calling it in the right place.

Option 1
We can do that by changing directory into the x64 folder:

cd __Download\x64
setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%'

This will change our working directory to be

__BESData\Customsite\__Download\x64

So that when we call setup.exe it is interpreted as:

__BESData\Customsite\__Download\x64 + \ + setup.exe

Option 2
or changing the call to reference the setup.exe in the __Download\x64 folder:

__Download\x64\setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%'

So that when we call setup.exe it is interpreted as:

__BESData\Customsite + \ + __Download\x64\setup.exe
1 Like
19

Ok now I am getting what you are saying is the setup.exe that is called out in silentclient.cmd is what cannot be found. I ran the
__Download\x64\setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%' and the program installed with Exit Code=1603

At 17:53:44 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command succeeded (Prefetch download manager collected file) prefetch 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 sha1:6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 size:321503353 http://itemserver.training.tivoli.edu:52311/Uploads/6b315ebbd5172fa48c5e32e285ca9b3b7c73df29/x64.tmp sha256:c7db1e4e865037c39db65a660723f9bd9917e74f3636123765f97a5ef2ca30f0 (action:3995)
At 17:53:47 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command succeeded extract 6b315ebbd5172fa48c5e32e285ca9b3b7c73df29 (action:3995)
At 17:53:48 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command started - wait __Download\x64\setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%' (action:3995)
At 17:53:48 -0800 - mailboxsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/mailboxsite9779153)
   Relevant - Run Capacity Scan and Upload Results (fixlet:1096)
At 17:53:49 -0800 - BES Support (http://sync.bigfix.com/cgi-bin/bfgather/bessupport)
   Fixed - Clear BES Local Download Caches (fixlet:679)
At 17:54:02 -0800 - actionsite (http://itemserver.training.tivoli.edu:52311/cgi-bin/bfgather.exe/actionsite)
   Command succeeded (Exit Code=1603) wait __Download\x64\setup.exe -s /REALLYLOCAL /RESPFILE:'%RESPFILENAME%' (action:3995)
20

So the issue now is probably that you’re calling setup.exe outside of your .cmd script – the .cmd script sets up a bunch of variables including the response file that are probably required.

1 Like