Unable to start SiteMinder Policy Server due to error "Crypto provider not configured"
search cancel

Unable to start SiteMinder Policy Server due to error "Crypto provider not configured"

book

Article ID: 54629

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Description:

I am trying to start up a newly deployed instance of the policy server, but all I am getting is an error message in my smexec.log file that says "Crypto provider not configured". None of the other log files are being generated. Any idea what this means?

Solution:

The SiteMinder Excecutive (smexec) will fail upon startup if it cannot correctly read the sm.registry. The first operation it performs is the initialization of the crypto provider, if the operation to read the crypto provider configuration from the sm.registry fails, smexec will exit, logging the "Crypto provider not configured" error message.

Please check if the sm.registry file under $NETE_PS_ROOT/registry has the right permissions and if it is in the correct format.

Environment

Release:
Component: SMPLC