locked
Event id 6102 RRS feed

  • Question

  • I'm getting lots of event id 6102? Any idea?

    Wednesday, October 15, 2008 6:52 PM

Answers

  • Hi
    This may because of loadbalancer.RegisterLauncher failure.
    Go to
    Central Administration
    Click Operations
    Click Service Account
    Change the service account to Document Conversions Load Balancer Service
    And Select   Network Services
    Click Save

    Try this and let me know

    Regards
    Xavier Ravi
    Wednesday, October 15, 2008 7:06 PM
  • Hi,


    As Xavier said,
    this usually happens when the Document Conversions Load Balancer Service is using a bad service account. Though the document conversion Launcher services were shown as started on one and starting mode on another server but the account that were used to start and stop these services were incorrect. You must set a proper service account for the service.


    In this blog, there is detailed resolution: http://blog.tylerholmes.com/2008/01/improperly-configured-service-accounts.html


    Hope it helps.


    Xue-Mei Chang
    Wednesday, October 22, 2008 8:38 AM
    Moderator

All replies

  • Hi
    This may because of loadbalancer.RegisterLauncher failure.
    Go to
    Central Administration
    Click Operations
    Click Service Account
    Change the service account to Document Conversions Load Balancer Service
    And Select   Network Services
    Click Save

    Try this and let me know

    Regards
    Xavier Ravi
    Wednesday, October 15, 2008 7:06 PM
  • Have you setup content sources for searching? If yes, did you use FQDN of the server or just the server name? Try using FQDN, that should resolve the issue.
    SSA
    Wednesday, October 15, 2008 7:13 PM
  • Hi,


    As Xavier said,
    this usually happens when the Document Conversions Load Balancer Service is using a bad service account. Though the document conversion Launcher services were shown as started on one and starting mode on another server but the account that were used to start and stop these services were incorrect. You must set a proper service account for the service.


    In this blog, there is detailed resolution: http://blog.tylerholmes.com/2008/01/improperly-configured-service-accounts.html


    Hope it helps.


    Xue-Mei Chang
    Wednesday, October 22, 2008 8:38 AM
    Moderator