IBM Cognos 10.2.1 FP1 : scheduled jobs failed

[maxcoder]

Hi,

We've been using the distributed environment on running Windows Server 2008 R2 Enterprise Edition OS. Recently , I've upgraded my system from 10.1 to 10.2.1 FP1. But when to running scheduled jobs then I got the following the error. All of those configurations are configured  as correctly. All scheduled jobs is ends like below error. sometimes it works and sometimes does not work

Error details;                                                         
DPR-ERR-2072 Unable to load balance a request with absolute affinity,   
most likely due to a failure to connect to the remote dispatcher. See   
the remote dispatcher detailed logs for more information. Check the     
health status of the installed system by using the dispatcher           
diagnostics URIs. Handler trace back: [the_dispatcher] com.cognos.pogo.
handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.
cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.   
pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.   
pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.       
clerver.LoadBalanceHandler

[Grim]

There is a configuration error in one of the components. Most likely a dispatcher. Check to ensure that there are no typos in the configs. Specifically check the dispatcher and gateway machines. Anywhere that there is a dispatcher URI.

[maxcoder]

There is a configuration error in one of the components. Most likely a dispatcher. Check to ensure that there are no typos in the configs. Specifically check the dispatcher and gateway machines. Anywhere that there is a dispatcher URI.

Hi ,

As mentioned before your message I've been controlling all those configurations. But I have some those questions. Like I said I have a distributed environment.
Here is my environment :
- 3 Dispatcher/App Tier :
1st Dispatcher/App Tier  : Local Configuration -Environment ->
External dispatcher  URI http://test03:9300/p2pd/servlet/dispatch
Internal dispatcher  URI http://test03:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications http://test03:9300/p2pd/servlet/dispatch
Content Manager URIs http://testcm01:9300/p2pd/servlet and http://testcm02:9300/p2pd/servlet
  2st Dispatcher/App Tier  : Local Configuration -Environment ->
External dispatcher  URI http://test04:9300/p2pd/servlet/dispatch
Internal dispatcher  URI http://test04:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications http://test04:9300/p2pd/servlet/dispatch
Content Manager URIs http://testcm01:9300/p2pd/servlet and http://testcm02:9300/p2pd/servlet (is it sort important? )
3st Dispatcher/App Tier  : Local Configuration -Environment ->
External dispatcher  URI http://test05:9300/p2pd/servlet/dispatch
Internal dispatcher  URI http://test05:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications http://test05:9300/p2pd/servlet/dispatch
Content Manager URIs http://testcm01:9300/p2pd/servlet and http://testcm02:9300/p2pd/servlet (is it sort important? )
-----------------------------------------------------------------------------------------
- 2 Content Manager(CM) :
1st Content Manager(CM) active : Local Configuration -Environment ->
External dispatcher  URI http://testcm01:9300/p2pd/servlet/dispatch
Internal dispatcher  URI http://testcm01:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications http://testcm03:9300/p2pd/servlet/dispatch    ??????
Content Manager URIs http://testcm01:9300/p2pd/servlet and http://testcm02:9300/p2pd/servlet  (is it sort important? )

2st Content Manager(CM) passive : Local Configuration -Environment ->
External dispatcher  URI http://testcm02:9300/p2pd/servlet/dispatch
Internal dispatcher  URI http://testcm02:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications http://testcm03:9300/p2pd/servlet/dispatch    ??????
Content Manager URIs http://testcm01:9300/p2pd/servlet and http://testcm02:9300/p2pd/servlet (is it sort important? )

----------------------------------------------------------------------------------

- 3 Web Gateway :
1 st web gateway : Dispather URIs for gateway : http://test03:9300/p2pd/servlet/dispatch/ext,http://test04:9300/p2pd/servlet/dispatch/ext,http://test05:9300/p2pd/servlet/dispatch/ext
2 st web gateway : Dispather URIs for gateway : http://test05:9300/p2pd/servlet/dispatch/ext,http://test04:9300/p2pd/servlet/dispatch/ext,http://test03 :9300/p2pd/servlet/dispatch/ext  (is it sort important? )

Last question : I assuming there are typos in the configs. (cogstartup.xml) My question is : How do I create new cogstartup.xml file for all those system? is there any special procedure for distributed environment?

thanks in advance,
kind regards,

[Grim]

To start with a fresh cogstartup.xml follow the steps for regenerating crypto keys but skip the step for restoring the cogstartup.xml file.

[maxcoder]

To start with a fresh cogstartup.xml follow the steps for regenerating crypto keys but skip the step for restoring the cogstartup.xml file.

thanks for your answer. But I have no answer another question.  So is there any wrong my configuration?

[Grim]

Without knowing the environment it's hard to say. Plus I'd have to get the cogstartup.xml and cmplst.txt files from each server/install to determine if there is anything wrong with the config.

[sunosoft]

Grim - I am not sure but I did this very long back - To generate fresh cogstartup.xml file if we stop the services and rename the current cogstarup.xml file as cogstartup.xml.old. Then while starting the services fresh cogstarup.xml file will be generated automatically.


@maxcoder - Please check what all services are enbaled on your dispatcher servers. Try with dipatcher diagnostic tool to check if all dispatchers are in sync. Also in such cases sometimes setting routing rules and testing the issue on each dispatcher individually helps to find more info. While working with routing rules, it will be great if you generate fresh logs, by stopping the services and renaming the old log file.

[maxcoder]

Grim - I am not sure but I did this very long back - To generate fresh cogstartup.xml file if we stop the services and rename the current cogstarup.xml file as cogstartup.xml.old. Then while starting the services fresh cogstarup.xml file will be generated automatically.


@maxcoder - Please check what all services are enbaled on your dispatcher servers. Try with dipatcher diagnostic tool to check if all dispatchers are in sync. Also in such cases sometimes setting routing rules and testing the issue on each dispatcher individually helps to find more info. While working with routing rules, it will be great if you generate fresh logs, by stopping the services and renaming the old log file.

Hi,

First of all thanks for your answer. I will try your those instructions. But  I have short question too. What can I define in Dispatcher URI for external applications on content manager? So  dispatcher URI or something else?

Kind Regards,

[SomeClown]

Content Manager dispatcher URI: your current settings in the example appear correct. (It's not used by CM itself but client tools like Framework Mgr, etc).  Dispatchers find Content Manager, not the other way around.
Sort orders:

• CM URI - not too important - Content Manager startup determines primary/secondary. It's recommended that configuration order match desired primary/secondary
• Gateway dispatcher URI - make the order the same only for consistency - order isn't too important (just determines who routes initial request)

To provide more detail on other answers, look at your Cognos services inside Configuration and see if any are turned off.  That would be the first place to look.  Absolute affinity routing error says Cognos tried to run something on a specific server and the service was not available on that server.

       

[maxcoder]

Content Manager dispatcher URI: your current settings in the example appear correct. (It's not used by CM itself but client tools like Framework Mgr, etc).  Dispatchers find Content Manager, not the other way around.
Sort orders:

• CM URI - not too important - Content Manager startup determines primary/secondary. It's recommended that configuration order match desired primary/secondary
• Gateway dispatcher URI - make the order the same only for consistency - order isn't too important (just determines who routes initial request)

To provide more detail on other answers, look at your Cognos services inside Configuration and see if any are turned off.  That would be the first place to look.  Absolute affinity routing error says Cognos tried to run something on a specific server and the service was not available on that server.

     

I assuming there is a wrong define in Content Manager dispatcher URI. Because  another content manager URI instead of the Dispatcher URI is defined. I guess due to this something goes wrong in the system. Am I Correct?

[SomeClown]

Probably not - if Content Manager is not configured properly, the environment typically does not even start.  Things appear to be running, so it's unlikely that.

Your issues are probably more related to what components have been installed to which servers, and if there was leftover configuration picked up (like routing or services not running).

[sunosoft]

I am agree with SomeClown.

Need not to worry about CM configuration.

[Saivenkat7]

Hi maxcoder,

Were you able to resolve the issue? We are facing similar issue now, please let us know how you resolved it?

Thanks
Sai