SyntaxHighlighter.config.bloggerMode=true; SyntaxHighlighter.all();

Thursday, April 28, 2011

Notes error: Document has been deleted

Oh well! Another issue that our beloved email client Lotus Notes might surprise you with! This is one is very popular in places where local replicas are used. Below the resolution that has worked for me in most of the cases.

Notes error: Document has been deleted (When archiving using a criteria)

Description:
Lotus Notes is trying to archive a document that has been deleted.
Solution:


1. Normally, recreating the views will fix the problem. (CRTL + SHIFT + F9)
2. If option 1 does not work, disable the Soft Deletions on the database properties
a. Open the mail and go to File  Properties.
b. Choose Database from the dropdown box
c. Select the tab Advanced (The last one)
d. Uncheck the option Allow Soft Deletions
e. Archive email.
f. Check back the option Allow Soft Deletions

33 comments:

  1. great !!
    The only one I found and it works fine !!
    Thank you !

    ReplyDelete
  2. You are fantastic - I have searched on this issue for about an hour before I found this and it worked!

    ReplyDelete
  3. Excellent. Only way I can get my client's LN 8.5.1 to work. You're awesome dude.

    ReplyDelete
  4. Awesome! It on the first try & was easier to find than IBM's own support site.

    ReplyDelete
  5. Worked for me thanks

    ReplyDelete
  6. Thank you, this with "Notes error: Document has been deleted" worked also for me! Great job!

    ReplyDelete
  7. Cheers - Worked for me to.

    ReplyDelete
  8. Amazing! It was so easy! Why isn't IBM more forthcoming with such an elegant fix?

    ReplyDelete
  9. It worked for me too... thanks a ton

    ReplyDelete
  10. Worked Perfect, What a POS mail system. :-)

    ReplyDelete
  11. Unfortunately it hasn't worked for me :-( I still have about 40,000 deleted emails in a users database that refuse to delete (but still saying they are deleted when I try and open them). Anymore ideas please?

    ReplyDelete
    Replies
    1. Hello,
      I'm pretty sure that disabling the "soft deletions" will fix your problem so make sure the change is being applied.

      Delete
  12. Spent an hour hacking, trying to figure out why archiving wouldn't work. Applied the steps above, took 8 minutes to finish. Much appreciated, the gift that keeps on giving.

    ReplyDelete
  13. Thanks saved me from smashing head into keyboard !

    ReplyDelete
  14. This issue manifested for one of my senior executive (Notes 9.0.1) users. Thank you for sharing, worked like a charm!

    ReplyDelete
  15. Worked for me as well - really appreciate the post!

    ReplyDelete
  16. Thanks for posting this. Worked for me too!

    ReplyDelete
  17. Thank you! the second option worked for me!

    ReplyDelete
  18. Recreating index didn't help. But it was also not necessary to temporarily change database options. For me it works when I just empty the Trash.

    ReplyDelete
  19. Some backgroung info to this issue: When Domino archives, it temporarily deletes the archived documents using the method given by the database property. Default is to delete the documents using the trash. Unfortunately the trash has a 32768-document limit, so rule based archiving fails when you archive mor than 32768 documents at a time. Open the DB and clear the trash and Domino will be able archive the next 32768 documents. The softdeletion setting also overrides the trash use, but you should still empty the trash cause it was not emptied automatically during archiving. Otherwhise any user deletion will also cause an error message.

    ReplyDelete
  20. Emptying the trash also seems to have solved my problem. For whatever reason they've locked down my ability to alter the 'soft delete' option at my site.

    ReplyDelete
  21. worked for me, saved me A LOT of time (not having to call helpdesk people etc)

    ReplyDelete
  22. Empty trash and it will work fine.

    ReplyDelete
    Replies
    1. YES! This was the problem! TRASH! Thank You!

      Delete
  23. If you don't have an ability to uncheck the Soft Delete options - simply go into your Trash file - empty it and try again.
    That worked for me

    ReplyDelete
  24. Excellent! Emptying the trash did the trick!

    ReplyDelete
  25. thank you so much !!

    It is big solution for me!

    ReplyDelete
  26. Formidable! The user had set the Soft deletion time on 32768 hours. I disabled it and it's working again. Merci beaucoup

    ReplyDelete
  27. Emptying the Trash worked for me, I'd just removed 1400 rep conflicts using Ytria's scanEZ, most of which met the archive criteria, didn't realise it had only soft-deleted the, Thanks!!

    ReplyDelete

Content belongs to Tips4teks.blogspot.com. All Rights Reserved. Powered by Blogger.