Empty node with no servers causing problem

[Former Member]

We are installing BO 4.1 on a server that used to be part of a BO 4.0 cluster.  We have uninstalled 4.0 and installed 4.1 but now our 4.0 system is not running.  The only service that will run is the CMS - all other services are stopped and will not start.  i can only assume it is something to do with the node for the second server still being present with no services - any ideas anyone.

NB this is a live production server so any help gratefully appreciated

[joshua_kuhn]

For clarity, let's assume server1 is the BI4.0 system and server2 is the BI4.1.

When you installed BI4.1, did you choose a new CMS db?  Assuming you pointed the BI4.1 install to a new db instance and didn't update the existing BI4.0 tables, you should be ok.  Before installing BI4.1, did you uncluster this node from the 2 node cluster?  In other words, does Server1 still think it belongs to a cluster in which server2 is a member?  This is the situation I believe you're in.

As a quick test, stop BI4.1 completely and stop/restart the BI4.0 system.  If BI4.0 starts while BI4.1 is stopped, then good news, your BI4.0 database was probably not updated during the BI4.1 install.  The trick is the next step which is unclustering server2 from server1.  For this, I would ensure the BI4.1 system is fully stopped and you may want to also make a backup of the CMS db on both systems prior.  Once you have all your backups completed (BI4.1 = stopped, BI4.0 = running) you will want to create a new SIA on the BI4.0 system with the same name as the old BI4.0 SIA you uninstalled.  You'll do this in the CCM (central configuration manager).  The SIA name you choose is the same name as you see in the CMC for the node with the missing services.  Choose the option to create a new SIA with no services.  The port you choose should be different than your existing BI4.0 CMS is using on the same machine.  The new SIA you create will automatically be linked to the existing one you see in the CMC without the services.  During this process you'll need to login to the running CMS to authenticate.  Once it creates the new SIA (with the old name), don't start it.  Immediately after, choose the 'X' at the top of the CCM to delete it.  This will not only delete the SIA you just created in the CCM, but it will also delete the old node from the BI4.0 CMS database which happens to be looking for a CMS over on the BI4.1 host.  Once this is cleaned up, and each server is running independantly of the other you should be ok to start the opposite installation and run both in parallel.

[Former Member]

Could you let us know whether the CMS Db of 4.1 and 4.0 are same.