Is it GBPVR that has a lock on MPEGImport Process?

[jksmurf]

Sub,

I know this is partially plugin/utility related, but I'd really like to get the MPEGImport utility working again the way it used to i.e. both generate and import Recording-Dump.xml while GBPVR is running.

My glitch is explained here and the error repeated below. Basically MPEGImport used to be able to both generate and import the file of the shows in a particular dir, now it can generate the Recording-Dump.xml, but when the import task (in MPEGImport) is selected, the reproducible error below is produced:

Code:

=====================================================================
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.IOException: The process cannot access the file 'C:\Program Files\devnz\gbpvr\recording-dump.xml' because it is being used by another
process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
   at MpegImport.MainForm.RunImport()
   at MpegImport.MainForm.btnImport_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll]file:///C:/WINDOWS/Microsoft.NET/Fra...7/mscorlib.dll[/url]
----------------------------------------
MpegImport
    Assembly Version: 0.7.0.0
    Win32 Version: 0.7.0.0
    CodeBase: [url=file:///C:/Program%20Files/Antony%20Scott/MpegImport/MpegImport.exe]file:///C:/Program%20Files/Antony%20...MpegImport.exe[/url]
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...dows.Forms.dll[/url]
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...089/System.dll[/url]
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...em.Drawing.dll[/url]
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...figuration.dll[/url]
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...System.Xml.dll[/url]
----------------------------------------
FileSystems
    Assembly Version: 0.7.0.0
    Win32 Version: 0.7.0.0
    CodeBase: [url=file:///C:/Program%20Files/Antony%20Scott/MpegImport/FileSystems.DLL]file:///C:/Program%20Files/Antony%20...ileSystems.DLL[/url]
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.42 (RTM.050727-4200)
    CodeBase: [url=file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll]file:///C:/WINDOWS/assembly/GAC_MSIL...isualBasic.dll[/url]
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
----------------------------------------------------------------------------------------------------

The author explained why he thought there was a glitch which summarised, says "Tells me that some other process, possibly GBPVR itself, has a lock on the file".

If you get time (LOL) and this is a simple identification if it is indeed a GBPVR process , it'd be nice to have that utility work again. I currently use the utility to generate the xml and GBPVR's config "Import" button to import it, but this means starting config each time (no biggie, but it is a separate process).

Cheers,

k.

[sub]

I just checked the code, and cant see how it could be GB-PVR - but never say never and that...

You could try using the "handle" utility from http://www.microsoft.com/technet/sysinte...ities.mspx to check.

[jksmurf]

I just checked the code, and cant see how it could be GB-PVR - but never say never and that...

You could try using the "handle" utility from http://www.microsoft.com/technet/sysinte...ities.mspx to check.

Cheers sub, I'll give it a whirl tonight and get back to you. I see that util is in process explorer, which runs in my tray, so I'll try and access it from there, if I can work it out.

k.

[jksmurf]

sub,

I read up about it, but I'm not sure exactly how handles works, I used the thing from within ProcessExplorer and it gave me this.

The second 1/2 of this output has details for MPEGImport. Is this what you need? If not, can you give me a tip how to use handles from within ProcessExplorer ?

Ta

k.

[sub]

Part of that output lists the "File" handles this process has opened. You could do the same thing for the GB-PVR processes to see if GB-PVR is using this Recording-Dump.xml file. I dont think it is though.

[jksmurf]

Sub

1. OK, I put them side by side in the attached xls file and I can't see the file recording-dump.xml in either set of file handles. :confused:
   
2. I then tried WinDBG (and clearly I have no idea what I'm doing, but that's attached anyway)....
   
3. I then had a brainwave (yes, it hurt). Would it work with a different file name? The answer is YES. If I used dump.xml it works. If I use recording-dump.xml it fails everytime with the message "The process cannot access the file 'C:\Program Files\devnz\gbpvr\recording-dump.xml' because it is being used by another process"
   
4. Even if I delete recording-dump.xml and MPEGImport re-creates it, it fails with that "cannot access the file" message.
   
5. I wonder if it just doesn't like hyphens, so I tried dump-dump.xml. That works. So it is only recording-dump.xml that is being used by another process.

So, while I haven't located the cause (sorry) the solution to get MPEGImport to work is to use an output file name which is NOT the same as GBPVR's recording-dump.xml (which crashes every time) and MPEGImport will work all by itself (both Go and Import). If for some perverse reason you want to use recording-dump.xml, Go will work but Import (in MPEGImport) will not, although Import in the config will happily call up recording-dump.xml made by MPEGImport. Whew.

k.

[sub]

OK, I put them side by side in the attached xls file and I can't see the file recording-dump.xml in either set of file handles.

Thats pretty much what I'd expect. I'm sure GB-PVR is not using the file. When it needs the file, it opens the file, writes to it, then closes it immediately.

Anyway, glad you found a work around for your problem.