Here's an irritating error that I bump into lately:
Event Source: Office SharePoint Server Event
Category: Launcher Service
Event ID: 6102
User: N/A
Description: LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server.
This error usually happens when Document Conversions Load Balancer Service is using a wrong service account.
To resolve this error Try the following steps:
This error usually happens when Document Conversions Load Balancer Service is using a wrong service account.
To resolve this error Try the following steps:
1. Configuring the proper Service Accounts
- Central Administration -> Operations.
- Security Configuration -> Service account.
- Click the Windows Service radio button -> select Document Conversions Load Balancer Service.
- Fill in the proper service account. <<- 네트워크 서비스 로 수정 후 시작
2. restarting the services.
- Central Administration -> Operations -> Services on Server.
- Click Stop on the Document Conversions Load Balance Service. …And stop the Document Conversions Launcher Service too.
- Start the services and the error will not appear again.
After this procedure the error will disappear.
(그림 포함한 잘 정리된 링크: http://www.jasonslater.co.uk/2009/08/24/dealing-with-moss-error-event-id-6102/)
아악 징글징글 하다 MOSS를 몇번이나 지우고 다시 깔았는지 모르겠지만.. 이 방법 안해 본것도 아닌데..
어째... 갑자기 잘되는 걸까? 싸악~ 잘 지우고 다시 깔고 셋팅 해서 그러는 것일까??
내가 시도 한 방법 두번째
Document Conversions Launcher Service is stuck on starting
(그림 포함한 잘 정리된 링크: http://www.jasonslater.co.uk/2009/08/24/dealing-with-moss-error-event-id-6102/)
아악 징글징글 하다 MOSS를 몇번이나 지우고 다시 깔았는지 모르겠지만.. 이 방법 안해 본것도 아닌데..
어째... 갑자기 잘되는 걸까? 싸악~ 잘 지우고 다시 깔고 셋팅 해서 그러는 것일까??
내가 시도 한 방법 두번째
Document Conversions Launcher Service is stuck on starting
If the Document Conversions Launcher Service is stuck on starting you should be able to fix this via the following steps: -
1. You must log in with moss admin account before running these commands in a DOS window. Execute this command
Cd %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\bin
2. Execute this command:
STSADM.EXE -o provisionservice -action stop -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
3. Execute this command:
iisreset /noforce
4. Execute this command:
STSADM.EXE -o provisionservice -action start -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
5. Execute the command
iisreset /noforce
6. Check that the status is set to Started to confirmed it has worked
세번째는 MSDN에 나와있는 해결 방법 이었는데, 링크를 어따 두었는지..
여튼.. 해결 휴... ㅜ
Cd %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\bin
2. Execute this command:
STSADM.EXE -o provisionservice -action stop -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
3. Execute this command:
iisreset /noforce
4. Execute this command:
STSADM.EXE -o provisionservice -action start -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
5. Execute the command
iisreset /noforce
6. Check that the status is set to Started to confirmed it has worked
세번째는 MSDN에 나와있는 해결 방법 이었는데, 링크를 어따 두었는지..
여튼.. 해결 휴... ㅜ
댓글 영역