Troubleshooting
Problem
The Planning dispatcher could not be registered in the Content Store after a reboot. The Content Manager is on a separate machine.
Symptom
cogserver.log error on the Planning Server:
DPR-DPR-1026 Unable to register dispatcher in Content Manager. <server>:9305/p2pd/servlet at this time. Will retry periodically.
Message on service startup in Cognos Configuration on machine where CM is:
CM-SYS-5160 Content Manager is running in standby mode.
Cause
A 2nd Content Manager (which was, inadvertently, designated as the Primary) was discovered to be preventing the Planning dispatcher from being registered because it only referenced the "fail over" Content Manager.
Notice the port number (9305) in the error message. By default the port is 9300.
Resolving The Problem
A. If there are NO plans to use the current Primary Content Manager.
1. Stop all services
2. Identify the service of the current Primary CM and change it's Startup Type to Manual in the Service Properties
This prevents the service from starting up again during a reboot.
3. Start the services in Cognos Configuration, making sure that it is for the desired Content Manager
NOTE: This 2nd Content Manager should be uninstalled at the soonest possible time.
B. If the current Primary Content Manager WILL be kept.
1. In Cognos Configuration on the Planning server, navigate to Local Configuration --> Environment
2. Click on Content Manager URIs to highlight it, then click on the button with the pencil icon
3. In the Value - Content Manager URIs dialog box, highlight the existing URI then hit Ctrl-C
4. Change the existing server name and port to where the Primary Content Manager is
5. click on the Add button
6. Highlight the entire localhost line then hit Ctrl-V
7. Click on OK
8. Click on the Play button to start the services
.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21419291