Using an empty Database throws SystemDB does not exist error
When attempting to use an empty database the alter scripts references SystemDB
I get the following error when pointing to a sql 2008 r2 server with a catalog named Bartender
Failed to execute sql command. Line: 168 - 196 Database 'SystemDB' does not exist. Make sure that the name is entered correctly.
This issue also extended to using an already created DB, when attempting to connect to a previously created DB, Even if its named SystemDB it will run the create scripts everytime....0
Also when creating a database on a sql server the system service user is not added to the security area...0
I believe you are running into a known bug with 2016 R3, and related to connecting to an existing BarTender System Database.
As a workaround, I recommend setting and connecting to the BarTender System Database using the Windows Command line. You can find the detail instructions here.
Here are some examples of commands to connect to existing system database. The first example runs the BarTender system database wizard without user dialog and generates a log file. Also sets up a connection to an already existing BarTender system database. It will create a new BarTender system database on the SQL server if one does not already exists. The 2nd example is similar but uses SQL Server authentication instead. Note, when you use the /Silent parameter to run the database connection setup so Windows do show, you have to specify a location to generate a log file. Also, make sure to replace the parameters with the appropriate SQL Server name, database name, username, and password.
- SystemDatabaseWizard.exe /Silent /Log=C:\log /Type=Connect /Server=<SQLServername> /Authentication=Windows /Database=BarTender
- SystemDatabaseWizard.exe /Silent /Log=C:\log /Type=Connect /Server=<SQLServername> /Authentication=SQL /UserName=JohnDoe /Password=test /Database=BarTender
Really close this does work for
creating a DB from scratch
connecting to an existing bartender DB
It does not work for
updating an empty DB
I was able to get to my end goal. One thing that I think would be great is that an empty DB would be detected if the only objects in the DB are not tables. I had a view that is automatically created on catalog creation that was causing the GUI to not show the DB even though there was no physical data.
Still seeing this in 2016 R5. Tried to delete config.xml, cycle BT System Service but still got the error. Ended up having to have BarTender create the new database (called 'bartender') rather than updating an empty database named 'bartender'.0
Please sign in to leave a comment.