Highlighted
kpatterson1 Absent Member.
Absent Member.
10379 views

Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Hi,

I have upgraded to WebInspect 10.40 and now when I try and run reports I get an error.

Has anyone reported this?

ERROR:

[5/14/2015 2:07:56 PM]: Report Failed System.Data.SqlClient.SqlException (0x80131904): Cannot open user default database. Login failed.

Login failed for user 'Kxxxxxxxx\xxxxxx'.

…..

…..

[5/14/2015 2:07:56 PM]: Exception in Viewer doWork: Cannot open user default database. Login failed.

Full error:

ERROR:

[5/14/2015 2:07:56 PM]: Report Failed System.Data.SqlClient.SqlException (0x80131904): Cannot open user default database. Login failed.

Login failed for user 'xxxxxxx/xxxxxxx'.

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)

   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)

   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)

   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at HP.AppSec.Reporting.DataProviders.ScanDataProvider.d(IQuery A_0, Boolean A_1, IRtfFontToFieldMapper A_2, IPropertyToFieldMapper A_3)

   at HP.AppSec.Reporting.DataProviders.ScanDataProvider.GetData(IQuery queryDescriptor, Boolean topZeroFlag, IRtfFontToFieldMapper rtfFontMapper, IPropertyToFieldMapper propertyMapper)

   at HP.AppSec.Reporting.ReportDataSource.getReportData(IQuery queryDescriptor, Boolean topZeroFlag, IRtfFontToFieldMapper rtfFontMapper, IPropertyToFieldMapper propertyMapper)

   at HP.AppSec.Reporting.ReportDescriptor.getReportRunInstance(ActiveReport3 clonedReport, ReportDescriptor mainReport)

   at HP.AppSec.Reporting.ReportDescriptor.getLinkedReportRunInstance(ActiveReport3 clonedReport, ReportDescriptor parentReport, ReportDescriptor mainReport, Dictionary`2 dynamicMapping)

   at HP.AppSec.Reporting.ReportEventHandlers.SubReportFormatHandler.handleLinkedSubReports(LinkedSubReportModel lsrm, Section sendingSection)

   at HP.AppSec.Reporting.ReportEventHandlers.SubReportFormatHandler.handleActiveReportSubReports(SubReport sr, Section sendingSection)

   at HP.AppSec.Reporting.ReportEventHandlers.SubReportFormatHandler.formatHandler(Object sender, EventArgs ea)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at DataDynamics.ActiveReports.Section.#7kf()

   at DataDynamics.ActiveReports.Section.#Clf(ActiveReport3 report)

   at #kyd.#TD.#1mf(Section section)

   at #kyd.#TD.#Nqf()

   at #kyd.#TD.#Iqf(Page newPage, Single left, Single top, Single right, Single bottom, UInt32 flags, UInt32& status)

   at DataDynamics.ActiveReports.Section.#wlf(ActiveReport3 parentReport, #Oaf rData)

   at #kyd.#Haf.#Ukf(Int32 pieceIndex)

   at #kyd.#Haf.#Skf()

   at #kyd.#Haf.#lW(Section section, Int32 insPos)

   at #kyd.#Haf.#lW(Section section)

   at #kyd.#TD.#Nqf()

   at #kyd.#TD.#Iqf(Page newPage, Single left, Single top, Single right, Single bottom, UInt32 flags, UInt32& status)

   at DataDynamics.ActiveReports.ActiveReport3.#Smf()

   at DataDynamics.ActiveReports.ActiveReport3.Run(Boolean syncDocument)

   at HP.AppSec.Reporting.ReportDescriptor.runReport(Boolean syncDocument)

ClientConnectionId:6daed19b-7fb4-488a-aff6-3d40a3b45b52

[5/14/2015 2:07:56 PM]: Exception in Viewer doWork: Cannot open user default database. Login failed.

Login failed for user 'xxxxxxxxxxxx\xxxxxxxxx'.

Labels (2)
Tags (1)
0 Likes
1 Solution

Accepted Solutions
Outstanding Contributor.. pprofili Outstanding Contributor..
Outstanding Contributor..

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Close WebInspect,  navigate to the folder referenced in the error message (usually C:\PROGRAMDATA\HP\HP WEBINSPECT\REPORTING\) and delete the files

  • ReportDatabase.mdf
  • Report Database_log.LDF

Reopen WebInspect and try the report generation again.

0 Likes
9 Replies
Micro Focus Expert
Micro Focus Expert

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

You did not specify, but given the Login Failed error I will assume you are using a Standard or Enterprise edition of SQL Server rather than SQL Express.  To generate reports, WebInspect uses write-space in the same database it uses for storing its scans.

  • Are you still able to Import or run new Scans in WebInspect without such errors?  Does the Manage Scans feature on the Start Page tab work appropriately to display the scans?

  • Does this error occur immediately when clicking Generate Report, after selecting the template(s) and Run, or part-way through the processing job?

  • Were there other related errors appearing in the Windows Event Viewer, or within WebInspect Log Viewer tool?

  • Check under the Edit menu > Application Settings > Database panel.  Are the details for the database still valid and operational?

  • When you SmartUpdated from 10.30, there may have been a prompt that the database schema needed an update.  Did you opt to have it update that automatically, or did you pass the displayed SQL query to the DBAs to run directly?  Fortify Support (support.fortify.com) can assist you if this is a concern.

  • Has the SQL Server been updated, perhaps to a version not supported such as SQL 2014?  (See the Fortify 4.30 System Requirements document at   )

-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
0 Likes
nizampathan Absent Member.
Absent Member.

Re: Upgraded to WebINspect 10.40 (from 10.30)  Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Close the tool and kill the sql server process in task manager. Reopen the tool and try again, I hope it will work.

0 Likes
kpatterson1 Absent Member.
Absent Member.

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

This did not work.

We now have a 2nd user that upgraded and is facing same issue.  Thanks

0 Likes
kpatterson1 Absent Member.
Absent Member.

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Hi, thanks for your help.

FYI.  I now have 2nd user that upgraded to 10.40 and haveing same issue.

  • Are you still able to Import or run new Scans in WebInspect without such errors?  Does the Manage Scans feature on the Start Page tab work appropriately to display the scans?
    • Yes - Import or run new Scans in WebInspect without such errors 
    • Yes - Manage Scans feature on the Start Page tab work appropriately to display the scans

  • Does this error occur immediately when clicking Generate Report, after selecting the template(s) and Run, or part-way through the processing job?
    • Go to Reports >Select a scan >Check the checkbox of a scan >Next > Select Vulnerability Checkbox > Keep defefault checkboxes > Press Finish
    • > Error [5/18/2015 7:36:22 AM]: Report Failed System.Data.SqlClient.SqlException (0x80131904): Cannot open user default database. Login failed. >[5/18/2015 7:36:22 AM]: Exception in Viewer doWork: Cannot open user default database. Login failed.
    • Login failed for user xxxxxxxxxx\xxxxxxxx'.
  • Were there other related errors appearing in the Windows Event Viewer, or within WebInspect Log Viewer tool?
    • Do not see any errors in log
  • Check under the Edit menu > Application Settings > Database panel.  Are the details for the database still valid and operational?

  o    Radio button “On” for “Use SQL Server Express” 

  • When you SmartUpdated from 10.30, there may have been a prompt that the database schema needed an update.  Did you opt to have it update that automatically, or did you pass the displayed SQL query to the DBAs to run directly?  Fortify Support (support.fortify.com) can assist you if this is a concern.
    • Did not notice a prompt
  • Has the SQL Server been updated, perhaps to a version not supported such as SQL 2014?  (See the Fortify 4.30 System Requirements document at Fortify Product Documentation  )
    • Running SQL 2008
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Based on the Application Settings, it seems you are using SQL Express 2008.  Odd, because Express usually works flawlessly with updates compared to (normal) SQL Server users.

  • For WebInspect 10.30, the supported SQL Express 2008 versions had been R2 SP3 or just SP3.  They dropped the 2008 Express SP3 option with WebInspect 10.40, only supporting SQL Express 2008 R2 SP3, plus the other Express 2012 options listed.  I'm not sure how important that distinction might be, or if it only indicates that QA did not regression test with SP3.

  • WebInspect normally expects to use the default Named Instance of SQL Express, "SQLEXPRESS", although I have also seen it use the alternate "MSSQLEXPRESS".  Can you verify that in the Services Control Panel that the Instance Name shown in the service name matches one of those, e.g. "SQL Server (SQLEXPRESS)"?

  • Have you stopped that SQL Server service, plus killed any lingering "sqlservr.exe" Processes, then restarted the service?

  • Are you running that SQL Server service with Network Service, Local System, or a specific Administrator account?

  • Are you running WebInspect as a local Administrator account or attempting to use the Run As feature?

  • Have you escalated to Fortify Support?

  • If you choose to uninstall and reinstall SQL Express (requires reboot), your scans will still remain untouched in the default WebInspect folder as defined under the Edit menu > Application Settings > Directories.

-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
0 Likes
Outstanding Contributor.. pprofili Outstanding Contributor..
Outstanding Contributor..

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Do you use Roaming profiles?

0 Likes
New Member.. arikanter1
New Member..

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

I have this same problem as well after an upgrade to 10.50.  Report Failed System.Data.SqlClient.SqlException (0x80131904):


REPORTDATABASE.MDF' cannot be opened because it is version 706. This server supports version 663 and earlier. A downgrade path is not supported.

Cannot open user default database. Login failed.

0 Likes
Outstanding Contributor.. pprofili Outstanding Contributor..
Outstanding Contributor..

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Close WebInspect,  navigate to the folder referenced in the error message (usually C:\PROGRAMDATA\HP\HP WEBINSPECT\REPORTING\) and delete the files

  • ReportDatabase.mdf
  • Report Database_log.LDF

Reopen WebInspect and try the report generation again.

0 Likes
New Member.. arikanter1
New Member..

Re: Upgraded to WebINspect 10.40 (from 10.30) Now can't run reports.in Viewer doWork: Cannot open user default database. Login failed.

Jump to solution

Thanks Phil-- I tried that after I posted, and that fixed it. Glad you got yours working as well.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.