Packager Service Does Not Start If SQL Server Is Not Running (231644)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

If the SQL Server computer that Windows Media Rights Manager uses is installed on the same computer as the Rights Manager, the Rights Manager may fail to start if the SQL Server service is not started first.

CAUSE

Windows Media Rights Manager Packager Service requires SQL Server to be running when the Packager Service starts. If SQL Server is installed on a separate computer, the MSSQLServer service must be started before the Packager Service will start. The same applies if SQL Server is installed on the same computer as Windows Media Rights Manager; however, you can make the Packager Service a dependency service of SQL Server.

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To make the Packager Service depend on SQL Server at startup, use the following steps:

Start Registry Editor (Regedt32.exe).
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WMPackager
On the Edit menu, click Add Value, and then add the following registry value:
Value Name: DependOnService
Data Type: REG_MULTI_SZ
Value: MSSQLServer
Quit Registry Editor.
Shutdown and restart your computer.