IBM BigFix Pre Upgrade Check (Version 9.5.9)

Usage and Config
1

I’ve had the fixlet “IBM BigFix Pre Upgrade Check (Version 9.5.9)” running for about 30min now with a “running” status. It completed successfully on 3/4 deployments but this one is taking longer for some reason.

is there a point when I should stop the action and kill the besadmin.exe process on the server and if so, then what?

Running wait cmd.exe /C __Local\PreCheck\BESAdmin.exe /username={parameter "Username" of action} /password={parameter "Password" of action} /preupgrade /standalone

2

Don’t really know an answer, but this looks time-sensitive, so…

When running the real upgrade, besadmin keeps a running log in the user’s TEMP folder. You might check the \windows\temp folder to see whether there are any directories or log files that might look like besadmin output

1 Like
3

there is a file called big9208.tmp in c:\windows\temp from about the start time of the action, but size is 0 KB.

4

Is there a subdirectory? I thought it created a new subdir…but I’ve only run the upgrades interactively, not through the fixlet.

5

What do you see in memory? Is the BESAdmin.exe growing in terms of memory?
-jgo

1 Like
6

I only do upgrades manually too, but thought it might be a good idea to run this pre-check fixlet first. There are no directories in \temp\ related to besadmin that i see.

Besadmin.exe is running with 0% cpu and 2,184K memory usage with no fluctuations.

7

Working on an open case with IBM.

C:\Windows\System32\config\systemprofile\AppData\Local\BigFix\BESAdminDebutOut.txt:

Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- (critical log messages enabled)
Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- (debug log messages enabled)
Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- (database log messages enabled)
Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- Admin tool version 9.5.9.62
Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- Lang option specified: 
Thu, 07 Jun 2018 09:39:45 -0500 -- 7460 -- Error: File error "class RootHasNoParent" on "d:"
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- (critical log messages enabled)
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- (debug log messages enabled)
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- (database log messages enabled)
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- Admin tool version 9.5.9.62
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- Lang option specified: 
Thu, 07 Jun 2018 11:11:37 -0500 -- 1704 -- Error: File error "class RootHasNoParent" on "d:"
1 Like
8

When the server setup.exe is manually ran, it shows checking the same items that the PreCheck does which is helpful

9

…but all database updates fail because the same error occurs when running the default besadmin.exe

10

the issue was that I had created the client setting “_BESTools_Logging_LogPath” on the root server with a value of “d:” when I was doing some besadmin perf testing with v9.5.4 (even though that client setting did nothing in v9.5.4) and the v9.5.9 besadmin.exe tool required a folder + filename to be in the value (or the client setting to not exist).

2 Likes