I've been experiencing this problem on & off for a while now, but now I have a file that crashes every time I try and attach a reference file. It doesn't matter which approach I try, drag & drop from the model dialog box or File-Attach from the reference dialog box, I get the same result:
I've tried compressing the file, deleting my user preference file, and running VerifyDgn in SS10 to clean up the file, to no avail. Has anyone else had this problem with Connect?
if its only a specific active file that crashes when any ref is attached try this approach
Create a new file A from a clean seed file ( means recently deleted all and compressed) now reference attach your problem file B
make sure all levels are turned on in file B.
Select all and copy all visible elements from file B into the active file A use a known point on an object like a corner intersection with the snap tools and back to the same spot. Detach the reference.
Now try attaching your File C reference to this new File A .. if it doesn't crash you fixed the problem... now replace the original File B with this File A and rename it to File B..
Another trick from Bad old days was to draw a line in th bad file Select all and rotate about the tip of the line 0.99999 as many nines as you can type in the rotate box, now re rotate the selection back with -0.99999 same number but - ive about the same point.. this somehow resets tables etc within microstation and can fix a lot of bad things.. but I would now use the ref method to a new clean file to remove all other corruption or bad elements.. it's difficult to copy bad invisible elements thru the ref attachment.. apart from that you need to send your original file to Bentley for analysis or to Axiom if your subscriber to Axiom.. Otto has posted a method to fix and check corrupted dgns but you need to instal some extra software packages and not all are freeware..
I couldn't do his method it at my works as we low life drafting users don't have install access right to install programs and as a corporate for profit business we can't use freeware for free.. but you could do it as a trial at home on your own pc and then if it works you have a test case to BUY and install these repair test tools that Otto suggested a few days ago .. I'm struggling at work to get paid for proprietary software installed that I really need let alone freeware
Currently Using V8iss10 (8.11.09.919)
and dabbling in CE update 16 (10.16.00.80)
Pwise Administrator ( yeah I passed the training course!)
MicroStation user since 1990 Melbourne Australia.click link to PM me
I tried to reproduce the issue but it is not reproducing at my side. Meanwhile please help us with the following information to investigate this issue.
If possible, please provide the dataset (*.dgn) so that, we can check or test the issue.
I think I have some more information about this issue and to its potential cause. I run Microstation with 2 application windows open, 1 on each monitor, and I have my reference file dialog box docked at the top of the right monitor. On the the left monitor I have the model dialog box docked & pinned along the right hand side of the screen. When I try to drag drop a model from the expanded model dialog flyout on the left monitor to the docked reference dialog on the right screen, that is when Microstation crashes. The model I'm dragging doesn't display the (+) sign when the cursor is inside the reference dialog box like it normally should. I've since undocked & unpinned the model dialog box from the left monitor and placed it on the right monitor (undocked) and tried the drag & drop method again. This time I do get the (+) sign when the cursor is above the reference dialog box and when I release the mouse the file attaches as it should and Microstation doesn't crash. I think this is a GUI problem with Microstation similar to the other problem I reported in another post regarding the tool settings window when it was also docked & pinned (service request 7001393550 was filed for that issue).
Yes have noticed such issue that file which opens in v8i is not possible to open in CONNECT (SR7001386669).
Merging it to new clean file fixed the issue but still program shouldn't crash as this sounds like a security hole. Merging to new file is not a solution to underlying problem.
edit: checked that my SR has status defect filed but there is no defect number provided.