Přihlásit
 
HlavníKnihovnaCertifikaceDownloadPodporaKomunitaFóra
Zdroje informací pro profesionály v oboru IT >
> 
> 
SharePoint 2010: FSCcontroller failed to start

Unanswered SharePoint 2010: FSCcontroller failed to start

  • 25. února 2012 13:42
     
     
    Přihlásit se a hlasovat
    0

    FSCcontroller failed to start after install of Forefront Protection 2010 for SharePoint.

    I installed Hotfix Rollup 2 for Forefront Protection 2010 for SharePoint... the error I get now is FSCcontroller failed to start. I uninstalled the application completely and made sure the folder and services were gone.  I reinstalled the application and I still receive the same error. I tried installing it under the FARM ADMIN and under the service account created for Forefront, the same error happens.

    Any help would be much appreciated.  Thanks!

     

Všechny reakce

  • 27. února 2012 6:41
    Moderátor
     
     
    Přihlásit se a hlasovat
    0
     

    Hi,

    Thank you for the post.

    Is it clean server? Or is there any other third party service installed on the server? What is the detailed error message you have occurred?

    Regards,

    Nick Gu - MSFT

     
  • 28. února 2012 15:15
     
     
    Přihlásit se a hlasovat
    0

    BAinsight Longitude Search is installed.

    Log Name:      Application
    Source:        Application Error
    Date:          2/25/2012 12:20:41 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sdi-sharepoint.test.org
    Description:
    Faulting application name: FSCController.exe, version: 11.1.413.0, time stamp: 0x4e5bfbc6
    Faulting module name: FSCController.exe, version: 11.1.413.0, time stamp: 0x4e5bfbc6
    Exception code: 0xc0000417
    Fault offset: 0x000000000012f638
    Faulting process id: 0xdd0
    Faulting application start time: 0x01ccf37d2d9edfb0
    Faulting application path: c:\Program Files\Microsoft Forefront Protection for SharePoint\FSCController.exe
    Faulting module path: c:\Program Files\Microsoft Forefront Protection for SharePoint\FSCController.exe
    Report Id: 753048e0-5f70-11e1-bb09-005056a80044
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-02-25T05:20:41.000000000Z" />
        <EventRecordID>411087</EventRecordID>
        <Channel>Application</Channel>
        <Computer>sdi-sharepoint.test.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>FSCController.exe</Data>
        <Data>11.1.413.0</Data>
        <Data>4e5bfbc6</Data>
        <Data>FSCController.exe</Data>
        <Data>11.1.413.0</Data>
        <Data>4e5bfbc6</Data>
        <Data>c0000417</Data>
        <Data>000000000012f638</Data>
        <Data>dd0</Data>
        <Data>01ccf37d2d9edfb0</Data>
        <Data>c:\Program Files\Microsoft Forefront Protection for SharePoint\FSCController.exe</Data>
        <Data>c:\Program Files\Microsoft Forefront Protection for SharePoint\FSCController.exe</Data>
        <Data>753048e0-5f70-11e1-bb09-005056a80044</Data>
      </EventData>
    </Event>

     
  • 29. února 2012 8:19
    Moderátor
     
     
    Přihlásit se a hlasovat
    0
     

    Hi,

    Thank you for the update.

    We need to bring down services to enable Forefront, your best option would be to upgrade to the latest rollup.

    1- Bring down SharePoint services

    2- Upgrade to rollup2 http://support.microsoft.com/kb/2592450  

    3- Enable Forefront via Fscutilty.exe /enable

    4- Bring up SharePoint and Forefront services

    Regards,

    Nick Gu - MSFT

     
  • 29. února 2012 15:21
     
     
    Přihlásit se a hlasovat
    0
    Yes, I already tried that.  Im still having the issue (application error log).
    • Navržen jako odpověď Cory_Stewart 16. března 2012 16:19
    • Zrušeno navržení jako odpověď Cory_Stewart 16. března 2012 16:19
    •  
     
  • 16. března 2012 16:24
     
     
    Přihlásit se a hlasovat
    0
    I have had this same problem and found that permissions were not applied on the forefront install target correctly. The eventing service would not start which would not allow anything to start. I checked the permissions and the Network Service did not have full control over the incidents directory. I fixed the permissions and all is now working is expected. I suggest that you check the perms and ensure everything is as expected.