You are on page 1of 1

Note: This is usually due to a configuration problem where the FMS master config

has not been updated with the proper volume/accesson id (requires an FMS restart).
It can also indicate a multisite configuration that is missing information about
the given enterprise.

You might also like