Hello,

Please, disable scanning of Macs, Linux machines and SNMP-powered devices in Settings ("General" tab). Then check again if the crash occurs. If the problem persists, please, remove all data categories in "Windows reports" tab.

Make sure that you are running the latest version of Network Inventory Advisor.

Hi,
I just updated to the current version of NIA this morning. Prior to the update, I had successfully run a full network scan, no issues. After the update, I am getting the same crashes as cclark. Event log shows Event ID 1000 errors for each crash: Faulting application iadvisor.exe, version 3.9.1554.0, faulting module iadvisor.exe, version 3.9.1554.0, fault address 0x00265697. I have rebooted the machine, removed macs, linux machines and SNMP devices, and removed everything from the windows reports tab that I could. Application is still crashing. I would like to avoid having to delete all of my reports/logs and uninstall reinstall... but that is quickly coming up as my last option available. It is crashing at about 25% complete.

Sorry, it truncated my post:
Any help you could give would be appreciated. If I don't hear anything in the next day or so, I will do a clean wipe of the application and start over, hoping for the best.

Thanks,

Looking into this now. We'll update you shortly.

Still can't reproduce your exact scenario...

Can you try to specify scanning in 1 thread? This will help us identify whether it's just one node that causes the crash. Will you be able to reproduce this? Are you using Smart Scan, IP range scanning, re-scanning of the existing network?

If you are still inclined to testing with a clean network, just backup your [information] folder (inside of the installation directory of Network Inventory Advisor), this will make a copy of almost everything inside of the software.

Hi Jeff,
First, thanks for the quick reply, much appreciated.
Ok, so an update after I tested a few more things. A forced rescan runs flawlessly now. But I am getting crashes and errors when running a scheduled scan. It is running off of the same settings as my forced scan.The scheduled scan is running over an IP range, using the existing nodes from the completed forced scan (so known good information is coming at least from the nodes).

I am trying a re-scan with only the tabular report chosen (instead of the 7 reports I had checked previously). The scheduled scan with only 1 report crashed. Trying again with 0 reports selected.
This has worked. No crash.
Verifying with 1 report again, this time using Network Inventory Report. This ran correctly. Looks like some setting from the tabular report I had configured prior to the update is ... unhappy with something.
Settings from Tabular Report (figure you would appreciate this information)
# (consecutive), Node name, IP address, Device Type, OS name, Support phone number, domain/workgroup, MS Office version

As I look at this, I really do not remember ever adding the Support phone number to my tabular reports, as we don't have that information configured on any of our desktops.
Building a manual tabular report after removing Support phone number - Report ran correctly.
Re-running test-scheduled scan with the tabular report added back in - it crashed again, around 29% complete.

I will keep testing the tabular report using the test-scheduled scan and report back. But this is a long enough post to allow you to run with the information on your side as well

Sorry for the long post, but more information is almost always good. And I know even if it is annoying to read, full troubleshooting steps/diagnostics are always useful to some degree.

Thanks Jeff,

Hi again, and thank you for this long detailed explanation of what exactly happens. Seems that thanks to these details we were able to reproduce... something. We are investigating this now and will keep you updated.

There will be a minor update every other day. It will feature the fix of this issue!

Can you please redownload Network Inventory Advisor build 3.9.1554? We silently updated it today. It also includes the fix of this issue. Here's the link: http://www.clearapps.com/download.html

Add me to the list. Latest build. Disabled scanning if Linux, Mac and SNMP. No joy. Same error. Same crash. How annoying.

jimbecher, can you be more specific? What exactly do you mean by "Same error. Same crash"?

"iadvisor.exe has encountered a problem and needs to close."

Add me to the list. Just updated to newest version on my Windows 7 64-bit PC and when I try to scan my IP range for new assets or network scan I receive iadvisor.exe has encountered a problem and needs to close.

jimbecher and danno44, please, be more specific. Does the crash occur on scanning? Or when? Can you scan nodes one by one to see which one produces the error?

Also, how many nodes are you scanning? After you are able to disable scanning of Macs, Linux, SNMP-nodes, if you are still able to reproduce the crash, can you narrow down enabled categories in Windows Reports? If you disable collecting some of these data groups, will you be able to find the one that causes the issue?

I would recommend sending the details to help@clearapps.com - this would greatly help us provide more individual replies.

It fails at about 25% of completion when scanning for new assets. Anywhere from 50-75% of completion on standard network scan. I have approx 130 nodes. It happens whether or not Macs, Linux, SNMP-nodes scanning is enabled or diabled. All my Windows systems are in one group and if I scan that group, it fails. I don't have time to scan 130 nodes one-by-one to see what happens.

Here's the Event 1000 error code:

Classic 1/24/2011 12:05:56 PM Application Error 1000 (100)

Faulting application name: iadvisor.exe, version: 3.9.1554.0, time stamp: 0x4d1b94ca
Faulting module name: iadvisor.exe, version: 3.9.1554.0, time stamp: 0x4d1b94ca
Exception code: 0xc0000005
Fault offset: 0x001e709c
Faulting process id: 0x112c
Faulting application start time: 0x01cbbbf00ce17476
Faulting application path: C:\Program Files (x86)\ClearApps\Network Inventory Advisor\iadvisor.exe
Faulting module path: C:\Program Files (x86)\ClearApps\Network Inventory Advisor\iadvisor.exe
Report Id: 96d94f97-27e4-11e0-9d4e-001ec92cae3a

Ok, then here's the step-by-step instruction how to narrow down to the cause of the problem:

1. Start Network Inventory Advisor with the command-line parameter:

iadvisor.exe /log=crashlog.txt

See User Guide for more command-line options.

2. Go to Settings -> General, set 'Maximum simultaneous scanning threads' to 1

3. Scan your network. Reproduce the crash.

4. Locate the log file after the crash and send it to help@clearapps.com with the reference to this thread.

Thanks

My situation echos danno44's. I can almost guarentee it happens when scanning an asset. All my users are gone and their computers turned off. The scan worked fine. I have the latest build and do not scan for Linux, Macs of SNMP clients. Here is my event 1000:

Faulting application iadvisor.exe, version 3.9.1554.0, faulting module iadvisor.exe, version 3.9.1554.0, fault address 0x001e709c.

I too have 95 clients and can't really afford to spend the time trying to pin down which one is causing the pronlem.

Hi Jeff. I tried rinning iadvisor from the command line with the /log=crashtest.txt and it did not work. The splash screen came up for about two seconds then closed and that is all she wrote. Anyway...

Setting scanning threads=1 helped a great deal. It now sequentially scans the workstations from top to bottom and you can see which one it crashes on. I confirmed the problem child by scanning it individually and the crash occured again. If what I am seeing is correct it crashed while gathering Antivirus software. What would you like me to try now that I have found a workstation that will crash NIA consistantly?

We are already preparing a build to fix the issue with the crash on Antivirus data collection. A couple of other users also reported that. Let me talk to my test lab and get back to you asap.

I don't know if interesting is the word... I uninstalled and re-installed the virus software (Trend Micro WFBS 6.0) from this problem child. When I scanned it again NIA seemed to "hang" forever. I looked and the workstation and it has a pop up error on it "piagent encountered a problem and needs to close". I think all I did was move the crash from the scanning computer to the workstation LOL! I don't think that is what I wanted to do :)

So, you are scanning using an agent. Does the same happen if you scan directly using WMI only (see Settings -> General)? Also, seems like the build of Network Inventory Advisor that Kim sent you fixed the issue, right?

Any update on the build to fix the issue that Jeff mentioned on January 25th?

danno44, Kim will contact you shortly.