mohamadDev / aforge

Automatically exported from code.google.com/p/aforge
Other
0 stars 0 forks source link

Crash due to missing olepro32.dll #118

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The call
((VideoCaptureDevice)videoSource).DisplayPropertyPage(this.Handle);" leads
to the following uncaught Exception (System is Win7-HP-x64):

System.DllNotFoundException wurde nicht behandelt.
  Message="Die DLL \"olepro32.dll\": Das angegebene Modul wurde nicht
gefunden. (Ausnahme von HRESULT: 0x8007007E) kann nicht geladen werden."
  Source="AForge.Video.DirectShow"
  TypeName=""
  StackTrace:
       bei
AForge.Video.DirectShow.Internals.Win32.OleCreatePropertyFrame(IntPtr
hwndOwner, Int32 x, Int32 y, String caption, Int32 cObjects, Object& ppUnk,
Int32 cPages, IntPtr lpPageClsID, Int32 lcid, Int32 dwReserved, IntPtr
lpvReserved)
       bei
AForge.Video.DirectShow.VideoCaptureDevice.DisplayPropertyPage(IntPtr
parentWindow)
       bei
MotionDetectorSample.MainForm.localVideoCaptureSettingsToolStripMenuItem_Click(O
bject
sender, EventArgs e) in C:\Users\stephan\Desktop\AForge.NET
Framework-2.1.0\Samples\Vision\MotionDetector\MainForm.cs:Zeile 500.
       bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key,
EventArgs e)
       bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
       bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
       bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
       bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
       bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
       bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
       bei System.Windows.Forms.Control.WndProc(Message& m)
       bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
       bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
       bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       bei System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr
hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       bei
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNat
iveMethods.IMsoComponentManager.FPushMessageLoop(Int32
dwComponentID, Int32 reason, Int32 pvLoopData)
       bei
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
       bei
System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
       bei MotionDetectorSample.Program.Main() in
C:\Users\stephan\Desktop\AForge.NET
Framework-2.1.0\Samples\Vision\MotionDetector\Program.cs:Zeile 17.
       bei System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       bei Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       bei System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
       bei System.Threading.ThreadHelper.ThreadStart()
  InnerException: 

What steps will reproduce the problem?
1. Start Motion-Detection example
2. Select File->Local VideoCapture Device
3. Click on Tools->Local Video Capture Settings

What is the expected output? What do you see instead?

What version of the product are you using?
Happens on Version 2.1.0 of AForege .zip download

Please provide any additional information below.
olepro32.dll seems to be some part of VisualBasic Runtime. 

Original issue reported on code.google.com by sz.temp....@googlemail.com on 3 Jan 2010 at 4:40

GoogleCodeExporter commented 9 years ago
The issue was fixed by fixing issue 113.
http://code.google.com/p/aforge/issues/detail?id=113

Original comment by andrew.k...@gmail.com on 4 Jan 2010 at 10:41

GoogleCodeExporter commented 9 years ago
Ok, didn't see that one. Thanks.

Original comment by sz.temp....@googlemail.com on 4 Jan 2010 at 6:47

GoogleCodeExporter commented 9 years ago

Original comment by andrew.k...@gmail.com on 24 Jan 2010 at 2:31