Trouble shooting

This section gathers real life problems and solutions as found by the author or other users. In the case of solutions provided by users, their names are quoted either as initials or Internet pseudonyms unless requested otherwise by authors. The information is provided in the spirit of solving tricky problems but Team uStation AB and Chris Zakrewsky take no responsibility whatsoever for accuracy or fitness of information provided in this chapter. We will replace parts of this information whenever a better solution is found, but you still may only use it at your own risk.

Environment: MicroStation + SynchByLevel add-on

Problem description:

If SYNCHBYLEVEL Select enhancement is installed, there will be a warning written to Message Center each time SYNCHBYLEVEL circumvents snatching data from the InfoSnap popup (i.e. snatched element symbology is not activated as active symbology).

Solution (by Chris Zakrewsky/Jeffrey Malter, July 26, 2003):

If you don't want SYNCHBYLEVEL to interfere with InfoSnap, make sure that you have the Level Name and Number being defined AFTER the Color, Weight and Style in InfoSnap Toggles tab (only then they take precedence over SYNCHBYLEVEL's all overrides).

Another workaround is to attempt snatching twice. At the second time the level is already changed and SYNCHBYLEVEL does not interfere.

Environment: MicroStation + DGNAPPS

Problem description:

WARNING: InfoSnap is not set as the very last item in your MS_DGNAPPS (Design Applications) configuration. See the docs how to avoid InfoSnap malfunction.

This warning is issued as the response to a weird (and reproducible) problem with MicroStation 8.1.1.9 as identified by Jamey White in Beta 5i. Some applications (like DAILYTIP) seriously interfere with InfoSnap if they are loaded as a Design Application after InfoSnap.

Solution (by Jamey White/Jeffrey Malter, July 21, 2003):

Make sure that InfoSnap is the very last item in the list: Workspace -> Configuration> Category (All) -> MS_DGNAPPS -> Edit, or as an advanced user you may want to place the line 'MS_DGNAPPS > INsFOSNAP' as the last line in your mslocal.cfg file, after the %include statement instead of using MicroStation Workspace Configuration dialog box.

Environment: ProjectWise

Problem description:

Unexpected read-only files.

Double clicking on the top DGN Model in the Model History Tree (or pressing the 'Home'-key) returns to home DGN but MicroStation warns that file is now Read-Only. Jumping to other DGN Models does not exhibit any anomalies.

Solution (by C.L. Oct. 18, 2002):

After double clicking on the top DGN Model or pressing the 'Home'-key, when ProjectWise asks "Do you wish to check-out <FilenameToBeOpened>", answer: YES. When ProjectWise asks "Do you wish to check-in <CurrentlyOpenedFile>", answer: NO. You may be breaking some rules here by keeping several files checked out, but there seems to be no other way.