I have a user that when he comes in, in the morning and fires up Civil 3D then does an import event and process the linework it always crashes.. It only happens when he just starts the day. After that seems to be ok. I reproduced this and not sure why this would be happening.
This has happened on several versions of Civil 3D.
All updates and such are applied.
Any thoughts?
Thanks
Thomas Glidewell
Are you starting a new survey database before the import? After restart, is the import event there and do you just reimport from the import event or do you have to start from scratch?
Whenever I start having issues like your describing, first thing I go about going is a uninstall and re-install of all MS SQL products. These have been known to become corrupt from time to time.
HTH
Rick Jackson
Survey CAD Technician VI
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Thank you, thank you! The fieldwork has been coming in slowly. We work over the network. I thought what the hey and searched through Add/Remove programs and found my sql.... microsoft sql server compact 4.0 sp1 x64 enu. I downloaded it and re-installed/repaired it. And now the fieldwork processing in a flash!
Something else that will really slow imports down, is have the Figure Database, Codeset etc... Located on a server, I always have these files on my local drive, in a standards folder, and path the Survey Database Defaults accordingly.
Rick Jackson
Survey CAD Technician VI
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
We do the same. We have a place on the server for all our standards. When anything gets updated, they get pushed out to everyone's local drive when they login.
Can't find what you're looking for? Ask the community or share your knowledge.