PRB: Database not upgraded and logging disabled after upgrading WebMarshal

Expand / Collapse

This article applies to:

  • WebMarshal 6.X and 7.X


  • Database did not upgrade when upgrading WebMarshal
  • Database logging disabled


When you upgrade WebMarshal to version 6.1 or above, the SQL database could fail to upgrade. This issue can occur when the Windows or SQL account being used as the "Operational User" to log data to the WebMarshal database does not have sufficient privileges to upgrade the SQL database. 

If necessary, the upgrade process prompts for credentials of a user with the required privilege to upgrade the database (database owner privilege).

Note: Windows administrator accounts and the SQL "SA" user have this privilege by default.

If you cancel the credentials request, the WebMarshal software will upgrade correctly, but database logging will be disabled until the database is upgraded.            


To manually upgrade the database follow the steps below:

  1. In the WebMarshal Console click Tools and select Global Settings or Server and Array Properties.
  2. In the left pane select Reporting Database or Database Logging. Make sure that you have checked the box Enable database logging.
  3. Click Create Database.
  4. On the Create Database window, enter the credentials of a user that has the required privileges to upgrade the database.

    Note: Do not check the box Recreate the database. 

  5. On the Create Database window, click OK. The database will be upgraded.
    • Note: If this action returns the error SQL Server or instance not found see below.
    • On the Database Logging window, click Change User to re-select the Operational User if necessary.
    • Click OK and then Apply.

    Server or instance not found

    This issue can occur if the SQL Server is configured to listen only on IPv4, but the server name resolves to an IPv6 address.

    • On some Windows versions this can happen if you use "localhost" as the server name.
    • To resolve this issue, enter the SQL Server name as an IPv4 address, or use a server name that can be resolved to an IPv4 address. Then try again to upgrade the database.
    • For a local connection, try replacing localhost\ with\ (keep the same instance name if one was present, for example:\SQLEXPRESS)
    • You can also use SQL Server Configuration Manager to change the listening ports or protocols. See Microsoft documentation.

    To contact Trustwave about this article or to request support:

    Rate this Article:

    Add Your Comments

    Comment submission is disabled for anonymous users.
    Please send feedback to Trustwave Technical Support or the Webmaster