Amanda,

I couldn't answer that question. I know that .NET is involved here.

Russ

Okay, I'll try uninstalling that service pack and will see if it fixes the problem.

Amanda,

It's been a time since you last posted and I was wondering if you have managed to resolve this problem. I too am experiencing the exact same issues under the same conditions and I'm getting very frustrated.

Thanks

Paul,

What Product Version of Family Tree Maker are you using? (Help, About)

What version of Windows are you using?

What, exactly, is the problem that YOU are experiencing. It's easier to reply when your message, with the details, is being replied to.

Thank you,

Russ

I haven't seen this problem in about a week - in that time, I ran a Windows update and my archival tool was also updated. Happily for me (but unfortunately for you), it appears to have resolved itself. I'll post again if it starts happening again.

Russ,

I've been following the actions as previously posted for Amanda and Brian, i.e.

uninstalling completeley and removing all files, reinstalling to .095,
installing patch to get to .305,
installing patch to get to .307,
registering online etc etc

I am using FTM2009 (18.0.0.307) on Windows Vista SP1 (all MS services/patches applied) and Internet Explorer 8

Everything seems to be working fine until I try to merge data from Ancestry.co.uk - If I do not select Merge Media then the fact is merged correctly.

However, if I select Merge Media then I get the "not responding" message and this stays like this until I restart the application - I have left this in this state for over an hour to see if it resolves itself, but it doesn't.

When the application is restarted I find that the fact has been merged but not the media.

I have 749 persons in the database and have compacted the file to no avail. I strongly suspect that this may be due to the recent Microsoft patches and/or IE8 as everything worked OK until a few weeks ago.

Thanks, Paul

Paul,

Thank you for the details. I suspect you may be correct. What might be interesting is the .NET version that is on your PC.

Before you did the Web Merge, did you Look at the Image, from within Family Tree Maker?

Russ

Russ,

The version of .NET installed is below:-

Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86

I usually merge records just from the search results. However, I have tried merging when opening the search record (get "not responding") and I have tried merging after looking at the image, still get "not reponding".

I have once again uninstalled FTM, reinstalled and tested the various versions.

.095 - merges work OK, with or without merging media, however when using the publish option this locks up

.305 - merges work OK but publishing fails

.307 - one person only in the database, merges OK without media, locks with media

If this software works fine for other Vista users then there must be something installed on my PC which is causing the issue. I have rebuilt my PC recently and Vista is fully up to date with all patches (and SP1). I only have MS Office 2007 and Bullguard antivirus software loaded.

I'm getting to the point where I will either need to rebuild my PC so that only Vista and FTM is loaded, this may prove that FMT 2009 does or does not work well with Vista, or otherwise forget using FTM 2009 all together.

Any further help/ideas would be truly appreciated.

Thanks, Paul

Paul,

When you reinstalled, did you re-register?

Is it possible that your Firewall or Anti-Virus is causing this problem, especially since all three versions hae issues.

What are the Publish error messages, or do you just see Not Responding?

Russ

Unfortunately, I'm still seeing this problem as well. I've noticed that it seems to work better if I merge while the image is up, but even that fails from time to time (about once every 10 merges or so).

I have Office 2007 and Norton Antivirus installed. I do have Windows Firewall and Norton Internet security on, so I've included exceptions for FTM 2009 in both (although that doesn't seem to be necessary all of the time). We'll see how that goes.

I did try using FTM 2008, and that works without issue.