locked
File Not Found Version History Error Sharepoint 2007 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I'm new to SharePoint and I'm running into the following issue that has just started recently out of the blue in SharePoint 2007.

    If you click Version History for any document type it is returning the following generic error message:

    Error

    File Not Found.

    If anybody has any suggestions I'd love to know how to fix this.  Our Dev and Test environments are not running into the same issue.

    Thanks

    Wednesday, January 22, 2014 11:01 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    as i know it is most probably because of the 3rd party antivirus, last time i referenced to this article:

    http://www.symantec.com/business/support/index?page=content&id=TECH47375

    but, is there any process that happened that you aware so it was triggering this issue?

    because, if you just added the version history settings, and had documents already in the library with more version than you specified, the settings you made will only be applied the next time the document is saved. Setting versioning history does not cause Sharepoint to go through the entire document library and remove the older versions immediately.

    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, January 28, 2014 9:04 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Could antivirus be to blame? Please see this thread for more information.

    Danny Jessee | MCPD - SharePoint Developer 2010 | MCTS - SharePoint 2010, Configuring
    Blog: http://dannyjessee.com/blog | Twitter: @dannyjessee

    Wednesday, January 22, 2014 11:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Symantec was installed, but has since been disabled so I'm not sure if that would necessarily be the issue as it is not currently active on the server.

    I had seen that post but the error is not exactly the same when you read through the Symantec fix.

    Wednesday, January 22, 2014 11:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hmmm...some more possible options discussed in this thread.

    Your best bet is to correlate any server-level configuration changes that were made with the "out of the blue" time that this error started occurring. Odds are it wasn't a coincidence. It didn't start right after disabling Symantec, did it?

    Danny Jessee | MCPD - SharePoint Developer 2010 | MCTS - SharePoint 2010, Configuring
    Blog: http://dannyjessee.com/blog | Twitter: @dannyjessee

    Wednesday, January 22, 2014 11:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Have you found some ULS log messages related to this issue from SahrePoint server?

    I am trying to involve someone familiar with this topic to further look at this issue.

    Thanks,
    Daniel Yang
    Forum Support
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Daniel Yang
    TechNet Community Support

    Tuesday, January 28, 2014 7:35 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    as i know it is most probably because of the 3rd party antivirus, last time i referenced to this article:

    http://www.symantec.com/business/support/index?page=content&id=TECH47375

    but, is there any process that happened that you aware so it was triggering this issue?

    because, if you just added the version history settings, and had documents already in the library with more version than you specified, the settings you made will only be applied the next time the document is saved. Setting versioning history does not cause Sharepoint to go through the entire document library and remove the older versions immediately.

    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, January 28, 2014 9:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mad Developer,

    Is there any update for your issue?

    Thanks

    Daniel Yang
    TechNet Community Support

    Thursday, February 13, 2014 7:05 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Sorry it took so long to respond, but yes it was that the Symantec Enterprise Vault components were not installed and configured correctly. 

    However they removed the steps outlined in the link you originally sent and I just followed this:

    http://www.symantec.com/business/support/index?page=content&id=HOWTO60773

    Thanks,

    Mike

    Wednesday, May 21, 2014 4:58 PM