I can run the same scan under "Create a Basic scan" but when I try to schedule the same scan, it always fails. Any idea on where I can look at logs to get a better idea of the failure?
Cybersecurity
DevOps Cloud
IT Operations Cloud
I can run the same scan under "Create a Basic scan" but when I try to schedule the same scan, it always fails. Any idea on where I can look at logs to get a better idea of the failure?
It depends on where the failure is. Does a scan get created and try to start? If so, look at the the scan log of that scan. If the scan is not created, then I would look at at the logs under C:\ProgramData\HP\HP WebInspect\Schedule.
Thanks for the reply Ethan. It looks like, according to the error logs, that an authentication error is occurring. Specifically, the error says "Login failed for user "domain name\computer hostname" is trying to authenticate to the backend SQL database. I have copied the entire error below and replaced the domain name and user name with "domain name\user name" but the user name is actually the computer host name and not a user name.
2024-07-22 14:19:52,580 ERROR [1 ] SPI.Scanners.Web.Scanner in logging_LogEvent, this.Scan == null
2024-07-22 14:19:52,580 ERROR [1 ] SPI.Scanners.Web.Framework.DataManager.Providers.SQLServer.SQLServerFrameworkDataProvider in SQLDataProvider.CreateDBConnection, SqlException thrown ,rethrowing number=18456,sql=(null)
System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'domain name\username$'.
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 SPI.Scanners.Web.Framework.DataManager.Providers.SQLServer.SQLServerFrameworkDataProvider.RetryOpen(IDbConnection iDbConnection)
at SPI.Scanners.Web.Framework.DataManager.Providers.SQLServer.SQLServerFrameworkDataProvider.CreateDBConnection()
ClientConnectionId:71eb50e1-e2a1-4aab-9de4-3023de6e300a
Error Number:18456,State:1,Class:14
Any thoughts?
You will encounter this error if WIRCServer (WebInspect API) service is configured to run as Local System and you have WebInspect configured not to use SQLExpress.
Login failed for user '<domain>\<machine hostname>$'.
as Local System is the “user” account trying to login to the database. You can resolve this by changing the Log On As for the WebInspect API service to an account that has access to the database (usually a service account or the user where running WI GUI is successful).
Hi Ethan, Sorry for not getting back to you earlier. Other projects took precedence. No bueno on changing the "Log on as" section in the services.msc panel. I used the account that I sign onto the PC (and this account also has access to the database) and the log file still says "Login failed for user 'domain\computername". It keeps trying to login to the SQL database as a computer name as you described above. Any ideas on what to troubleshoot next? Really appreciate the help!
I originally missed where you were encountering this while scheduling scans. Did you try changing the log on account for the WebInspect Scheduler Service?
Yes, that is what you had suggested in your original answer - "You can resolve this by changing the Log On As for the WebInspect API service to an account that has access to the database (usually a service account or the user where running WI GUI is successful). I can run the application to perform a normal scan with this same account and it runs successfully. I t just seems like the authentication part to this whole thing appears as thought it still trying to use computer name rather than the user account that I use to run the application.
My apologies for the confusion. There are two services in question:
My original post was for WebInspect API, my follow-up was to do the same for the WebInspect Scheduler Service.
That did the trick, Ethan! Thank you very much.