In the console tree, click the broadcast publishing point you
want to log multicast information for. If it is started, stop the
publishing point.
In the details pane, click the Properties tab.
In Category, click Multicast streaming.
In Plug-in, click WMS Multicast Data Writer, and
then click Properties.
WMS Multicast Data Writer Properties
appears.
In the Windows Media Services snap-in, click the
Advanced tab.
Configure the following setting:
Logging URL. Type the URL of the Wmsiislog.dll file on
your Web server, such as
http://web_server_name/virtual_directory/wmsiislog.dll.
Click OK to apply the new setting to the plug-in.
In the details pane, click the Enable button.
Run the Multicast Announcement Wizard to create a new multicast
information file (.nsc file) for your multicast.
Notes
This procedure requires that your Web server
running Internet Information Services (IIS) has a virtual directory
that references the %systemdrive%\WMPub\WMIISlog directory
and that the Wmsiislog.dll has been granted executable permissions
on the virtual root. For more information about using executable
ISAPI filters and Web service extensions, see Internet Information
Services Help.
If you want to change the log file recycling
period, you can change the setting in Internet Information Services
(IIS). For more information about log file settings, see IIS
Help.
A client sends logging information to the IIS
server after the client stops streaming a multicast. After the
server receives logging information from a client, it may take
several minutes before that information is added to the log
file.
If you change the settings of the WMS Multicast
Data Writer plug-in, you must create a new multicast information
file for clients to be able to receive to the multicast stream. You
can create the multicast information file by using the Multicast
Announcement Wizard available in the Windows Media Services
snap-in.
Windows Media Services does not include a
logging plug-in that works with encoder push scenarios. You can log
encoder push broadcast data by creating an active script logging
plug-in. For more information about creating a custom plug-in, see
the Windows Media Services Software Development Kit (SDK), which
can be downloaded from the Windows Media home page at the Microsoft Web site.
The default location of the multicast log files
created by the Multicast and Advertisement Logging Agent is
%systemroot%\System32\LogFiles\WMS_ISAPI. The log file name
is WMS_yyyymmdd.log, where yyyymmdd is the year,
month, and day when the log file is created. If more than one log
file is generated in a day, an incremented number is added to the
file name, using the format WMS_yyyymmdd_iiii.log. For
example, if the first log is named WMS_20040304.log, the second log
on that day is named WMS_20040304_0001.log, and so forth.
The server does not use your user account to
access folders and other resources; it uses the Network Service
account by default. If you are writing log files to a location
other than C:\WMPub and its subdirectories, make sure that the
folder is shared and that the Network Service account has read and
write permissions for the folder. If the Network Service account
does not have permissions for a folder, the server will not be able
to write log files to it. For more information about rights and
permissions, see Understanding
rights.
Multicast streaming and the WMS Multicast Data
Writer plug-in are available only if Windows Media Services 9
Series is running on the following editions of the operating
system: Windows Server 2003, Enterprise Edition and Windows Server
2003, Datacenter Edition. If you are running Windows Server 2003,
Standard Edition, these features are not supported.
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.
Notes