ControlUp users discussed an issue with upgrading a Hive via an endpoint management tool. A link to an article on upgrading Custom Hives was shared, mentioning the requirement of a token for upgrades. Another article with instructions for a silent installation was also mentioned. A user questioned the need for a /name switch during an update and it was clarified that the switch is only required if the Hive name needs to be changed. The article will be updated to reflect this.
Read the entire ‘Upgrading ControlUp Custom Hives: Understanding the /name Switch’ thread below:
Has anyone else run into an issue when upgrading a Hive via an endpoint management tool where it installs successfully but actually fails with error code: 1?
I’m using the following command: hive110_1238x64.exe /VERYSILENT
Curious if others have seen this behavior or found a workaround.
I think the command line is only for h
Upgrades not initial install
Correct, I’m performing an upgrade
I’ll test again on a second workstation, just to be sure this is not a one-off
@member might be able to assist tomorrow
Tested again with logging enabled, and it’s still exiting with error level 1 because a token is required even for an upgrade.
“`2025-10-24 09:08:43.625 usage: sb-hive.exe [-h] -setup_dir SETUP_DIR -token TOKEN [-name NAME]
2025-10-24 09:08:43.625 [-enrichment_username ENRICHMENT_USERNAME]
2025-10-24 09:08:43.625 [-enrichment_password ENRICHMENT_PASSWORD]
2025-10-24 09:08:43.625 [-use_proxy USE_PROXY] [-proxy_protocol PROXY_PROTOCOL]
2025-10-24 09:08:43.625 [-proxy_address PROXY_ADDRESS] [-proxy_port PROXY_PORT]
2025-10-24 09:08:43.625 [-proxy_username PROXY_USERNAME]
2025-10-24 09:08:43.625 [-proxy_password PROXY_PASSWORD] [-event_log EVENT_LOG]
2025-10-24 09:08:43.625 [-debug_mode DEBUG_MODE] [-ssl_verify SSL_VERIFY]
2025-10-24 09:08:43.625 [-interactive_logon INTERACTIVE_LOGON]
2025-10-24 09:08:43.625 [-use_citrix_workspace USE_CITRIX_WORKSPACE]
2025-10-24 09:08:43.625 [-allow_shell_execution ALLOW_SHELL_EXECUTION]
2025-10-24 09:08:43.625 [-use_default_values USE_DEFAULT_VALUES]
2025-10-24 09:08:43.625 sb-hive.exe: error: the following arguments are required: -token
2025-10-24 09:08:44.170 [2025-10-24 09:08:44,124][INFO][hive.py:155]:exit
2025-10-24 09:08:45.030 Process exit code: 1
2025-10-24 09:08:45.030 — Run entry —
2025-10-24 09:08:45.030 Run as: Current user
2025-10-24 09:08:45.030 Type: Exec
2025-10-24 09:08:45.030 Filename: C:\Program Files\Scoutbees Custom Hive\sb-hive.exe
2025-10-24 09:08:45.030 Parameters: –startup=auto install
2025-10-24 09:08:54.854 Output:
2025-10-24 09:08:54.854 Installing service ScoutbeesHive
2025-10-24 09:08:54.854 Service installed
2025-10-24 09:08:54.854 object address : 000002B3A84F05F0
2025-10-24 09:08:54.854 object refcount : 3
2025-10-24 09:08:54.854 object type : 00007FFFD001D410
2025-10-24 09:08:54.854 object type name: AttributeError
2025-10-24 09:08:54.854 object repr : AttributeError("type object ‘object’ has no attribute ‘flush’")
2025-10-24 09:08:54.854 lost sys.stderr
2025-10-24 09:08:55.498 Process exit code: 0
2025-10-24 09:08:55.498 — Run entry —
2025-10-24 09:08:55.498 Run as: Current user
2025-10-24 09:08:55.498 Type: Exec
2025-10-24 09:08:55.498 Filename: C:\Program Files\Scoutbees Custom Hive\sb-hive.exe
2025-10-24 09:08:55.498 Parameters: start
2025-10-24 09:09:13.821 Output:
2025-10-24 09:09:13.821 Starting service ScoutbeesHive
2025-10-24 09:09:13.821 object address : 000001F908B07920
2025-10-24 09:09:13.821 object refcount : 3
2025-10-24 09:09:13.821 object type : 00007FFFCEE6D410
2025-10-24 09:09:13.836 object type name: AttributeError
2025-10-24 09:09:13.836 object repr : AttributeError("type object ‘object’ has no attribute ‘flush’")
2025-10-24 09:09:13.836 lost sys.stderr
2025-10-24 09:09:14.530 Process exit code: 0
2025-10-24 09:09:14.530 Check registration exit code…
2025-10-24 09:09:14.811 C:\Program Files\Scoutbees Custom Hive\sb-hive.exe
2025-10-24 09:09:15.045 –check-setup –filelog -setup_dir="C:\Program Files\Scoutbees Custom Hive"
2025-10-24 09:09:25.342 Script executed. Exit code: 1
2025-10-24 09:09:25.628 Aborting…“`
The instructions at https://support.controlup.com/v1/docs/upgrade-your-custom-hives, does not mention the requirement of an additional switch for token.
good day, if you want upgrade /install silently with the new params , please have https://support.controlup.com/docs/silent-install-for-synthetic-monitoring-custom-hives
i will have the upgrade -your-custom-hives article updated
.\hive110_1230x64-44d352c5_job_5771.exe /VERYSILENT /SUPPRESSMSGBOXES /token="eu_0c2eebbd4cf1b8ef3eede3cae518ef3a819115dc42cc8ffd2d3f92a7f50f3f49" /name="ScoutbeesDemoHive" /use_default_values=True
from https://support.controlup.com/v1/docs/upgrade-your-custom-hives -> token is required, -> security feature so only people with access to SB can upgrade hives
There’s something not right with the link you posted. I need to upgrade about 10 Hives. You’re saying that during an upgrade I must use the /name switch, but that doesn’t make sense since each Hive already has its own unique name.
Why is /name required during an update?
Does this mean I need a unique deployment for every single hive?
if you have "custom Names" for the custom hive, you need to pass it
What if I need to upgrade 100 hives
?
if you left default -> computer name is the hive name
So /name is NOT a required switch if I want to leave the hive name as-is?
correct
Then the article needs to be updated to say the /name switch is required only if the name needs to change during an update. If the name does not need to change, the /name switch should be optional.
…the way it’s written now, it makes it sound like the /name switch is mandatory during an update.
will work to update the article
Continue reading and comment on the thread ‘Upgrading ControlUp Custom Hives: Understanding the /name Switch’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers, ControlUp Synthetic Monitoring