MDAC error with 10 or 11

[-LD]

I've installed 2.8 just to be sure
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: The .Net Data OLE DB Provider(System.Data.OleDb) requires Microsoft Data Access Components(MDAC).  Please install Microsoft Data Access Components(MDAC) version 2.6 or later. ---> System.Runtime.InteropServices.COMException (0x80040154): Class not registered
  at System.Data.Common.UnsafeNativeMethods.CoCreateInstance(Guid rclsid, IntPtr pUnkOuter, Int32 dwClsContext, Guid riid)
  at System.Data.OleDb.OleDbConnection.CreateInstanceDataLinks()
  at System.Data.OleDb.OleDbConnection.CreateInstanceMDAC()
  --- End of inner exception stack trace ---
  at System.Data.OleDb.OleDbConnection.CreateInstanceMDAC()
  at System.Data.OleDb.OleDbConnection.GetObjectPool()
  at System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString constr)
  at System.Data.OleDb.OleDbConnection.Open()
  at ab.a()
  at ac.v(Object A_0, EventArgs A_1)
  at System.Windows.Forms.Form.OnLoad(EventArgs e)
  at System.Windows.Forms.Form.OnCreateControl()
  at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
  at System.Windows.Forms.Control.CreateControl()
  at System.Windows.Forms.Control.WmShowWindow(Message&amp; m)
  at System.Windows.Forms.Control.WndProc(Message&amp; m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m)
  at System.Windows.Forms.ContainerControl.WndProc(Message&amp; m)
  at System.Windows.Forms.Form.WmShowWindow(Message&amp; m)
  at System.Windows.Forms.Form.WndProc(Message&amp; m)
  at System.Windows.Forms.ControlNativeWindow.OnMessage(Message&amp; m)
  at System.Windows.Forms.ControlNativeWindow.WndProc(Message&amp; m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
Config
   Assembly Version: 1.0.1493.13891
   Win32 Version: 1.0.1493.13891
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/Config.exe
----------------------------------------
System.Windows.Forms
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0b77a5c561934e089/system.dll
----------------------------------------
GBPVRBackendCommon
   Assembly Version: 1.0.1493.10625
   Win32 Version: 1.0.1493.10625
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/GBPVRBackendCommon.DLL
----------------------------------------
System.Drawing
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0b77a5c561934e089/system.xml.dll
----------------------------------------
NativeUtilities
   Assembly Version: 1.0.1493.10624
   Win32 Version:
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/NativeUtilities.DLL
----------------------------------------
System.Data
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.[/QUOTE]

[sub]

Ok, cant say I've seen that one before. It looks like your .net installation is either damaged or something else that has been installed conflicts with the builtin .net 1.1 data access functionality.

I've havn't really got any suggestions other than try a bit of a search on google. sorry.

[-LD]

uninstalled .NET, reinstalled, reinstalled mdac 2.8...same error

[sub]

I've not installed mdac. No else has had to either to get GB-PVR going. The default components in the .net framework runtime should contain all the data access components required. Its failing to load the MS Access driver or similar.

[-LD]

well, ####...i was looking forward to playing with the mediamvp server

[sub]

This may apply to situation:

http://groups.google.com/groups?....b%2B1.1

[-LD]

no luck...other apps that use .net are working

[sub]

Sorry, I'm just not sure. Its definitely something on you machine thats different from everyone elses.

[-LD]

same thing with 12a...i'd love to try this out, but can't get pastt this problem...any ideas anyone? i had gbpvr installed at one point in time on this system

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
  at ah.q(Object A_0, EventArgs A_1)
  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&amp; m, MouseButtons button, Int32 clicks)
  at System.Windows.Forms.Control.WndProc(Message&amp; m)
  at System.Windows.Forms.ButtonBase.WndProc(Message&amp; m)
  at System.Windows.Forms.Button.WndProc(Message&amp; m)
  at System.Windows.Forms.ControlNativeWindow.OnMessage(Message&amp; m)
  at System.Windows.Forms.ControlNativeWindow.WndProc(Message&amp; m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
Config
   Assembly Version: 1.0.1495.14689
   Win32 Version: 1.0.1495.14689
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/Config.exe
----------------------------------------
System.Windows.Forms
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0b77a5c561934e089/system.dll
----------------------------------------
GBPVRBackendCommon
   Assembly Version: 1.0.1495.9880
   Win32 Version: 1.0.1495.9880
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/GBPVRBackendCommon.DLL
----------------------------------------
System.Drawing
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0b77a5c561934e089/system.xml.dll
----------------------------------------
NativeUtilities
   Assembly Version: 1.0.1495.9878
   Win32 Version:
   CodeBase: file:///C:/Program%20Files/devnz/GBPVR/NativeUtilities.DLL
----------------------------------------
System.Data
   Assembly Version: 1.0.5000.0
   Win32 Version: 1.1.4322.573
   CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.[/QUOTE]

[-LD]

still getting this with 13

i found this info on the web regardign the System.Runtime.InteropServices.COMException

The exception that is thrown when an unrecognized HRESULT is returned from a COM method call.

i'm not a programmer so i'm not sure what that means