New cognos installation sometimes trying to register itself in the CM of old ins

[prikala]

Have you ever seen this, what could be the problem:

I have two cognos versions installed in the same server:
- Cognos 10.2.0 (no fp) at port 9301
- Cognos 10.2.2 FP2 at port 9302

There are no traces of port 9302 in cogstartup.xml of 10.2.0 verion
and no traces of 9301 in cogstartup.xml of 10.2.2 version.

And yet, sometimes, not sure after what, 10.2.2 environment starts complaining:
   DPR-DPR-1026 Unable to register the dispatcher in Content Manager.
        <serveraddress>:9301/p2pd/servlet at this time.
        Will retry periodically
Luckily this fails because port 9301 belongs to the old 10.2.0 environment.
Restart of 10.2.2 fixes things.

What makes 10.2.2 environment think it can talk to the 9301 port? How does it guess it exists?

10.2.2 environment was built starting from empty contentstore and then
importing full content store backup (cognos deployment archive).
Port 9301 can not be seen in dispatcher list of 10.2.2 version cognos administration.

[AM]

maybe a messed up setting in cognos configuration somewhere?

You can unregister dispatchers from the System tab in Cognos Adminsitration, if you do that do they come back?