Release Notes › Web Agent Release Notes › Defects Fixed › Defects Fixed in 6.x QMR 4 › Failure at Startup if LogFileName Parameter Was Not Set (40850)

Previous Topic: Password Services Potentially Vulnerable (46107)

Next Topic: User Not Challenged When the OverrideIgnoreExtFilter Parameter Set to a Substring (43106)
Failure at Startup if LogFileName Parameter Was Not Set (40850)

Symptom:

The Web Agent failed to start if you did not specify the LogFileName configuration parameter.

Note: This issue affected all Web Agents except IIS 6.0 and Apache 2.0 Agents.

Solution:

The Web Agent starts successfully if you leave the LogFileName parameter blank.