DCLauncher issues while configuring Document Conversion in MOSS 2007
The other day I was trying to enable the Document Conversion on my SharePoint farm and had some issues. After some research I found two different different articles that helped me fix this issue. You might encounter any one of the following issue. I encountered the second one. And I've explained the steps involved by combining the steps from these two different articles, in order.
Issue 1: Document Conversions Launcher Service is always in "starting" state (specifically when trying to enable the Launcher Service on more than one Server in the farm). The Document Conversions Launcher Service Admin UI is not functional for any Launcher that will run on a server that is not hosting the Central Administration web application. The UI will never reflect current state in this configuration.
Issue 2: You might get DCLauncher error at Microsoft.SharePoint.Win32.SPAdvApi32.SetServiceStartupType
Follow the steps to resolve these issues.
Step 1: Start the load balancing service in your application server and make a note of the port#.
Step 2: To enable the Launcher Service you must specify the necessary Launcher information that the UI normally provides. This is done by updating two values in a registry key located on the machine on which you are trying to run the Launcher service. This includes the location of the Load Balancer and the Port to use for the connection.
Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\LauncherSettings]"LoadBalancerUrl"="http://server:port/HtmlTrLoadBalancer""Port"=dword:port
LoadBalancerUrl: This is the full URL to the .NET Remoting channel that the Load Balancer opens. The scheme should be http://[please specify Load Balancer server]:[please specify Load Balancer port]/HtmlTrLoadBalancer and ensure they are accurate.
Port: This is the port that the launcher service will open for incoming .NET Remoting requests to do Conversions, e.g. "8082".
Step 3: After changing either of these settings (initially or if future machines are added and require settings changes), you must stop and start the Launcher service (Office Document Conversions Launcher Service) in the Services control panel (Start|Control Panel|Administrative Tools|Services). The services should be set to Enabled and set to start automatically (Automatic) if not so already. Any future changes to the Load Balancer settings will require updating the Launcher settings on each machine to reflect those changes. The services will also have to be stopped and then started again to pick up the new changes once updated.
If you continue to get the same issue, try restarting the service using STSADM utility.
Stop the Document Conversions Launcher Service
| 1. | Click Start, click Run, type cmd, and then click OK. |
| 2. | At the command prompt, type the following command: cd \Program Files\Common Files\microsoft shared\web server extensions\12\bin |
| 3. | At the command prompt, type the following command to create a .txt file that contains the names of all the services, and then press ENTER: STSADM -o enumservices > Drive\serv.txt Note In this command, Drive is the letter of the drive in which you want to save the .txt file. |
| 4. | At the command prompt, type the following command, and then press ENTER: stsadm -o provisionservice -action stop -servicetype ServiceTypeName -servicename ServiceName Note In this command, ServiceTypeName is the name of the servicetype that is contained in the serv.txt file. Additionally, ServiceName is the servicename that is contained in the serv.txt file. |
| 5. | At the command line, type the following to reset Internet Information Services (IIS), and then press ENTER: iisreset |
Start the Document Conversions Launcher Service
| 1. | Click Start, click Run, type cmd, and then click OK. |
| 2. | At the command prompt, type the following command: cd \Program Files\Common Files\microsoft shared\web server extensions\12\bin |
| 3. | At the command prompt, type the following command, and then press ENTER: stsadm -o provisionservice -action start -servicetype ServiceTypeName -servicename ServiceName Note In this command, ServiceTypeName is the name of the servicetype that is contained in the serv.txt file. Additionally, ServiceName is the servicename that is contained in the serv.txt file. |
| 4. | At the command line, type the following to reset Internet Information Services (IIS), and then press ENTER: iisreset |
Comments
Ran into this issue here with less favorable results:
http://www.sharepointblogs.com/spfromscratch/archive/2008/02/29/document-conversion-launcher-service-won-t.aspx
Thanks!
JK
Posted by: John K | March 3, 2008 07:01 AM