There is a UUID in the Windows registry (or in the Linux config file) that identifies that Helix ALM server. When a database is created, that UUID is stored in the database to make sure that only one Helix ALM server will be writing to the database. Since the Helix ALM server caches some information, it is important that a second Helix ALM server is not simultaneously making changes.
If you received this error, then it is likely the result of moving your Helix ALM server to a new machine. Perforce support staff can help with this situation, or you can look at the following knowledgebase articles (not the exact situation you are describing but they are related).