Description:
This Document list the CA SiteMinder log file needed by support / SE to trouble shoot different components of the SiteMinder Agent for SharePoint family:
Solution:
General Guidelines for Providing Log files to CA SiteMinder Security Support Cases
To determine root cause, CA SiteMinder Security Support typically needs a certain set of data to be collected. Providing the information as described in the table below up front when the case is opened will expedite resolution.
The logs with full tracing (as opposed to partial tracing) provide the Support Engineer a great deal of insight into the state of the environment leading up to the error condition. More limited tracing or no logging is almost always insufficient
CA SiteMinder Security Support certainly understands that most production environments are not set to full logging. In these scenarios, CA will do its best to analyze the data provided however in many cases this may not provide enough information to determine the root cause of the issue and higher log levels will be requested. This document is only a baseline of data as some issues will require additional data collection which the Support Engineer will request as necessary.
Steps:
In sharepoint server side,we need to do the following steps
In Central Administration,
on the home page,
click Monitoring.
On the Monitoring page,
in the Reporting section,
click Configure diagnostic logging and select
CA Siteminder Trace and event log should select verbose and get CA siteminder log / SiteMinder Log
Problem Area | Log File(s) | Ideal Log Level |
SharePoint Server |
|
|
HTTP Head tools:
In order or preference for Support
HTTP Watch is not recommended as this is a licensed product that CA does not currently license. Because of this the information that CA support can see when they use the free copy of this software is very limited.
Release:
Component: SMSPA
CA SiteMinder log.