19-02-20 06:32 AM
19-02-20 09:57 AM
20-02-20 06:34 AM
20-02-20 08:44 AM
Hell Fei Ye,
With the Blue Prism Trial and Learning Edition installation, we deploy Microsoft SQL Server 2017 LocalDB, create an instance called .\BluePrismLocalDB and within that instance a database call BluePrism.
We have seen this issue before and we think we've prevented it happening within the next release of Blue Prism, which as I type this will be v6.7 which we expect to release within the next month or so.
Question: Have you previously had Blue Prism setup and running on this computer?
Rationale for asking: This error has been reported a few times and up to now we've been unable to replicate to prevent it happening. It seems to occur when someone setups up Blue Prism Trial or Learning Edition, then removes some of it and attempts to install it again. The reason for my question is to understand whether you have received the error is a similar way to other people or there is something else causing the issue.
To resolve the issue, the following steps seems to have resolved for other people:
Completely remove Blue Prism from your system and install Blue Prism Trial or Learning Edition again:
If its previously worked, I suspect when you clear down and reinstall, everything should work again. I suspect that Microsoft SQL Server 2017 LocalDB thinks the Blue Prism instance and database is still there, but you have removed them from the file system.
It would be good for the community if you let us know how you get on. This will help the next person who sees this error.