News:

HOT TIP! Enable the History Window in the main UI when trying to problem solve. It provides a handy log of what is happening. Roll over lines in the History to get more details.

Main Menu

Error message on launching VC with W7

Started by Bleazle, February 01, 2012, 03:10:36 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Bleazle

As per the subject title I get the following message when VC (0.937) launches with W7 on startup - I'm getting this message on both my main htpc and the client. I've searched the forum for some keywords from the error report but haven't found anything so here it is...

Cheers

Bleazle

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 VoxCommando.MainWindow.doEvent(String strEventName, List`1 payloads)
   at VoxCommando.MainWindow.timerCheckFocus_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.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.5448 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VoxCommando
    Assembly Version: 0.9.3.7
    Win32 Version: 0.9.3.7
    CodeBase: file:///C:/VoxCommando0937/VoxCommando.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
PluginInterface
    Assembly Version: 1.0.4348.29252
    Win32 Version: 1.0.4348.29252
    CodeBase: file:///C:/VoxCommando0937/PluginInterface.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Speech
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.6920.1109 (lh_tools_devdiv_wpf.071009-1109)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Speech/3.0.0.0__31bf3856ad364e35/System.Speech.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.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.



dumheter

I'm also getting the same error message. You are not alone!

Kalle

#2
Quote from: dumheter on February 16, 2012, 09:01:07 AM
I'm also getting the same error message. You are not alone!
Hi dumheter, welcome in VC forum.
Can you tell us what version of VC you use and wich W7 (32/64 bit) too?

Kalle

If you use VC0.937 please test VC0.939 from here: http://voxcommando.com/forum/index.php?topic=720
***********  get excited and make things  **********

jitterjames


alexdepalma


Kalle

Quote from: alexdepalma on February 16, 2012, 01:38:36 PM
Same here on version 0.9.3.9

Alex
I've tested the Option in VC0.939 "Start With Windows" on Win7-Ultimate 32bit and it works.
You can copy the VC-link from Desktop in Autostart folder too, without a checkmark in VC Option "Start With Windows" and test this, if came the same error, there is a other problem.

Kalle
***********  get excited and make things  **********

jitterjames

OK.  I think this is something different from what I thought it was.  I was able to recreate it just now so that will make it easier to fix.  For now you should be safe clicking "continue"

mclough6

Hello James,
What did you do to fix this problem?  I have another program I purchased that has this same error message "Object reference not set to an instance of an object"  I have not been able to get it to work for several months now.  I am hoping that error message points to a particular common problem that I can fix.  If it is too much trouble or the answer is too broad, don't bother, I don't want to waste your time.
Regards,

jitterjames

this error could be caused by a million different things.  It happens when you try to access something that does not exist yet.

In the case of VC certain objects were loading too slowly when the system was starting up and doing a bunch of other things at the same time, and the focus event was firing and trying to reference something that had not been created yet.

There is nothing you can do to fix this yourself.  You need to file a bug report with the maker of the software in question.  Unfortunately, not all software outfits are quite as responsive as I am.  :biglaugh

mclough6

You are right about that James.  Your product support is the best!