"Error linking to source"
Last week, out of the blue, I got the above error message when using the Opera browser.
Have worked with FamilySearch more than 10 years, never seen the error message before. Can manually enter the data, no problem.
Tried CROME, things worked fine, and CROME implemented local language.
Any suggestions on what can be wrong?
Answers
-
I see this error sometimes. It is not new. It is transient.
The web page you see is constructed behind the scenes on the FamilySearch servers. This error says some database failed to respond in time to complete the linking operation. When I see this error I refresh the page and try to make the attachment one more time. If I get the error a second time I go do something else for a while.
1 -
Since my post above, it has become worse.
"Internal Server Error" is seen more an more frequently.
When I started on the homepage this morning, it worked, but for the photos uploaded recently. They did not load. Then I got a message when starting a new Opera window, that I had no data entered - at the same time I could see my family Tree as usual when clicking on the front page link. Now my start screen is "internal server error"
Same screen when clicking "Family Tree", "Overview". The Tree is complitely normal, Tree/Person looks like this:
Tree/pedigree/landscape/ list all my recent people looked at. Search/find/Find is normal. Following and My Contributions completely normal with data.
0 -
YES!!!!
thx so much - few minutes after posting everything was magically fixed :)
0 -
I tried what was suggested - do something else for a while and come back, but it didn't work for me. I stopped for the day and picked up next day. Still getting Error linking to source.
0 -
@Smith-Rossman, your browser may have "helpfully" saved a file that was corrupted by a momentary internet glitch. The easiest way to test whether this is the case is to try the action in a different browser. If it works there, then clear your FS-related history (cache and cookies) in the original browser and try again.
0 -
It seems to be related to enabled ad blockers. Most of my issues disappeared when I told my browser to accept ads etc when I am using familysearch
0
