Unhandled Exception 007DA767

Started by Hendry

Hendry

Unhandled Exception 007DA767   07 April 2016, 15:46

Dear Andrew,

The latest final build of netscan 6.1.5 showing error when scanning network:
Unhandled Exception : Access violation at address 007DA767 in module "netscan.exe". Read addrees 00000004

32-bit version, Win XP SP3, same on Win 7 SP1
SoftPerfect Support forum - Andrew avatar image

Re: Unhandled Exception 007DA767   07 April 2016, 16:00

Sorry and thank you for reporting: it was an oversight. Please download the fixed build here.
Corey

Re: Unhandled Exception 007DA767   09 April 2016, 01:47

Similar problem. Since updating to the current release I get this:

Unhandled exception: Access violation at address
0000000000009B69D9 in module 'netscan.exe'. Read of address
000000000000000008


Removing the netscan.xml file make the problem go away, but it appears that some combination of settings causes the issue to come back. I tried older versions and the same issue happens. It sort of seems like the XML parsing/utilization has a flaw that certain combinations trigger. Once the XML file is corrupted, even the older versions choke when trying to use it unless the XML file is removed.

The error only shows up after the first invocation and then after attempting to scan. If it will help I can send an example XML configuration file...

Thank you for such a handy product.
Corey

Re: Unhandled Exception 007DA767   09 April 2016, 01:49

BTW, I already downloaded the fixed version mentioned above and it shows v6.1.5 and ran into the same results.

Thank you.
SoftPerfect Support forum - Andrew avatar image

Re: Unhandled Exception 007DA767   09 April 2016, 07:24

Please send me your XML config and I will have a look.
Corey

Re: Unhandled Exception 007DA767   10 April 2016, 14:14

If it helps, this is a Windows 7 64-bit platform. If no options are changed, it seems to be more stable. As options are adjusted, it seems to get out of sorts. I have tried several single changes, but have not found the one that causes the most trouble.

Changing IPv4 ranges seems to be an are where it is very sensitive. The first range entered after a fresh XML is created works generally. For example, changing the 3rd octet from 192.168.3.x to 192.168.99.x will reliably crash it for me.

Aborting a scan before it is complete and answering "yes" to the abort questions sometimes causes the same issue.

Thank you for any assistance you can offer.
SoftPerfect Support forum - Andrew avatar image

Re: Unhandled Exception 007DA767   10 April 2016, 15:44

I have received your XML config.

I think the problem is to have the max thread run-time set to 3 seconds. You will end up with memory leaks and generally the software may become unstable. This feature should only be used when for some reason scanning never ends and even then with caution.

Otherwise I recommend setting it to zero or a large value, maybe 60 seconds.

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

  *******   ********  **    **  **         *******  
 **     **  **        ***   **  **        **     ** 
 **     **  **        ****  **  **               ** 
  ********  ******    ** ** **  **         *******  
        **  **        **  ****  **               ** 
 **     **  **        **   ***  **        **     ** 
  *******   **        **    **  ********   *******  

Message: