28-10-24 02:15 PM
Hi Community,
We are Setting up the Blue prism HUB 5.1. and getting error in Power script Run error.
Completed the prerequisites Message Broker setup, .NET Core components, downloading the HUB 5.1 Bundle and Updating the config.jason file with Mandatory details.
After completing, we have run the HUB Power Shell Script and getting the below Log error.
The IIS install, script run was success and success message also came.
Please suggest the Resolution to the Script error.
Log Error details below :-
**********************
Transcript started, output file is C:\BP_Hub\BluePrismHub-5-1\logs\script-output-2024-10-28-08-44-24.log
Parameters validated
#===============================================#
#-- Checking if IIS component is installed... --#
#===============================================#
PS>TerminatingError(Get-WindowsOptionalFeature): "The requested operation requires elevation.
"
>> TerminatingError(Get-WindowsOptionalFeature): "The requested operation requires elevation.
"
>> TerminatingError(Get-WindowsOptionalFeature): "The requested operation requires elevation.
"
>> TerminatingError(Get-WindowsOptionalFeature): "The requested operation requires elevation.
"
The requested operation requires elevation.
**********************
Windows PowerShell transcript end
End time: 20241028084425
**********************
Adding the PowerShell window Error Picture below :-
30-10-24 10:51 AM
Hi @KodiSrihari - sorry that you haven't had a response on this one 😞
Have you managed to get anywhere since making this post, or are you still facing this issue?
01-11-24 06:45 AM
Hi @Michael_S
Thanks for asking, i have raised and Blue Prism Support ticket and as team suggested that the error in Running the HUB PowerShell Script is due to "Not having Elevated Permission of Local Administrator".
But the User Account which we have is having Administrator access, as per Control Panel in Windows.
I am checking with my Internal Windows Network support team, on this issue.
(1)- BP HUB Script Run Sequence 1
And the HUB PowerShell Script is in the File Format.
We are opening it with Notepad > Copying the Script > Opening Windows PowerShell as Admin > Pasting the Script > Running.
If we run the Script as above and error comes up, no log files are Generating in "logs " folder as in below pic of HUB Bundle Files.
(2)- BP HUB Script Run Sequence 2
- If we Right Click on Script file > Click on Run with PowerShell.
- Here, as error occurs, Log file is generating in the "logs " folder as in below pic of HUB Bundle Files.
* But Blue prism Support Team suggested to Run the Script as "BP HUB Script Run Sequence 1 ".
* Currently, checking with internal team.
Thanks,
Srihari
01-11-24 11:17 AM
Hi @Michael_S
Now i can be able to Run the Script.
And getting the Below error log during Script Run:
Installing application FileService...
MSI Version: 5.1.0.4.
Installation of FileService exited with code 1603. Please see https://learn.microsoft.com/en-us/windows/win32/msi/error-codes for more information.
Transcript stopped
I have gone through the File Service Install error 1603, in Microsoft doc. Still could not found the Exact Reason of this error.
Please let me know if any possible resolution methods.
Thanks,
Srihari
05-11-24 09:56 AM
Hi Srihari,
It seems to me like you might be missing some steps out of the required config.
Please double check you are following all steps correctly as per the below url:
Install Blue Prism Hub and plugins
05-11-24 12:08 PM
Hi @asilarow
Thanks for the Suggestion i will double check.
During PowerShell Script Run Below 10 are Good with Installations. But For File Service , Gateway, Usm only getting the 1603 error as below.
Installation of FileService exited with code 1603. Please see https://learn.microsoft.com/en-us/windows/win32/msi/error-codes for more information.
Installed
Not Installed & Installation of Usm exited with code 1603.
I have tried to Run the Script with below to check if only File Service getting error or all services.
Example Script with Parameter Below: -
& "C:\BP_Hub\BluePrismHub-5-1\Install-hubv5.ps1" -exclude "FileService", "Gateway", "AuditService", "EmailService", "LicenseManager", "NotificationCenter", "SubmitFormManager", "SignalR", "AuthServer", "Audit", "InteractRemoteApi", "LayoutManager", "Settings", "Usm", "Alm", "Decision", "Decision Model Service", "Director", "Interact"
Thanks,
Srihari
19-11-24 12:36 PM
Hi Srihari,
Please check if the user running the installation has got the dbcreator and sysadmin roles assigned in the SQL DB.
If so, try dropping the File Service DB and creating it again.
Cheers,