It would help to report what OS and OS version you are using. The obvious potential issue here is that you are using a very, very old version of server and thus an update might very well result in your system no longer being compatible with software this old.
thanks for your reply Phil. The OS is windows 2008 x64 with SP2. I did try to roll the server back to the state before windows updates and no help. Also, my new test installation on different boxes, I don't even install windows updates and any anti-virus scan. I thought of Windows Update breaking, too but no luck!
If you already have server up on the net, your second install on "different boxes" will likely trip this error unless those "boxes" are not connected to the network.
I am aware of that. My current server is offline, decommissioned off the domain (domain account deleted). Those test boxes were brought up one at a time as trial on different domains and also in workgroup and still no go! it seems like license expired but it's not true because other department having older version like 3.0 or 4.0
My post from yesterday; could not save it because of the limitation due to spammers (will stop posting afterwards)
We have had this - but always when a second instance of FMS with the same serial# was in the same network. therefore:
any chance that there is a second installation of FMS in the same network? Usually this message is true (FMS5). The second instance will show this message...
Maybe restarting the server could help (when a phantom instance seem to be detected)
There are more than one service for FMS5 when my old brain remembers correctly. (not sure if the '~helper' process will cause this too)
Was the update on more than one machine installed - could be that FMS was disabeled on the second machine - but was activated by restarting..