DPR 1035 Error in a distributed environment

[pkrishnaq]

Hello there ,

I am experiencing an unusual issue in my distributed environment. Everything was up and running until i made a reset of my content store password.

I got 2 app servers: app1 and app2 .  The app1 restarted fine and is good after content store password reset. However, I am having issues with the server app2. I get the DPR DPR 1035 Error .
I tried changing the dispatcher password on both the machines, but to no success. Do i have to reboot the boxes? These are production environments, so any immediate suggestions are greatly appreciated.
I get this during restart :

15x.127.924.xxx:9300   4804   2011-05-13 22:42:04.402   -6   BootstrapConfigurePublish   na      0   BootstrapConfigurePublish-thread   DISP   727   1   Audit.Other.dispatcher.DISP.com.cognos.pogo.contentmanager.coordinator.CMBootstrap   StartService   dispatcherBootstrap      Info      DPR-DPR-1002 Successfully registered the dispatcher http://app2:9300/p2pd in Content Manager.
15x.127.924.xxx:9300   4804   2011-05-13 22:42:04.527   -6   BootstrapConfigurePublish   na      0   BootstrapConfigurePublish-thread   DISP   727   1   Audit.Other.dispatcher.DISP.pogo   pogo   com.cognos.pogo.contentmanager.coordinator.ConfigurationCMQuery      Failure   <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message></messages>   Dispatcher is missing, will reregister


Thank you very much in advance! Please HELP!

[AussiePete2011]

Hi there

I gather that App1 also had the content Manager installed?  Does app2 have the content manager installed?  If not, you need to open the configuration in App2 and locate the Notification entry and see if there is a database entry there.  This sometimes points to the content store as well if you have not created a separate Notification store.

Test all the DB connections.
Also, you should see a better message from the details when you attempt to start the dispatcher from the Configuration.
paste this info in and we'll see what the real problem is.
Cheers
Peter B

[SIM0N]

As well as checking ALL the configured database connections (as Pete says) you could try going into the the Admin interface and unregistering all the Dispatchers - they should then re-register.

[bvk.cognoise]

Hi kratos,

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.
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.


thanks
bvk