I have been creating DTM files of existing roads and waterways features but occasionally the files corrupt and I can narrow it down to specific features in the file. When I try and use these features it sends a message of internal error; access violation and will force the program to close. Is there a way I can recover these features other than keeping regular backups and is this something that I will have to live with or is this avoidable by doing something different.
I find the features usually corrupt when updating in a profile or similar.
I've attached a DTM where the corrupt features are:
E CLARKSON AVE E ELKHORN ST EXCELSIOR AVE HOUSTON AVE and STATE HWY 43
Any insight or advice would be appreciated.
Regards, Mick
V08.09.02.16
Hello Michael,
Once a surface file is corrupt, there is no way to fix it. I downloaded this surface file and attempted to delete those features and it still caused the crash. The only way to fix this is to recreate the surface with a new *.DTM file. Can you tell me how this surface was created? Did you receive this file or did you create it? Also, these surface corruptions can occur when a third party application is present. Do you have any third party applications installed on your system?
Thanks,
Andrea
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
The problem with this surface file, since it's corrupt, you cannot run any commands that consist of accessing these features. You will not be able to run the View Features command on these features that have corrupt the file.
Thanks for looking into this Andrea. The file is one we created in V8.5 and converted to V8.9 and have not used any other input. We have an internal setup of microstation which uses various macros but we don't have any other 3rd party apps running.
We have been working around this by copying the features that were still good to another surface and using the graphics to import the corrupted features again (hadn't thought of tags caddcop, will be handy when creating backups).
Is there a limit of points that InRoads can handle or would this be something else I am doing?
Thanks for the help,
Mick
Hello Mick, I just received word back from development and they were able to fix your file. I am unsure how it was repaired exactly but it is nothing that could have been done without understanding the source code. I will attach the file. There is no "limit" per se. Microsoft only allows a certain amount of memory per program. Each program is allowed 2Gigs of memory to be used. Once InRoads uses this, Microsoft can stop/exit the software. This being said, there is a roundabout number of 8 million points that InRoads can contain in one surface. Thank you, Andrea Presto