[V8i SS3 Update 2] Read access problem on an element object

• Prefer to attach a large amount of text as a file.
  •  It makes it easier to search and understand your problem.
• What were you doing when this exception occurred? 
• What product are you using? 
• What version of that product?

I actually cannot find a way to reproduce. But it happens 3 times (count from yesterday).

What I remember about the same condition is: I attached a dwg, I copied elements from dwg to 2D dgn. I was modifying elements which in dgn only. Last time when it pop-up, I was just deleting 2 line elements. Of course, I've immediately tried to press Ctrl+Z and delete them again, but nothing happened. Also, I always turn off the "Automatially Save Design Changes", so it should not write anything onto the disk.

Tested with version: 08.11.09.578.

Unknown said:

This issue also occur at v08.11.09.536 yesterday in university. I installed 08.11.09.578 at office

Most of us don't have those versions: we use the standalone version of MicroStation SS3 Update 2 available for download.  If you are using another version, provided by Bentley Systems only for use with another application, it is hard to tell whether your problem rests with MicroStation SS3 in general, or if it is related to that specific point release of MicroStation.

Unknown said:

I found that it runs more stable on closing a file/application

I have never encountered problems of 'instability' when closing a file, or closing an application.  If that is a continuing problem for you, please start a new thread with that topic.

If I may make a suggestion .. my observation is that in the later versions of mstn ie after xm , mstn is very unforgiving with bad acad elements... I have been persuading my users not to copy data  from DWG refed into DGN but to convert the DWG to dgn first then attach DGN to DGN  and copy whatever you want  or even merge ...

since we adopted this policy we have not had to use axiom tools repair kit  and  had far less crashes of major files.... much more stable environment this way.... plus you can enforce standards symbology easier too....

what is the differences in procedure of the program between copying elements from DWG to DGN and exporting elements from DWG to DGN?

Concerning your original inquiry, we would need to work together to try to find a reproducible workflow.  With that workflow we can capture the correct logs/ data and be able to work towards a resolution.  Otherwise, it will make trouble shooting your issue very difficult.

Have you been able to narrow down the workflow?  Is it:

- Attach a DWG

- Copy elements from DWG to 2D DGN

- Modify elements in DGN

If this appears to be the general workflow, please confirm and we can attempt to gather more information.

Where are the files located that you are working on?

What is the environment you are working in, both client machine and server(if accessing files off of the network)

Very hard to reproduce.... today I worked with MicroStation whole day but i still couldn't meet this problem. If I could reproduce it, I should have already posted the steps. Those files are located on a 128GB USB flash drive, MicroStation is installed on the locate computer.

Very hard to reproduce.... today I worked with MicroStation whole day but i still couldn't meet this problem. If I could reproduce it, I should have already posted the steps. Those files are located on a 128GB USB flash drive, MicroStation is installed on the locate computer.