Share via

Event ID 329 — Event Notification

  • Article

Applies To: Windows Server 2008

You can configure Event Notification plug-ins in Windows Media Services to receive notices of client and server internal events and then respond to changes in the state of the Windows Media server. For example, you can use a script to customize the way that the Windows Media server authorizes and responds to internal events or you can receive notification of internal Windows Media server events through Windows Management Instrumentation (WMI) and route them to an external application. To view all the possible internal events that the Windows Media server can report, see Windows Media Services SDK: Internal Events.

Event Details

Product: Windows Media Services
ID: 329
Source: WMServer
Version: 9.5
Symbolic Name: WMS_EVMSG_ACTIVE_SCRIPT_ERROR
Message: The WMS Active Script Event Handler plug-in encountered the following error:
%1 reported the following: %2
Line number %3
Character: %4

Resolve

Debug the script file

To resolve this issue, do the following in the specified order:

  • If necessary, enable script debugging.
  • Configure Windows Media Services to operate in the Local System account.
  • Debug the script.
  • Return Windows Media Services to operate in the Network Service account.

Enable script debugging

To enable script debugging:

  1. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server or the publishing point for which the WMS Active Script Event Handler plug-in is enabled.
  3. In the details pane, click the Properties tab.
  4. In Category, click Event notification.
  5. In Plug-in, right-click WMS Active Script Event Handler, and then click Properties.
  6. In the WMS Active Script Handler Properties dialog box, on the General tab, select the Enable script debugging check box.
  7. Install a script debugger if you do not have one installed. You can download Microsoft Script Debugger from MSDN: Scripting.

Note: Custom scripts must be written in a scripting language that supports Microsoft ActiveX scripting interfaces and the correct script engine must be installed for the debugger to work correctly. The Microsoft Visual Basic Scripting Editing (VBScript) and JScript engines are installed by default with the Windows operating system. If you use another scripting language, make sure to install the correct script engine.

Configure Windows Media Services to operate in the Local System account

To use Microsoft Script Debugger, you must configure Windows Media Services to operate in the Local System account.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To configure Windows Media Services to operate in the Local System account:

  1. Click Start, click Administrative Tools, and then click Services.
  2. In the Services list, right-click Windows Media Services, and then click Properties.
  3. In the Windows Media Services Properties (Local Computer) dialog box, on the Log On tab, click Local System account.
  4. Click OK to save the changes.

Debug the script

When script debugging is enabled for Windows Media Services, the script debugger attached to the script file collects the error information to allow you to troubleshoot the callback procedures in the script. To view the error information trapped by the script debugger, perform the following procedure.

To debug the script file:

  1. If script debugging was not previously enabled, run the script again.
  2. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  3. In the console tree, click the Windows Media server or the publishing point for which the WMS Active Script Event Handler plug-in is enabled.
  4. In the details pane, click the Properties tab.
  5. In Category, click Event notification.
  6. In Plug-in, right-click WMS Active Script Event Handler, and then click Properties.
  7. In the WMS Active Script Handler Properties dialog box, on the General tab, view the information about the error that was encountered in the Last script error information box.

Configure Windows Media Services to operate in the Network Service account

Windows Media Services must operate in the Network Service account to maintain adequate security. After script debugging is completed, perform the following procedure to return Windows Media Services to operate in the Network Service account.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To configure Windows Media Services to operate in the Network Service account:

  1. Click Start, click Administrative Tools, and then click Services.
  2. In the Services list, right-click Windows Media Services, and then click Properties.
  3. In the Windows Media Services Properties (Local Computer) dialog box, on the Log On tab, click This account.
  4. Click Browse, and then in the Select User dialog box, in Enter the object name to select, type Network Service.
  5. Click OK to save the changes.

Verify

The steps to verify that an Event Notification plug-in is working correctly vary depending on the plug-in that you want to use.

For the WMS Active Script Event Handler plug-in:

  1. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server or the publishing point for which you want to enable script responses to internal events.
  3. In the details pane, click the Properties tab.
  4. In Category, click Event Notification.
  5. In Plug-in, right-click WMS Active Script Event Handler, and then click Properties.
  6. In the WMS Active Script Event Handler Properties dialog box, in File name of script to run, enter the path of the script file.
  7. In Plug-in, right-click WMS Active Script Event Handler, and then click Enable.
  8. The WMS Active Script Event Handler plug-in will respond to event notices raised from the Windows Media server by calling the appropriate callback function in the script file that you created. Verify that the Windows Media server performs the action indicated by the callback function in the script file.

For the WMS WMI Event Handler plug-in:

  1. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server or the publishing point for which you want to receive notification of internal events.
  3. In the details pane, click the Properties tab.
  4. In Category, click Event Notification.
  5. In Plug-in, right-click WMS WMI Event Handler, and then click Properties.
  6. In the WMS WMI Event Handler Properties dialog box, in Classes, select which event to report individually or by clicking Select All or Clear All. For more information about the WMI event classes that Windows Media Services reports, see WMS WMI Event Handler.
  7. In Plug-in, right-click WMS WMI Event Handler, and then click Enable.
  8. For each Windows Media Services internal event, the WMS WMI Event Handler plug-in will generate an event notification for other applications by using Windows Management Instrumentation (WMI). Verify that the application receives notifications for the selected events.

Event Notification

Streaming Media Services