PUSH encoding errors
John
little problems. However, all of a sudden lately I have been getting clients
setting up new encoders with PUSH and they are getting the "The service that
received the HTTP push request is not a compatible
version of Windows Media Services (WMS). This error may indicate the
push request was received by IIS instead of WMS. Ensure the WMS
is started and has the HTTP Server control protocol properly enabled
and try again".
I have multiple PUSH sessions working on the server, so I am pretty sure it
is not the server. Any idea why this has been happening so frequently in
just the last couple of weeks? Or is it just a coincidence?
Neil Smith [MVP Digital Media]
The message is exactly that, as above :
(1) Did somebody start using IIS or another web server on that server,
without telling you ? Check !
Anything listening on port 80 will block the media server from binding
(listening) on port 80 itself - that might also include a wide range
of other random programs like Skype for one - although obviously
you're not going to run that on a server, RIGHT? LOL
(2) Make sure you have the HTTP protocol enabled and running.
On the Server (not PP) tab, go to Properties -> Control Protocol and
ensure WMS HTTP Server control protocol is set to Enabled.
If not Enable it. If it fails to Enable, you have a port 80 conflict
and need to disable the web server we mentioned before, or bind the
web server to a specific IP address not used by the media services.
HTH
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2009
http://mvp.support.microsoft.com/mvpfaqs
Darrell Yaw
Are you running your Streaming Server on the same machine as a Web Server. If you got that error every time, it would suggest that you are trying to push to the port of the Web Server instead of the Streaming Server port.
Are the encodings using a port number in the server address?
>> On Sunday, November 29, 2009 9:06 AM Neil Smith [MVP Digital Media] wrote:
>> The message is exactly that, as above :
>>
>> (1) Did somebody start using IIS or another web server on that server,
>> without telling you ? Check !
>>
>> Anything listening on port 80 will block the media server from binding
>> (listening) on port 80 itself - that might also include a wide range
>> of other random programs like Skype for one - although obviously
>> you are not going to run that on a server, RIGHT? LOL
>>
>> (2) Make sure you have the HTTP protocol enabled and running.
>>
>> On the Server (not PP) tab, go to Properties -> Control Protocol and
>> ensure WMS HTTP Server control protocol is set to Enabled.
>>
>> If not Enable it. If it fails to Enable, you have a port 80 conflict
>> and need to disable the web server we mentioned before, or bind the
>> web server to a specific IP address not used by the media services.
>>
>> HTH
>> Cheers - Neil
>> ------------------------------------------------
>> Digital Media MVP : 2004-2009
>> http://mvp.support.microsoft.com/mvpfaqs
>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>> Auto-Generate Code for LINQ to SQL Repository Pattern using T4
>> http://www.eggheadcafe.com/tutorials/aspnet/a7ee34d2-c297-4ec8-a933-69254242b21b/autogenerate-code-for-linq-to-sql-repository-pattern-using-t4.aspx
Darrell Yaw
Are you running your Streaming Server on the same machine as a Web Server. If you got that error every time, it would suggest that you are trying to push to the port of the Web Server instead of the Streaming Server port.
Are the encodings using a port number in the server address?
> On Monday, November 23, 2009 7:28 PM John wrote:
>> On Sunday, November 29, 2009 9:06 AM Neil Smith [MVP Digital Media] wrote:
>> The message is exactly that, as above :
>>
>> (1) Did somebody start using IIS or another web server on that server,
>> without telling you ? Check !
>>
>> Anything listening on port 80 will block the media server from binding
>> (listening) on port 80 itself - that might also include a wide range
>> of other random programs like Skype for one - although obviously
>> you are not going to run that on a server, RIGHT? LOL
>>
>> (2) Make sure you have the HTTP protocol enabled and running.
>>
>> On the Server (not PP) tab, go to Properties -> Control Protocol and
>> ensure WMS HTTP Server control protocol is set to Enabled.
>>
>> If not Enable it. If it fails to Enable, you have a port 80 conflict
>> and need to disable the web server we mentioned before, or bind the
>> web server to a specific IP address not used by the media services.
>>
>> HTH
>> Cheers - Neil
>> ------------------------------------------------
>> Digital Media MVP : 2004-2009
>> http://mvp.support.microsoft.com/mvpfaqs
>>> On Thursday, September 09, 2010 11:46 AM Darrell Yaw wrote:
>>> Many time when we experience that error it is because the port that we are trying to use or the url of our server is being blocked by a firewall at the location where we streaming from.
>>>
>>>
>>>
>>> Are you running your Streaming Server on the same machine as a Web Server. If you got that error every time, it would suggest that you are trying to push to the port of the Web Server instead of the Streaming Server port.
>>>
>>>
>>>
>>> Are the encodings using a port number in the server address?
>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>> Assemblies in Folder Debug Build Checker
>>> http://www.eggheadcafe.com/tutorials/aspnet/d7de5fe1-6155-4e81-96e1-9806fd69d760/assemblies-in-folder-debug-build-checker.aspx