Just for the record this has happened to me twice since I upgraded to the TV pack. Once I restored just the eHome directory, and the second time I rebuilt from scratch.

Now I'm doing diff' images every night in case it happens again.

I'm convinced it is bad guide data as both times it happened when I was adding/removing recordings from the guide.

I have two CableCARD tuners and a HDHomeRun (ATSC).

---

Ben
How good can it be, if it isn't HD?
Engadget HD

Heh i actually already do that as we speak.. its the only way to ensure full-backupability.  

Who else here thinks that all these bugs would of been squashed already if they would of allowed more of us to test the TV pack or even had a Public beta.   I can imagine the headaches this is already causing the customer integrator market who were sent this officially.

I doubt they would've been fixed, in fact what I'm told is that none of the bugs by the semi-public beta were even fixed before it was released. You can go back and read my posts about how all the beta testers refused to believe the news that the TV Pack went RTM, with responses like, "no way it's out with the bugs that haven't been fixed yet." But yet here it is, enjoy.

---

Ben
How good can it be, if it isn't HD?
Engadget HD

I had this, it started as an inability to search for programmes in the guide, followed a week later by all scheduled recordings being completely ignored.

Solved it by stopping all MCE services, then deleting the guide database file mcepg1-0 and a folder with the same name. Its located in C:\ProgramData\Microsoft\eHome. You have to run guided setup again for TV signal after doing this. This appeared to be corruption of the database and was accompanied by a crash report log in the eHome directory each time a recording attempted to start.

For anyone searching, here was the data in my crash logs:

 

[Crash Information]
ReportVersion=2
MainBinary=C:\Windows\ehome\ehRec.exe
MainBinaryVersion=6.1.1000.18273 (longhorn_mc_dev(wmbla).080702-2208)
CrashTime=09/22/2008 20:14:19 UTC
Exception=System.NullReferenceException
ExceptionMessage=Object reference not set to an instance of an object.

[Stack Trace]
IP=0x00000010 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.GetOrCreateQueueForContentRecorder(Microsoft.MediaCenter.Guide.ContentRecorder contentRecorder)+0x0 :0,0
IP=0x00000091 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.AddRecordingSession(Microsoft.MediaCenter.Pvr.Recording recording)+0x7A :0,0
IP=0x0000012e Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.ProcessRecordingSessions()+0x6B :0,0

 

 

 

mrphil:

[Crash Information]
ReportVersion=2
MainBinary=C:\Windows\ehome\ehRec.exe
MainBinaryVersion=6.1.1000.18273 (longhorn_mc_dev(wmbla).080702-2208)
CrashTime=09/22/2008 20:14:19 UTC
Exception=System.NullReferenceException
ExceptionMessage=Object reference not set to an instance of an object.

[Stack Trace]
IP=0x00000010 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.GetOrCreateQueueForContentRecorder(Microsoft.MediaCenter.Guide.ContentRecorder contentRecorder)+0x0 :0,0
IP=0x00000091 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.AddRecordingSession(Microsoft.MediaCenter.Pvr.Recording recording)+0x7A :0,0
IP=0x0000012e Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.ProcessRecordingSessions()+0x6B :0,0

 

This one is a known bug and a fix via Windows Update is in the pipeline for this.

 

FYI: Providing the contents of crash files is very useful in determining what problem you are experiencing so thanks for this.

 

To see the crash files:

• Start button
• type "%programdata%\microsoft\ehome" into the "Start Search" text box and press enter
• (a file explorer should appear)
• click on the Views pull down (near the top of the file explorer window) and choose Details.
• scroll down and see if there are files of type Crash files
• double click on the file to open it
• if a dialog appears saying it doesnt know how to open it, choose the option to "select a program from a list of installed programs" and in the following dialog left click on notepad and then click on the Ok dialog.

If the media center application itself is crashing, then

• Start button
• type "media center" in the "start search" text box
• (the media center icon should appear in the list of programs)
• right click and choose "Run as Administrator"
• get the media center application to crash
• Start button
• type "%windir%\ehome" into the "Start Search" text box and press enter
• (a file explorer should appear)
• click on the Views pull down (near the top of the file explorer window) and choose Details.
• Scroll down and look for a ehshell Crash file.

Cheers

Mike

 

 

 

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi guys n´ gals

Been using tv-pack for a while now, and now I just installed dvbsbridge for dvbviewer. This works well, but I suspected this program to be my resent problem regarding shows not recording.

Then I found that many people have issues recording from standby.

My new problem is, selecting a show from guide or manually scheduling it, triggers a eventlog error.

Recording started at 10:45 and ended at 10:00 as planned, thus not being recorded at all.

The PC never wakes to record, been sitting and watching it waiting to start but it didn´t, and when I wake it my self, this is what it writes...

Weird isn´t it...

I'm having this problem, also.  Programs will randomly not record, despite showing up in my list of upcoming recordings.

Unfortunately, no crash files are being generated.  In fact, once the show is past, there is no evidence of the missed recording at all in my Media Center history logs.

This isn't an issue with resuming from S3 sleep, because last night Survivor didn't record, but Smallville recorded fine.  Both shows aired at the same time.  I had plenty of available tuners, so that shouldn't have been an issue.

I have 2 QAM tuners via HDHomerun, and 2 NTSC tuners (ATI 650 PCI and an ATI Digital CableTuner tuning NTSC).  I'm running Home Premium Vista.

I've had missed recordings at least once before and once after this past week's Media Center & TV Pack updates.

---

Velocity Micro Cinemagix S85
Intel DP35DP MB, Intel E6600 CPU, 2GB RAM
Video: ATI HD 2600 XT
Tuners: ATI DCT (Internal), ATI Theater PRO 650 PCI, Silicondust HDHomerun, AVerMedia M780
Blog: http://pharmnerd.com

mrphil:

I had this, it started as an inability to search for programmes in the guide, followed a week later by all scheduled recordings being completely ignored.

Solved it by stopping all MCE services, then deleting the guide database file mcepg1-0 and a folder with the same name. Its located in C:\ProgramData\Microsoft\eHome. You have to run guided setup again for TV signal after doing this. This appeared to be corruption of the database and was accompanied by a crash report log in the eHome directory each time a recording attempted to start.

I did this on my system, and so far it seems to have worked. I was pulling out my hair last night, and was going to do a complete reinstall.

I have Vista Ultimate with a dual analog tuner and an HD Homerun

TV Pack with lastest patch.

---

Foxer

Just wan't to confirm the same issue on DVB-C (fireDTV) on a norwegian system. TV-pack all patches.

Pretty frustrating not being able to record anything for the moment, and not very pleasant explaining it for my wife...

Here is my crash log, and I have a lot of these :(

[Crash Information]
ReportVersion=2
MainBinary=C:\Windows\ehome\ehRec.exe
MainBinaryVersion=6.1.1000.18273 (longhorn_mc_dev(wmbla).080702-2208)
CrashTime=10/28/2008 20:42:34 UTC
Exception=System.NullReferenceException
ExceptionMessage=Object reference not set to an instance of an object.

[Stack Trace]
IP=0x00000010 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.GetOrCreateQueueForContentRecorder(Microsoft.MediaCenter.Guide.ContentRecorder contentRecorder)+0x0 :0,0
IP=0x00000091 Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.AddRecordingSession(Microsoft.MediaCenter.Pvr.Recording recording)+0x7A :0,0
IP=0x0000012e Microsoft.MediaCenter.Pvr.Service.RecordingSessionManager.ProcessRecordingSessions()+0x6B :0,0

Please fix this ASAP.

Thanks!

Delete the mcepg1-0.db from c:\ProgramData\Microsoft\eHome seems solved the problem.

 

Yes it does, but along with it goes all your channel mappings, and series recordings, and any other customization you made to your guide.

---

Ben
How good can it be, if it isn't HD?
Engadget HD

bjdraw:

Yes it does, but along with it goes all your channel mappings, and series recordings, and any other customization you made to your guide.

Has anyone tried backing up the mcepg1-0.db file, and restoring it when encountering this problem. Its probably pretty difficult to figure out when the problem began so it may end up being a hit or miss process to keep restoring older backups until you get a working one. Also, will VMC rebuild the database to include the entries for the newer recordings (ones done after the date that the backup used for the recovery was made)? May be a question for Mike Hayton or one of the Microsoft experts.

Just ran into this same issue after enabling clear QAM.  Had to delete the .db file, and with it, all my season passes and guide data.  Very annoying.

Has solution or fix been offered from Redmond yet?

---

VMC w/ TV Pack on a Zalman HD160 case, Asus M2N-SLI Deluxe w/ 2GHz Athlon 64 x2, 4x 512MB DDR2 @ 800MHz, GeForce 7600GT fanless, HVR-1600 x2, PVR-250, 1TB WD Green Drive RAID1 (OS & MP3 archive) & 500GB SATA (video)

So from the ehshell.crash file sent in (text file, you can notepad)

It had the contents of

 

 

Unhandled Exception - 12/16/2008 19:08:49

Message: Unable to cast object of type 'Microsoft.MediaCenter.Playback.LiveBroadcastMediaItem' to type 'Microsoft.MediaCenter.Playback.IUriMediaItem'.

Exception:

System.InvalidCastException: Unable to cast object of type 'Microsoft.MediaCenter.Playback.LiveBroadcastMediaItem' to type 'Microsoft.MediaCenter.Playback.IUriMediaItem'.

   at Microsoft.MediaCenter.Playback.MediaSessionBindings.ProceedWithBinding()

   at Microsoft.MediaCenter.Playback.MediaSessionBindings.ProceedWorker(Object notUsed)

   at Microsoft.MediaCenter.UI.Application.DeferredInvokeItem.Dispatch()

   at Microsoft.MediaCenter.UI.Dispatcher.ConfigurableMainLoopBody(Feeder feeder, Boolean includeExtensibility)

   at Microsoft.MediaCenter.UI.Dispatcher.MainLoopBody(Feeder feeder)

   at Microsoft.MediaCenter.UI.Dispatcher.MainLoop(LoopCondition condition, LoopBody body)

   at Microsoft.MediaCenter.UI.Dispatcher.MainLoop(LoopCondition loopCondition)

   at Microsoft.MediaCenter.UI.Application.Run()

   at ServiceBus.UIFramework.PageBasedUCPService.Run()

   at ServiceBus.UIFramework.UserControlPoint.Launch(String args)

   at Microsoft.MediaCenter.Internal.LaunchMediaCenter.LaunchMediaCenterHelper()

 

This is a known bug fixed in Win7. At this stage there are not sufficient instances of it reported to warrant backporting the fix (and then doing the full test pass to ensure that in this version of the code that it hasnt broken something else).

from tasks->settings->tv->guide->edit channels->hide Preview

you can uncheck and 'hide' the channel that is creating the problem.

re-runing tv signal setup from under tasks->settings->tv should clear the channel out.

 

 

 

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Nothing is more frustrating to me than known bugs that won't be fixed.  And I'm sure others will share my sentiments.

Oh well.  I've given up on TV Pack, and am (im)patiently waiting for Windows 7..

mikehayton:

So from the ehshell.crash file sent in (text file, you can notepad)

It had the contents of  

...code that hurts Brad's brain...

This is a known bug fixed in Win7. At this stage there are not sufficient instances of it reported to warrant backporting the fix (and then doing the full test pass to ensure that in this version of the code that it hasnt broken something else).

from tasks->settings->tv->guide->edit channels->hide Preview

you can uncheck and 'hide' the channel that is creating the problem.

re-runing tv signal setup from under tasks->settings->tv should clear the channel out.

 

 

 

---

Velocity Micro Cinemagix S85
Intel DP35DP MB, Intel E6600 CPU, 2GB RAM
Video: ATI HD 2600 XT
Tuners: ATI DCT (Internal), ATI Theater PRO 650 PCI, Silicondust HDHomerun, AVerMedia M780
Blog: http://pharmnerd.com