Hi Shilpi Verma,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
It sounds like you're having trouble with the RD Connection Broker role service on Azure Stack HCI. Here are some steps to help:
Uninstall the Windows Internal Database, rename the old WID folder (e.g., C:\Windows\WID to WID_old), and reinstall the RD Connection Broker role service. (External reference: Fixed: RD Connection Broker Role Service Fails to Install 2016 - AnyViewer)
Note: Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Review the known issues for your specific version of Azure Stack HCI in the release notes.
https://learn.microsoft.com/en-us/azure-stack/hci/known-issues-2402
Make sure that all nodes in your cluster have proper connectivity and that there are no network issues. You can use the Invoke-AzStackHciConnectivityValidation cmdlet from the AzStackHCI.EnvironmentChecker module to test connectivity
Collect and review the PowerShell registration logs and hcisvc debug logs from each server in the cluster.
If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".