Active scanning OU filtering - crash

[joegasper]

Clicking the button to display OU paths for the OU filtering option, lsmanage crashes seen below. I image it could be the fact we have 8700 OUs. I wonder if the component to display the list of OUs could be a tree view and only query and display the next level as you drill down.


Problem signature:
Problem Event Name: APPCRASH
Application Name: lsmanage.exe
Application Version: 4.1.0.68
Application Timestamp: 4ced0c5e
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdbdf
Exception Code: 0eedfade
Exception Offset: 0000b727
OS Version: 6.1.7600.2.0.0.274.10
Locale ID: 1033
Additional Information 1: dc75
Additional Information 2: dc754b7954f37a0862c7f078ce1b52ac
Additional Information 3: 06bc
Additional Information 4: 06bc7b5b59a2bbf2411848da521eb34a

[Hemoco]

Fixed in latest beta

[Hemoco]

Could you please contact us by e-mail for a test version of the OU selector.

[joegasper]

On a physical Windows 2003 SP2 box:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 1/4/2011
Time: 9:49:32 AM
User: N/A
Computer:
Description:
Fault bucket 45740507.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 34 35 37 34 30 35 30 37 45740507
0010: 0d 0a ..

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1/4/2011
Time: 9:50:42 AM
User: N/A
Computer:
Description:
Faulting application lsmanage.exe, version 4.1.0.68, faulting module unknown, version 0.0.0.0, fault address 0x00000000.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6c 73 6d ure lsm
0018: 61 6e 61 67 65 2e 65 78 anage.ex
0020: 65 20 34 2e 31 2e 30 2e e 4.1.0.
0028: 36 38 20 69 6e 20 75 6e 68 in un
0030: 6b 6e 6f 77 6e 20 30 2e known 0.
0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 30 30 30 30 30 30 00000000



This is from a physical R2 box:

Faulting application name: lsmanage.exe, version: 4.1.0.68, time stamp: 0x4ced0c5e
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0x0eedfade
Fault offset: 0x0000b727
Faulting process id: 0x2f84
Faulting application start time: 0x01cbac1c883805fe
Faulting application path: E:\LansweeperActions\lsmanage.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 0ecfb5ee-1810-11e0-91e2-005056c00008

Fault bucket 2253385148, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: lsmanage.exe
P2: 4.1.0.68
P3: 4ced0c5e
P4: KERNELBASE.dll
P5: 6.1.7600.16385
P6: 4a5bdbdf
P7: 0eedfade
P8: 0000b727
P9:
P10:

Attached files:
C:\Users\myaccount\AppData\Local\Temp\WER94CA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\myacount\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lsmanage.exe_f2501182ceeb5ccf23f117f98430e8b32cfd2c8_0e6ab17e

Analysis symbol:
Rechecking for solution: 0
Report Id: 0ecfb5ee-1810-11e0-91e2-005056c00008
Report Status: 1

[Hemoco]

We haven't been able to reproduce this, can you get it running on a different OS?

[Hemoco]

Can you try running lsmanage.exe on a different OS in the same domain to see if you have the same problem.

[joegasper]

Server 2008 R2 RTM (as ESX VM)

[Hemoco]

Which is the OS/SP you are running Lsmanage.exe on?