News:

Thou shalt confirm thine airspeed on final, lest the earth rise up and smite thee. (pre-landing checklist, v1)

Main Menu

Plan G stopped working on startup

Started by m_clark_38, March 05, 2014, 10:59:23 PM

Previous topic - Next topic

m_clark_38

Hello,

I downloaded and installed the newest version of Plan G yesterday and installed the newest .Net Framework.  I still receive the "Plan G has stopped working" error a few minutes after I log the program.

Here's what I get when I click show details:

Problem signature:
Problem Event Name:   CLR20r3
Problem Signature 01:   plan-g3.exe
Problem Signature 02:   3.1.0.82
Problem Signature 03:   53109070
Problem Signature 04:   UIAutomationTypes
Problem Signature 05:   4.0.30319.18408
Problem Signature 06:   52313183
Problem Signature 07:   e
Problem Signature 08:   0
Problem Signature 09:   System.DllNotFoundException
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

And the Plan G log:
16:43:26.8 Starting Plan-G, build 3.1.0.82
16:43:26.8 OS is Microsoft Windows NT 6.1.7601 Service Pack 1
16:43:27.0 InitDataFolder
16:43:27.0 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\PlanG3_FSX.sdf
16:43:27.0 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\PlanG3_FS9.sdf
16:43:27.0 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\PlanG3_XPX.sdf
16:43:27.0 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\PlanG3_P3D.sdf
16:43:27.0 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\PlanG3_NAVI.sdf
16:43:27.1 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\UserWaypoints.sdf
16:43:27.1 Data Source = C:\Users\Mike\Documents\Plan-G Files\Data\MEF.sdf

Any Ideas on how to fix this?

Thanks,
Mike

tim arnot

Hi Mike,

There's been a couple of people reporting similar issues just after startup, but as yet we haven't got to the bottom of it. And to confound things further, the error you're showing is different to the others. You have a "dll not found" error, which suggests something isn't installed (SQL Server CE, maybe? - it would have helped if Windows reported *which* dll wasn't found!)

Tim. @TimArnot

m_clark_38

Pulled this from the event viewer if it helps at all

Faulting application name: Plan-G3.exe, version: 3.0.7.71, time stamp: 0x525a9d7a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x1f50
Faulting application start time: 0x01cf38c51acabc80
Faulting application path: C:\Program Files (x86)\TA Software\Plan-G v3\Plan-G3.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5c7fcf07-a4b8-11e3-be75-bacc9b1a02f7


Application: Plan-G3.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException
Stack:
   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
   at System.Windows.Application.LoadComponent(System.Uri, Boolean)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at Plan_G3._Main.Main()


tim arnot

Thanks, it still doesn't say what it was trying to load. My guess from the P-G log is still with SQLserver, since it gets to the point where it's about to start accessing the database.

Tim. @TimArnot

nic_bos