Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
General approach for troubleshooting plug-in issues
To effectively resolve a plug-in issue, you should first isolate the issue to the server, plug-in, or to context, and use the following guidelines:
Identify the steps to reproduce the error.
Review the error message to identify relevant configuration settings. For information on error messages reported by the plug-in server, see Error-messages-8501-to-8799.
If the plug-in failed to load, check the plug-in logs.
If the plug-in is of the type Filter and if it has failed to load, the filter log displays the ARERR 8755 error. For example, ARERR 8755. The specified plug-in does not exist. DSO.FILTERCONFIGURATION Where DSO.FILTERCONFIGURATION is the name of the plug-in. Review the error message to identify the plug-in encountering the error and the plug-in server, which hosts the plug-in.
If you receive the ARERR 8755 error message, check whether the AR System Administration: Plugin Server Configurationform includes the plug-in file name and path. For more information, see To verify plug-in server configuration.
Verify that the plug-in file is located in the path specified in either the AR System Administration: AR System Configuration Generic UI form or the AR System Administration: Plugin Server Configuration form and that permissions are consistent with the user who executed arserver.exe (arserverd). This is important if you are performing the installation as a non-root user.
Restart AR System server to restart the Java plug-in server. For information on how to stop a Java process associated with a Java plug-in server without restarting AR System server, see Knowledge Base article ID 000305806.
