Verizon Wi-Fi Connect App

SKRosen1

Distinguished
Oct 7, 2009
3
0
18,510
This app no longer works since receiving some Windows 10 updates a few months ago. I am getting an unhandled exception stating object reference not set to an instance of an object. It is apparently not getting my Verizon login credentials in order to connect to any network. The details are as follows and I am hoping that you can help me fix this.

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 Quintech.ROVA4.FormWirelessScanList.FormWirelessScanList_Load(Object sender, EventArgs e)
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& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WiFiConnect
Assembly Version: 4.200.213.0
Win32 Version: 4.200.213.0
CodeBase: file:///C:/Program%20Files%20(x86)/Verizon/Enterprise%20Connect/WiFiConnect.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
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.8670 (QFE.050727-8600)
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.8681 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
QTSharedNET
Assembly Version: 4.200.213.0
Win32 Version: 4.200.213.0
CodeBase: file:///C:/Program%20Files%20(x86)/Verizon/Enterprise%20Connect/QTSharedNET.DLL
----------------------------------------
QTConnectEngine
Assembly Version: 4.200.213.0
Win32 Version: 4.200.213.0
CodeBase: file:///C:/Program%20Files%20(x86)/Verizon/Enterprise%20Connect/QTConnectEngine.DLL
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8677 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8679 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SQLite
Assembly Version: 1.0.66.0
Win32 Version: 1.0.66.0
CodeBase: file:///C:/Program%20Files%20(x86)/Verizon/Enterprise%20Connect/System.Data.SQLite.DLL
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.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" ></system>
</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.


 

SKRosen1

Distinguished
Oct 7, 2009
3
0
18,510


The problem is that Verizon will not send my request to the developer (and they are unable to fix it) and the developer cannot breach his agreement with Verizon (I did try calling directly). Regardless, I have seen some very technical type fixes on the internet for these kinds of error messages by making changes to the registry. It seems that this is actually a Windows issue, possibly with .NETFramework. It seems that it happens with other people's random apps too. I was hoping someone could decipher the exact issue and instruct me on those kinds of changes to make the object "point" to the right instance of an object. The fact that it used to work fine and only after Windows regular updates did it stop working, would surely lead me to believe that it is Windows related.
 

SKRosen1

Distinguished
Oct 7, 2009
3
0
18,510


I will keep trying to get Verizon to provide assistance. Thanks for trying to help.