The eaDocX trace is from a went-wrong (“EA has stopped working”) run; the doc (which looks at least superficially fine) is the output from that failed scenario. I posted the trace because there’s that one warning about “First-time” in it and I thought perhaps that would be a clue, though I don’t actually see how.
There was still the same general Application Error pair in the Windows Logs/Application:
Faulting application name: EA.exe, version: 10.0.0.1006, time stamp: 0x5109a97f
Faulting module name: DAO350.DLL, version: 3.51.1608.0, time stamp: 0x352b9adf
Exception code: 0xc0000005
Fault offset: 0x000196b4
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15
Application: EA.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at EA.RepositoryClass.GetElementByID(Int32)
at TSF.UmlToolingFramework.Wrappers.EA.Model.getElementWrapperByID(Int32)
at TSF.UmlToolingFramework.Wrappers.EA.Diagram.get_owner()
at TSF.UmlToolingFramework.Wrappers.EA.Diagram.get_fqn()
at TSF.UmlToolingFramework.EANavigator.NavigatorControl.getToolTipText(TSF.UmlToolingFramework.UML.UMLItem)
at TSF.UmlToolingFramework.EANavigator.NavigatorControl.makeElementNode(TSF.UmlToolingFramework.UML.UMLItem, System.Windows.Forms.TreeNode, System.Windows.Forms.TreeNode)
at TSF.UmlToolingFramework.EANavigator.NavigatorControl.bw_DoWork(System.Object, System.ComponentModel.DoWorkEventArgs)
at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
I hope EA comes up with a suggestion, this is a bit frustrating (not a good “trial” experience 🙂
