IIS Media Services publish point state after machine rebootRSS

2 replies

Last post Mar 12, 2014 07:33 PM by DBristol

  • IIS Media Services publish point state after machine reboot

    Feb 25, 2014 02:01 AM|devendra_sipl|LINK

    I'm working on a Smooth Streaming project and using Windows Azure virtual machine (Windows Server 2008 R2) to store media contents. Streaming is working fine, but having some problem with publish point state. Publish point states are

    Idle: Publish point created/Shut down

    Starting: Publish point is connected

    Started: It's streaming

    Stopped: Streaming stopped

    Please read the following two cases:

    Case-1: Windows Azure virtual machine (Windows Server 2008 R2) I've IIS Media Services installed on this machine. I create publish point and start encoding using Microsoft Expression Encoder. Now the publish point is in Stopped state. I've selected to archive my streaming. So, publish point associates the archive path of the media contents (ismv, ism, ismc). But, if virtual machine restart manually or inadvertent, then all my publish points turned to idle state. In that case I lost the associated archive path and now can't do the on-demand streaming.

    Case-2: My local computer Windows 8 Pro I do the same as case 1 but the difference is that after reboot/restart computer my publish point states become same it was. I mean idle publish point will be idle and stopped will be stopped. In that case I can do the on-demand streaming.

    So, finally I don't want to stop my on-demand streaming after machine reboot. I want my publish points in same states.

    Is there any way/utility which help me?

  • Re: IIS Media Services publish point state after machine reboot

    Feb 26, 2014 03:46 AM|SenneVL|LINK

    I think this is what you need:

    http://technet.microsoft.com/en-us/library/cc725841.aspx

     

     

  • Re: IIS Media Services publish point state after machine reboot

    Mar 12, 2014 07:33 PM|DBristol|LINK

    The publishing points really weren't designed to be resiliant after a reboot.  I would suggest that after a live event that you point to the archive location directly for the on demand clip and not always have the ISML file as your source.  The ISML should only be used temporarily after the live broadcast.