Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

BURP Suite Enterprise fails installing with an existing MS SQL server

ILGUIZ | Last updated: Sep 05, 2018 11:46PM UTC

After receiving a JDBC URL and credentials that appear passing a connection test, the installer proceeds to creating a database. This fails with a non-descript message. The installer log file has a liquibase error that indicates attempting to use an SQL dialect incompatible with MS SQL. 17:47:45.223 [main] DEBUG liquibase - default_schema_changelog.xml: true::update_status_oracle::PortSwigger: Computed checksum for inputStream as 1983f87ef7ff7a338f73db6dad35128c 17:47:45.223 [main] DEBUG liquibase - default_schema_changelog.xml: true::update_status_oracle::PortSwigger: Computed checksum for 7:933d3f700d65049e5da311350208fca4:7:0e8b4cdc5c0c5831abe19ef1faa30891:7:1983f87ef7ff7a338f73db6dad35128c: as 1bc9c68af8a3a636f25bf51928cd0b00 17:47:45.232 [main] DEBUG liquibase - Executing QUERY database command: SELECT [LOCKED] FROM [dbo].[DATABASECHANGELOGLOCK] WHERE [ID]=1 17:47:45.233 [main] DEBUG liquibase - Lock Database 17:47:45.236 [main] DEBUG liquibase - Executing UPDATE database command: UPDATE [dbo].[DATABASECHANGELOGLOCK] SET [LOCKED] = 1, [LOCKEDBY] = 'MLISCCLDA0143 (10.201.130.153)', [LOCKGRANTED] = '2018-09-05T17:47:45.234' WHERE [ID] = 1 AND [LOCKED] = 0 17:47:45.239 [main] INFO liquibase - Successfully acquired change log lock 17:47:45.250 [main] DEBUG liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Running Changeset:true::find_scan_status_mssql::PortSwigger 17:47:45.251 [main] DEBUG liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Changeset true::find_scan_status_mssql::PortSwigger 17:47:45.251 [main] DEBUG liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Reading ChangeSet: true::find_scan_status_mssql::PortSwigger 17:47:45.252 [main] DEBUG liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Executing Statement: DROP FUNCTION IF EXISTS dbo.find_scan_status; 17:47:45.252 [main] DEBUG liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Executing EXECUTE database command: DROP FUNCTION IF EXISTS dbo.find_scan_status; 17:47:45.271 [main] ERROR liquibase - default_schema_changelog.xml: true::find_scan_status_mssql::PortSwigger: Change Set true::find_scan_status_mssql::PortSwigger failed. Error: Incorrect syntax near the keyword 'IF'. [Failed SQL: DROP FUNCTION IF EXISTS dbo.find_scan_status;] 17:47:45.272 [main] DEBUG liquibase - true::find_scan_status_mssql::PortSwigger: Release Database Lock 17:47:45.273 [main] DEBUG liquibase - true::find_scan_status_mssql::PortSwigger: Executing UPDATE database command: UPDATE [dbo].[DATABASECHANGELOGLOCK] SET [LOCKED] = 0, [LOCKEDBY] = NULL, [LOCKGRANTED] = NULL WHERE [ID] = 1 17:47:45.276 [main] INFO liquibase - true::find_scan_status_mssql::PortSwigger: Successfully released change log lock 17:47:45.277 [main] DEBUG com.zaxxer.hikari.pool.PoolBase - bewspool - Reset (autoCommit) on connection ConnectionID:2 ClientConnectionId: 56e5c0c4-5f7e-490c-abbc-b3a4b82c29ae ---END--- return value is 1 [INFO] com.install4j.runtime.beans.actions.misc.RunExecutableAction [ID 3472]: Variable changed: db_migration_code=1[class java.lang.Integer] [ERROR] com.install4j.runtime.beans.actions.misc.RunExecutableAction [ID 3472]: return value is 1 Execute action not successful after 7325 ms [INFO] com.install4j.runtime.beans.actions.misc.RunExecutableAction [ID 3472]: Rollback barrier reached [INFO] com.install4j.runtime.beans.actions.control.RunScriptAction [ID 9537]: Execute action Property rollbackScript: null Property script: com.install4j.script.I4jScript_Internal_261 Property rollbackSupported: false [ERROR] com.install4j.runtime.beans.actions.control.RunScriptAction [ID 9537]: Execute action not successful after 1 ms

PortSwigger Agent | Last updated: Sep 06, 2018 08:13AM UTC

Hi Ilguiz, What version of SQL Server are you running, and at which compatibility level? Our database initialization scripts are relying on the "DROP FUNCTION IF EXISTS" syntax which is only available in SQL Server 2016 onward.

Burp User | Last updated: Sep 12, 2018 06:30PM UTC

Version 2014 here. C:\Users\XXXXX>osql -E -w 9999 -Q "print @@version" Microsoft SQL Server 2014 - 12.0.4213.0 (X64) Jun 9 2015 12:06:16 Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

PortSwigger Agent | Last updated: Sep 13, 2018 08:00AM UTC