none
SharePoint Services Search - Error 6398 RRS feed

  • Frage

  • Hallo,

    Ich habe auf einen SBS2008 folgenden Fehler:
    Windows SharePoint Services 3, Zeitgeber, Ereignis-ID 6398

    Zudem kann ich den SharePoint Services Search Dienst nicht mehr starten.
    Fehler 183: Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist.

    Ich habe den SharePoint BPA ausgeführt und folgenden Fehler erhalten:
    The SharePoint 3.0 Central Administration Web application account and the Windows SharePoint Services Timer Service account must be the same.

    Aufgrund einer früheren Fehlermeldung habe ich letzte Woche versucht, in der Anwendungsverwaltung den Suchdienst mit dem Administratorkonto zu verbinden. Jetzt kann ich diese Option nicht mehr zurücksetzen, da der Suchdienst in der Anwendungsverwaltung nicht mehr angezeigt wird, da er ja auch nicht startet.

    Wie gehe ich vor?

     

    Vielen Dank an alle, die helfen können.

    Weihnachtliche Grüsse,
    Marianne

    Sonntag, 26. Dezember 2010 11:54

Antworten

  • Hallo Marianne,

    Google liefert jede Menge Lösungsansätze. ;) Probiere aber diesen hier mal:

    If you are running SQL server on the same server, the Windows SharePoint Services search logon account may not have the correct permission to access
    or to query the Windows SharePoint Services database on the computer that is running SQL Server. To work around this issue, stop the Windows SharePoint Services
    Search service. Then, add a domain account that has permissions to access the computer that is running SQL Server. To do this, follow these steps:
    1. Use an account that has administrative permissions to log on to the computer that is running Windows SharePoint Services 3.0.
    2. Click Start, click Run, type cmd in the Open box, and then click OK.
    3. At the command prompt, move to the %programfiles%\common files\microsoft shared\web server extensions\12\bin folder.
    4. Type the following at the command prompt, and then press ENTER:
    stsadm -o spsearch -action stop
    This command stops and disables the Windows SharePoint Services Search service.
    5. Click Start, point to Administrative Tools, and then click Services.
    6. In the Services MMC snap-in, right-click Windows SharePoint Services Search, and then click Properties.
    7. In the Windows SharePoint Services Search Properties dialog box, click the Log On tab.
    8. Click This account, type the name of the domain account that has the correct permissions, type the password, and then type the password again in the Confirm
    password box.
    9. Click the General tab, click the list next to Startup type, and then click Automatic. Click Apply, click Start, and then click OK

    If the issue persists, please download and apply the WSS 3.0 update 934525. More information here:

    Description of the security update for Windows SharePoint Services 3.0
    http://support.microsoft.com/kb/934525

    SharePoint Products and Technologies Wizard Fails on Step 5

    Please feel free to let us know the event log from the configuration wizard.

    Hope this helps.


    Best regards,
    Robbin Meng(MSFT)
    Microsoft Online Newsgroup Support

    Dienstag, 28. Dezember 2010 22:51

Alle Antworten

  • Hallo Marianne,

    Google liefert jede Menge Lösungsansätze. ;) Probiere aber diesen hier mal:

    If you are running SQL server on the same server, the Windows SharePoint Services search logon account may not have the correct permission to access
    or to query the Windows SharePoint Services database on the computer that is running SQL Server. To work around this issue, stop the Windows SharePoint Services
    Search service. Then, add a domain account that has permissions to access the computer that is running SQL Server. To do this, follow these steps:
    1. Use an account that has administrative permissions to log on to the computer that is running Windows SharePoint Services 3.0.
    2. Click Start, click Run, type cmd in the Open box, and then click OK.
    3. At the command prompt, move to the %programfiles%\common files\microsoft shared\web server extensions\12\bin folder.
    4. Type the following at the command prompt, and then press ENTER:
    stsadm -o spsearch -action stop
    This command stops and disables the Windows SharePoint Services Search service.
    5. Click Start, point to Administrative Tools, and then click Services.
    6. In the Services MMC snap-in, right-click Windows SharePoint Services Search, and then click Properties.
    7. In the Windows SharePoint Services Search Properties dialog box, click the Log On tab.
    8. Click This account, type the name of the domain account that has the correct permissions, type the password, and then type the password again in the Confirm
    password box.
    9. Click the General tab, click the list next to Startup type, and then click Automatic. Click Apply, click Start, and then click OK

    If the issue persists, please download and apply the WSS 3.0 update 934525. More information here:

    Description of the security update for Windows SharePoint Services 3.0
    http://support.microsoft.com/kb/934525

    SharePoint Products and Technologies Wizard Fails on Step 5

    Please feel free to let us know the event log from the configuration wizard.

    Hope this helps.


    Best regards,
    Robbin Meng(MSFT)
    Microsoft Online Newsgroup Support

    Dienstag, 28. Dezember 2010 22:51
  • Hallo Active Director,

    Habe grad bemerkt, dass ich den Thread mit dem falschen Login gepostet habe; jetzt ist es richtig.

    Kurze Frage zum Lösungsansatz:
    Kann ich dafür den Account nutzen, den ich zur Installation und zur Verwaltung verwende, oder spricht aus Sicht der Sicherheit etwas dagegen?

    Danke und Grüsse,

    Marianne

     

    Mittwoch, 29. Dezember 2010 06:58
  • Ich würde dafür sicherheitshalber den Domänen-Admin Account nehmen. Ich gehe von aus, dass du weisst, was du am Server machst, insofern spricht da erstmal nichts gegen.

    Gruß

    Martin

    Mittwoch, 29. Dezember 2010 15:02