I am all of a suuden having an issue streaming my webguide vidoes from my Vista PC. This has worked fine in the past and now for some odd reason it will not. I am getting the error message "Windows Media Player cannot find the file. If you are trying to play, burn, or sync an item that is in your library, the item might point to a file that has been moved, renamed, or deleted."
I can play media from my library no problem and I even tried connecting to my webguide from a differnt PC so I know it is mine that is having the issue. I have tried these options below and it still is giving me fits. i have seen a lot of posts where people have this problem, but haven't seen any real solutions.
You've encountered error message C00D1197 while using Windows Media Player. The following information might help you troubleshoot the issue.
Windows Media Player cannot find the file. You might encounter this error message for one of the following reasons:
You are trying to use a file in the Windows Media Player library, but the Player cannot find the file. The file may have been moved, renamed, or deleted from your computer.
You are trying to use a file that is stored on another computer, but you are not connected to a local area network (LAN) or to the Internet. Connect to the network or Internet, and then try again.
You entered a Uniform Resource Locator (URL) in the Open URL dialog box, but the path is not valid. Verify that the file name is spelled correctly and that the path to the file is correct.
You clicked a link on a Web page, but the link is not valid.
You are trying to use a file that is stored on a server, but the server is not available (for example, the server is busy or not online).
You are trying to use a file that is stored on a server, but some network protocols in the Player are not enabled. Enable all network protocols, and then try again.
You are trying to use a file that is stored on a server, but the server is not configured correctly for protocol rollover (for example, you connected to the server using the MMS protocol, but the server cannot roll over to the HTTP protocol to deliver the content). If you still cannot use the file after enabling all network protocols in the Player, contact the Web page provider.
You are trying to use a file that is stored on another computer, but the proxy server settings for the Player are not configured properly. Verify that your proxy settings are correct.
Click the arrow below the Now Playing tab, and then click More Options.
Click the Network tab.
In the Streaming protocols area, select all the protocol check boxes.
Verify your settings in the Streaming proxy settings area.
If you do not know what your proxy server settings should be, on the Network tab, select a protocol, click Configure, and then select Autodetect proxy settings or Use proxy settings of the Web browser (available for HTTP protocol only).
This error might have been triggered by an error in another program or component of Windows. The following information describes the original error.
Original Error Code
Original Error Message
error message not available
For information about obtaining technical support from Microsoft, see the Troubleshooting Windows Media Player page.
For general information about using Windows Media Player and other Windows Media technologies, see the Windows Media Player FAQ page or the Windows Media Knowledge Center.
System: Windows 7 64-bit; MSI 785GTM-E45; AMD Phenom II X6 1045T (95W)Hardware: 1.5TB WD Green HDD; 4GB (2x2GB) DDR2 800 SDRAM; Silverstone Grandia GD04B; Scythe Shuriken Rev B.Tuners: HD HomeRun; Ceton InfiniTV 4Networking: Linksys DMA2100 (x2); Xbox 360; Netgear WNDR4000 Router; WHS (Acer EasyStore AH341);Display: Samsung HP-R4252
Actually, I just solved it. Not sure why it was needed, but in the config tool, I disabled everything that had to do with streaming and reset the recorded TV folder to the default location on the c drive (I have D drive dedicated to recordings). I saved, then re-enabled, and replaced the recorded tv location to my D drive.
Another save and everything works again. No clue, but one less thing that's broken.