11-08-20 08:58 PM
17-08-20 05:34 PM
Hello Steven,
OK, I see, one of the screenshots threw me. The Database Connection window is also available via the Login screen (which you'll see in a minute).
Let's try a workaround and "switch off" the Microsoft LocalDB check.
The following will remove Microsoft SQL Server 2017 LocalDB from your computer and also stop Blue Prism checking for it:
I'm now expecting you to be presented with the Login screen. However, we're in untested territory so if you get the error again, I'm also going to ask you to remove your LocalDB Connection from your configuration.
17-08-20 06:20 PM
17-08-20 07:23 PM
Hello Steven,
Excellent, that's more like it.
I can see from your screenshot that your Learning Edition license isn't yet Activated. You should have been guided through the License Activation by way if a step by step wizard.
Not to worry, simply select Not Activated within the Activation Status field. (It's within System > License)
Tip: As a part of the process, you'll be guided to our License Activation page on our website. This is normal and expected.
17-08-20 07:34 PM
23-08-20 02:46 PM
24-08-20 01:03 AM
24-08-20 08:47 AM
Hello Amy,
Your error looks similar although, from your screenshot, seems to be occurring when Blue Prism is attempting to install Microsoft SQL Server LocalDB 2017. Things to consider, do you have full admin rights to your computer, what happens when you install the Microsoft application outside of Blue Prism etc.
I'll repeat my original reply to Steven:
We saw this back in October 2019 on another thread (Learning Edition - Cannot find DB error) and it seemed the root cause of the issue was down to not having the right permission to install and setup Microsoft SQL Server LocalDB 2017.
I'll stick to the previous guidance, which was confirming whether Microsoft SQL Server LocalDB 2017 is already installed, if not, attempt to install it manually outside Blue Prism. Based on this information, we provided some further troubleshooting steps.
Tip: See the comments on 11 October and 27 November 2019.
In Summary: We're seeing a Microsoft SQL Server LocalDB error, we're trying to determine whether that same issue appears without Blue Prism being involved, this will help troubleshoot.