Namespace Mismatch

[matt.brown]

Anyone else seeing this on occasion?

Seems to happen every other day and occurs when the forward/back buttons are used.  When switching drawing files, the command line history shows the text below and the command prompt changes to "s::startup" without the quotes and effectively locks the program and requires a restart of the application to do anything.

Thanks!

Enter name of drawing to open <H:\Drawings\WIP\XXX1.dwg>: H:/Drawings/WIP/XXX2.dwg
Regenerating model.
Command:
Command:
Command: .ZOOM
Specify corner of window, enter a scale factor (nX or nXP), or
[All/Center/Dynamic/Extents/Previous/Scale/Window/Object] <real time>: E
Command: DISPLAYVIEWCUBEIN2D
Enter new value for DISPLAYVIEWCUBEIN2D <OFF>: off
Command: NAVBARDISPLAY
Enter new value for NAVBARDISPLAY <0>: 0
Command:
Command: *Cancel*
Command: *Cancel*
Command:
 Checking files for any marked in-use/read-only . . .
Regenerating model.
Command:
Command:
Command: "\n*** INTERNAL ERROR: VL namespace mismatch\n"" type Y to reset: ".ZOOM "\n*** INTERNAL ERROR: VL namespace mismatch\n"" type Y to reset: "
Command: *Cancel*
*Cancel*
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: _quit
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command: *Cancel*
Command:
Command:
Command:
Command:
Command:
Command:
Command:
Command: *Cancel*

[AcadE2014]

check to see if you have a ACADDOC.LSP running. Do a windows search for that file.

If you find this file and it's in your drawing path, it will run each time you open a drawing.

I would suppect that there is a bad command line in there.

Hope this helps

Dennis

[s.emmsley]

@matt.brown There is no direct command to edit the namespace; were you able to locate a lisp file that might be causing the error? 

[AcadE2014]

The other issue could be the SDI command.

I have been working with Autodesk for the SDI mode.

try running the same issue with SDI=0

[matt.brown]

I have re-loaded all lisp files including acadlisp.doc to verify there are no errors.

I do have a startup script that sets SDI to 1 because it is easier for me to keep track of which drawings I opened to modify versus which ones I have opened only for reference, preventing un-intended edits from being saved in files that should not be changed, (Using vault is not an option for me, and makes little economical sense in a single user non server based deployment).