Windows Media Services (web) David McCollough 03.07.2007 21:16:01 We have installed Windows Media Services Version 9.01.01.3841 on a server running Windows 2003 Standard patched to SP2. This server has Internet Explorer 7 installed. Whenever we attempt to access the Windows Media Service (web) shortcut, or inside of IIS if we attempt to browse to the web site. We get the following error message: Browser not supported The Windows Media Services Web Administrator requires Netscape version 5 or later. You are currently connected using: Browser: Netscape Version: 4 I saw a blurb stating that we had to make the URL for the Web Administrator either a trusted site or a local intranet site. I have tried both and still get the error message. I can dig into the javascript and fix this problem myself, but I thought I would check and see if there is a more approved method of correcting this error. Thanks David M. McCollough

Re: Windows Media Services (web) "Neil Smith [MVP Digital Media]" <neil[ at ]nospam.com> 04.07.2007 19:55:04 On Tue, 3 Jul 2007 14:16:01 -0700, David McCollough <david.mccollough[ at ]newsgroups.nospam> wrote: [Quoted Text] >We have installed Windows Media Services Version 9.01.01.3841 >on a server running Windows 2003 Standard patched to SP2. > >This server has Internet Explorer 7 installed. > >Whenever we attempt to access the Windows Media Service (web) shortcut, or >inside of IIS if we attempt to browse to the web site. > >We get the following error message: > >Browser not supported > >The Windows Media Services Web Administrator requires Netscape version 5 or >later. > >You are currently connected using: > Browser: Netscape >Version: 4 > >I saw a blurb stating that we had to make the URL for the Web Administrator >either a trusted site or a local intranet site. > >I have tried both and still get the error message. > >I can dig into the javascript and fix this problem myself, but I >thought I would check and see if there is a more approved method >of correcting this error. > The web administrator tool hasn't been updated for ages (hence it's still even aware of NN4). You could try Sandy Hardmeiers advice and set the user agent string to IE6, http://www.ie-vista.com/sites.html Let me know if that works cause otherwise I'll have to fire up vista and install the web admin here to check ;-) HTH Cheers - Neil ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs

Re: Windows Media Services (web) David McCollough 05.07.2007 15:48:03 Neil: I have tried the utility mentioned in Sandy's article. Using it I can at least get to the first page of the Web Administration tool, however if I try and click on publishing points the web site throws a 500 error. If I use the MMC snap in on the server it seems to work fine. Does Microsoft not intend for us to be able to administer via the web ? I am fine using using the MMC on the server to administer, however one of my colleagues is pretty adamant about wanting to use the web administration. Thanks "Neil Smith [MVP Digital Media]" wrote: [Quoted Text] > On Tue, 3 Jul 2007 14:16:01 -0700, David McCollough > <david.mccollough[ at ]newsgroups.nospam> wrote: > > >We have installed Windows Media Services Version 9.01.01.3841 > >on a server running Windows 2003 Standard patched to SP2. > > > >This server has Internet Explorer 7 installed. > > > >Whenever we attempt to access the Windows Media Service (web) shortcut, or > >inside of IIS if we attempt to browse to the web site. > > > >We get the following error message: > > > >Browser not supported > > > >The Windows Media Services Web Administrator requires Netscape version 5 or > >later. > > > >You are currently connected using: > > Browser: Netscape > >Version: 4 > > > >I saw a blurb stating that we had to make the URL for the Web Administrator > >either a trusted site or a local intranet site. > > > >I have tried both and still get the error message. > > > >I can dig into the javascript and fix this problem myself, but I > >thought I would check and see if there is a more approved method > >of correcting this error. > > > > The web administrator tool hasn't been updated for ages (hence it's > still even aware of NN4). You could try Sandy Hardmeiers advice and > set the user agent string to IE6, http://www.ie-vista.com/sites.html > > Let me know if that works cause otherwise I'll have to fire up vista > and install the web admin here to check ;-) > > HTH > Cheers - Neil > ------------------------------------------------ > Digital Media MVP : 2004-2007 > http://mvp.support.microsoft.com/mvpfaqs >

Re: Windows Media Services (web) "Neil Smith [MVP Digital Media]" <neil[ at ]nospam.com> 05.07.2007 21:40:52 On Thu, 5 Jul 2007 08:48:03 -0700, David McCollough <david.mccollough[ at ]newsgroups.nospam> wrote: [Quoted Text] >Neil: >I have tried the utility mentioned in Sandy's article. Using it I can at >least get to the first page of the Web Administration tool, however if I try >and click on publishing points the web site throws a 500 error. The 500 range of error messages are "server mis configuration", so are unlikely to be caused by your web server. Please can you review the requirements for running the web admin, for example it might require ..NET1 (though it could be ASP classic, I can't remember without installing) >If I use the MMC snap in on the server it seems to work fine. >Does Microsoft not intend for us to be able to administer via the web ? The snap in are HTA applications, which run most of their code in IE browser. I don't think there's a specific relation given that the error above is a server error not a client error. >I am fine using using the MMC on the server to administer, however one of my >colleagues is pretty adamant about wanting to use the web administration. You might want one of your web team to look at the IIS error log, to see what they can glean from the 500 server errors. Make sure they've turned on error logging in IIS, of course ;-) HTH Cheers - Neil ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs

Re: Windows Media Services (web) David McCollough 05.07.2007 21:58:01 Neil: It's working now, I'm not sure how it got fixed. But it is definetely working. Thanks for your help. David "Neil Smith [MVP Digital Media]" wrote: [Quoted Text] > On Thu, 5 Jul 2007 08:48:03 -0700, David McCollough > <david.mccollough[ at ]newsgroups.nospam> wrote: > > >Neil: > >I have tried the utility mentioned in Sandy's article. Using it I can at > >least get to the first page of the Web Administration tool, however if I try > >and click on publishing points the web site throws a 500 error. > > > The 500 range of error messages are "server mis configuration", so are > unlikely to be caused by your web server. Please can you review the > requirements for running the web admin, for example it might require > ..NET1 (though it could be ASP classic, I can't remember without > installing) > > > >If I use the MMC snap in on the server it seems to work fine. > >Does Microsoft not intend for us to be able to administer via the web ? > > > The snap in are HTA applications, which run most of their code in IE > browser. I don't think there's a specific relation given that the > error above is a server error not a client error. > > > >I am fine using using the MMC on the server to administer, however one of my > >colleagues is pretty adamant about wanting to use the web administration. > > You might want one of your web team to look at the IIS error log, to > see what they can glean from the 500 server errors. Make sure they've > turned on error logging in IIS, of course ;-) > > HTH > Cheers - Neil > ------------------------------------------------ > Digital Media MVP : 2004-2007 > http://mvp.support.microsoft.com/mvpfaqs >

Re: Windows Media Services (web) "Neil Smith [MVP Digital Media]" <neil[ at ]nospam.com> 06.07.2007 17:22:59 The techies probably pressed the magic red button (the one developers press when they realise they've cocked up, and fix it without telling anybody ;-) Cheers - Neil On Thu, 5 Jul 2007 14:58:01 -0700, David McCollough <david.mccollough[ at ]newsgroups.nospam> wrote: [Quoted Text] >Neil: > >It's working now, I'm not sure how it got fixed. But it is definetely working. > >Thanks for your help. >David > >"Neil Smith [MVP Digital Media]" wrote: > >> On Thu, 5 Jul 2007 08:48:03 -0700, David McCollough >> <david.mccollough[ at ]newsgroups.nospam> wrote: >> >> >Neil: >> >I have tried the utility mentioned in Sandy's article. Using it I can at >> >least get to the first page of the Web Administration tool, however if I try >> >and click on publishing points the web site throws a 500 error. >> >> >> The 500 range of error messages are "server mis configuration", so are >> unlikely to be caused by your web server. Please can you review the >> requirements for running the web admin, for example it might require >> ..NET1 (though it could be ASP classic, I can't remember without >> installing) >> >> >> >If I use the MMC snap in on the server it seems to work fine. >> >Does Microsoft not intend for us to be able to administer via the web ? >> >> >> The snap in are HTA applications, which run most of their code in IE >> browser. I don't think there's a specific relation given that the >> error above is a server error not a client error. >> >> >> >I am fine using using the MMC on the server to administer, however one of my >> >colleagues is pretty adamant about wanting to use the web administration. >> >> You might want one of your web team to look at the IIS error log, to >> see what they can glean from the 500 server errors. Make sure they've >> turned on error logging in IIS, of course ;-) >> >> HTH >> Cheers - Neil >> ------------------------------------------------ >> Digital Media MVP : 2004-2007 >> http://mvp.support.microsoft.com/mvpfaqs >> ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs