Symantec IGA

  • 1.  CA Role and Compliance Manager error connecting to database

    Posted Mar 05, 2015 11:18 AM

    Hi, I trying to use the windows interface CA Role and Compliance Manager, if I work with the files works ok, but when I want to connect to database I have the following error

     

    Provider cannot be fount. It may not be properly installed

     

    Any idea of what can be happening

     

    Thanks



  • 2.  Re: CA Role and Compliance Manager error connecting to database

    Posted Mar 05, 2015 12:32 PM

    Hi Alejandro.

     

    The error "Provider cannot be found ..." is related to data access layer used to communicate with the database.

    Is mandatory to install all the prerequisite packages (I don't remember if it use a old ODBC or a.NET connection).

    I will review my notes, meanwhile please could you check:

     

    - Which RCM Client Tool version are you using ? x64 ?

    - Check if you installed all prerequisite (.NET framework, etc.)

     

    regards, Roberto



  • 3.  Re: CA Role and Compliance Manager error connecting to database

    Posted Mar 05, 2015 01:22 PM

    Hi I installed using this procedure, is x64 I ran the step 3 also but in the first I got the following error

     

    C:\Windows\Microsoft.NET\Framework64\v2.0.50727>regasm.exe "C:\Program Files\CA\
    RCM\Client Tools\Software\Microsoft.Web.Services3.dll"
    Microsoft (R) .NET Framework Assembly Registration Utility 2.0.50727.5420
    Copyright (C) Microsoft Corporation 1998-2004.  All rights reserved.

    RegAsm : warning RA0000 : No types were registered

    C:\Windows\Microsoft.NET\Framework64\v2.0.50727>

     

    Where I can find the prerequisites ?

     

     

     

     


     

    Install Client Tools

    Use the Client Tools to import and modify data, and analyze, construct and administer the role hierarchy. Install the Client Tools on a Windows computer that can communicate with the CA Identity Governance server and the database server.

    Follow these steps:

    1. On a Windows computer, run the .msi file you prepared earlier:
      • On a 64-bit computer, run CA-RCM-rel#-Client-Tools-x64.msi
      • On a 32-bit computer, run CA-RCM-rel#-Client-Tools-x86.msi
      The Client Tools installation wizard opens.
    2. Complete the installer following the wizard prompts. If you selected to install additional components, the installation prompts you for the required files:
      • To install the UUID and IM Connector tools, locate the CA-RCM-rel#-Client-Tools-Open-Source.zip file.
      • To install the Online Help, locate the CA-RCM-rel#-Language-Files.zip file.
      The installer runs and installs the CA Identity Governance client tools on the computer.
    3. (64-bit computers only) Run the Microsoft Assembly Registration Utility:
      1. Open a command line window and navigate to the following folder: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
      2. Enter the following commands: regasm.exe "C:\Program Files\CA\RCM\Client Tools\Software\Microsoft.Web.Services3.dll" regasm.exe "C:\Program Files\CA\RCM\Client Tools\Software\SageSOAP.dll"

      You have installed the Client Tools on a Windows computer that can communicate with the CA Identity Governance server and the database server.



  • 4.  Re: CA Role and Compliance Manager error connecting to database

    Posted Mar 06, 2015 06:50 AM

    Hi Alejandro,

     

    Are you using MS-SQL Server or Oracle as database ?

    I remember that based on which database you are connecting, it is necessary to install a client to deploy some DLLs.

     

    Please review carefully the documentation regarding setting this.

     

    regards, Roberto



  • 5.  Re: CA Role and Compliance Manager error connecting to database

    Posted Mar 06, 2015 06:52 AM

    look at this:

     

    Missed the Microsoft Visual C++ 2005 SP1 Redistributable Package x86 or x64

    ==> found in Chapter 2: System Requirements page 19. <===

     

    regards, Roberto



  • 6.  Re: CA Role and Compliance Manager error connecting to database

    Posted Mar 06, 2015 12:13 PM

    Thanks for your help, The problem was that I needed the MS SQL Server Native Client