CA Client Automation

Hello,

I'm getting this error message while installing CA Client Automation. This is a new/fresh install of this suite.

DB Server (MSQL), Enterprise Manager and 3 Domain servers are all individual /dedicated virtual boxes.

The log shows this:

11/28/16 13:42:44.0329|1680:|CiCheckMDBMsSQL::checkConnection: Start
11/28/16 13:42:44.0329|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0329|1680:| dbPwd: <*******>
11/28/16 13:42:44.0329|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0329|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0329|1680:| dbName: <mdb>
11/28/16 13:42:44.0329|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0329|1680:| trying server name <SQL2012DB,1433>
11/28/16 13:42:44.0329|1680:| mdbsql_testConnection
11/28/16 13:42:44.0345|1680:| db connection: <ok>
11/28/16 13:42:44.0345|1680:|CiCheckMDBMsSQL::checkConnection: End <0>
11/28/16 13:42:44.0345|1680:| mdb connection ok
11/28/16 13:42:44.0345|1680:|CiCheckMDB::isRXXAlreadyInstalled: Start
11/28/16 13:42:44.0345|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0345|1680:| dbPwd: <*******>
11/28/16 13:42:44.0345|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0345|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0345|1680:| dbName: <mdb>
11/28/16 13:42:44.0345|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0439|1680:|CiCheckMDBMsSQL::isRXXAlreadyInstalled: End <0>
11/28/16 13:42:44.0439|1680:|CiCheckMDB::checkMDB: Start
11/28/16 13:42:44.0439|1680:| checking active sessions in MDB...
11/28/16 13:42:44.0439|1680:|CiCheckMDBMsSQL::checkActiveSessions: Start
11/28/16 13:42:44.0439|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0439|1680:| dbPwd: <*******>
11/28/16 13:42:44.0439|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0439|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0439|1680:| dbName: <mdb>
11/28/16 13:42:44.0439|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0439|1680:|CiCheckMDB::getActiveSessions: Start
11/28/16 13:42:44.0439|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0439|1680:| dbPwd: <*******>
11/28/16 13:42:44.0439|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0439|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0439|1680:| dbName: <mdb>
11/28/16 13:42:44.0439|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0454|1680:| no of active sessions: <1>
11/28/16 13:42:44.0454|1680:|CiCheckMDBMsSQL::getActiveSessions: End <0>
11/28/16 13:42:44.0454|1680:| no of active sessions: <0>
11/28/16 13:42:44.0454|1680:|CiCheckMDBMsSQL::checkActiveSessions: End <0>
11/28/16 13:42:44.0454|1680:| finished checking active sessions, found <0> sessions
11/28/16 13:42:44.0454|1680:| checking MDB version...
11/28/16 13:42:44.0454|1680:|CiCheckMDB::isCorrectMDBVersion: Start
11/28/16 13:42:44.0454|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0454|1680:| dbPwd: <*******>
11/28/16 13:42:44.0454|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0454|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0454|1680:| dbName: <mdb>
11/28/16 13:42:44.0454|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0454|1680:| file path: <F:\WindowsProductFiles_x86>
11/28/16 13:42:44.0454|1680:| version file: <F:\WindowsProductFiles_x86\version.txt>
11/28/16 13:42:44.0470|1680:| MDB version correct <TRUE>
11/28/16 13:42:44.0470|1680:| MDB version <1.4.30.-1>
11/28/16 13:42:44.0470|1680:|CiCheckMDB::isCorrectMDBVersion: End <0>
11/28/16 13:42:44.0470|1680:| finished version check
11/28/16 13:42:44.0548|1680:| found installed MDB, checking values...
11/28/16 13:42:44.0548|1680:|CiCheckMDB::checkManagerValues: Start
11/28/16 13:42:44.0548|1680:| dbUser: <ca_itrm>
11/28/16 13:42:44.0548|1680:| dbPwd: <*******>
11/28/16 13:42:44.0548|1680:| dbServer: <SQL2012DB>
11/28/16 13:42:44.0548|1680:| dbInstance: <,1433>
11/28/16 13:42:44.0548|1680:| dbName: <mdb>
11/28/16 13:42:44.0548|1680:| dbType: <IDb::MSSQLSERVER>
11/28/16 13:42:44.0564|1680:| tier: <enterpriseTier>
11/28/16 13:42:44.0564|1680:| link to domain exists: <FALSE>
11/28/16 13:42:44.0564|1680:| checking no of manager in MDB...
11/28/16 13:42:44.0564|1680:| no of domain manager: <1>
11/28/16 13:42:44.0564|1680:| Getting MDB owner...
11/28/16 13:42:44.0564|1680:| actual MDB owner: <CACLIAUTH14-EM>
11/28/16 13:42:44.0564|1680:| SetupMode is <1>
11/28/16 13:42:44.0564|1680:| Checking MDB owner...
11/28/16 13:42:44.0564|1680:| error actual MDB owner not equal to requested MDB server name <SQL2012DB>
11/28/16 13:42:44.0564|1680:|CiCheckMDB::checkManagerValues: End <-3007>
11/28/16 13:42:44.0564|1680:| error in checkManagerValues <-3007>
11/28/16 13:42:44.0564|1680:|CiCheckMDB::checkMDB: End <-3007>
11/28/16 13:42:44.0564|1680:|CiCheckMDB::finish(removeCreatedUser <FALSE>) Start
11/28/16 13:42:44.0611|1680:|CiCheckMDB::finish End <0>

It seems that this is expecting to see the SQLServer and Enterprise Manager sharing the same server or that the instance for DOMAIN server MUST be another diferent from the one for ENTERPRISE server.

How can I overcome this error?

On Client Automation Manual I find no explicit reference saying it is a must to have, lets say, one DB Server handling one instance for each component talking in "tiers" (Enterprise, Domain) or even one instance for each component talking in "servers/boxes".

Is it necesary to have an instance for each?

If so, that means that I have to run the program that creates the "mdb" several times (one per nedded instance) and naming each instance different?

Is this an installation,upgrade etc.  has this been working or is it a new install.

Sent from my Verizon, Samsung Galaxy smartphone

Hello Richard, 

This is a New install

Can you make sure that there is not a mdb database on the server ?

This usually only happens when the ca_manager is populated.

If this is a fresh install there should not be a mdb database on that SQL server.

Make sure you are pointing to the correct mdb server when you do the install and make sure you are checking the correct mdb when looking for the mdb server.

Also make sure that you are administrator in SQL to be able to see what databases are on that machine.

Thanks Gordon

But then whats the right process to install this suite on separated boxes?

1) Install SQL Server on a dedicated box

2) Install all other Servers OS with all dependencies (DB Client, .Net Frame, etc)

3) Run MDB utility to create MDB, since it is required to install Enterprise Manager

4) Install Enterprise Manager pointing to that MDB

5) Install one by one the Domain Servers pointing "to the same instance" or "to a new/diferent instace" on the same SQL Server?

6) Install all the other servers.

Hi

You need a separate MDB in a separate instance for each manager (EM or DM)

You cannot share an MDB between managers

This is documented here

Preparing to Work with a Microsoft SQL Server MDB - CA Client Automation - 14.0 - CA Technologies Documentation 

regards

Rich

In addition as of 12.9 if you are not using CCS then you do not need to install the mdb separately. the installer will lay down the mdb on the remote dbms. YOu just give the installer the correct instance details

As Rich said each manager has it's own MDB, which can either be local or remote.

If you want to centralize all your databases ,  you can put the mdb for each manager on a separate instance on the same SQL server.

Then once the DM's and EM's are up and running, you link the EM's to the DM's from the Enterprise and the data from the EM

is replicated up to the EM  and some data is replicated from the EM down to the DM

Thank you all for your answers.

I have more clear now the topic and could install with no problems the Client Management.