Issues with Audit, System Status and Primary Content manager

[Gaby]

Hi everybody,

I need the advice of some of the brilliant minds in this forum.

I have a Primary Content Manager server (Server A) and a Stand-By Content Manager (Server B).

I had issues with the audit reports the didn't showed results even thought all the setting was correct. When I reviewed the audit package in Framework, I notice the reports logs were there but the user session logon was not recorded when Server A was primary. I modified the package to change the relation from were logon to reports table from 1:1 <-> 1:n to 0:1 <-> 1:n to make the reports run.

During the testing, and after many re-starting of the servers reviewing the audit set up, I notice that in some occasions we have user logon data. That happen when Server A is running as Stand-By and Server B was running as primary.

I leave it that way for some time as nothing else was affected, however I was trying today to setup the metrics (Server B is running as primary) all the status of the services and servers were showing as unknown. So, I switch them back and they are showing again available.

So,
1.- Where I can start reviewing why the users logon are not recorded when the Primary Content manager is running as designed? (not Stand-by)
2.- Why when the Stand-By Content manager is running as primary it cannot identify the status of the services?

I think both issues are related, but no idea where to look at.

Thanks,

Gaby.

[sunosoft]

Hi,

Did you check the logging level set for both of Content manager services ?

I believe you will be stopping server A to make server B as active content manager.

In this scenario, when you stop service for Content manager A then make sure you dont have any running process with cognos service account on that server. After stopping cognos service just go to task manager and make sure that nothing is there with Cognos service account.

Now before starting this server A make sure that your server B is active and all services are showing correct status. Dont make any hurry to start server A.

If still B is having issue you can give a try by restarting the complete environment in correct order.