Search for content in message boards

FTM 2014 New Installation Crashing

FTM 2014 New Installation Crashing

Posted: 16 Jan 2015 7:48PM GMT
Classification: Query
Just installed FTM for the first time. Updated to SP5
Sync to website - download tree.
Switch to family view and the program crashes everytime
After about 4 or 5 crashes (after taking backups) the program will not start.

Windows 10 64 bit
i5
4GB Ram
SSD
Acer Laptop

Message:
Family Tree Maker 2014 has stopped working.

A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

Been using Windows 10 for roughly 4 or 5 months and as of yet not had a single program fail - until today!

Re: FTM 2014 New Installation Crashing

Posted: 16 Jan 2015 7:58PM GMT
Classification: Query
More information:

Set system to Windows 7 - run FTM as administrator still will not start - even using Temp profile:

Windows error message:
Timestamp: 16/01/2015 19:50:19
Message: HandlingInstanceID: 11f25c3d-b3dd-427d-96ed-939a1ddcf721
An exception of type 'Microsoft.Practices.CompositeUI.EventBroker.EventTopicException' occurred and was caught.
---------------------------------------------------------------------------------------------------------------
01/16/2015 19:50:19
Type : Microsoft.Practices.CompositeUI.EventBroker.EventTopicException, Microsoft.Practices.CompositeUI, Version=1.0.51205.0, Culture=neutral, PublicKeyToken=69cf5367912b86b4
Message : One or more exceptions occurred while firing the topic 'OpenFtmFile'
Source : Microsoft.Practices.CompositeUI
Help link :
Exceptions : System.Collections.ObjectModel.ReadOnlyCollection`1[System.Exception]
Topic : Microsoft.Practices.SmartClient.Library.MyEventTopic
Data : System.Collections.ListDictionaryInternal
TargetSite : Void CallSubscriptionHandlers(System.Object, System.EventArgs, Microsoft.Practices.CompositeUI.EventBroker.EventTopicFireDelegate[])
HResult : -2146233088
Stack Trace : at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.CallSubscriptionHandlers(Object sender, EventArgs e, EventTopicFireDelegate[] handlers)
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Object sender, EventArgs e, WorkItem workItem, PublicationScope scope)
at Microsoft.Practices.SmartClient.Library.MyEventTopic.Fire(Object sender, EventArgs e, WorkItem workItem, PublicationScope scope)
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Publication publication, Object sender, EventArgs e)
at FTM.UI.PlanModule.PlanMainPanelViewPresenter.OpenFtmDatabase(Object sender, EventArgs e)
at Microsoft.Practices.CompositeUI.Commands.Command.OnExecuteAction(Object sender, EventArgs e)
at Microsoft.Practices.SmartClient.Library.Commands.MyCommand.Execute(EventArgs args)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Microsoft.Practices.CompositeUI.CabApplication`1.Run()
at FTM.FTMApplication.ᙆ(String[] ᙂ)

Additional Info:

MachineName : ???????????????
TimeStamp : 16/01/2015 19:50:19
FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=2.0.0.0, Culture=neutral, PublicKeyToken=69cf5367912b86b4
AppDomainName : FTM.exe
ThreadIdentity : ???????????????
WindowsIdentity : ???????????????

Subscriber Exception(s):
Inner Exception
---------------
Type : Microsoft.Practices.CompositeUI.EventBroker.EventTopicException, Microsoft.Practices.CompositeUI, Version=1.0.51205.0, Culture=neutral, PublicKeyToken=69cf5367912b86b4
Message : One or more exceptions occurred while firing the topic 'FtmDatabaseOpened'
Source : Microsoft.Practices.CompositeUI
Help link :
Exceptions : System.Collections.ObjectModel.ReadOnlyCollection`1[System.Exception]
Topic : Microsoft.Practices.SmartClient.Library.MyEventTopic
Data : System.Collections.ListDictionaryInternal
TargetSite : Void CallSubscriptionHandlers(System.Object, System.EventArgs, Microsoft.Practices.CompositeUI.EventBroker.EventTopicFireDelegate[])
HResult : -2146233088
Stack Trace : at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.CallSubscriptionHandlers(Object sender, EventArgs e, EventTopicFireDelegate[] handlers)
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Object sender, EventArgs e, WorkItem workItem, PublicationScope scope)
at Microsoft.Practices.SmartClient.Library.MyEventTopic.Fire(Object sender, EventArgs e, WorkItem workItem, PublicationScope scope)
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Publication publication, Object sender, EventArgs e)
at FTM.FTMController.ᙒ(Boolean ᙂ, Boolean , Guid ᙄ)
at FTM.FTMController.ᙎ(String ᙂ, Boolean , Boolean ᙄ)


Subscriber Exception(s):
Inner Exception
---------------
Type : System.Reflection.TargetInvocationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : Exception has been thrown by the target of an invocation.
Source : mscorlib
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : System.Object InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
HResult : -2146232828
Stack Trace : at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.RuntimePropertyInfo.SetValue(Object obj, Object value, Object[] index)
at Microsoft.Practices.ObjectBuilder.PropertySetterStrategy.InjectProperties(IBuilderContext context, Object obj, String id)
at Microsoft.Practices.ObjectBuilder.PropertySetterStrategy.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.CreationStrategy.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.ReflectionStrategy`1.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.ReflectionStrategy`1.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.ReflectionStrategy`1.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.SingletonStrategy.BuildUp(IBuilderContext context, Type typeToBuild, Object existing, String idToBuild)
at Microsoft.Practices.ObjectBuilder.TypeMappingStrategy.BuildUp(IBuilderContext context, Type t, Object existing, String id)
at Microsoft.Practices.ObjectBuilder.BuilderBase`1.DoBuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)
at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)
at Microsoft.Practices.CompositeUI.Collections.ManagedObjectCollection`1.BuildFirstTimeItem(Type typeToBuild, String idToBuild, Object item)
at Microsoft.Practices.CompositeUI.Collections.ManagedObjectCollection`1.Build(Type typeToBuild, String idToBuild, Object item)
at Microsoft.Practices.CompositeUI.Collections.ManagedObjectCollection`1.AddNew[TTypeToBuild]()
at FTM.People.Collection.CollectionController.AddViews()
at FTM.People.Collection.CollectionController.Run()
at FTM.People.PeopleModuleController.ViewCollection(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Microsoft.Practices.CompositeUI.Commands.Command.OnExecuteAction(Object sender, EventArgs e)
at Microsoft.Practices.CompositeUI.Commands.Command.Execute()
at Microsoft.Practices.CompositeUI.Commands.Command.OnExecuteAction(Object sender, EventArgs e)
at Microsoft.Practices.CompositeUI.Commands.Command.Execute()

Inner Exception
---------------
Type : System.Runtime.InteropServices.SEHException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : External component has thrown an exception.
Source :
Help link :
ErrorCode : -2147467259
Data : System.Collections.ListDictionaryInternal
TargetSite :
HResult : -2147467259
Stack Trace : The stack trace is unavailable.

Category: Exception
Priority: 0
EventId: 100
Severity: Error
Title:FTM Exception Handling
Machine: ???????????????
Application Domain: FTM.exe
Process Id: 4860
Process Name: C:\Program Files\Family Tree Maker 2014\FTM.exe
Win32 Thread Id: 11040
Thread Name:
Extended Properties:

Followed by:
Application: FTM.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Practices.CompositeUI.EventBroker.EventTopicException
Stack:
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.CallSubscriptionHandlers(System.Object, System.EventArgs, Microsoft.Practices.CompositeUI.EventBroker.EventTopicFireDelegate[])
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(System.Object, System.EventArgs, Microsoft.Practices.CompositeUI.WorkItem, Microsoft.Practices.CompositeUI.EventBroker.PublicationScope)
at Microsoft.Practices.SmartClient.Library.MyEventTopic.Fire(System.Object, System.EventArgs, Microsoft.Practices.CompositeUI.WorkItem, Microsoft.Practices.CompositeUI.EventBroker.PublicationScope)
at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Microsoft.Practices.CompositeUI.EventBroker.Publication, System.Object, System.EventArgs)
at FTM.UI.PlanModule.PlanMainPanelViewPresenter.OpenFtmDatabase(System.Object, System.EventArgs)
at Microsoft.Practices.CompositeUI.Commands.Command.OnExecuteAction(System.Object, System.EventArgs)
at Microsoft.Practices.SmartClient.Library.Commands.MyCommand.Execute(System.EventArgs)
at System.Windows.Forms.ToolStripItem.RaiseEvent(System.Object, System.EventArgs)
at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStripDropDown.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at Microsoft.Practices.CompositeUI.CabApplication`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Run()
at FTM.FTMApplication.ᙆ(System.String[])


and then:
Faulting application name: FTM.exe, version: 22.0.0.1345, time stamp: 0x54925b28
Faulting module name: KERNELBASE.dll, version: 6.4.9879.0, time stamp: 0x54586150
Exception code: 0xe0434352
Fault offset: 0x000000000001c328
Faulting process ID: 0x12fc
Faulting application start time: 0x01d031c5991e938d
Faulting application path: C:\Program Files\Family Tree Maker 2014\FTM.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report ID: e5d90af3-9db8-11e4-beb7-2089847e28dd
Faulting package full name:
Faulting package-relative application ID:

Re: FTM 2014 New Installation Crashing

Posted: 5 Feb 2015 5:29AM GMT
Classification: Query
This is an issue that some of us are having. To resolve clear your start up options when you get the crash screen and then just use FTM for syncing a local copy and close the tree each time you exit. Don't change to the family view, just leave it in pedigree. Are you using a MB with Intel 4600 graphics built in? Curious because that is what I am using. There are some people on 9926 that are not having the issue but I am. I updated from 8.1 to 9926 over the weekend. Let me know if you hear anything. It is pretty normal for support to not respond and I don't remember a major windows update where FTM did not break. I am glad I have an online account right now because if I did not and I was in my normal scanning images mode locally I might not be as relaxed. I know the answer is it's a pre release version but this one is 5 months into the process and probably will be released in mid spring. It would be nice if FTM for once got it right.

Re: FTM 2014 New Installation Crashing

Posted: 5 Feb 2015 3:17PM GMT
Classification: Query
Are you rebooting Windows between crashes? FTM leaves a lot of stuff hanging around when it crashes. I am running Vista and have found in the past that after a crash I have had to reboot before FTM will run again. Windows 8.1 onwards doesn't do a full reboot does it? I think it sort of hibernates so it will start up quickly. If there is a way of doing a full reboot then try that - might allow the program to run again but probably won't stop it crashing!

Chris.

Re: FTM 2014 New Installation Crashing

Posted: 6 Feb 2015 2:59AM GMT
Classification: Query
This has nothing to do with your computer crashing, this is just FTM. When you get the ability to pull up the crash report, there is a button to allow you to deal with the start up options and then to clear them. You restart and pick your trees again, pick the method to work with your trees and I believe to log back in again. Before I was doing this all the time, then I did it one time and make sure that I do not use the family view at all anymore and always close the tree before I exit FTM. Someone will fix this probably in the next month or too. I have learned over the years that when I have an paid ancestry.com period to do all my work online and sync when I am not online. Then when I am not paying, I just upload pictures and stories and articles to my tree. I have been burned to many time with sync issues because I was using both at the same time. Of course if you are just using the ftm product and really need it now then I would roll back to what you had before for windows.

Re: FTM 2014 New Installation Crashing

Posted: 18 Jul 2015 4:48AM GMT
Classification: Query
As of 7/17/2015 still not working with Windows 10 TH1 which is should be the release they push out. There will be additional patches of the next 12 days but Ancestry needs to release the patch for FTM 2014 that solves this problem. I don't want to wait for FTM 2016 to see the family view problem resolved.

Re: FTM 2014 New Installation Crashing

Posted: 26 Jul 2015 9:22AM GMT
Classification: Query
Last week I updated to the "Release version" of Windows 10 and FTM seems to be stable except one menu item - "Family Tree View" if you click this then the program just crashes!!

I have managed to merge 2 tree's - on the third or fourth attempt - kept getting different problems - with the host tree getting corruptions - finally had an almost clean merge.

I have just gone back into FTM having completed the merge - updated the website - re-invited my guests and closed down - only to have the start up crash and have to re-connect the tree.

29th is going to be fun for FTM users around the world - hopefully they will fix the program before then - but I suspect not!!

Re: FTM 2014 New Installation Crashing

Posted: 26 Jul 2015 9:24AM GMT
Classification: Query
Windows 8.1 and 10 does hibernate if you shut down - if you restart then it restarts a clean windows session.

Re: FTM 2014 New Installation Crashing

Posted: 26 Jul 2015 6:13PM GMT
Classification: Query
I am just finishing up my 6 month membership, normally I do three months each year and put that note in my cancellation comments. It amazes me how much money they put in the web site and it makes sense but they really don't put much into the software. Last year was the first time in many years that they did not do an upgrade. Having the product working has never been a priority as part of a windows upgrade. My main issue is that I use the family view for everything so during the off season it is a pain.
per page

Find a board about a specific topic