Announcement

Collapse
No announcement yet.

Repeated corrupt file!!!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Repeated corrupt file!!!

    In need of some help here. Me and my partner have just started using revit recently for our new project and we keep having problems with corrupted files. It keeps happening every week nearly. I've tried manual recovery from back ups of the central file, I've even redrawn the whole project from scratch in a new file and it keeps coming back. How do I locate the source of the corruption? And the strangest thing is that at the moment my computer says the central file is corrupt, I can't sync and I can't audit the central file... But my partner can sync, can open it....??? I've tried making a new local file and auditing my local file but it's having none of it.

    Thanks in advanced

    #2
    If one of you can open and the other can not, I would suspect a currupt install. Try uninstalling and reinstalling.
    Greg McDowell Jr
    about.me/GMcDowellJr

    Comment


      #3
      Thanks, I'll give that a try!

      Comment


        #4
        since you say you just started using revit, are you sure you are working in a local copy of the file and not the central. Do you both have unique worksharing names? Files typically don't get corrrupt. If one of you can open and sync it sounds like a process issue. Where is your central file located? How are you opening the model?
        Scott D. Brown, AIA | Senior Project Manager | Beck Group

        Comment


          #5
          What kind of specs does you computer have?
          If it's an older computer, there's a good chance you have a ****load of Temporary files clogging things up.
          And Revit doesn't deal with low disk space very well.
          Look at the folder where your Local Copies are kept, and delete everything you can. Especially those _backup folders.
          Then type in
          %temp%
          in your Window Explorer address bar. It'll got to something like C:\Users\yourname\AppData\Local\Temp
          Also delete everything in there. You'll probably get a couple of errors about files in use. Check the "Do this for all files" and click the "Skip" button.
          Finally, do the same for your C:\Windows\Temp folder if you have admin access to it.
          Of course, frequent reboots are also a healthy habit. Preferably daily. At the worst weekly.
          Dave Plumb
          BWBR Architects; St Paul, MN

          CADsplaining: When a BIM rookie tells you how you should have done something.

          Comment


            #6
            Make sure you are on the same build.

            Also, if you were not on the same build, create a new central model after you get on the same build.
            Last edited by Charles Karl; February 26, 2016, 05:11 PM.
            Bettisworth North

            Comment


              #7
              File corruption reasons for file corruption we've encountered thus far:

              1. As Charles said, different build numbers.

              How to tie build number to updates.

              2. Loading families that were built in a previous version of Revit into the file without auditing them.

              3. Syncing to the central on a network drive, when connection to the network is lost.

              We also recommend deleting your local file every couple of weeks and starting fresh, or making sure you select the "Append timestamp to existing" to keep it from referencing potentially old, glitchy information in an outdated local file. If you select the Append option, you need to be consistent about cleaning out your local files regularly, because it adds up quickly.

              Our process for replacing a Corrupt Central:
              1. Determine which team member has the most recent healthy Revit file on their local drive. Open this file.
              2. Click R-> Save as -> Project
              3. In the “Save As” window, select “Options…” select “Make this a Central Model after save.” Save the model with the same Central Model name, but add an appendage identifying the file version number. (Example: ProjectR16_v1.1)
              This make take a little longer than usual, as it is a longer save process when creating the central model as opposed to a local model or synchronization.
              4. Once the new Central Model has been saved, synchronize the file and exit. After this, reopen as normal (as a new local file), and test to make sure the corrupt file error does not occur.


              If there are no more errors, the Central Model is now a healthy Revit file and can replace the previous Central. If the file is still corrupt, repeat steps with the next most recent local file until the most recent healthy Revit file has been identified.

              Comment


                #8
                Thanks for all the replies. The set up we have is pretty simple, we have our local files on our respective computers and the central file is on shared NAS drive. The problem may be that my partner is connected by wifi to the NAS but this should be sorted soon. Other than that our computers are both only a few years old and are kept quite clean as far as temp files, etc. I'd never audited families from older versions before so that could be a cause. We'll start doing that from no on.
                Thanks again everyone, hopefully it's sorted now.

                Comment


                  #9
                  Back again.... We're still having the same issue of repeated corruption/software problem notifications when syncing. I've implemented some of the suggestions made such as auditing imported families. Now we are both connected by ethernet cables to the NAS so that's ruled out as a possiblity. Any other suggestions on identifying the cause of this?

                  Comment


                    #10
                    Originally posted by id211 View Post
                    Back again.... We're still having the same issue of repeated corruption/software problem notifications when syncing. I've implemented some of the suggestions made such as auditing imported families. Now we are both connected by ethernet cables to the NAS so that's ruled out as a possiblity. Any other suggestions on identifying the cause of this?
                    Suddenly this seems all too familiar...central files, corruption, NAS.. Autodesk forums perhaps?
                    Michael "MP" Patrick (Deceased - R.I.P)

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X