MediaView uses Hyperlink output to create the M14 file. Occasionally a build may fail during the MediaView compile stage. It may be possible to resolve MediaView errors or warnings as described below. (Errors and warnings during the MediaView run are stored in the project file DBDOC.log.) Otherwise, contact GMCL.
(Fatal error has occurred in ExecuteMedialViewCall(). Build cannot continue.)
If this message appears, it may be resolved by rerunning MediaView compiler, probably by running MVCC14N.exe from the programs directory. If this doesn't resolve the problem, contact GMCL.
The M14 file is very large, and large temporary files are created during the hyperlink and MediaView compile stages of the build, which cannot be cleaned up until after the MediaView compile is complete.
If you are running out of temporary file space, try deleting old .M14 files and cleaning up the temporary directory and rerunning MediaView compiler. If this doesn't resolve the problem, contact GMCL.
The DBDOC.M14 file may already exist and be open or read-only. If you rename your DBDOC.M14 file after building, or change how future M14 files will be named and rebuild, you should be able to avoid this problem. If this doesn't resolve the problem, send files involved to GMCL.
This warning may indicate a problem with a specific CAD file. If you search the DBDOC.err file for "Invalid spec length", you may be able to identify which file was being scanned at the time the error was encountered. If this doesn't resolve the problem, send files involved to GMCL.
This may be resolved by rerunning MediaView compiler, probably by running MVCC14N.exe from the programs directory.
If this message appears, please contact GMCL.
This message may indicate archaic broken unicode files. Please send files involved to GMCL.
This means there is not enough disk space in the TEMP folder to complete the build. If you are running out of temporary file space, try cleaning up the temporary directory. If this doesn't resolve the problem, send files involved to GMCL.