FAQ

Create a trace file

When running into an issue creating a trace file will help us to diagnose it.

1. Set the custom server setting TRACE to X.
2. (Set the custom server setting TRACE_FILE to C:\OPENBI\OpenBiTrace.txt for example.)
3. Restart the open bi server. (Only required if TRACE wasn't already set to X.)
4. Redo your actions that led to the error.
5. Set the custom server setting TRACE to INFO or ERROR or (emtpy) or remove it.
6. Restart the open bi server.

Provide us the OpenBiTrace.txt file.

See also:

• https://openbi.info/blog/troubleshooting-tracing-with-open-bi

Service does not start

This can happend for example when the license is expired. To see the error there are two options:

1. Start the open bi server by running the OPENBI\ibssolution.bioxRepository.exe as administrator. Errors are shown in red.
2. Check the Windows Event Viewer for any errors in the Application section with Source = OpenBIServer.

Reset admin password

To reset the admin password make sure the open bi server is stopped, open a CMD or PowerShell as administrator and run:

$ OPENBI\ibssolution.bioxRepository.exe –-RESET_ADMIN=X

Check if the default admin login works again, close the CMD or PowerShell and start the open bi server as before.

See also:

• https://openbi.info/blog/how-to-reset-the-admin-password

Database login failed issue

This could be because the SqlLocalDB version was updated to a newer version.

Cannot open database "\OPENBI\DATABASE\DATABASE.MDF" requested by the login. The login failed.

Check which versions are currently installed:

$ SqlLocalDB versions

Check the version of the MSSQLLocalDB instance:

$ SqlLocalDB info MSSQLLocalDB

1. Stop and delete the old MSSQLLocalDB instance

$ SqlLocalDB stop MSSQLLocalDB
$ SqlLocalDB delete MSSQLLocalDB

2. Create and start a new MSSQLLocalDB instance

$ SqlLocalDB create MSSQLLocalDB
$ SqlLocalDB start MSSQLLocalDB

Backup database

To backup the database while the server is running you need to run SQL queries for the user that started the open bi server.

When running as a service this will be the Local System user by default. So you need the PSTools to start a PowerShell session for the Local System user like this:

$ psexec -i -s powershell.exe

Then install the SqlServer PowerShell module

$ Install-Module -Name SqlServer

Backup the database:

$ Invoke-Sqlcmd -Query "BACKUP DATABASE [C:\OPENBI\Database\database.mdf] TO DISK = 'C:\database.bak' WITH FORMAT;" -ServerInstance "(LocalDb)\MSSQLLocalDB" -Database "C:\OPENBI\Database\database.mdf"

When PowerShell modules are not allowed use the sqlcmd-utility which requires these tools:

1. Microsoft Visual C++ Redistributable
2. ODBC Driver for SQL Server

$ sqlcmd -Q "BACKUP DATABASE [C:\OPENBI\Database\database.mdf] TO DISK = 'C:\database.bak' WITH FORMAT;" -S "(LocalDb)\MSSQLLocalDB" -C -d "C:\OPENBI\Database\database.mdf"