Dealing with MOSS Error Event ID 6102
This morning a user, who is testing the MOSS Search component, reported the MOSS Search component was failing to find files that exist. This article isn’t about that error – instead when I looked at the Application Event Log on our test MOSS Server I found a swathe of Event ID 6102 Errors on the Launcher Service of Office SharePoint Server.
The particular error was referring to the LoadBalancer Service – as we have only one MOSS server we don’t use any load balancing however we can’t have this many errors blocking up the event log – otherwise I won’t be able to locate proper errors.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Launcher Service
Event ID: 6102
LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server
The first place to start with things like this is the Central Administration Component, and as the problem seems to indicate a connection problem the Service accounts section under Security Configuration section seemed like a likely place to start.
There are a few service accounts to check under this option including the Document Conversions Load Balancer Service which had no service account attached to it. This is a little unusual as we don’t fiddle around with these settings – so I switched this to a Predefined Network Service Account.
Changing this setting and confirming the changes automatically restarted the service and the Event Error messages have disappeared from the Event Log. At least now I can head off to sort out the other problem.