Results 1 to 3 of 3

Thread: It's me again, the guy with the unsolvable error.

  1. #1

    Thread Starter
    New Member
    Join Date
    Feb 2016
    Posts
    11

    Question It's me again, the guy with the unsolvable error.

    Welp, basically
    Code:
    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.
    
    ************** Exception Text **************
    System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
       at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateCall(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack, Boolean IgnoreReturn)
       at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)
       at Swaggy.Form1.reco_SpeechRecognized(Object sender, RecognitionEventArgs e)
       at System.Speech.Recognition.SpeechRecognitionEngine.SpeechRecognizedProxy(Object sender, SpeechRecognizedEventArgs e)
    
    
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18063 built by: FX45RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    Swaggy
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Users/s197662.OCSB/AppData/Local/Apps/2.0/2W7EKRC8.62D/4MT0RV8N.C81/swag..tion_0000000000000000_0001.0000_3bab96e6493f35fa/Swaggy.exe
    ----------------------------------------
    Microsoft.VisualBasic
        Assembly Version: 10.0.0.0
        Win32 Version: 11.0.50709.17929 built by: FX45RTMREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
        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.0.30319.34270 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Runtime.Remoting
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34245 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    System.Speech
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll
    ----------------------------------------
    Accessibility
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.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.
    I try to run a voice control program and I get this message after running the
    Code:
    programVC.application
    and it runs fine. BUT when I try to say a command that's part of the grammar builder it gives me that BS error message. I can't even begin ti decipher the error and I am on the verge of pulling my teeth out with a wrench.

  2. #2
    Lively Member
    Join Date
    Dec 2011
    Posts
    116

    Re: It's me again, the guy with the unsolvable error.

    There is literally nothing anyone is going to be able to help you out with. Answer this: "I have this thing on my desk that is ugly and does not move, what is it???"

    That is essentially what you are doing, asking the board to give you a clue with no context of how to approach a logical answer. Please try again.

  3. #3
    You don't want to know.
    Join Date
    Aug 2010
    Posts
    4,578

    Re: It's me again, the guy with the unsolvable error.

    To augment.

    It's a COMException, so that means it's a problem in some code that's interoperating with a COM API. If you wrote that code, and it were a widely used API then someone might be able to help you work through it.

    It's not definitively code you wrote yourself, but let's give the benefit of the doubt here. The call stack tells us:
    • Some MS type SpeechRegognitionEngine has an event handler SpeechRecognizedProxy() that is called.
    • That calls your reco_SpeechRecognized() event handler.
    • You make a late-bound call to... something. That's the bad part about late-bound calls, I can't tell you from the call stack what you called.
    • That late-bound call does something that returns HRESULT 0x8004005, which is a fairly generic value that doesn't seem to give us much insight.

    So. Step 1. You're going to have to go over your reco_SpeechRecognized() handler and figure out where the call that's failing is. Maybe you're configuring something wrong, or using something wrong. But this is where it's failing, so even if this is just a symptom of the real problem, this is where the exception's being thrown.

    Problem: the System.Speech namespace is relatively new, and it's not part of most VB developer's repertoire. That means there aren't a lot of people familiar with the ins and outs of its configurations. And when I search the internet about it, it seems the API on which it's based is very temperamental, and problems arise based on Windows version, platform, .NET version, and practically anything else. My guess is if you aren't fairly well-versed in the COM API on which this .NET API is built, it's hard to use. If true, it wouldn't be the first time MS has released a very bad layer on top of a COM API.

    I think you should widen your net and ask about this on a generally-oriented site like stackoverflow.com, and provide a good bit more detail and code. It's more likely someone in a more generally-oriented environment like that will have wrestled with the API and encountered something similar.
    Last edited by Sitten Spynne; Jun 3rd, 2016 at 02:24 PM.
    This answer is wrong. You should be using TableAdapter and Dictionaries instead.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width