AGX 1700 crashes with multiple 3D SDE layers

[PeterLindstrom]

The problem: When I add multiple SDE layers that have Z-values to a map in ArcGIS Explorer (AGX) and zoom in or out, the program crashes. Not necessarily every time, but at least half the time. Panning seems to work fine, as do layers without Z-values. Here's the "problem signature" from Windows:

Problem Event Name: APPCRASH
  Application Name: E3.exe
  Application Version: 2.0.0.1700
  Application Timestamp: 4df14603
  Fault Module Name: ntdll.dll
  Fault Module Version: 6.1.7600.16695
  Fault Module Timestamp: 4cc7ab86
  Exception Code: c0000005
  Exception Offset: 00032ec0
  OS Version: 6.1.7600.2.0.0.256.4
  Locale ID: 1033

Desktop platform: AGX build 1700 with the data access expansion pack installed. Workstation-class Dell with Windows 7 64-bit and the most recent graphics drivers from NVIDIA.

Server platform: Windows Server 2008 R2 running SQL Server 2008 R2 and ArcSDE v10.

I'm pretty sure I've experienced this problem since I started using AGX at build 1200, but it hasn't really come to a head until now.

[AndreiIvanov]

Peter,

looks like ntdll.dll has caused the crash, which is a Microsoft dll. Unfortunately, information you've provided is not enough for us to trace the cause of the issue. If you could - attach the crash file to this post. I will take a look at it.

[PeterLindstrom]

I made it crash a bunch more times and got a couple of different results. I can't figure out how to save a crash file from any of them. I'm attaching an image of what it typically looks like (note that it crashed in gsrvrsql100.dll that time) - I tried clicking each button and it just closes every time. Here's the full text from one time when it just hung:

Description:
  A problem caused this program to stop interacting with 

Windows.

Problem signature:
  Problem Event Name: AppHangB1
  Application Name: E3.exe
  Application Version: 2.0.0.1700
  Application Timestamp: 4df14603
  Hang Signature: f304
  Hang Type: 2305
  OS Version: 6.1.7600.2.0.0.256.4
  Locale ID: 1033
  Additional Hang Signature 1: 

f304c9dedd50b8a75ea7715bfc0658d9
  Additional Hang Signature 2: 2d56
  Additional Hang Signature 3: 

2d56183ec4f7ec4b6b663dd28ad3c669
  Additional Hang Signature 4: c663
  Additional Hang Signature 5: 

c66340c1addd1327c20d970e9953ba6b
  Additional Hang Signature 6: f36a
  Additional Hang Signature 7: 

f36a83672a2e6debcf237a66b2bda20c

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please 

read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

[AndreiIvanov]

crash dumps should automatically be saved to the folder:

<drive>:\Users\<user name>\AppData\Roaming\esri\ErrorReports

[PeterLindstrom]

See attached. I noticed that it didn't generate the error report the first time it crashed this morning - maybe two different types of crashes are happening?

[PeterLindstrom]

I could have sworn that it worked fine with 2D feature classes yesterday, but today they're all crashing AGX. Confirmed the same problem on a Windows XP laptop running AGX 1700 (also with the data access expansion pack). Happy to try anything else that might lead to a fix...

[AndreiIvanov]

Crash dump did not reveal any info unfortunately. This is not obvious crash to decipher. We are trying to repro the case locally. Will keep you updated.

[AndreiIvanov]

just to confirm you are in 3D mode, right?

[PeterLindstrom]

Actually, no, the crashes I was experiencing were in 2D mode. I just thought it was related to having 3D data (i.e., with Z-values).

I just tested in 3D mode and got a similar crash. I'd been using direct connections to SDE, so I stood up a service and so far it seems to be working flawlessly.