Previous Topic: TroubleshootingNext Topic: Agent Error Codes

Web Agent Guides › Web Agent Configuration Guide › Troubleshooting › Agent Error Codes

Agent Error Codes

Agent for IIS Troubleshooting Log

Symptom:

Is there an IIS 7.x log file that can help me troubleshoot the CA SiteMinder® Agent for IIS?

Solution:

Open the following log file:

web_agent_home\log\IIS70Trace.log

This log file contains the following types of information:

Duplicate LLAWP Error Appears in Log File

Symptom:

My log file shows the following error:

Duplicate LLAWP

Solution:

This error occurs when an application pool recycles. The application pool tries to start new LLAWP processes before the current LLAWP processes are fully shut down.

To prevent this error, configure the application pools in your IIS web server to disallow overlapping rotation. This setting forces the application pool to wait for the current LLAWP processes to stop before any new ones are started.

Note: For more information, go the IIS website and search for the phrase, "DisallowOverlappingRotation"

Custom Error Pages not Appearing

Valid on Oracle Directory Enterprise Edition (formerly Oracle iPlanet Directory Server Enterprise Edition)

Symptom:

I set either of the following configuration parameters, but users receive a generic error message from the server instead:

CSSErrorFile

Specifies the location of a custom-error message file or URL that you want to display to the users if they try to open a URL that contains possible cross-site scripting characters.

Default: No default

ServerErrorFile

Instructs the Web Agent to display a custom error page to users who encounter server errors. Specify a file path or URL for this parameter.

Default: No default

Solution:

Do the following steps:

  1. Open the instance_name-obj.conf file on your web server.
  2. Locate the following line: 
    AuthTrans fn="SiteMinderAgent"
  3. Add UseOutputStreamSize="0"to the end of the previous line, as shown in the following example: 
    AuthTrans fn="SiteMinderAgent" UseOutputStreamSize="0"
  4. Save the file, and then restart the web server.

Unable to initialize tracing error

Valid on IIS 7.x

Symptom:

I am running 32-bit and 64-bit agents on the same IIS web server. I want to record trace logs for the 32-bit agent, but I'm seeing the following message instead:

[INFO] LLAWP: Unable to initialize tracing.

The 64-bit agent trace log is not affected.

Solution:

Verify that the following configuration parameters are defined for your agent:

TraceConfigFile32

Specifies the location of the WebAgentTrace.conf configuration file that determines which components and events to monitor. Set this parameter if you have a CA SiteMinder® Agent for IIS installed on a 64-bit Windows operating environment and protecting a 32-bit Windows application. The 32-bit applications run in Wow64 mode on the 64-bit Windows operating environment. If logging is enabled but this parameter is not set, the Web Agent for IIS appends _32 to the file name.

Default: No default.

Limits: For Windows 64-bit operating environments only. Specify the configuration file name at the end of the path.

Example: (Windows 64-bit operating environments using Wow64 mode) web_agent_home\config\WebAgentTrace32.conf.

LogFileName32

Specifies the full path of a log file for a CA SiteMinder® Web Agent for IIS (on 64-bit Windows operating environments protecting 32-bit applications). The 32-bit applications run in Wow64 mode on the 64-bit Windows operating environment. If logging is enabled but this parameter is not set, the Web Agent for IIS appends _32 to the log file name.

Default: No

Limits: For Windows 64-bit operating environments only. Specify the file name at the end of the path.

Example: (Windows 64-bit operating environments using Wow64 mode) web_agent_home\log\WebAgent32.log.

TraceFileName32

Specifies the full path to the trace file for the CA SiteMinder® Agent for IIS is running on a 64-bit Windows operating environment and protecting 32-bit applications. Set this parameter if you have a CA SiteMinder® Agent for IIS installed on a 64-bit Windows operating environment and protecting a 32-bit Windows application. The 32-bit applications run in Wow64 mode on the 64-bit Windows operating environment. If trace logging is enabled but this parameter is not set, the Web Agent for IIS appends _32 to the file name.

Default: No default.

Limits: For Windows 64-bit operating environments only. Specify the trace file name at the end of the path.

Example: (Windows 64-bit operating environments using Wow64 mode) web_agent_home\log\WebAgentTrace32.log.

Enable KeepAlives When Agents and Policy Servers are Separated a Firewall

Symptom:

I use a firewall between my agent and Policy Server. Sometimes the agent returns a 500 error when I try to access a page.

Solution:

Enable Keepalives on the agent by doing the following steps:

  1. Locate the following environment variable on the computer hosting the web agent: 
     SM_ENABLE_TCP_KEEPALIVE
  2. Set the value of the previous environment variable to 1.

Japanese Pages Rendered Improperly (153202, 153609)

Symptom:

When a user is redirected to another page for one of the following reasons, content in the resulting page is not rendered properly.

Solution:

Add the following line to the http.conf file of your Apache web server:

“BrowserMatch ".*" suppress-error-charset”

Save the http.conf file and restart your web server for this setting to take effect.

Non-english Input Characters Contain Junk Characters

Symptom:

When I install or configure SiteMinder components in the console mode on UNIX machines, few non-English input characters are not displayed correctly in the console window.

Solution:

Verify terminal settings of your console window and confirm that the console does not clear high (8th) bit of input characters by executing the following command:

stty -istrip