Hello Everyone!
We have discovered a major bug in Blue Prism 6.6 so before you update read on:
When starting a Blue Prism Server service, the service will always use the [Default] connection configuration. If you are using multiple configurations and multiple services on a one server, only 1 Blue Prism server service will be functional and that service is forced to use Default configuration instead of any other present configurations.
Example:
Both services have been created by Blue Prism BPServer.exe. When trying to start either of the services, it says that the configuration is not valid.
"Service cannot be started. BluePrism.BPCoreLib.MissingItemException: Database connection is not configured correctly"
When we examine and test the configurations on the BPServer.exe everything works as expected. When started from services.msc they will not start due to "No valid connection". We then noticed that if we configure the Default connection, the first service starts normally but the second complains that port is already taken and vice versa. If you configure the Default configuration you are able to start either of the services but not both at the same time due to port is being used. This means that on Blue Prism 6.6 you can only use Default configuration for the Blue Prism server service and that means you can run only 1 Blue Prism Server service per actual Server.
This can also be tested:
Create multiple configurations and create services for them. Configure Default configuration to be valid
Remove all configurations.
Start any one of the created services and it will start despite the configuration has been removed.
I hope that this is fixed as soon as possible.
------------------------------
Petri Kaukua
Certified Blue Prism Architect
Digital Workforce
Europe/Helsinki
------------------------------