file crashes

Couple of ideas...

Are you familiar with the FDOT workspace? There are tools in there to help clean up issues.

Delete GeoPak config files.

Compress the file.

Any error messages?

Cliff, thanks for the reply.

I'm not familiar with FDOT workspace. The error message is .NET Framework "Unhandled exception has occurred in a component in your application....  I don't know how to delete the GeoPak config files.  I compressed the file and that did not resolve the issue.

Another bit of information, I'm working in ProjectWise with our client.

Last night I tried several things and the profiles started working again.  I thought turning the display for the reference file with the existing surface may have been what helped.  The surface is 111mb.  Unfortunately the issue has reoccurred today so that did not resolve it either.

https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/15923/geopak-resource-files-how-to-remove-them-and-why

This will help explain about clearing the resource files. Sometimes some bit of data will get written badly, and that can cause some odd glitches.

Projectwise is another can of worms entirely, and if the problem continues, it may be worth an email to your PW administrator. I have seen some funny things when the permissions were not just right.

I was looking for that link. Thanks MaryB.

Thank you MaryB.

I'll try cleaning the resource files as suggested.

Another individual in the office had the same issue with the file.  To help me understand the resource files better, are these related to just on computer or does this impact others too?

I copied out, and checked out the file from PW.  I was able to get the profile to work.  Uncertain if this is where the issue is or not though.  I'll post again either way.

Those resource files are local files that Geopak writes along the way. They include preferences and other data bits for Geopak to "remember" as you work along. There's nothing design-critical in them that I've ever seen. Each computer will have its own set of resource files.

I remember, a long time ago writing up a simple BAT file for my users to run to delete those files any time Geopak started acting up.

Those resource files are local files that Geopak writes along the way. They include preferences and other data bits for Geopak to "remember" as you work along. There's nothing design-critical in them that I've ever seen. Each computer will have its own set of resource files.

I remember, a long time ago writing up a simple BAT file for my users to run to delete those files any time Geopak started acting up.

Thanks again MaryB.  Apprciate the help.

I found the issue can be recreate if view 8 is selected for the view.  I tired another view (3) and did not have the issue.  Not sure why this would be.

I have had to open files in Connect or v8i no GeoPak. Then delete the elements causing the issue. In survey we struggle with shared cells. These cause issues like you mention. There is a ton of elements that get linked to each other in ss4 and even more in ORD.

Compress the file often. In survey if we do any deletes to the survey database we compress. Seems to make a big difference in stability.

Thanks Cliff

I'll try to remember to compress the file as suggested.