Restoring a Firebird vault does not work on Manage joined server - Workaround

Overview

Restoring a Firebird vault does not work on a server joined to Manage. You might see the error stack below. 

RPCScheduledJobsHelper.cpp, 3600, Processing of the external object type or value list "User" failed. (0x8004011F)
RPCScheduledJobsHelper.cpp, 2859, Processing of the external object type or value list "User" failed. (0x8004011F)
VaultManager.cpp, 3964, Processing of the external object type or value list "User" failed. (0x8004011F)
VaultManager.cpp, 997, Processing of the external object type or value list "User" failed. (0x8004011F)
AccountSynchronizator.cpp, 492, Processing of the external object type or value list "User" failed. (0x8004011F)
AccountSynchronizator.cpp, 1811, Processing of the external object type or value list "User" failed. (0x8004011F)
AccountSynchronizator.cpp, 1443, Processing of the external object type or value list "User" failed. (0x8004011F)
UserAccountOneDb.cpp, 712, Processing of the external object type or value list "User" failed. (0x8004011F)
RPCLoginsHelper.cpp, 3641, Processing of the external object type or value list "User" failed. (0x8004011F)
RPCLoginsHelper.cpp, 4193, Processing of the external object type or value list "User" failed. (0x8004011F)
RefreshExternalObjects_Private.cpp, 5946, Processing of the external object type or value list "User" failed. (0x8004011F)
RefreshExternalObjects_Private.cpp, 5946, Unspecified error. (0x80004005)
RefreshExternalObjects_Private.cpp, 4438, Unspecified error. (0x80004005)
RefreshExternalObjects_Private.cpp, 4268, Unspecified error. (0x80004005)
RefreshExternalObjects_Private.cpp, 3936, Unspecified error. (0x80004005)
RefreshExternalObjects_Private.cpp, 6478, Unspecified error. (0x80004005)
RefreshExternalObjects_Private.cpp, 6591, Unspecified error. (0x80004005)
RPCEventsHelper.cpp, 575, Unspecified error. (0x80004005)
Vault.cpp, 13707, Unspecified error. (0x80004005)
(M-Files 25.8.15085.11 2025-09-23T05:43:21.748Z)

Workaround

Instead of restoring, attach the vault.

You can use the following procedure:

1. Take the source vault offline via the admin tool.
2. Copy its vault data folder (all folders inside - metadata, filedata, and the secondary data with the indices and logs). You can zip it for easier handling as a single file.
3. Paste (unzip) the folder on the new server.
4. Use the admin tool Attach Vault context menu option (as opposed to Restore Vault) - there you give it the path(s) to the location you just used.

Solution

The situation is recorded for improvement on our internal database on ID CLOSS-986. When the fix is implemented, it can be found from the release notes https://www.m-files.com/customers/m-files-online-release-notes by its ID.