Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago Update to version 2.1.6 generated the same error as expected since no update was
performed with the programs interface detection engine.Original comment by peterwor...@gmail.com on 14 May 2009 at 11:45
GoogleCodeExporter
commented
9 years ago The problem seems to be resolved at the moment. The problem was either one of
two
things. One, renaming as mentioned before or, more likely, installing the
software
for the first time while static network settings for my wireless card were set.
It
is unclear as usual to what the actual problem was caused by. This issue can be
considered closed, but perhaps there is enough information for someone here to
try to
recreate the problem and benefit the project.Original comment by peterwor...@gmail.com on 15 May 2009 at 12:55
GoogleCodeExporter
commented
9 years ago I have tried 2.1.6 and get the same Exception as peterworden - I don't think
this
issue can be considered closed.
Exception details below:
-------------------------------------------------------------------------
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 Net_Profiles.Globals.PopulateNetworkCardArray()
at Net_Profiles.MainForm.TimerLoadTick(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.3082 (QFE.050727-3000)
CodeBase: file:///c:/WINXP/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Net Profiles
Assembly Version: 1.0.3421.15076
Win32 Version: 1.0.3421.15076
CodeBase: file:///C:/Program%20Files/Net%20Profiles/Net%20Profiles.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a
3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e08
9/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Syst
em.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934
e089/System.Runtime.Remoting.dll
----------------------------------------
MessageBoxHook
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///C:/Program%20Files/Net%20Profiles/MessageBoxHook.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.3053
Win32 Version: 8.00.50727.3053
CodeBase:
file:///C:/WINXP/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x
-ww_b80fa8ca/msvcm80.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.X
ml.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase:
file:///C:/WINXP/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/S
ystem.Management.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.
Original comment by andrew.o...@googlemail.com on 15 May 2009 at 10:00
GoogleCodeExporter
commented
9 years ago Try this:
Get the command prompt open. If you are using Vista either upgrade to XP or
run the
command prompt with elevated rights.
At the command prompt run the following commands, hit enter for each line:
netsh winsock reset
netsh int ip reset all
Next, uninstall the drivers for your network adapters, all of them. If you are
running Vista then choose "no" when asked to delete the files. Just uninstall,
don't
delete.
Reboot and retry running NetProfiles
Post back here to see if that helped. I shotgun troubleshooted my computer and
don't
know what exactly fixed my problem.Original comment by peterwor...@gmail.com on 16 May 2009 at 11:37
GoogleCodeExporter
commented
9 years ago Thx for peterworden,your method works to me.Net profile 2.1.6 is pretty good!!Original comment by ligac...@gmail.com on 19 May 2009 at 2:43
GoogleCodeExporter
commented
9 years ago I have the same problem with the 2.1.7 under XP (Same message on searching
network
cards). It seems that is because of lot of network cards (some virtuals because
of
VMWare and Bluetooth)...
No issue found for that.
I can't remove drivers without uninstall VMWare and it's a software I use every
days,
I don't want to lost my big configuration!
Waiting for updates...
Original comment by zetesage...@gmail.com on 26 May 2009 at 6:34
GoogleCodeExporter
commented
9 years ago Seems like in some configurations, the WMI query used to populate the adapter
list
returns invalid (null?) objects. I tried to patch the code in
Globals.PopulateNetworkCardArray() to check for that.
If you still get the above error, will you try replacing your net profiles.exe
with
the one I attached? Original comment by potofcoffee@gmail.com on 26 May 2009 at 9:08
Attachments:
GoogleCodeExporter
commented
9 years ago Issue 6 has been merged into this issue.Original comment by potofcoffee@gmail.com on 27 May 2009 at 7:54
GoogleCodeExporter
commented
9 years ago i tryed the .exe , same error for me (vista 32 french)Original comment by sebastie...@gmail.com on 29 May 2009 at 11:59
GoogleCodeExporter
commented
9 years ago So, this being open source, is any of you guys ready to debug this issue? I'm
not
able to reproduce the problem here (I still think it's dependent on specific
configurations), so somebody else will have to try.
Original comment by potofcoffee@gmail.com on 29 May 2009 at 12:04
GoogleCodeExporter
commented
9 years ago On a different computer I was able to recreate the error only once. It was a
Dell
D630 with Virtualbox 2.2.2. Prior to installing NetProfiles I already had a
static
IP and DNS assignment. Starting up NetProfiles with the static IP existing
resulted
in the same error. Releasing the Static IP assignment back to DHCP and DNS to
DHCP
cleared the error condition. No other actions were necessary.
I suggest trying to recreate the error by assigning the computer a static IP and
static DNS, via "Network Connections", Start->Run->"ncpa.cpl"->Local Area
Connection->Right Click->Properties->Internet Protocol (TCP/IP)->Properties.
Then
try to run NetProfiles and verify if this condition generates an error.
My logic for this approach is because both computers that generated the error
shared
one similarity. They both had static IP and DNS assignments at the time of the
error.Original comment by peterwor...@gmail.com on 4 Jun 2009 at 3:33
GoogleCodeExporter
commented
9 years ago Dear potofcoffee,
I'm a developper and I understand what causes this problem.
In my notebook I installed Hamachi, that creates a virtual network interface;
if I
enable it, when "Net Profiles" starts I recive the error. If I disable the
Hamachi
virtual network card "Net Profiles" runs perfectly.
So I think you should catch this condition inside the function
"PopulateNetworkCardArray()" , when you do loop of search.
Andrea Finaurini
ICT Consultant
Original comment by finaur...@jumpy.it on 9 Jun 2009 at 8:04
GoogleCodeExporter
commented
9 years ago Dear Andrea,
Thank you for your investigation. Now, I'm not really anybody here. I just
offered to
fix one of the bugs that annoyed me the most. Right now, I'm not even using Net
Profiles any more, since Win7's network handling does enough for me.
Do you think you might be able to provide a patch that fixes that condition?
I'd be
happy to push it into svn for you. Alternatively, I'm sure Daniel Milner would
be
happy to accept you as a project member, so you can push your own changes.
God bless you,
potofcoffeeOriginal comment by potofcoffee@gmail.com on 11 Jun 2009 at 7:38
GoogleCodeExporter
commented
9 years ago Hi there...
I'm having the same error.
I have a wireless interface, Ethernet interface, 2 Vmware interface, a 1394
interface
and the bluetooth interface.
I'm not a developer, but it will be a pleasure helping with tests or something
you
need to fix that.
Thanks, and I'll be waiting.
JuanOriginal comment by elk...@gmail.com on 13 Jun 2009 at 1:57
GoogleCodeExporter
commented
9 years ago Hi,
I have the same error but I noticed it happens when I have the Miniport WAN
(PPPOE)
connection enabled (to use my internet ADSL connection). If I disconnect it,
the
error doesn't happen.
MarcoOriginal comment by abelmarkus@gmail.com on 16 Jun 2009 at 12:20
GoogleCodeExporter
commented
9 years ago I might have failed to mention that both computers that had the error I
experienced
were running Virtual box version 2.2 or 2.4. The network virtualization could
have
been involved in the error, but I'm not sure. I see above in the reported
issues
that a common element, although not absolute, is virtualization of the network
interface or some virtual machine software was present.Original comment by peterwor...@gmail.com on 17 Jun 2009 at 3:17
GoogleCodeExporter
commented
9 years ago I have the same error occurring, I also have Virtual Box 2.2 and the Microsoft
Loopback adapter. If I disable both adapters I can start Net Profiles without
the
exception.Original comment by jtbutc...@gmail.com on 27 Jun 2009 at 11:44
GoogleCodeExporter
commented
9 years ago I have the same error ... thanks good netprofiles goes open ...
So I have fixed the bug ... I don't know if it is right way to solve the
problem, but
for me it works fine. In attached file you can see a change I made to file
Globals.vbOriginal comment by ivan.hre...@gmail.com on 30 Jun 2009 at 1:41
Attachments:
GoogleCodeExporter
commented
9 years ago 
Hi, i have the same issue with a Dell Laptop. setting to DHCP does not help.
ivan.hrehor, could you please upload your compiled version with the fix
included?Original comment by alois.ba...@gmail.com on 7 Jul 2009 at 9:04
GoogleCodeExporter
commented
9 years ago ivan.rhevor, thank you for your patch. I just committed it to svn. I'm not able
to
release a new version (dmilner needs to do that), but you can grab the compiled
exe
from here:
http://netprofiles.googlecode.com/svn/trunk/bin/Debug/Net%20Profiles.exe
Original comment by potofcoffee@gmail.com on 8 Jul 2009 at 9:40
GoogleCodeExporter
commented
9 years ago Has this been identified then as the root cause for all cases with ivan.rhevor's
implementation of injected code as the fix? I'm just wary that the first
solution is
not always the best solution is all I'm saying.
On a side note, If anyone tries my initial fix, comment #4 on May 16, 2009 to
this
issue, then you will most likely be required to reinstall your virtual machine
solution to add the network interfaces required or added by the virtual machine
software. Just a word of advice prior to making blind changes by a guy that
looks
for trouble and tries to take it head on without proper tools or training:)Original comment by peterwor...@gmail.com on 8 Jul 2009 at 11:11
GoogleCodeExporter
commented
9 years ago @peterworden: Well, at least I'm quite sure that his patch is dealing with the
right
part of the code :).
Generally speaking, the condition that he patched shouldn't have been necessary
in
the first place -- but it keeps coming back with some specific configurations.
ivan.rhevor augmented the existing check to include another case, which, at
least in
his setup fixes it.
I can't verify anything -- I can't even reproduce the error. Since the change
doesn't
break anything, I see no reason why not to include the patch.
Original comment by potofcoffee@gmail.com on 9 Jul 2009 at 4:57
GoogleCodeExporter
commented
9 years ago In my case the crash was caused by the virtual interfaces created by Vmware.
with the patch created by potofcoffee in #20 the problem is gone.
thanks for your help.Original comment by nesto...@gmail.com on 12 Jul 2009 at 9:25
GoogleCodeExporter
commented
9 years ago My crashed were caused after installation of Cisco VPN client. I had no
problems with
virtual interfaces create by VmWare.
I was also helped with patch created by potofcoffee in #20.
Thx a lot!Original comment by stijn.fo...@gmail.com on 2 Sep 2009 at 7:51
GoogleCodeExporter
commented
9 years ago I also would like to confirm that the code edit fixes any crashes from
VirtualBox
version 3.0.4 and most likely all other versions. There is one side effect,
but it
is only cosmetic. I'm not at work with the test machine, but I will post again
when
I have the information available to explain.Original comment by peterwor...@gmail.com on 3 Sep 2009 at 12:11
GoogleCodeExporter
commented
9 years ago I have the same problem after installation of Check Point VPN client. I have
VMware
installed and I haven't had any problem before.Original comment by maurizio...@gmail.com on 30 Sep 2009 at 6:18
GoogleCodeExporter
commented
9 years ago Is there someone still working on this program? It works wonders (after the
patch),
and it really should get an official release.
Thank you!Original comment by maxzag...@gmail.com on 28 Oct 2009 at 10:15
GoogleCodeExporter
commented
9 years ago I can confirm that ivan.rhevor's patch fixes the issue on my machine. I believe
that
the Juniper Networks WAN miniport was causing the issue to occur.Original comment by imxco...@hotmail.com on 26 Nov 2009 at 4:10
GoogleCodeExporter
commented
9 years ago It worked for me as well.
I have both Checkpoint and Virtualbox, and was having the problem, but it works
now.
Mickets
Original comment by malexl...@gmail.com on 28 Dec 2009 at 12:06
GoogleCodeExporter
commented
9 years ago Win XP Pro incl. SP3, Dot Net Framework 3
The SVN "Net Profiler.exe" provided in comment #20
(http://code.google.com/p/netprofiles/issues/detail?id=1#c20) worked for me...
Thank
you very much.
Sad that this was not released since then :-(Original comment by ray.schr...@gmx.ch on 20 May 2010 at 5:12
GoogleCodeExporter
commented
9 years ago Thank You very much for your help, i use netprofile for few times and also
VirtualBox...
After the ultimate version of VirtualBox...my netprofile had the same
issue...thanks at everybody for all!!Original comment by Jonathan...@gmail.com on 12 Aug 2010 at 9:53
GoogleCodeExporter
commented
9 years ago This fix has been implemented in v2.1.8.Original comment by dmil...@gmail.com on 17 May 2011 at 8:28
GoogleCodeExporter
commented
9 years ago help when open this error
Original comment by sou.sokc...@gmail.com on 7 Feb 2015 at 5:10
Attachments:
GoogleCodeExporter
commented
9 years ago 
This project is no longer maintained.
Please see: https://code.google.com/p/netprofilesmod/Original comment by dmil...@gmail.com on 7 Feb 2015 at 5:45
Original issue reported on code.google.com by
peterwor...@gmail.comon 14 May 2009 at 11:43