Narrative Reports Freezing

I am using RM10, on a Windows 11 PC, with plenty of RAM. I’ve run the usual tools to no avail.

When I try to generate a narrative report covering more than three or four generations, the process simply freezes up. I am left with a dialog box which states “Generating Narrative Report for …” and nothing happens, even if left for a couple of hours. This is very, very frustrating, as all I want to do is generate a PDF report.

I did look at an old topic that mentioned to turn the sources off, but this problem still remains.

Is this a known issue? If so, is anything being done to resolve it, as it seems to have been similar to the ones people were talking about on RM7 and 8.

I would try just 1 generation, then 2 generation and see the results.

Smaller generations work, but that is not what I require.

There is probably an issue with someone in the line you are printing. Run the database tools under File, Tools and see if that helps. If not you will have to try different start people to see which person is causing the issue.

I’ve run all the database tools on multiple occasions. This has no effect, I’m afraid.

I’ve also tried this with multiple people, and the moment it goes much above 6 generations, it simply freezes, irrespective of what type of report I attempt to generate.

Best to open a support ticket with a backup of the database.
https://support.rootsmagic.com/hc/en-us/requests/new

The problem may be with one particular person rather than with the number of generations per se.

You didn’t say, but I’m guessing you are doing a descendant narrative report rather than an ancestors narrative report. So let’s suppose it freezes if you run descendants of John Doe for 6 generations but not if you run descendants of John Doe for 5 generations. I would start to diagnose the problem by running a 5 generation report for each of John Doe’s children in turn. Hopefully, it will freeze on one of the children and not the others. So doing it that way, you might be able to work your way down a generation at a time until you find the culprit.

If there is no culprit to be found, you are probably going to need to open a trouble ticket with the RM HelpDesk and submit your RM database along with the ticket.

2 Likes