01-04-20 02:43 PM
Answered! Go to Answer.
02-04-20 01:54 PM
Hello Shraddha,
Thank you for the extra information.
We seem to have resolved the original error "The file '' is invalid". I suspect the restart resolved this as, thanks to your screenshot, we can see that Microsoft SQL Server 2017 LocalDB was installed today and your other screenshots show the registry key is setup correctly.
However, you now have a different error "An error occurred whilst configuring Blue Prism localdb", which I do not recognise.
Questions:
I'm hopeful that there is something in the error which indicates the problem you are facing.
Workaround:
If not, as you want a quick resolution, the following will workaround the problem by switching you to Enterprise mode. Which may be beneficial as I see you already have SQL Server installed on your computer.
02-04-20 08:18 AM
Hello Shraddha,
We saw this error for the first time in February 2020.
Error: Blue Prism Trial and Learning Edition: Database Setup Error: The file '' is invalid
Resolution: Restart computer and reopen Blue Prism
Root Cause: We believe the computers impacted would recently have had a Windows update that requires a restart. If a restart is not preformed, then new items that go into the Windows Registry go to a 'Virtual Area' until a restart is performed. Therefore, our Database setup is unable to read the Key which states where the location of the MS SQL Server 2017 LocalDB is.
Other Community posts:
02-04-20 08:57 AM
Hello Shraddha,
We saw this error for the first time in February 2020.
Error: Blue Prism Trial and Learning Edition: Database Setup Error: The file '' is invalid
Resolution: Restart computer and reopen Blue Prism
Root Cause: We believe the computers impacted would recently have had a Windows update that requires a restart. If a restart is not preformed, then new items that go into the Windows Registry go to a 'Virtual Area' until a restart is performed. Therefore, our Database setup is unable to read the Key which states where the location of the MS SQL Server 2017 LocalDB is.
Other Community posts:
02-04-20 12:01 PM
Hello Shraddha,
Oh no, that's not what I expected. Everyone else who has restarted their computer, has resolved the issue.
Not to worry, we'll go back to basics and start off with some troubleshooting steps we've previously used.
Questions:
Rationale for asking: The information may help us narrow down the cause of the issue.
Steps to troubleshoot:
If Microsoft SQL Server 2017 LocalDB is not installed, move to next step:
My guess right now is that the LocalDB key exists, but the data is not set correctly to the location of Microsoft SQL Server 2017 LocalDB. If this is the case, populating the Data in the key may resolve, but not actually tell us what caused the issue in the first place.
Let me know how you get on with the above and either myself or another community member will attempt to help further.
Screenshot:
02-04-20 12:16 PM
Hello Shraddha,
We saw this error for the first time in February 2020.
Error: Blue Prism Trial and Learning Edition: Database Setup Error: The file '' is invalid
Resolution: Restart computer and reopen Blue Prism
Root Cause: We believe the computers impacted would recently have had a Windows update that requires a restart. If a restart is not preformed, then new items that go into the Windows Registry go to a 'Virtual Area' until a restart is performed. Therefore, our Database setup is unable to read the Key which states where the location of the MS SQL Server 2017 LocalDB is.
Other Community posts:
02-04-20 12:48 PM
Hello Shraddha,
Oh no, that's not what I expected. Everyone else who has restarted their computer, has resolved the issue.
Not to worry, we'll go back to basics and start off with some troubleshooting steps we've previously used.
Questions:
Rationale for asking: The information may help us narrow down the cause of the issue.
Steps to troubleshoot:
If Microsoft SQL Server 2017 LocalDB is not installed, move to next step:
My guess right now is that the LocalDB key exists, but the data is not set correctly to the location of Microsoft SQL Server 2017 LocalDB. If this is the case, populating the Data in the key may resolve, but not actually tell us what caused the issue in the first place.
Let me know how you get on with the above and either myself or another community member will attempt to help further.
Screenshot:
02-04-20 01:54 PM
Hello Shraddha,
Thank you for the extra information.
We seem to have resolved the original error "The file '' is invalid". I suspect the restart resolved this as, thanks to your screenshot, we can see that Microsoft SQL Server 2017 LocalDB was installed today and your other screenshots show the registry key is setup correctly.
However, you now have a different error "An error occurred whilst configuring Blue Prism localdb", which I do not recognise.
Questions:
I'm hopeful that there is something in the error which indicates the problem you are facing.
Workaround:
If not, as you want a quick resolution, the following will workaround the problem by switching you to Enterprise mode. Which may be beneficial as I see you already have SQL Server installed on your computer.
02-04-20 02:51 PM
Hello Shraddha,
Thank you for the extra information.
We seem to have resolved the original error "The file '' is invalid". I suspect the restart resolved this as, thanks to your screenshot, we can see that Microsoft SQL Server 2017 LocalDB was installed today and your other screenshots show the registry key is setup correctly.
However, you now have a different error "An error occurred whilst configuring Blue Prism localdb", which I do not recognise.
Questions:
I'm hopeful that there is something in the error which indicates the problem you are facing.
Workaround:
If not, as you want a quick resolution, the following will workaround the problem by switching you to Enterprise mode. Which may be beneficial as I see you already have SQL Server installed on your computer.
02-04-20 09:24 PM
Hello Shraddha,
OK, so we know we resolved the first issue and now we're hitting an issue with Microsoft SQL Server 2017 LocalDB. Unfortunately, we need this part working to automatically create the Blue Prism database to hold your data.
So, we're going to completely strip Blue Prism off your computer by uninstalling it and removing all the files so that when we reinstall, we are trusting that all the right file and folder permissions are setup correctly.
The following steps are extracted from 6.7 Getting started | Blue Prism Trial and Learning Editions (Page 6)
Completely strip and then reinstall Blue Prism:
This should install Blue Prism, then ask you for a password to use with your Blue Prism admin user account, install LocalDB and set you up a Blue Prism database.
(Only use the following if the database setup fails again)
If the database setup fails again and you want a quicker resolution, the following will workaround the problem by switching you from Learning Edition to Enterprise install mode. Which may be beneficial as I see you already have SQL Server installed on your computer.
Note: You'll still have Blue Prism Learning Edition, there is just extra steps to create a database.
Workaround:
03-04-20 09:33 AM
Hello Shraddha,
OK, so we know we resolved the first issue and now we're hitting an issue with Microsoft SQL Server 2017 LocalDB. Unfortunately, we need this part working to automatically create the Blue Prism database to hold your data.
So, we're going to completely strip Blue Prism off your computer by uninstalling it and removing all the files so that when we reinstall, we are trusting that all the right file and folder permissions are setup correctly.
The following steps are extracted from 6.7 Getting started | Blue Prism Trial and Learning Editions (Page 6)
Completely strip and then reinstall Blue Prism:
This should install Blue Prism, then ask you for a password to use with your Blue Prism admin user account, install LocalDB and set you up a Blue Prism database.
(Only use the following if the database setup fails again)
If the database setup fails again and you want a quicker resolution, the following will workaround the problem by switching you from Learning Edition to Enterprise install mode. Which may be beneficial as I see you already have SQL Server installed on your computer.
Note: You'll still have Blue Prism Learning Edition, there is just extra steps to create a database.
Workaround: