Problem
The following error is returned when attempting to validate platform credentials or in the Burst or
XDC activity log during LOG ON:
Unable to connect to cluster @boprod to retrieve CMS member list. Locally cached member list not
present. Logon cannot continue
Cause
The issue only occurs when using a BusinessObjects platform where connection type is Local Client. The registry
settings used by the BusinessObjects Client Tools does not contain the desired CMS name or CMS cluster name.
Solution
Making the CMS connection from the client writes the CMS name to the BusinessObjects registry key.
Bryan Baca
Problem
The following error is returned when attempting to validate platform credentials or in the Burst or
XDC activity log during LOG ON:
Unable to connect to cluster @boprod to retrieve CMS member list. Locally cached member list not
present. Logon cannot continue
Cause
The issue only occurs when using a BusinessObjects platform where connection type is Local Client. The registry
settings used by the BusinessObjects Client Tools does not contain the desired CMS name or CMS cluster name.
Solution
Making the CMS connection from the client writes the CMS name to the BusinessObjects registry key.