What difference is there between logging on to Deski (12.3.6.1006) with System set to “@xxx.yyy.zzz.com” vs “xxx.yyy.zzz:8400”?
We’ve finally migrated to Windows 7, and where previously either way worked fine, now if we use the “xxx.yyy.zzz:8400” format, BO gets itself confused and can’t automatically import universes or recognise previously imported ones. Manually importing a single universe makes it all work fine for the remainder of that session.
If we log in with System of the format “@xxx.yyy.zzz.com”, then it behaves correctly.
The @ sign indicates a cluster name; without the @ sign, the name is interpreted as a server (host) name. Things can get messy if you have a cluster name that matches a host name of a different CMS.
For example, if your production cluster is named “@BO”, and there is a server on the network named “bo”, but hosting a different CMS, you will have problems.
Specific to DeskI, it keeps local copies of universes in directories named for the cluster. I can’t imagine a scenario that would cause the behavior you’re describing, but I imaging it has something to do with the locally-cached cluster member list.
(BOB member since 2002-08-29)