Skip to content

Known Issues

HyWorks v3.3-R3 Known Issues

# Subject
18291 [HyLabs] Enabling flag Remove HyLabs temporary assignment on logout will override default reservation settings Enable VM retention option after logoff. This will result in release of reserved VM, even when participant is opting to retain it.
18290 Various buttons and UI controls on HyWorks Management Console are not appearing correctly on Internet Explorer browser.
Workaround: It is recommended to use Chrome, Chromium Edge or Firefox.
18289 Controller setup is not integrated with Microsoft Sync Framework in Japanese language and thus it does not install it with HyWorks Controller installation.
Workaround: Install Microsoft Sync Framework after or before controller installation in the clustered environment.
18288 Upgrading broker node before Management nodes will result in mismanagement in cluster configurations and functioning
Workaround: Restart broker node service after upgrading all the nodes
Recommendation: Upgrade Management nodes before upgrading broker nodes.
18265 [HyLabs] Appropriate validation error is not shown, when Password/ Confirm Password fields are left blank in provisioning profile.
18225 Scheduler installation wizard does not respond when Next button on the database configuration screen is clicked multiple times.
18206 Broker node gives unnecessary prompt to use existing log database during installation.
Workaround: Continue installation by confirming the use of existing log database.
18193 Prompt displayed (For using existing database of lower version in two-node active-passive deployment type) is not user-friendly.
Recommended Action: During installation if existing database is used then click Yes, or click No to specify new database to be configured.
18123 In an unidentified condition, duplicate VM entries are observed in Source VM list in desktop pool - deployment screen from Azure provider.
18122 In an unidentified condition Desktop VM count is not getting updated for Azure provider
18078 HyWorks Controller does not fetch groups of a user that reside in the child domain and it's groups are in parent domain and authorization server is parent domain.
Workaround: Use built-in user/group directory for authorization.
18075 In an unidentified condition, managed SHD are being polled for status and information, though agent has already pushed information via scale booster.
18073 HyWorks Controller installation fails with error "The object identifier does not represent a valid object.
18026 HyWorks controller does not support database restore during installation or repair if SQL server is hosted on other than controller server.
Workaround: Restore database on SQL server using SQL Management Studio and then install HyWorks Controller to use restored database.
18022 "Error while cleaning .Access to the path 'EDC.Core.dll' is denied" Error is logged in HyWorks-Controller-logs.
18017 Error DVMTools: noDocument: company_info.xml does not exist is thrown during uninstallation of broker node
Workaround: Re-run HyWorks controller setup, after rebooting server.
18015 Ability to access and modify configurations from broker node (Management console pointing to broker node)
Workaround: Currently broker nodes need to be installed with HyWorks Controller service only without management console.
18003 Broker node/ Management node service can not be started after uninstalling and re-installating in cluster configurations
Workaround: Access HyWorks Controller Database on all management nodes and delete entry of controller node which is having issue in service start.
18002 Broker node installation fails if any of management node is not reachable.
17860 In an unknown condition, entry of deleted unmanaged SHD pool does not get removed from DB hence controller keeps on trying to fetch details.
17843 Desktop pool cloning is failing on Azure if desktop prefix name having space in it
Workaround: Do not use space in Desktop prefix for Microsoft Azure.