Elle__

Commendable
Dec 16, 2016
24
0
1,560
Does anyone have any idea why Norton is being a *bleep* making it difficult to use WinTV? It was working fine until 12 hours ago or so. I didn't do anything different. I even restarted my computer and still problems!! I can't schedule anything in scheduler.. I think it has quarantined NativeMMS.dll but when I tried excluding it from scans it didn't work

The following is the screen I get when I try
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Could not load file or assembly 'NativeMMS.dll' or one of its dependencies. Access denied.

Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileLoadException: Could not load file or assembly 'NativeMMS.dll' or one of its dependencies. Access is denied.
File name: 'NativeMMS.dll'
at TVServices.MultiMedia.ServiceFactory.GetBoardStatus(Board board)
at TVServices.MultiMedia.ServiceFactory.RecordingPossible(Channel selectedChannel, DateTime startTime, DateTime endTime, List`1 overlaps)
at WinTV7.Scheduler.ManualRecordingControl.TunerAvailable(List`1 overlaps)
at WinTV7.Scheduler.ManualRecordingControl.buttonRecord_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: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
WinTV
Assembly Version: 1.2.34284.0
Win32 Version: 1.2.34284.0
CodeBase: file:///C:/Program%20Files/WinTV/WinTV8/WinTV8.exe
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
DataModel
Assembly Version: 1.2.34284.0
Win32 Version: 1.2.34284.0
CodeBase: file:///C:/Program%20Files/WinTV/WinTV8/DataModel.DLL
----------------------------------------
MultiMediaServices
Assembly Version: 1.2.34284.0
Win32 Version: 1.2.34284.0
CodeBase: file:///C:/Program%20Files/WinTV/WinTV8/MultiMediaServices.DLL
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Data.OracleClient
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data.OracleClient/v4.0_4.0.0.0__b77a5c561934e089/System.Data.OracleClient.dll
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------

************** 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.


 
Solution
With Norton not installed a WinTV reinstall did not resolve the error message - correct?

Go into Event Viewer and look for red icons that occur just before or at the time of the "Could not load file or assembly 'NativeMMS.dll' or one of its dependencies. Access denied." error message.

May even be a yellow icon but start with red. Right click the log entry for more details.
You did not necessarily have to have done anything: could have been some update installed or some file got corrupted.

Two things:

1) Close Norton and prevent it from starting at reboot. See if WinTV again works. If so then Norton may be the culprit.

2) "Could not load file or assembly 'NativeMMS.dll' or one of its dependencies. Access denied."

Note "one of its dependencies". You may need to exclude that dependency as well.

Could become very tedious and messy. And probably not really necessary as things originally did work without needed to provide exceptions to Norton.

Overall, I think I would start by reinstalling all relevant WIN TV files - hopefully just file corruption and the reinstall will fix the scheduler.

 

Elle__

Commendable
Dec 16, 2016
24
0
1,560
I don't remember if what I pasted was from after reinstalling but what I did was uninstall using the uninstall feature many programs provide, then reinstalled. Still have the problem.
 
With Norton not installed a WinTV reinstall did not resolve the error message - correct?

Go into Event Viewer and look for red icons that occur just before or at the time of the "Could not load file or assembly 'NativeMMS.dll' or one of its dependencies. Access denied." error message.

May even be a yellow icon but start with red. Right click the log entry for more details.
 
Solution