more 'failed to save document' - now in win32!

Discussion in 'SolidWorks' started by Zander, Oct 11, 2006.

  1. Zander

    Zander Guest

    I'm receiving this message now in win32 sw2007 sp1 working on a local
    drive. sigh..............
     
    Zander, Oct 11, 2006
    #1
  2. Zander

    Tim Markoski Guest


    You're not alone

    It seems to be a bug that crept in with SW2006 SP5.

    SW2006 SP5 also GPFs when using the linear pattern function.
     
    Tim Markoski, Oct 11, 2006
    #2
  3. I have received that error, but I traced it to the action of deleting a
    block definition in a drawing when there were instances of that definition
    still on the sheet and the instances didn't completely highlight to delete.
    The definition would delete, leaving the instances, and then it would fail
    to save.

    WT
     
    Wayne Tiffany, Oct 11, 2006
    #3
  4. Zander

    Zander Guest

    This is happening to me under very typical circumstances. with an
    assembly and a few parts open, saving occasionly while modelling and
    editing parts etc. Suddenly when trying to save this message will
    appear.
     
    Zander, Oct 11, 2006
    #4
  5. Zander

    matt Guest

    This can happen to you if your virus software is scanning the file while
    you are trying to save to it. Give that a shot. Either turn off the AV
    or limit it so that it doesn't scan SW files.
     
    matt, Oct 11, 2006
    #5
  6. Zander

    Zander Guest

    Good idea - I'll try that, although I just read in another thread here
    that this is supposedly a sp1.0 bug of sw2007?
     
    Zander, Oct 11, 2006
    #6
  7. Zander

    matt Guest

    the SW site confirms that only for 64 bit, not 32 bit.
     
    matt, Oct 11, 2006
    #7
  8. Zander

    L Z Guest

    We have 2 seats here of 2007 running on 64 bit machines. Both are
    running the 32 bit SolidWorks version. When we upgraded to SP 1, we
    started getting the failed to save error on both machines. It seemed to
    happen after creating 3-4 features or edits to the model and then
    saving. It could happen either in the part model or in an assembly.
    Workaround was to save as.
    We switched back to SP 0 and that seemed to solve the problem. The same
    thing happened with the x64 version of SolidWorks SP 1 installed. Our
    VAR turned in a request last week on this.
    Service Request Number: [SR:1-367144661] VAR SR#
    Lynnz
     
    L Z, Oct 12, 2006
    #8
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.