Scanning results in "Communication Error" in AppScan Standard 9.0

最新推荐文章于 2017-07-03 11:39:00 发布

炀大人

最新推荐文章于 2017-07-03 11:39:00 发布

阅读量470

点赞数

分类专栏：运维文章标签： appscan

运维专栏收录该内容

7 篇文章

订阅专栏

本文介绍了解决IBM Security AppScan Standard 9.0.x版本中出现的“通信错误”问题的方法。即使应用程序可访问，扫描启动时仍可能出现该错误。通过禁用服务器故障检测功能可以避免这一问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Technote (troubleshooting)

Problem(Abstract)

Attempts to start scanning with IBM Security AppScan Standard version 9.0.x result in "Communication Error", even if the application is accessible.

Cause

The issue could be that the application responses to the AppScan system down checks took a some time, and AppScan declared "Communication error" even if AppScan could communicate with the application.

Resolving the problem

Workaround:

Disable the server down check by setting to False the following two options:

Scan Configuration -> Advanced Configuration -> Server-down detection: Check for "server down" in Explore
Scan Configuration -> Advanced Configuration -> Server-down detection: Check for "server down" in Test

Note: Disabling the server-down function will not have any critical impact on the scan. The only impact is that if there is a communication problem, AppScan will take a longer time to report it, or it may report it a form of another error message.