| Event Id | 5000 |
| Source | Office SharePoint Server Error Reporting |
| Description | EventType ulsexception12, P1 owstimer.exe, P2 12.0.4518.1016, P3 45529fd9,P4 microsoft.office.server.search, P5 12.0.4518.0, P6 45439dcc, P7 2681, P8 136, P9 invalidoperationexception, P10 837q. |
| Event Information | According to Microsoft: Cause:This issue occurs 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. WorkAround: To work around this issue, follow steps given in Article MS895574 in Reference links. |
| Reference Links | MS895574 "Users cannot search for content on the portal site, the content indexes do not propagate to the search server, and event error messages are logged to the Application log in SharePoint Portal Server 2003" |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.