Trimble Business Center

I'm running a quick earthwork calc for a local engineer and keep getting a TBC error message asking me to save, shut down and try again.  Nothing I haven't seen in the past except it won't go away no matter how many times I restart TBC.  The surface model stops at about 9% on the finished design creation.  I found this after trying to run an earthwork report after I created my dynaview and plansheet.  

I've played around with the error and it seems to be a problem with the dynaview.  Everything is good until I add the dynaview and then the error pops up when re-building the surface.  When I delete it everything goes back to normal.  I've included a txt file with the error message.  You should get the same error as I confirmed this on another workstation here in the office and with a different project.  This may be normal as I'm still very green on using dynaviews but this doesn't seem normal.

I'll use the plotbox in the mean time.  If you need more information, please let me know.  thanks!

strange- is the data in the zip file - I will try my own test on my own data - I don't see why a DV will have an effect on an Earthwork report but will try it anyway to see if I can recreate it

Alan

Alan,

I've attached a link below to the TBC file that where this shows up.  The last save was with the DV and the FG surface could not rebuild so it is blank.  You should be able to just deleted the DV and let it rebuild.

Dropbox - Oakmont Ph 2A.vce 

Alan

Changing the layer of the DV to a non-design layer worked.  I need to update my template with a layer specifically for dynaviews so this doesn't happen again.  Thanks for the help!

The issue here Ben is that you have created a Dynaview Collection in the Plan View and you have put it on a layer categorized as Finished grade in the Takeoff - so it is trying to add the DV Collection to the Surface which is illegal - it is a kind of bug because this should not stop everything working and that is why you are getting the exception error that you are seeing - if you change its layer property to a Layer outside of the Takeoff Layers you will be fine. I just tried that and it works just fine for me now.

I have reported the defect so it can get rectified in the software - I have never tried that so have never seen that one before - nice catch

Alan