Microsoft KB Archive/895574

From BetaArchive Wiki

Article ID: 895574

Article Last Modified on 11/30/2006


APPLIES TO

  • Microsoft Office SharePoint Portal Server 2003


Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


SUMMARY

This article describes an issue that occurs in Microsoft Office SharePoint Portal Server 2003 where the content indexes do not propagate from the Index Management Server to the search server on your server farm. Additionally, event error messages are logged to the Application log. This issue occurs if the number of log files that are created for the property store, Sps.edb, reach the maximum number of log files. This article describes a workaround that you can use to delete the log files. After the log files are deleted, SharePoint Portal Server 2003 can create new log files. This article also describes how to increase the log file size. By increasing the log file size, you can help prevent this issue from occurring.


SYMPTOMS

You experience all the following symptoms in your server farm deployment of SharePoint Portal Server 2003:

  • Users cannot search for content on the portal site.
  • The content indexes do not load. Additionally, the content indexes do not propagate from the Index Management Server to the search server on the server farm.

  • The following events are logged to the Application log:

    Type: Error
    Source: Microsoft SharePointPS Search Service
    Category: Content index server
    Event ID: 7051
    Date: Date
    Time: Time
    User: N/A
    Computer: ComputerName
    Description:
    Index propagation to search server <SearchServerName (IP IPAddress)> was not accepted. Context: http://ServerName / Application, KBCatalog Catalog
    Details:
    The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

    For more information visit http://www.microsoft.com/servers/redirect/contentredirect2.asp
    For more information, see Help and Support Center at http://support.microsoft.com.

    Type: Error
    Source: SharePoint Portal Server Error Reporting
    Category: None
    Event ID: 5000
    Date: Date
    Time: Time
    User: N/A
    Computer: ComputerName
    Description:
    EventType office11sharepointportalmanagedexception, P1 mssearch.exe, P2 11.0.6715.0, P3 00000000, P4 1657, P5 1, P6 NIL, P7 NIL, P8 NIL, P9 NIL, P10 NIL. For more information, see Help and Support Center at http://support.microsoft.com.
    Data:

    0000: 6f 00 66 00 66 00 69 00 o.f.f.i.
0008: 63 00 65 00 31 00 31 00 c.e.1.1.
0010: 73 00 68 00 61 00 72 00 s.h.a.r.
0018: 65 00 70 00 6f 00 69 00 e.p.o.i.
0020: 6e 00 74 00 70 00 6f 00 n.t.p.o.
0028: 72 00 74 00 61 00 6c 00 r.t.a.l.
0030: 6d 00 61 00 6e 00 61 00 m.a.n.a.
0038: 67 00 65 00 64 00 65 00 g.e.d.e.
0040: 78 00 63 00 65 00 70 00 x.c.e.p.
0048: 74 00 69 00 6f 00 6e 00 t.i.o.n.
0050: 2c 00 20 00 6d 00 73 00 ,. .m.s.
0058: 73 00 65 00 61 00 72 00 s.e.a.r.
0060: 63 00 68 00 2e 00 65 00 c.h...e.
0068: 78 00 65 00 2c 00 20 00 x.e.,. .
0070: 31 00 31 00 2e 00 30 00 1.1...0.
0078: 2e 00 36 00 37 00 31 00 ..6.7.1.
0080: 35 00 2e 00 30 00 2c 00 5...0.,.
0088: 20 00 30 00 30 00 30 00 .0.0.0.
0090: 30 00 30 00 30 00 30 00 0.0.0.0.
0098: 30 00 2c 00 20 00 31 00 0.,. .1.
00a0: 36 00 35 00 37 00 2c 00 6.5.7.,.
00a8: 20 00 31 00 2c 00 20 00 .1.,. .
00b0: 4e 00 49 00 4c 00 2c 00 N.I.L.,.
00b8: 20 00 4e 00 49 00 4c 00 .N.I.L.
00c0: 2c 00 20 00 4e 00 49 00 ,. .N.I.
00c8: 4c 00 2c 00 20 00 4e 00 L.,. .N.
00d0: 49 00 4c 00 20 00 4e 00 I.L. .N.
00d8: 49 00 4c 00 0d 00 0a 00 I.L.....

    Type: Information
    Source: SharePoint Portal Server Error Reporting
    Category: None
    Event ID: 5001
    Date: Date
    Time: Time
    User: N/A
    Computer: ComputerName
    Description:
    Bucket 00980185, bucket table 5, EventType office11sharepointportalmanagedexception, P1 mssearch.exe, P2 11.0.6715.0, P3 00000000, P4 1657, P5 1, P6 NIL, P7 NIL, P8 NIL, P9 NIL, P10 NIL.
    For more information, see Help and Support Center at http://support.microsoft.com.
    Data:

    0000: 42 00 75 00 63 00 6b 00 B.u.c.k.
0008: 65 00 74 00 3a 00 20 00 e.t.:. .
0010: 30 00 30 00 39 00 38 00 0.0.9.8.
0018: 30 00 31 00 38 00 35 00 0.1.8.5.
0020: 0d 00 0a 00 42 00 75 00 ....B.u.
0028: 63 00 6b 00 65 00 74 00 c.k.e.t.
0030: 54 00 61 00 62 00 6c 00 T.a.b.l.
0038: 65 00 20 00 35 00 0d 00 e. .5...
0040: 0a 00 ..

    Type: Error
    Source: Microsoft SharePointPS Search Service
    Category: Content index server
    Event ID: 7060
    Date: Date
    Time: Time
    User: N/A
    Computer: ComputerName
    Description: Index propagation to search server <SearchServerName (IPAddress)> failed to commit. Context: http://ServerName/ Application, KBCatalog Catalog
    Details:
    The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

    For more information visit http://www.microsoft.com/servers/redirect/contentredirect2.asp
    For more information, see Help and Support Center at http://support.microsoft.com.


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

Note Follow the workaround steps in this article only if the log file name is MssFFFEF.LOG. Do not follow these steps if you experience the errors listed in the "Symptoms" section of this article, but the log file name is different.

To work around this issue, follow these steps:

Step 1: Delete the log files for the property store

Stop the Microsoft SharePointPS Search service, run the eseutil /mh command to verify that the property store is in a clean shutdown state, delete the log files, and then restart the Microsoft SharePointPS Search service. After you do this, SharePoint Portal Server 2003 can create new log files for the property store.

Note You must perform this procedure on each server in your server farm that experiences the symptoms that are described in the "Symptoms" section.

To delete the log files, follow these steps:

  1. Copy the Ese*.* files from the SharePoint Portal Server 2003 CD to the folder that contains the Sps.edb file and the log files. To do this, follow these steps:
    1. Copy the Eseutil.exe file and the Ese*.* files that are associated with the Eseutil.exe file from the following folder in the SharePoint Portal Server 2003 CD:

      Optional\Server\Web Storage System\Bin

      The files that you must copy are listed as follows:

      • Ese.dll
      • Eseback2.dll
      • Esebcli2.dll
      • Eseperf.dll
      • Eseperf.hxx
      • Eseperf.ini
      • Eseutil.exe
    2. Paste the files to the following folder:

      Drive:\Program Files\SharePoint Portal Server\Data\GUID

  2. Stop the Microsoft SharePointPS Search service. To do this, follow these steps:
    1. Click Start, click Run, type cmd in the Open box, and then click OK.
    2. Type net stop sharepointpssearch at the command prompt, and then press ENTER.
  3. Run the eseutil /mh command to verify that the property store is in a clean shutdown state. To verify that the property store is in a clean shutdown state, follow these steps:
    1. At the command prompt, change to the following folder:

      Drive:\Program Files\SharePoint Portal Server\Data\GUID

    2. Type eseutil /mh sps.edb at the command prompt, and then press ENTER:

    3. Determine whether State: Clean Shutdown appears in the output that is displayed at the command prompt. The following is an example of a part of the output that is displayed after you run the eseutil /mh command on the property store.

      Microsoft(R) Exchange Server Database Utilities 
Version 6.5 
Copyright (C) Microsoft Corporation. All Rights Reserved. 
 
Initiating FILE DUMP mode...
         Database: sps.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,9
 Engine ulVersion: 0x620,9
Created ulVersion: 0x620,9
     DB Signature: Create time: DateTime Rand:105592556 Computer:
         cbDbPage: 4096
           dbtime: 14717 (0-14717)
            State: Clean Shutdown
     Log Required: 0-0
   Streaming File: No
         Shadowed: Yes
       Last Objid: 38
     Scrub Dbtime: 0 (0-0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
    4. Do one of the following:
      • If State: Clean Shutdown appears in the output that is displayed at the command prompt, go to step 4.
      • If State: Clean Shutdown does not appear in the output that is displayed at the command prompt, restart the Microsoft SharePointPS Search service. To do this, type net start sharepointpssearch at the command prompt, and then press ENTER. Then, repeat step 2 to step 3 until State: Clean Shutdown appears in the output that is displayed at the command prompt.
  4. Delete the following files:
    • Mss.chk
    • Res*.log
    • Mss*.log

    Note These files are located in the following folder:

    Drive:\Program Files\SharePoint Portal Server\DATA\GUID

  5. Restart the Microsoft SharePointPS Search service. Type net start sharepointpssearch at the command prompt, and then press ENTER.

Step 2: Increase the log file size

By default, the log file size is 5 megabytes (MB) and the LogFileSize registry entry is set to 5120. To help prevent this issue from occuring, increase the log file size to 30 MB. To do this, add the LogFileSize registry entry to the following registry subkey, and then set the value of the LogFileSize registry entry to 30720:

HKEY_LOCAL_MACHINE\Software\Microsoft\SPSSearch\Databases


Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To do this, follow these steps:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate, and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\SPSSearch\Databases

  3. Point to New on the Edit menu, and then click DWORD Value.
  4. Type LogFileSize, and then press ENTER.
  5. Right-click LogFileSize, and then click Modify.
  6. Type 30720 in the Value data box, click Decimal, and then click OK.

    Important When you set the LogFileSize registry entry to 30720, you increase the log file size to 30 MB. Do not increase the log file size to more than 30 MB.
  7. Quit Registry Editor.

Note You must make this change on all SharePoint server computers in the farm. This includes all Web front-end servers, search servers, index servers, and job servers. If you do not update this registy key on all computers, problems with searching or propagation will occur.

MORE INFORMATION

For more information about content indexes in SharePoint Portal Server 2003, see the "Managing Content Indexes" topic in the "Managing Search Settings for the Portal" section of the "Administration" chapter of the Microsoft Office SharePoint Portal Server 2003 Administrator's Guide. The Microsoft Office SharePoint Portal Server 2003 Administrator's Guide (Administrator's Help.chm) is located in the Docs folder in the root folder of the SharePoint Portal Server 2003 CD.


Additional query words: sps

Keywords: kbconfig kbprb kbtshoot KB895574



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/895574&oldid=335631’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki