The following sections detail common problems you may experience with the Policy Server during installation and the proposed solutions.
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.
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 Platform Support Matrix on the Technical Support site.
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
Specifies the Policy Server installation path.
smprofile.ksh
The CA SiteMinder® environment variables are set.
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:
Important! If you are accessing this graphical user interface on Windows Server 2008, open the shortcut with Administrator permissions. Use Administrator permissions even if you are logged in to the system as an Administrator. For more information, see the release notes for your CA SiteMinder® component.
Symptom:
Solution:
To request a CA SiteMinder® license
The CA Customer Care site opens in a new window.
An online request form opens in a new window.
To add a permanent CA SiteMinder® license to a Policy Server
Specifies the Policy Server installation path.
To find an existing CA SiteMinder® license
The CA Licensing screen appears.
All license details, including the respective key, appear.
To apply a CA SiteMinder® license key to the license file
Specifies the Policy Server installation path.
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
Symptom:
When I attempt to uninstall the Policy Server, Web Agent, SDK, or the documentation, the uninstallation program stops and issues one of the following error messages:
Solution:
Make sure the JRE is in the PATH variable.
To set the JRE in the PATH variable
To set the JRE in the PATH variable
Run the following commands:
Specifies the location of your JRE.
Valid on Windows
Symptom:
When I try to install Adobe Acrobat, the installation program hangs.
Solution:
If the Acrobat Reader installation program hangs while the Policy Server service is running, stop it using the Policy Server Management Console’s Status tab. After stopping the service, the installation program should start.
Important! If you are accessing this graphical user interface on Windows Server 2008, open the shortcut with Administrator permissions. Use Administrator permissions even if you are logged in to the system as an Administrator. For more information, see the release notes for your CA SiteMinder® component.
Symptom:
When I use Active Directory as a user store, the Policy Server issues error messages that it cannot connect to this store.
Solution:
When creating an Active Directory-based user store, make sure you specify a fully qualified host name (for example, host.domain.com) in the Administrative UI and do not use the machine's IP Address. Moreover, make sure you can ping host.domain.com and domain.com from the machine where the Policy Server is installed since Active Directory sends referrals to the Policy Server that are identified by the fully qualified host name. If the fully qualified host names are invalid and unreachable, the Policy Server issues error messages.
Valid on Windows and UNIX Systems
Symptom:
During Authorization, I receive the "AE failed to load library 'smjavaapi'. System error: The specified module could not be found." error message.
Solution:
Set the PATH variable to <SiteMinder_installation>\config\JVMOptions.txt for Windows or the LD_LIBRARY_PATH to <SiteMinder_installation>/config/JVMOptions.txt for UNIX systems.
Copyright © 2013 CA.
All rights reserved.
|
|