Recurrent Messages
Abnormal operation when refreshing a private workspace
Symptom: Message stating "Could not refresh your private workspace".
Reason: Rejects occurred when importing private workspace updates into the reference repository.
Solution:
1. Examine the reject file Rmmjj.MGL (eg: MGL R07150000.MGL) in the user work repository (<repository>\USER\<user code>).
3. Delete reject files that are no longer needed.
For as long as reject files are not deleted, a warning persists when connecting to MEGA.
Environment version
Symptom: Message "Your environment and site are not of the same version" when opening an environment from the MEGA administration console" (or "Your environment and site are not of the same version. Your environment requires updating. Refer to documentation for how to carry out this action").
Click
OK.
Another window appears displaying a second message: "Your environment requires an update for compatibility with your version of MEGA". Do you wish to run this procedure now? ".
Reason: It is possible that the environment has not been created, or is not at the same version level as the site referencing it: an update is therefore proposed:
if you have a physical backup of environment data, accept modification by clicking
Yes.
If this is not the case, refuse the modification by clicking
No to exit the MEGA data administration console. Then execute physical backup of data.
"Later" option not proposed at disconnect
Symptom: When you exit MEGA, the dialog box that appears does not propose the "Later" option to save your modifications.
Reason:
• You are not connected to MEGA (Windows Front-End) and the license used does not have technical module MEGA Lan.
You prevent other users from dispatching their private workspaces.
• You are connected to MEGA (Web Front-End), in a public workspace.