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

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'.

Parents
  • 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.
Reply
  • 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.
Children
No Data