Office SharePoint Server Error Reporting error : 5000 RRS feed

  • Question

  • Hi,

       I am getting an error as in below in event viewer in MOSS 2007. COuld you please let me know  the cause for it

    Category: 0
    Time: 08/24/2011 20:33.21
    EventCode: 5000
    Message: EventType ulsexception12, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435e74, P4 kernel32.dll, P5 5.2.3790.4480, P6 49c51cdd, P7 na, P8 dd50, P9 e0434f4d, P10 8gec.
    RecordNumber: 32420
    SourceName: Office SharePoint Server Error Reporting
    Type: Error

    Any help would be really helpful
    • Moved by Mike Walsh FIN Monday, August 29, 2011 12:12 PM Not a search q (From:SharePoint - Search (pre-SharePoint 2010))
    • Edited by SaravananMichael Thursday, October 20, 2011 4:24 AM
    Monday, August 29, 2011 10:18 AM

All replies

  • Saravanan Michael,

    1: This issue can occur if the number of log files that are created for the Sps.edb file reaches the maximum number of log files. That is, this issue occurs if the name of the log file is MssFFFEF.log. The Sps.edb file is the property store that stores the properties of the items that are crawled by SharePoint Portal Server 2003. The Sps.edb file and the log files are located in the following folder:Drive:\Program Files\SharePoint Portal Server\Data\GUID
    The names of the log files that are created for the property store contain a hexadecimal number. The hexadecimal number is incremented for each new log file that is created. When the log file name is MssFFFEF.log, no more log files can be created for the property store. 
    ref: http://support.microsoft.com/kb/895574
    2: Issue might also occur due to some synchronization failures. Please refer below link for more detail and suggested solutions:

    Leonid Lyublinski Wizard of MOSS
    Monday, August 29, 2011 6:24 PM
  • 1) Determine what account is running the application pool for the Office Server Web 
    Services (Network Service by default)
    2) Grant this account Read, List Folder Contents on the Root folder as well as the 
    files within
    3) Reset IIS
    Wednesday, August 31, 2011 7:38 PM