Resolving MediaView errors

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.

Contents

MediaView fatal error

(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.


Out of disk space

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.


Warning 1150: Cannot write to file 'C:\DBDOC_BUILDS\PROJECT1\DBDOC.M14'. It may be read only or in use by another program.

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.


Warning 1230: File 'rtf\00000016.rtf' not found.

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.


Warning 1581: Sort failure due to error '1'. Compilation failure during context string resolution.

This may be resolved by rerunning MediaView compiler, probably by running MVCC14N.exe from the programs directory.


Warning 4011: Context string '0x0001F8C3' already used.

If this message appears, please contact GMCL.


Error 4624: Unmatched curly brace: missing '}'

This message may indicate archaic broken unicode files. Please send files involved to GMCL.


Warning 6521: Indexer: insufficient disk space. (MVB topic #582367) Error 1609: Produced file will lack full-text index.

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.


Warning 6761: Indexer: unmapped error. (MVB topic #102884) Error 1609: Produced file will lack full-text index.

This can sometimes be avoided by using the BuildPlus option for Processing databases in order of descending number of tags, or by Changing included databases, to exclude those with very few tags.


See also