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
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.)
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.5420Copyright (C) Microsoft Corporation 1998-2004. All rights reserved.
RegAsm : warning RA0000 : No types were registered
Where I can find the prerequisites ?
CA Identity Governance Installation Guide › Installing Additional Components › 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:
You have installed the Client Tools on a Windows computer that can communicate with the CA Identity Governance server and the database server.
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.
look at this:
Missed the Microsoft Visual C++ 2005 SP1 Redistributable Package x86 or x64
==> found in Chapter 2: System Requirements page 19. <===
Thanks for your help, The problem was that I needed the MS SQL Server Native Client