Welcome
Welcome to the HCL AppScan Enterprise 10.6.0 documentation, where you can find information about how to install, maintain, and use HCL AppScan Enterprise.
Accessibility features for AppScan® Enterprise
Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
Overview
Learn general information about the product.
Installing
Learn how to install the product.
Upgrading and migrating
Learn how to upgrade the product.
Integrating
Learn how to integrate the product with other solutions.
DevOps
Learn how to extend the product with REST APIs and plugins.
Best practices
Learn best practices for using the product.
Configuring
Learn how to configure the product.
Administering
Learn how to administer the product.
Managing application risk
Follow this workflow to manage application security risks in your organization.
Troubleshooting and support
To help you understand, isolate, and resolve problems with your HCL® software, the troubleshooting and support information contains instructions for using the problem-determination resources that are provided with your HCL products.
- Troubleshooting a problem
  Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and explain how to resolve the problem.
- Template: Contacting HCL® Support
  HCL® Support provides assistance with product defects, answers FAQs, and helps users resolve problems with the product.
- Troubleshooting the Dynamic Analysis Scanner
  Learn how to troubleshoot the Dynamic Analysis scanner.
- Troubleshooting the Enterprise Server
  Learn how to troubleshoot the Enterprise Server.
- Messages
  These messages explain serviceability codes for: internal product messages, scan log messages, and web Services messages
Reference
Review reference information for the product.
Glossary

CRWAE1505W

Scanned page does not match recorded page: <URL>.

During playback, each URL in the login sequence is checked to see if it matches the URLs that were recorded. The scan stops at the first scanned page that does not match the recorded page. For example, if cookies or parameters are not tracked, this error might occur.

Check the HTTP Request responses to determine what caused the error.
If you have identified any session cookies that were missed, you must configure their names in the scan. Go to the Parameters and Cookies page on the content scan job.
- Select the cookies or parameters you want to track and click the "Track" button on the Edit Parameters and Cookies page.
- Click Add. Select 'Cookie' as the Type. You can enter a full name or a regular expression as the name. Select Session ID: Track this parameter during scan. AppScan Enterprise Server will track this session cookie and update the value when needed during the scan. Click Done.