Jump to content


Photo

RM7.2.3.0 stalling on backup

FTM 14

  • Please log in to reply
12 replies to this topic

#1 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 19 March 2017 - 07:59 PM

FTM file will import to RM7.2.3.0 but will not make backup file either by using toolbar or by clicking Exit which then prompts to backup.  On backup, file hangs for up to 30 minutes, maybe longer but shutdown program after that through Task Manager which shows 'Not Responding' all three times.  Have tried this three times.  *.rmgc file does show in proper folder , file opens easily in RM and a quick check after opening file in RM7 program shows that media is linked but still cannot backup file.
FTM database was compacted before attempting to load FTM file into RM and I have confirmed that file is FTM2014 v.22.0.0.1410 and not 2014.1.
First time this has happened.  Imported FTM file with 29,698 people and 5.2GB of media end of February without problems.  File now is 29,731 people and 5.82GB of media.
I am running Win 7 Pro 64x.

Problem Signature shows two sets of hang signature; 71f1 and 2048 after three failures.  Details below.

Thank you for assistance.

 

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    RootsMagic.exe
  Application Version:    7.2.3.0
  Application Timestamp:    5887b2fc
  Hang Signature:    71f1
  Hang Type:    2048
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    4105
  Additional Hang Signature 1:    71f15326c811962bae229b54141ef98d
  Additional Hang Signature 2:    632f
  Additional Hang Signature 3:    632f937eea3a5597e73535463e09944a
  Additional Hang Signature 4:    71f1
  Additional Hang Signature 5:    71f15326c811962bae229b54141ef98d

 

Below seen with first and third backup hang.

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    RootsMagic.exe
  Application Version:    7.2.3.0
  Application Timestamp:    5887b2fc
  Hang Signature:    60ac
  Hang Type:    2048
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    4105
  Additional Hang Signature 1:    60ac140cd2ca6017c6c490e4cf84b13e
  Additional Hang Signature 2:    6fb2
  Additional Hang Signature 3:    6fb2552852a9c8e3fdc6e76f68678db3
  Additional Hang Signature 4:    60ac
  Additional Hang Signature 5:    60ac140cd2ca6017c6c490e4cf84b13e
  Additional Hang Signature 6:    6fb2
  Additional Hang Signature 7:    6fb2552852a9c8e3fdc6e76f68678db3



#2 zhangrau

zhangrau

    Advanced Member

  • Members
  • PipPipPip
  • 1175 posts

Posted 20 March 2017 - 03:55 AM

Where are the media stored? Local drive or an online cloud-based archive?



#3 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 7271 posts

Posted 20 March 2017 - 07:28 AM

Try running the Compact File tool inside of FTM and then do the direct import. 


Renee
RootsMagic

#4 kbens0n

kbens0n

    Advanced Member

  • Members
  • PipPipPip
  • 3290 posts

Posted 20 March 2017 - 10:15 AM

You don't specify location of backup, but make sure it is not to a sub-folder of the RootsMagic installation folder or any sub-folder of Program Files / Program Files (x86)
(They are system folders that Windows controls with strict permissions)

You might also try starting up RootsMagic by right-clicking on the shortcut you use and selecting Run As Administrator

---
--- "GENEALOGY, n. An account of one's descent from an ancestor who did not particularly care to trace his own." - Ambrose Bierce
--- "The trouble ain't what people don't know, it's what they know that ain't so." - Josh Billings
---Ô¿Ô---
K e V i N


#5 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 21 March 2017 - 10:08 PM

zhangrau,

Media are stored Local drive  as in "Documents\A N C E S T R Y\___RootsMagic\FTM2014 for new file\All the Strength of Our Ancestors - 2016-12-24-17.04 Media"

 

Renee,

FTM file was compacted 2.4% while it was open in FTM2014 then that file was imported to RM.

 

kbens0n

Tried backing up to external drive and to local drive in Documents.  Just tried again.   First backup without checking 'Backup media files' worked fine.  Second try with 'Backup media files' to same backup folder in MyDocs stalled.  Shut down after more than 30 minutes with no activity.

 

Could the media file be too large for RM to handle?  Currently sitting at 5.87 GB with 10,431 files.  Don't believe that backup file without media could be the problem as it appears to backup fine but FTM file is 132 MB and when imported to RM is 52.5 MB.  Was importing compacted FTM files and backing up just fine until this last try.  Made sure that the FTM tree has not been updated to macKiev 2014.1.

 

Now that I think about it, there was an update to RM just before I had problems.  Could the update not have installed properly?  Can I go back to an earlier version to confirm the problem started with the newest update or that the FTM file does open and backup in an earlier version?

 

Frustrating as RM was working fine and I was spending more time with it and only imported the larger tree so I wouldn't need to manually enter more than 200 people/media as RM doesn't sync yet.

 

Would really like to find a fix for this as RM is definitely more user friendly, especially with this large tree of almost 30K people.

Thanks for all your help.



#6 zhangrau

zhangrau

    Advanced Member

  • Members
  • PipPipPip
  • 1175 posts

Posted 22 March 2017 - 12:25 AM

A couple thoughts:

.

1 - I don't think the file size is the issue. I'm also using RM 7.3.2.0 and my main database RMGC is about 1.2 GB, and the backup without media RMGB is about 238 MB. Both of those sizes are larger than you mentioned.

.

2 - Your path name looks unnecessarily long to me. I'm still using Win7 64-bit, and the path length rules may be a bit different for Win10. In earlier versions of Windows the TOTAL path length, with drive letter, folders, punctuation, filename and extension was limited to about 264 characters. You're using a lot of those just for the path. If you also are using long filenames (in order to be descriptive) you may be exceeding a length limit.

.

3 - The maximum path & file length varies for CD or DVD or hard drive. I think USB has the same limits as a hard drive.

.

4 - Surely my habits are holdovers from DOS and early versions of Windows, but I avoid using spaces and punctuation in folder and filenames. I've found that the - _ # $ & characters are no problem, but some other characters will cause problems (especially / \ * and ? since they have special meanings as dividers and wild cards)  Again, early versions of Windows would choke on excess periods, but newer versions are pretty tolerant (although I personally avoid them except just before the file extension).

.

5 - Here's an article about Win 10 file name lengths - https://mspoweruser....ter-windows-10/

.

6 - Here's some older info on other file naming standards - http://en.community....3534/t/15838304



#7 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 7271 posts

Posted 22 March 2017 - 06:53 AM

Importing a FTM Backup over 4GB in Size.

 

http://support.roots...r-4-GB-in-size-


Renee
RootsMagic

#8 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 23 March 2017 - 09:06 AM

zhangrau
Thanks for the quick reply.
I am running Win 7 Pro 64-bit.  Avoiding Win10 like the plague after M$ snuck it in back in Sep 2015.  Took 3 re-formats to get back to a stable Win 7.

So threw the whole path into Notepad++, Word 2013 and Corel WPX7 for character count charac with no spaces  116  (103), charac without blanks 134 (122); brackets are for rmgc file.

C:\Users\Snowy\Documents\A N C E S T R Y\___RootsMagic\FTM2014 for new file\All the Strength of Our Ancestors - 2016-12-24-17.04 Media
and
C:\Users\Snowy\Documents\A N C E S T R Y\___RootsMagic\FTM2014 for new file\All The Strength of Our Ancestors - 2017-03-19.rmgc

Then opened new folder [Rootsmagic] on MyDocs, removed spaces from file name [AllTheStrengthofOurAncestors-2017-03-19] and import worked fine.  Drilldown is not so long now.  RM opened fine and was able to move around people without problems.  Backup worked quicker than I thought it would.  There is an 'rmgb' file on MYDocs but nothing in the Rootsmagic folder I directed the backup to go to.  There is no media file in either that folder or in the MyDocs folder.  Checked through 'search' in case the Media folder went somewhere unexpected but nothing.  Deleted the rmgb and redid a backup request again directing backup to the Rootsmagic folder but had same results.

 

Now thinking maybe one of the media names may be the problem thought I number code my own media.  May have picked up a long character from Ancestry.com that I missed as I did +++ work over the past few weeks before the last sync.  Will go through the FTM media folder tonight looking for that.

Renee  (eight hours after I did above)
Imported FTM file as you suggested and to a single folder on MyDocs [Rootsmagic2], assuming a similar problem as zhangrau above suggested.  Imported fine from opened zip file.  Now all media are showing with red X.  

 

UPDATE - 23 Mar at 0900 MDT

Now suspecting that installation of a 2016 Income Tax program last week, which demanded massive uploader updates to Windows before it would open may have caused major problems to the OS.  Been using the same tax product for more than 20 years and this is the first time it gave no end of grief on install and running.  Now other programs on this laptop are not working as cleanly as before.  Did a System Restore back three points and still having grief.  My son who is IT trained is coming on the weekend to see if M$ has caused the problems.

I do want this to be fixed, so should I repost to this same topic on Saturday if we do or do not resolve the problem(s) or let this topic close out and start a new one.  The new topic if there are still problems or if my son and I have been able to repair the OS, might be useful to anyone else who suddenly has similar problems.

 

Thank you for your patience.

Theresa



#9 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 7271 posts

Posted 23 March 2017 - 03:25 PM

Renee  (eight hours after I did above)

Imported FTM file as you suggested and to a single folder on MyDocs [Rootsmagic2], assuming a similar problem as zhangrau above suggested.  Imported fine from opened zip file.  Now all media are showing with red X.

 

Go to Lists>Media Gallery>Tools>Fix broken media links to repair the links. It will do so if the media is on the computer and the filenames have not been changed. 


Renee
RootsMagic

#10 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 26 March 2017 - 08:58 AM

Renee,

My laptop is on its second reformat right now and my son said he will do a third before Win7Pro 64x will be installed again. 

So loaded RM7 and installed updates to my daughter's laptop (running Win10Pro 64x) as well as the older copy of FTM2014 program saved to external from Sep 2016.  Bypassing 2014.1 and a newer FTM version from January 2017 this time after thinking the FTM update last January may have had bits of macKiev in it and causing grief. 

Downloaded a fresh tree from Ancestry.com to do another import to RM.  Compacted FTM tree, confirmed all media present in folder,  so zipped ftmb.  First attempt and Media again needing to be linked to RM tree as expected, so link repair started.  Assumed daughter's computer had stalled after about 9 hours, stuck at about 85% and shut down RM through Task Manager. Download from Ancestry took more than 7 hours so assumed that import would take that long.

Redid a fresh import to RM7 yesterday and as expected Media needed to be relinked to RM7 tree again.  Looked like it was going to take more time (already at 9 + hours) and as FTM media folder is quite large at 5.85GB, left it at about 85% complete and running overnight to finish. 

This morning still showing at about 85% complete now, more than 17 hours later.  Task Manager showed Rootsmagic still running happily and responding but track on "Relinking media" bar not moving even after waiting another hour or so this morning, so shut down program through Task Manager.

Unsure now what I am missing.  RM from import itself looks fine on opening and if I ignore missing media, people info appears to be where it should be, no error 'flags' on a quick go through.  Media that I do see is present with a few red 'x' present.

Could something on the downloads from Ancestry be the problem or maybe the size of my tree - 29781 people, the media file at 5.85GB.  RM 7 was working fine until the last backup about a week ago.  My tree size has been growing over the past six months or so as I add new media and people, but the stats I keep show that previous backups were still working with over 25K people and a media file larger than 4 GB and with media not needing to be relinked.

I agree with zhangrau that I need to keep the character line shorter but RM7 backup and now Media relinking seem to be affected now.   Maybe the backup program copies on my external are corrupted by being in contact with my laptop?  Possibly grasping at straws but I am frustrated.  My son says it is a possiblilty that something downloaded from Ancestry to cause problems and could have in the background fussed with other programs but then all the programs on my laptop started giving grief after installing that tax program.  Doesn't explain why same thing is happening on my daughter's OS.  Definitely something is not happy working with others in the sandbox.  Will need to rethink this through.

Thank you both for your assistance in this.  I have two 12 hour shifts Monday and Tuesday but am on Spring Break from the school I work at so have more free time later in the week to reload programs to my 'clean' laptop.  Will have another go over the next few days with the new OS install and post back results.

Theresa



#11 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 26 March 2017 - 06:01 PM

After doing some work on Ancestry.com today, I ran a sync in preparation to doing another FTM backup.  Couldn't figure out where it sent the profile as I shutdown so we could go out to Geocache, so had to do a search on Mydocs and found a new FamilyTreeMaker folder that I didn't make.  When clicking on the FTM file to open it, noticed that the icon on the bottom tray looked different and now said FTM 2014.1.  I didn't agree to anything on the sync, just the usual download but my son (the IT specialist) said Ancestry may have added 2014.1 capability to all sync function even though my FTM program still says it is 2014.  He said the change to 2014.1 may be miniscule enough that my original non-macKiev program can run the family tree which is why I didn't notice a change.

I made 3 FTM backups to three different locations over the past week hoping that one of them was not corrupted only to now find that they are all of macKiev 2014.1 formatted.

Opened an older file from last summer into the 2014 program, did a backup and now it too says 2014.1 format.  My son checked Ancestry.com's EULA but didn't see anything specific to accepting an update to the macKiev format but it does say you agree to any program changes when you use the program.

Looks to both of us that there is now something in the sync download that changes the file though possibly only the newest media and people changes have been affected which has caused RM to stall when importing.  Graeme suggested I start from scratch again so am in the process of downloading the full tree so everything has the 2014.1 update.  Download will probably take until tomorrow for all media to come in.  Will then do an export at the FTM2012 level and try an RM7 import.

Frustrating if Ancestry.com has forced an update on subscribers making it difficult to import their tree to Rootsmagic.  Very bad form.

Theresa



#12 mjashby

mjashby

    Advanced Member

  • Members
  • PipPipPip
  • 133 posts

Posted 27 March 2017 - 02:59 AM

Theresa,

 

You need to be quick if you need to get your Ancestry data fully synched via your 'old' copy of FTM.  According to MacKiev's site:

 

"

  • On March 29, 2017, Ancestry will be permanently retiring TreeSync® which is being replaced by Software MacKiev’s FamilySync. 
  • Between Wednesday, March 29 and Friday, March 31, 2017 syncing functionality will be unavailable as Software MacKiev and Ancestry deploy the new syncing technology.
  • FamilySync will be available only in Software MacKiev’s Family Tree Maker 2017 edition, which is planned for release on March 31, 2017.  No other FTM edition will sync with Ancestry trees.
  • Ancestry’s search, merge, and Ancestry hints will all work as they do now in FTM 2017 for users who sync with their Ancestry trees. After March 29th these functions will no longer work in any other FTM edition.
  • Among the new features of FamilySync is the ability for two or more computers in your home running Family Tree Maker, such as a desktop and a laptop, to sync with the same Ancestry Member Tree.

"

 

Mervyn


MJA

"A Mac User with Windows Tendencies"


#13 owlsquest

owlsquest

    Member

  • Members
  • PipPip
  • 10 posts

Posted 29 March 2017 - 11:22 AM

Mervyn,

Firstly, love your Snoopy icon.  Have more Snoopy scrub tops than you could imagine and an awesome Snoopy/Tardis hoodie my kids bought me last Christmas.

 

My son and I believe we have solved almost all of the import problems.  Full tree download took far less time than expected, about 3 hours vs. the 18+ hours last December, very nervous about that.  The latter file had almost 1K people less than this newest download so I was sceptical.  Properties on that newly downloaded tree now show FTM version 2014.1 even though I do not have the macKiev program on my laptop.  This newly downloaded tree still opened in my FTM 2014 which I checked through Help to confirm that my original software version had not been changed.  Tried to export to FTM2012 but FTM stalled, “export process failed because an error occurred”.  Would export to FTM2012 just fine last week during this mess, just would not then import to RM.  Took the full backup suggestion from Renee, changed format to zip and it opened in RM just fine.

Did a quick check of media for some problem people to find it was still missing, red 'x' noted.  Checked with those specific people on Ancestry tree only to find that many of the media that had been uploaded from my laptop over the past few months now had the dreaded grey "missing" icon.  Unsure how many more there are.

 

I also opened the newest email from macKiev last night about FTM2017 which now, at least to me, explains why I have been having so much trouble over the past month, the last week in particular.  $$$$ signs come to mind.  With the loss of Treesync expected tonight and the major jump in cost if you don't buy in before midnight Thursday, I reluctantly purchased the upgrade, hopefully so my online tree will not be damaged any more than it has while I await the upgrade for RM7.  BTW, a FTM2017 family license for three computers is an additional $30 Canadian on top of the upgrade price.  Did not purchase that license.  Just checked and Rootsmagic still grants a family licence, which saved my buns as I worked through this FTM mess over the past week.

 

I am unsure how to sort the RM7 media file for all the broken media in my tree so am scrolling through the file image by image and noting red x’s and their related person.  I have 10.5+K media items to check through and it appears that on rough estimate [left off at 1012 media items] that about 10% are red x’s; not in any particular order, tagged to a person, date image uploaded or saved to the tree from another AMT.

 

I am heartbroken over all the work I have put in over the past 20+ years as our family historian with my family members depending on me to "pull it together" only to have a company treat its customers with such distain.  I only moved from Ancestral Quest (over 20+ year usage) to FTM in August 2015, so my family could follow my progress online.  I feel so abused by Ancestry over the past while and am still angry when they left thousand plus to swing in the wind in Dec 2015.

 

I eagerly await when RootsMagic brings out their sync update.  RM has been much more reputable and upfront in insisting that their product have as many bugs removed and be stable before bringing it out to the public plus they are very courteous and informative when I chat or call.  Once my tree is imported to the updated RM7, I will never go back to FTM again.

 

Last thoughts.  "Bad Form!!!!" to Ancestry and macKiev.  You have forgotten what you learned in kindergarten and have forgotten how to play in the sandbox.

Theresa