DPR-ERR-2072 Unable to load balance a request with absolute affinity

This error message appears when you test the connection to a JDBC data source.

Here is the full text of the message:

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 [wrapped_lb_forwarder] com.cognos.pogo.auth.NewAuthHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler

The DPR-ERR-2072 error has several possible causes:

  • The dispatcher and the dataset-service have the same port value
  • Incorrect database server name or port value
  • Metadata service or query Service is not started
  • The firewall blocks the network traffic to the database server
  • Incorrect routing rules

Resolving the problem

To check for each possible cause, and remedy if necessary, follow these steps:

  1. Start Cognos Configuration.
  2. Check for port conflicts.
    1. Click Environment.
    2. Look at the port number values for the External dispatcher URI, Internal dispatcher URI, and Dataset Service port number properties.
    3. If the port numbers for the dispatchers and the Dataset service URI are the same, change the value of the Dataset service port number to an available value.
    Tip: It is a good practice to increment the port value by a 100, if the result value is available.

    For more information, see Changing a port or URI setting.

  3. Check the database properties.
    1. Click Data Access > Notification > database_name.
    2. Ensure that the properties Database server with port number or instance name and Database name have the correct values.
  4. Check that all of the required services are started.
    1. Click Environment > IBM Cognos services.
    2. Ensure that all the services are set to True.
    3. Right-click IBM Cognos and select Start to start all of the services.
    Tip: You can see problems that are related to the metadata service or the query service in the logs and in the error message. You can also inspect them further manually, or by using a task manager.
  5. Ensure that the firewall is not blocking network traffic to the database server.

    Check that the firewall configuration does not block ports that are used by the database server. For more information, see Review the default port settings and IBM Cognos Application Firewall.

  6. Ensure that the routing rules are configured correctly.

    For more information, see Setting routing rules for dispatchers.