DPR-DPR-1035 Dispatcher detected an error

DPR (Dispatcher) Errorcodes DPR-DPR
1

Symptom
In a distributed environment, when starting one of the Application Tier servers a “DPR-DPR-1035 Dispatcher detected an error” message appears in the details of the service starting in Cognos Configuration although the service does start successfully and appears to be working, i.e., reports execute successfully on it and there are no errors returned to end users, This server appears as “Unavailable” in Cognos Administration (under Status -> System) even though it is fully operational including executing new report requests

Problem
A “DPR-DPR-1035 Dispatcher detected an error” message appears in the details of the service starting in Cognos Configuration when starting up the App Tier only install. The dispatcher status is ‘Unavailable’ in Cognos Administration, but everything else appears to work correctly.

Cause
The affected dispatcher has a different Dispatcher password set in its Cognos Configuration, than that set for the active Content Manager.

Solution
Open up Cognos Configuration and select Environment.
On the Dispatcher password setting, make sure that all the dispatchers in the environment have set the same password.
The default dispatcher password is not blank! If you do not know the password, change on all servers the password and restart the servers again.

2

Symptom
In Cognos Connection:
CM-SYS-5170 Content manager is unable to clean deleted referenced objects
CM-SYS-5003 Content manager is unable to access the content store. Verify your database connection parameters and then contact your database administrator.
CM-CFG-5065 A content manager configuration error was detected while attempting to execute the content initialization script
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically
DPR-DPR-1035 Dispatcher detected an error

Problem
Unable to start the Cognos 8 Service

Cause
SQL Server was configured to allow only 3 concurrent connections to the instance where the Cognos databases were located.

Solution
Change the setting to allow unlimited concurrent connections to the instance.
Steps:

  1. Open SQL Server Enterprise Manager
  2. Right-mouse click on the SQL Server Registration (computer name) and click on Properties.
  3. Access the Connections tab - Change the Maximum concurrent user connections to 0 for unlimited or a higher number to allow the required connections from Cognos 8.