Permission Denied when using source linker

LegacyUser

Nolan Bateman said: Just got this message
Permission Denied
We are sorry, but you are not authorized to view this page.
Feel free to use any activity from the menu above to continue your family history.
Thank you for using FamilySearch.org

Try attaching birth sources from record.
Hattie Johnson
30 March 1879 – Deceased • LHY9-R46 ​​

Attaching the other sources worked from record hints.

LegacyUser

Ben Strubl said: I checked with PID she provided and is legitimate complaint

LegacyUser

David Wynn said: Yeah, I ran into this the other day with a family in West Virginia. This is a definite bug in the system. If the records are not ready for attaching to profiles, then the records should not be found yet in any searches, and they *definitely* should not come up as record hints. If its something about my personal login (I'm not an LDS member), then again, these should be blocked to my view.

This is unprofessional to hint that a record should be attached, then indicate we're not authorized to view it.

LegacyUser

JT said: I'm LDS (and an FHC director) and I still get the error.

LegacyUser

gasmodels said: I think the issue is that the records in the hints do not exist. I was looking for them today and could not find them. They may have been available and for some reason have been removed. Clearly the hints were generated from somewhere but the records do not exist today.

LegacyUser

Jason Daniels said: You are correct, if the Record can't be viewed, it shouldn't be viewed as a hint. To figure out where and why this is happening, can you provide more information about the record being attached? Either the name of the record or even better, when you click on it, copy the URL and provide it?

LegacyUser

TNLL said: This was happening to me a lot a few weeks ago. I haven’t experienced it lately. It was always with marriage records. I don’t know if it was related to the people I was working on or a system glitch.

LegacyUser

Jeff Wiseman said: David,

Just a clarification if I may. The statement "to hint that a record should be attached" is really incorrect and implies assumptions that don't really exist in FamilySearch.

A "Hint" is NEVER created to imply "that a source should be attached". That interpretation creates a lot of mistakes when people see the hints on one of their ancestors and interpret it as a fact that all of those sources must be attached. If that were the case, why wouldn't the system have already done it?

The hint is only a possible help to research on a person.

A hint is only the identification of a piece of information (e.g., a source) that may be relevant to the person it was created for. The origin of the word is partly from the basic notion being that something that may be taken advantage of" (reference the New Oxford American Dictionary)

In fact, as sources are attached to a person PID in the FamilyTree, the system will frequently REMOVE other hints that it had previously created for that person as it becomes clear that they really DO NOT apply to that person.

It should never be assumed that hints provided on a given name are actually pertinent to that specific PID. If that were true, the system could automatically attach them itself. But it is NOT true and it requires a researcher's scrutiny to determine whether it applies or not.

LegacyUser

David Wynn said: Ok, I see your point. But it completely misses the main crux of my point, as well as the point of this entire thread.

Yes, I understand that all of the documents need to have human review to verify which profiles they should be attached to. (The presence of a person's name on a document, at least the historic documents that we deal with here, implies that there was a person to which we could assign a profile for attaching the record. Whether its the particular profile I'm reviewing is up for review, but it could / should be attached somewhere.)

The point of this discussion though was that there were hints on a particular profile, yet when we followed the link, we ended up with a warning that we're not allowed to view the record. According to gasmodels research, the problem was that the records weren't there.

So, back to what I was saying -- the system should not be posting hints unless we're allowed to review, and potentially attach the documents.

LegacyUser

Jeff Wiseman said: Yea, I agree completely. And please forgive my impulse to hijack your discussion :-)

I've worked in Requirements management most of my life and I tend to see the real meaning of things as they have been worded--not necessarily what the author actually intended.

LegacyUser

Tom Huber said: Is this still a problem. I just looked (Window 7 with Chrome) and while the original records are from www.wvculture.org, supposedly the records are viewable on that site.

They are indexed, and so they should be attachable with the source linker. Remember that the source linker does not attach original records, only the index that is supposed to contain information found in the original record.

I just checked the four hints associated with Hattie Mae Johnson LHY9-R46 and all of them looked like they would attach with the source linker. I did not do any of them because I am not related, but was curious about this particular issue.

LegacyUser

David Wynn said: I agree. I checked those last night, but life got in the way, and I wasn't able to post an update. As you note, Tom, I believe the documents for the original post are OK now. And, I have lost track of the individuals I was working with from West Viriginia. I'm guessing that the hints for these West Virginia birth records were made available for the records themselves were released, however that all works in the background.

I believe this issue fixed itself for this set of records.

LegacyUser

Nolan Bateman said: I just checked out the record hints for LHY9-R46 this evening. I see the format has changed in record hints. I used to be able to look at them and right click them up into a new tab for review. Can not do that anymore. Now you have to select them one at time and it opens up into a new window. At least it works. Windows 10 and Firefox I have.

Main point is the one I tried went all the way and I was able to attach it. I went ahead and did the rest. Looks like the problem of getting "Permission Denied" when trying to look at the record hint has been fixed. Last step before pressing Attach that is. At least for this record and its record hints.

LegacyUser

Jeff Wiseman said: That's great it's fixed!

Now if we can just get them to consistently maintain a "Not a Match" button on the source linker. As you move around that area, sometimes it's there and sometimes it's not. Once it disappears, the only way to get it back is to shut down the source linker and then re-enter it.

Either put it there and keep it there, or don't put it there at all. It's a nuisance going for the button that I occasionally use only to discover it has vanished :-)

LegacyUser

Nolan Bateman said: I thought it was fixed, but I found some more. Hit and miss. I did not see as many as I was before.

LegacyUser

Tom Huber said: If you can post the IDs for the persons impacted, I'm sure the FS engineers will investigate further. Firefox has been problematical lately, so this is important that they be made aware of the records that are impacted by this issue.

LegacyUser

Marilyn Johnson said: I have been having this same problem for a couple of weeks, going back every few days to attempt to attach the record. The person is my great great uncle, George Wyckoff, his id number is KWJH-4Y7​​ . The record I am trying to attach is a birth record. I am able to view it on the WV Culture Archives. The surname is misspelled in the record as often happens : Wysloff. I am using Google Chrome and it is fully updated.

LegacyUser

David Newton said: I get File Not Found when I try and use that PID. That suggests to me you are trying to attach a transcribed record source to a living individual. It is quite possible to do that, but I am not going to tell you how since it is something that is not supposed to occur.

Is that PID for a living person?

LegacyUser

Robert Wren said: Cousin Marilyn,

The record is already attached to KWJH-4Y7​​ (one of the only two links, I added a date to the title) and clicking on the wvculture link goes to the image. PERHAPS that's the reason for the 'permission denied' message???? If so, it does seem it could be more clearly explained.

(FWIW, George shows up as a distant cousin of mine.)
However, it does show the correct name of George W WYCKOFF - not the Wysloff name in the 'hint' - ??

LegacyUser

Tom Huber said: George Wyckoff is decidedly deceased. I had no problem calling up his profile (record) in the tree by using Find by ID. There is a hint that does not work as well as it should.

First, I have to "show all" to be able to open it with Review and Attach. Just clicking on the hint produces a blank window. Clicking on Review and Attach, I get the dreaded
"Permission Denied
We are sorry, but you are not authorized to view this page.
Feel free to use any activity from the menu above to continue your family history.
Thank you for using FamilySearch.org"

This is a continuation of the original issue expressed in this thread.

LegacyUser

Tom Huber said: Definite BUG -- related to the original issue. The engineers will need to check this out. I had problems trying to view the record -- Windows 7 and Chrome.

LegacyUser

Brian Jensen said: We believe that many of the Record Hinting Permission issues have been addressed today. Please let us know if you see additional instances of the problem.
Thanks for your support and patience.

LegacyUser

Jeff Wiseman said: The exact sample that Marilyn Johnson gave above is still producing the error page and showing a blank page when viewing the hint directly for one of the hints that remain on that PID (KWJH-4Y7​)

LegacyUser

Brian Jensen said: ok, I've duplicated the problem on the "West Virginia Births" hint. Let me check with the team on this occurrence.

LegacyUser

Sonia Hermanstorfer said: As of March 2020, this is still a problem. I had not experienced this until recently and most of the affected records seem to be those tied to the 1860 and 1870 U.S Census. I can access for some people, but permission is denied for others. There doesn't seem to be any rhyme or reason.

LegacyUser

Paul said: I just received the same "Permission denied" page when trying to view 1860 & 1870 census records from https://www.familysearch.org/ark:/619...

LegacyUser

Rhonda Kidd said: I am given this hint but get the message:
403 - Record access denied.

Amos Keiser

United States Census, 1870

Other:

1870, Springfield, Bucks, Pennsylvania, United States
Birth:

1826, Pennsylvania

Today's date: 3/13/2020

LegacyUser

Paul said: Through reading other posts I now see there are specific problems when trying to view 1860 & 1870 US census sources.

Haven't signed in to FamilySearch today, but see Brett's post at https://getsatisfaction.com/familysea... Thanks for highlighting this, Brett.

LegacyUser

Sonia Hermanstorfer said: Received this reply from Family Search this morning: "Thank you for reporting the issues with Permission Denied. We had experienced issues in which some images of the U.S. Federal Census records were not available on FamilySearch.org. We apologize for any inconvenience. We believe the images are now restored. Thank you for your patience. If you are still having a problem viewing images of US Census records, please reply to this email and give specific information about your search and also your operating system and browser."

Unfortunately, the issue with the 1860 and 70 census records persists. It has not been resolved.