DispatcherStatusHandler failure when starting Planning services

[Dev1975]

Hello everyone,

I've got a multi-server environment (BI, Planning and DB) that was working fine last week but today, the Planning server has been giving the following error:

DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=8CB1C407-6FB2-4D44-AABE-13F1864F60FF, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store.  Request refused, GUID of source is unknown.

The ContentStore for BI is separate to the PlanningStore database and there is no notification database set. The environment recently had the ContentStore re-created (exported the content, new shell DB created and content imported) and, as mentioned, things were working perfectly last week. There are some database backup jobs that run over the weekend and since then, this has happened with the Planning instance only.

I have re-registered the Dispatcher but this hasn't helped as the same error occurs. The re-start of the Planning services was successful but there was an error in the startup text as follows:

12:44:30, 'com.cognos.p2plb.clerver.TestMsgSourceGUIDHandler', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
12:44:30, '', 'Request', 'Failure'.


[Start Service]
12:45:00, 'com.cognos.p2plb.clerver.balancer.LoadBalanceRequestParameters', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
12:45:01, '', 'Request', 'Failure'.

Anyone have any ideas/thoughts/suggestions?

Many thanks...

[simi123]

Did you find the solution?. If yes, please share your ideas so everyone can see and able to resolve their errors.

thanks in advance
Simi