INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: mr95adpa on July 06, 2006, 04:58:14 pm
-
Hi,
Unfortunately I have to test beta software and this time I've been acquainted with Internet Explorer 7 Beta 3.
After installing the beta strange things has started occurring.
RSS Feeds:
Can't get an RSS Feed for podcasts. MC11.1 gives me the message "Could not read URL". Pasting the URL into IE7 however works fine.
Update:
Help->Check For Updates gives the error message:
Failed to Connect to a server. Reason Unknown Error.
YADB:
Unable to Connect to yadb, unable to connect.
Strangely enough if the Podcasts tree node is clicked the "Find and Organise Podcasts" appear and is loaded correctly. Same for Find CD or Artist Info.
Has anyone had a similar problem? I'm not sure what the difference in programming libraries are for yadb access or html access are, could it be a setup problem on my machine?
Regards
-
Media Center uses the basic Windows internet layer WinInet. It's possible Microsoft broke something with the beta.
Has anyone else tried this beta?
Thanks.
-
I have it installed and my updates (help>check for update) also do not work. :o
Later
Simon.
-
Same here, no internet action with MC since installing IE7.
-
A while back when installing IE 7 beta 2, it did indeed "break" a few things. This was a big issue over on the adobe.com forums as I (and them as well) weren't able to update their products. (via the update link similar to MC)
There's actually an explanation to this, but I ..er... I forgot. Sorry. However... the solution to fixing this problem is to... uninstall IE 7. Right, I know, I know. Once uninstalled, everything returned to normal for me. However some users reported having some "things" still broken. The price of Beta!
I'm surprise this is still an issue with beta 3, I figured it'll be fixed by now. Then again, it is Microsoft we're talking about here. ::)
-
i had the same problem updating and also could not download album cover images. with IE Beta 3 uninstalled all is once again sweetness and light.
Colin
-
IE7 uses totally new DLL'S it is not compatible also with Visual Basic 6.0 and, when IE7 is installed then the Internet Explorer control in visual basic does not work since the compatible dlls are removed from the users system, thus breaking things.
I Said This Before
-
In general, I wouldn't recommend to use any MS beta software (unless you really are a beta tester).
If you are bored with IE6 try Opera or Firefox.
-
Does this mean there is no immediate plan to make MC work with ie7? I have been using ie7 beta for some time and would hate to have to uninstall it simply because MC can no longer download podcasts because of it.
-
This may not be a question of MC working with IE so much as one of IE working with MC.
Did you report it to MS?
-
beta, beta, beta, repeat after me, beta, beta, beta
-
I am unable to connect to my Media Server through my laptop at work. It has IE7 Beta 3 installed on it. I have done some troubleshooting and do not believe it to be a problem with my configuration. I am able to VNC to my media server at home without issue. Does the library server also use the same connection method as Media Center does to connect to the Internet?
-
yes it does...
j
-
Thanks for the quick response. It looks like Microsoft is shooting for a release of IE 7 the first half of next year. How soon before J River would start supporting IE 7?
-
Try going to internet options and turning off the automatic proxy configuration checkbox. If you are using a proxy (most of you will not) you'll need to enter it manually. I did this and it worked for me.
This appears to be a known problem.
http://msdn.microsoft.com/ie/releasenotes/default.aspx
-
From the page Bob linked to:
Web Site Connectivity Issues
SSL Changes
When navigating to an HTTPS site on Windows Vista, you may encounter a connection failure error page if the server does not correctly support the TLS standard. To work around this problem, uncheck the “Use TLS v1.0” checkbox in the Internet Control Panel’s Advanced tab and notify the web site owner about this problem. (A description of the changes in SSL can be found in the Internet Explorer blog).
Proxy Connectivity
If you notice slowness or a problem connecting to web sites after upgrading to Internet Explorer 7 Beta, it may be due to Proxy Auto Detection problems.
Launch the Internet Control Panel by clicking "Internet Options" From the Internet Explorer Tools menu.
Navigate to the Connections tab
Under Local Area Networks (LAN) settings choose LAN Settings
Uncheck "Automatically detect settings" in the Local Area Network (LAN) Settings dialog,
Check "Use a proxy server for your LAN" and specify your proxy server in the Local Area Network (LAN) Settings dialog,
Click OK, OK
You will now be able to navigate to internet sites.
Internet Connection Settings
If you notice a problem connecting to web sites, it may be because the upgrade to Internet Explorer 7 changed your Internet Explorer 6 Internet Connection settings. To work around the problem:
Launch the Internet Control Panel by clicking "Internet Options" from the Internet Explorer Tools menu.
Navigate to the Connections tab
For each connection in the "Dialup and Virtual Private Networks" list, click the "Settings" button
Verify that "Automatically detect settings" is checked. If not check it
Click the "Lan Settings" button in the Connections tab, and repeat step 4 6. Click OK on the Connections tab.
Close IE and restart it.
-
For what it's worth: I've been using IE 7 for some months now and I haven't had any problems connecting to YADB or with the update-server. That all works just fine.
As far as for RSS-feeds: I don't use that so I don't know about that.
-
For what it's worth: I've been using IE 7 for some months now and I haven't had any problems connecting to YADB or with the update-server. That all works just fine.
As far as for RSS-feeds: I don't use that so I don't know about that.
Do you have beta3 installed?
-
To verify that the issue was IE 7 I down graded to IE 6 and that resolved the problems with YADB and the streaming issue with my media server. I reinstalled IE 7 Beta 3 and tried the auto detect option on and off (in addition to the dial-up and VPN connections), and the TLS 1.0 option unchecked as well (this is not a secure http session though) and still no luck. I do not use a proxy server to connect the Internet. I believe (not certain) that this worked with the two previous beta versions of IE 7. Although it doesn't impact the Internet connection settings I also ran the Reset Internet Explorer settings as well. That didn't solve the problem either.
-
Do you have beta3 installed?
No, sorry about that. I didn't know it was a 7.x issue. I have IE 7 beta 2 and that one works fine.
-
Looks like there may be something else going on. I can't seem to get yadb lookups or podcasts now too with 7b3. Stay tuned...
-
There is a certain MC plugin that won't work as well...
If you are having a problem with a plug in, try uninstalling 7b3 and it will probably work.
-
I was experiencing all of the above mentioned problems with IE7 B3. Uninstalled B3 and reinstalled B2 and can connect to server for updates and YADB.
-
I had to do the same thing. None of the suggestions in this thread worked, so I reverted back to beta 2.
-
Did you report this to Microsoft?
-
After I Had Problems With B2 I Just uninsulated it, and figured I would wait.
I did not see anything really worth the Pain since it crashed too often.
-
I have removed all of the plugins that I had installed and I am still unable to connect to my media server.
-
Did you report this to Microsoft?
Yes. The issue was reported both by myself and one other person.
-
I reverted to IE 6.0 and podcasts began downloading again... thank for he post Jim, this was really bugging me, and I had no idea why it stopped working.
-
The issue may have been resolved. I was running a late version of Vista the other day and MC installed fine and all the plugins I could not install with XP and IE7 b3 running installed just fine. That was not the case with Vista B2 public release and the version of IE it has.
In any event, looks like IE7 is going to be on Auto Update soon. At least the blocking tool has been released by MS and that usually means whatever it is going to block will soon be here.
Overview
To help our customers become more secure and up-to-date, Microsoft will distribute Internet Explorer 7 as a high-priority update via Automatic Updates for Windows XP and Windows Server 2003 soon after the final version of the browser is released (planned for fourth quarter 2006). Microsoft is making a non-expiring Blocker Toolkit available for those organizations that would like to block automatic delivery of Internet Explorer 7 to machines in environments where Automatic Updates is enabled.
From IE7 Blocker (http://www.microsoft.com/downloads/details.aspx?FamilyID=4516a6f7-5d44-482b-9dbd-869b4a90159c&DisplayLang=en)
-
I've tried all the ideas listed above, and still having the connections issues with the updates/plugins downloading. Anything new we can try yet? Uninstalling IE7 is not an option for me. TIA ;D
-
The fault is clearly with IE7b3. No software maker in their right mind would target their product to work with a buggy beta release.
Of course, no user in their right mind should install beta software on a critical machine.
-
The fault is clearly with IE7b3. No software maker in their right mind would target their product to work with a buggy beta release.
Of course, no user in their right mind should install beta software on a critical machine.
Well their gonna do an auto update so be careful. I think there is a corporate blocking installer though.
-
I uninstalled IE 7b2, reverting back to IE 6 and still no MC internet action.
I installed IE7b3 and now have internet connection apart from Podcasts. ?
-
Try 11.1.191
-
Well, kudos to JR for figinring the issue out but I still think it's bad practice to accomodate a buggy beta (IE7b3) that will be a moving target for 6 months or more.
-
Try 11.1.191
It works! ;D
Thanks a lot.
-
Well, kudos to JR for figinring the issue out but I still think it's bad practice to accomodate a buggy beta (IE7b3) that will be a moving target for 6 months or more.
Yes, they should wait until it is on many systems, >THEN< start addressing compatibility.
That's the ticket!