Troubleshooting 'How To Fix' Service

This topic addresses issues related to 'How To Fix' Service.

When 'How To Fix' service goes down?

'How To Fix' service goes down then a valid error message is displayed in the AppScan Enterprise (ASE) UI and on the Console logs.

The corresponding information related to the error messages that is displayed on different ASE UIs are discussed below.

Monitor tab messages
  • UI Message: CRWAS2310E Cannot connect to the How to Fix service at:<host>:<port>. Ensure that the How to Fix service is running.

  • Log Message: User will see Cannot connect to the How to Fix service at <host>:<port> log message in the console.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Liberty\usr\servers\ase\logs.

Scan tab messages
  • UI Message: Error: Cannot connect to the 'How to Fix' service. Ensure that the 'How to Fix' service is running.

  • Log Message: User will see Cannot connect to the 'How to Fix' service at <host>:<port> log message in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.

Resolution: To start 'How To Fix' service purpose perform the following:
  1. Navigate to <ASE Install Dir>\AppScan Enterprise\ArticleService\security-info folder path and open command prompt.
  2. Take CustomAdvisoriesPort value from <ASE Install Dir>\AppScan Enterprise\Liberty\etc folder path server.env file then update <port> value in java -DServer.port=<port> -Dserver.address=0.0.0.0 -Dspring.mvc.servlet.load-on-startup=1 -Dlogging.config=log4j2.xml -Dsecinfo.data.dir=data -jar security-info.jar command.
  3. Copy command to command prompt and click on enter then 'How To Fix' service will startup.

When "How to fix" service port is already in use?

If "How to fix" service port is already in use, a valid error message is displayed in the UI and in the Logs.

The corresponding information related to the error messages that is displayed on UIs are discussed below.

Monitor tab messages
  • UI Message: CRWAS2313E Cannot connect to the How to Fix service at:<host>:<port>. Ensure that the How to Fix service port is not used by any other services.

  • Log Message: User will see Cannot connect to the How to Fix service at <host>:<port> log message in the console.txt file.

  • Log Message: User will see Cannot connect to the How to Fix service at :<host>:<port>. Ensure that the How to Fix service port is not used by any other services log message in the console.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Liberty\usr\servers\ase\logs.

Scan tab messages
  • Error: Cannot connect to the 'How to Fix' service. Ensure that the port is not used by another service.

  • User will see Cannot connect to the 'How to Fix' service. Ensure that the port is not used by another service. <host>:<port> log message in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.

You can see Web server failed to start. Port <Port> was already in use log message in 'How To Fix' service secinfo.txt log file also. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\ArticleService\security-info\logs.

Resolution: Rerun the Configuration wizard with the new "How to Fix" Port.

When How to Fix information is not available in exported security reports?

If the issuetype How to Fix information is not available in the exported security reports then the error message will be displayed in the logs.

The corresponding information related to the error messages that is displayed on UIs are discussed below.

Monitor tab messages

  • You will see No How to Fix information is available for the issue type: <IssueTypeId> or could not get How to Fix information from <host>:<port> log message in the console.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Liberty\usr\servers\ase\logs.

Scan tab messages

  • You will see No How to Fix information is available for the issue type: <IssueTypeId> (OR) Could not get How to Fix information from <host>:<port> log message in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.

When issueType id does not exists in 'How To Fix' service?

If the issueTypeId does not exists in 'How To Fix' service then you will see a valid error message in the ASE UI and on the Console logs. The corresponding information is mentioned below.

Monitor tab messages
  • UI Message: CRWAS2309E issue type name is invalid or non-existing.
  • You will see an invalid or non-existing issue type:<IssueTypeId> log message in the console.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Liberty\usr\servers\ase\logs.
Scan tab log messages
  • You will see an invalid or non-existing issue type:<IssueTypeId> log message in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.

In UI when How to Fix details are not displayed (OR) User cannot expand How to Fix information headers in Internet Explorer (IE) browser?

If in the IE browser, How to fix details are not displayed when you click on "How to Fix" (OR) and not able to expand How to Fix information headers, then perform the following steps.

To unselect Display intranet sites in Compatibility view option in IE browser:
  1. Click Tools icon in IE browser right corner then it will show pop up with options list.
  2. Click on Compatibility view settings option. The Compatibility view settings pop up will show.
  3. Unselect (OR) uncheck Display intranet sites in Compatibility view check box.
  4. Click on close button.

How user can get 'How To Fix' service issues related log messages?

For resolving 'How To Fix' service related issues purpose you can get log messages using the following information.

'How To Fix' service Monitor tab issues log messages.

To enable Monitor tab logging purpose perform the following steps.
  1. Select Administration tab from left side welcome slider of ASE.
  2. Click on General Settings in Administration tab and click on Log Settings Edit button.
  3. Select Debug Log Level in Edit Log Settings and click on save button.

After you update debug log level in Monitor tab you can see 'How To Fix' service Monitor tab issues log messages in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.

'How To Fix' service scan tab log messages
  • You will see 'How To Fix' service Scan tab issues log messages in the Log.txt file. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\Logs.
'How To Fix' service log messages
  • You can see 'How To Fix' service log messages in secinfo.txt log file also. The corresponding log file path is <ASE Install Dir>\AppScan Enterprise\ArticleService\security-info\logs.