Resolution:
Description: This was on a new install that the server would not come up.  This can also happen with an existing server if they do cloning.

InConcert Server debug log showed: 09:01:28 00000094 t000000c7: debug: svdbinit after openDatabase
09:01:28 00000094 t000000c7: debug: svdbinit Id initialize failed -- &ltError, IC, 100>: Row Not Found.
09:01:28 00000094 t000000c7: debug: Inconcert server process aborting
09:01:28 00000094 t000000c7: debug: Row Not Found.

The most straight forward way to fix the problem is to reinitalize the database.  The user has entered a different InConcert Server id then what is on line 3 of the license.dat.  The line that starts Server_xxxxx.

This value is stored in the table server_names as server_number.  This number is used to seed all object ids in the database and can not be updating without changing all other object ids at the same time.

One customer had either cloned or done a backup restore and had a different
value for SERVER2 of ID_COUNTERS.  It is not safe to simply fix SERVER2 as they may later have an uniqueness violation later.