I'm trying to troubleshoot ArcMap 10 crashing when I reconcile a version and I think it is OG1200ASU.DLL causing the problem. I'm guessing it's the attribute table or the attribute inspector.

GetProcAddress(0x773D0000 [c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\COMCTL32.DLL], "InitCommonControlsEx") called from "c:\windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4974_x-ww_a96f9c14\MFC90U.DLL" at address 0x78A43931 and returned 0x773D4088.
LoadLibraryW("DbgHelp.dll") called from "c:\program files\arcgis\desktop10.0\bin\AFCORE.DLL" at address 0x007144A4.
Loaded "c:\program files\arcgis\desktop10.0\bin\DBGHELP.DLL" at address 0x28380000.  Successfully hooked module.
DllMain(0x28380000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\program files\arcgis\desktop10.0\bin\DBGHELP.DLL" called.
DllMain(0x28380000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\program files\arcgis\desktop10.0\bin\DBGHELP.DLL" returned 1 (0x1).
LoadLibraryW("DbgHelp.dll") returned 0x28380000.
GetProcAddress(0x28380000 [c:\program files\arcgis\desktop10.0\bin\DBGHELP.DLL], "MiniDumpWriteDump") called from "c:\program files\arcgis\desktop10.0\bin\AFCORE.DLL" at address 0x007144B4 and returned 0x283DD4F0.
Second chance exception 0xC0000005 (Access Violation) occurred in "c:\program files\arcgis\desktop10.0\bin\OG1200ASU.DLL" at address 0x064A310B.
Exited "c:\program files\arcgis\desktop10.0\bin\ARCMAP.EXE" (process 0x1298) with code -1073741819 (0xC0000005).

I've narrowed my issue to the attribute table. When I start up ArcMap with the attribute table window docked, edit, then reconcile...ArcMap crashes.

If I start up ArcMap, close the attribute table window (or auto-hide), then edit, then reconcile...success!

If I start up ArcMap, close the attribute table window (or auto-hide), then open the attribute table window again, then dock (which effectively puts the attribute table window in same condition as it was on startup) , then edit, then reconcile...success!



2 Answers 2


That is the Open GL 2.0 compliant component according to ESRI OpenGL extensions viewer 3.31 is available here http://www.realtech-vr.com/glview/changes.html

  • Mapperz- I'm confused, are you saying that OG1200ASU.DLL is an ESRI provided component? Or suggesting that Jay is having a problem with OpenGL compliance with his installation? Can you expand any on the "according to ESRI" regards this particular DLL. Thanks! Stuart Commented Dec 30, 2010 at 16:47
  • I'm confused by the answer as well, but 3 others thought it was a good answer and I figured I must be missing something. I did run the extension viewer--OpenGL 2.1 and the rendering tests check out. Commented Dec 30, 2010 at 18:13

OK Jay, it's cheap since you've done the major lifting, but I'll go ahead and answer :)

ObjectiveGrid is the StingrayStudio (by Rogue Wave) programming widget set that ESRI uses for grided tabular data presentation and manipulation in ArcGIS. At ArcGIS 9.3.1 it is version 9.04 (og903asu.dll) and at ArcGIS 10 it is version 12.00 (og1200asu.dll).

To me, it looks like all ArcGIS graphical table based manipulations uses the ObjectiveGrid toolset. Over on the ESRI forums there have been multiple users and threads with issues regards Attribute table edits, for example NIM061049 is an ugly ctl-C, ctl-V deficiency that remains outstanding (NIM059999, NIM059402, NIM058769, NIM058886, NIM058820 are ESRI attribute related bugs supposedly fixed in SP1, certainly some may be ObjectiveGrid tabular data related). Unfortunately, ESRI doesn't really document the inner workings their GUIs and OO-glue for external reference. We're left guessing as to the exact role of their 3rd party development components and have to dig with tools like Process Monitor to peek under the hood, or to help identify problem components when crashes occur.

As users, the DbgHelp.dll error report we are presented submits a dump file back to ESRI and they can extract details of the crash for "internal use". Not sure how much they will provide back to the user community. And when I've dealt with ESRI tech support on issues, I've often had to run a Process Monitor log and tease out the offending modules in advance, as you've done for the og1200asu.dll on docked Attribute Table use in ArcMap.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.