Media Center guide download error code 13

re: Media Center guide download error code 13

Nick — Thu, 13 Jan 2011 16:10:59 GMT

I also was constantly recieveing error code#13. The Guide would download as much as 20% and then I would recieve the #13 error I found after synchronizing the time it would still have the same behavior. However disabling the Windows Firewall during the download seem to do the trick, the entire update downloaded successfully. Afterwards I re-enabled the firewall !

re: Media Center guide download error code 13

Dragonfly — Sat, 03 May 2008 18:57:19 GMT

#3 (adding ehSched.exe to the Windows Firewall Exception List) worked for me when I encountered this problem on one of my Vista Ultimate SP1 machines. Thanks!

re: Media Center guide download error code 13

hexangel — Thu, 03 Apr 2008 07:13:27 GMT

Thanks!

#2 worked great for me on XP Media Center Toshiba Qosmio G30 Laptop w/ cable modem.

re: Media Center guide download error code 13

joshua.mccullough@gmail.com — Tue, 26 Jun 2007 00:12:47 GMT

I hate to keep leaving comments but I just set the services back to NETWORK SERVICE and now I can download the guide. I guess I will have to reconfigure my media server to allow Everyone access to the media....any ideas on how to get MC to work when it is running under a different user?

re: Media Center guide download error code 13

joshua.mccullough@gmail.com — Mon, 25 Jun 2007 23:16:26 GMT

Forgot to mention, that HSM path does NOT exist. I tried to give everyone permissions to the eHome directory thinking that MediaCenter was unable to create that directory. (I have my MC services running under a different user.) But still no luck.

re: Media Center guide download error code 13

joshua.mccullough@gmail.com — Mon, 25 Jun 2007 23:05:40 GMT

BigStickCarpet: I have the same issue in Vista. When I look in my log I also see:

IOException in getting files from HmsFilePath System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\ProgramData\Microsoft\eHome\Hms'.

I, indeed, do not have this path. I'm not even sure what HMS is. Anyone know? Do other people have this path? In the beginning of the log you see MediaCenter trying to send an HMS file and failing. I wonder if this is why the entire guide-download process is failing for some of us.

More detailed error information

JM_MSDN — Mon, 19 Mar 2007 00:45:37 GMT

Vista Media Center writes detailed log information to the following file when retrieving guide listings: C:\ProgramData\Microsoft\eHome\EPG\tracehelper\DefaultDomain-MediaCenterService.xml

I opened this file and found that the actual error I'm getting (the one that's causing the "Error Code 13" message) is "Failure attempting to download new Guide data.

Unable to add files to bits job". Does that mean anything to anybody? Here's a snippet of the lines leading up to the error: Notice the warnings about a failure to upload HMS data. Could that be related to the problem?

<event level="Error" source="Media Center Guide" time="2007:03:18 04:30:04:111243" eventid="13" category="0">Failure attempting to download new Guide data.

Unable to add files to bits job</event>

<event level="Info" source="Media Center Guide" time="2007:03:18 04:30:04:111243" eventid="0" category="0">State now changed to: STATE_ERROR

</event>

<event level="Info" source="Media Center Guide" time="2007:03:18 04:30:03:828058" eventid="0" category="0">Downloading files http://epg.tvdownload.microsoft.com/epgdata/us/1/2642993102/29/31/58/28513928/28513928_ListingData.txt?clientId=e703fdfd2c224ee0870c9b22f3e63789&sessionToken=380A699E8772D72FE1BA1BFD13632FA285738C3B8DEB3D64566AC72AC132D481787CB63C1AD7C585BED7A9978AEC52C11233F0ED292EB8AC

</event>

<event level="Info" source="Media Center Guide" time="2007:03:18 04:30:03:827082" eventid="0" category="0">@ Ehepgdat Downloading files

</event>

<event level="Warning" source="Media Center Guide" time="2007:03:18 04:30:03:827082" eventid="0" category="0">Unable to send Hms file

</event>

<event level="Warning" source="Media Center Guide" time="2007:03:18 04:30:03:827082" eventid="0" category="0">@ Ehepgdat: HmsTransmit Run Failed

</event>

<event level="Info" source="Media Center Guide" time="2007:03:18 04:29:57:827466" eventid="0" category="0">@ Ehepgdat Uploading HmsInfo

</event>

re: Media Center guide download error code 13

Aaron Stebner — Mon, 19 Feb 2007 19:28:56 GMT

Hi Jperry13 - I don't know enough about how the guide functionality was implemented behind the scenes and I also haven't heard of a case like this in my past experience, so I'm not sure what to suggest as a workaround here. You might want to post a question on the Microsoft.Public.Windows.MediaCenter newsgroup or one of the Media Center forums like http://www.thegreenbutton.com and hopefully someone there will be able to assist.

AFN Guide times

Jperry13 — Mon, 19 Feb 2007 13:31:45 GMT

I am posting on your blog because you seem to be the authority on getting MC Guide issues worked out.

I recently set up my MC computer with my AFN satellite system. (I am stationed over in Japan.) And while the AFN schdule information is actually in the system under zip code 96349 (The FPO AP zip code), the schedule that is provided is shifted for the Central time zone.

My question; Is there a way to trick the system, short of changing the system clock and disabling the MS clock sync function?

Thanks,

Josh Perry

re: Media Center guide download error code 13

phobix — Wed, 14 Feb 2007 04:27:59 GMT

This blog was helpful. I am running Vista Ultimate and was experiencing the dreaded error 13, it so turns out that my firewall's (Astaro Security Linux) transparent proxy doesn't properly support http byte-ranged requests. ASL uses squid proxy, so I imagine that if your ISP is using some derivative of squid proxy you are out of luck. In my case it was easy to address since I am the custodian of the firewall and my ISP doesn't run any sort of transparent proxy. Interestingly, I did experience simular issues with YUM update on my Linux based VMs under vmware. What I did to solve the issue was the to define the Vista host under ASL, exclude it from the proxy, and then define 2 explicit packet filter rules to allow it direct access to TCP 80 and TCP 443. The guide worked great after that. Just thought I would let you all know what worked for me.