Previous Topic: TroubleshootingNext Topic: Non-english Input Characters Contain Junk Characters


Policy Server Troubleshooting

The following sections detail common problems you may experience with the Policy Server during installation and the proposed solutions.

NETE_PS_ALT_CONF_FILE Environment Variable on Solaris

After installing the Policy Server on Solaris, the nete_ps_env.ksh script may have the following entry:

export NETE_PS_ALT_CONF_FILE=/export/siteminder/config/.siteminder.conf

The NETE_PS_ALT_CONF_FILE environment variable is used by the stop-all and start-all scripts, which stop and start the Policy Server’s service. The .siteminder.conf file is a temporary, run-time file created by these scripts and has no affect your CA SiteMinder® configuration.

Do not modify the NETE_PS_ALT_CONF_FILE environment variable.

Policy Server Fails to Start After Installation

Valid on Windows and UNIX Systems

Symptom:

I have installed the Policy Server, but it is not starting.

Solution:

You may have the wrong JRE version installed. Make sure you have the correct JRE version.

Note: For a list of supported CA and third-party components, refer to the CA SiteMinder® 12.52 SP1 Platform Support Matrix on the Technical Support site.

More information:

Locate the Platform Support Matrix

CA SiteMinder® Environment Variables are not set in the Profile File

Valid on UNIX

Symptom:

The Policy Server was installed without adding the CA SiteMinder® environment variables (smprofile.ksh) to the .profile file. I need to set the CA SiteMinder® environment variables manually.

Solution:

To add the CA SiteMinder® environment variables

  1. Log in to the Policy Server host system.
  2. Open a shell and navigate to siteminder_home.
    siteminder_home

    Specifies the Policy Server installation path.

  3. Run the following command:
    smprofile.ksh
    

    The CA SiteMinder® environment variables are set.

Winsock error 10054 message

Valid on Windows

Symptom:

When I try to log into the Policy Server, I receive the "Unable to proceed, winsock error 10054" message.

Solution:

One of the following could be the cause of the problem:

Working with a CA SiteMinder® License

Symptom:

Solution:

To request a CA SiteMinder® license

  1. Go to the Technical Support site.
  2. Click CA Licensing Inquires. This link is located under Address Licensing Needs.

    The CA Customer Care site opens in a new window.

  3. Click Licensing Issue Request. This link is located under Contact Us.

    An online request form opens in a new window.

  4. Complete the required information and click Submit.

To add a permanent CA SiteMinder® license to a Policy Server

  1. Request a CA SiteMinder® license.
  2. Access the Policy Server host system.
  3. Do one of the following:
  4. Copy the license.dat file to the license directory.
  5. Restart the Policy Server.

To find an existing CA SiteMinder® license

  1. Log into the Technical Support site.
  2. Click Licensing. Licensing is located on the left side under Support.

    The CA Licensing screen appears.

  3. Click View Licenses. View Licenses is located under SiteMinder and Identity Manager Licenses.

    All license details, including the respective key, appear.

To apply a CA SiteMinder® license key to the license file

  1. Access the Policy Server host system.
  2. Do one of the following:
  3. Open the license.dat file.
  4. Copy and paste the license key acquired from the Support site into the license file.
  5. Save the license file
  6. Restart the Policy Server.