By Nand - Thursday, April 11, 2024
|
When generating an update to our family tree I got following errors in the log
 A re-run gave the same error.
Any clues?
|
By genome - Thursday, April 11, 2024
|
I have seen similar when publishing a large report. I put it down to a network glitch but as you had the same error twice maybe not.
I suggest running again with the 'Publishing Option' under Content tab set to 'No change of data ...' to reduce runtime since it would appear all data pages have been generated ok.
|
By Nand - Tuesday, April 16, 2024
|
Never used the 'Publishing Option' before. Looks promising. I'll give it a try. And thanks for masking out the sensitive info. Till now, when generating a report - let's call it "X" - I did the following: - Generate a report and name it "X-NEW"
- If all looks OK, rename the old "X" report into "X-OLD"
- and rename the "X-NEW" into "X"
(actually, one of the oldest tricks in the IT book) Unfortunately, last time I tried this, weird things happened (banner missing, menu inactive, previous theme used!). So I still need to look into this and the 'Publishing Option' will probably help.
|
|