1950 US Census record shows 403 - Record access denied.
Answers
-
I have tossed my cookies in Safari, FireFox and Chrome.
I get this error on 1950 us census that are in Union County and Monmouth County in New Jersey, USA
I found a 1950 ccensus for a profile in Virginia and had no issues attaching it.
This has been an issue since the 1950 US census appeared in the research helps.
These two profiles are example for me.
Donald Justus Shugard - GQCC-WTC !403 - Record access denied.
Alice Alma Klett Shugard - MW4Y-1D6 !403 - Record access denied.
I have many more.....
Any help in resolving this will be greatly appreciated!
0 -
I don't know how you got it to work. The 1950 census was available for a short while, but has been broken for over a month now. The record hints appear, but most of the time, neither the indexed record nor the census image can be viewed. The month prior to the break, the indexed record could be viewed, but not the image. Now none of it can be viewed. Clicking on the record hint for any PID results in an error: usually 'not found,' or 'is not available at this time.' Sometimes clicking on the hint just redirects one to the PID details page. 1950 census sources that were previously attached, now cannot be viewed.
0 -
@Southern Muse - if you read my reply to Mark and his further reply, you will see how it worked for him. And that won't work for the rest of us until the Engineers fix it.
1 -
I see this error quite often. A record will attach correctly to one person in the record, but not to another, e.g. husband and wife in same record. There does not seem to be a workaround. Please don't tell me to clear my cache memory. Try attached the record hint in the following person:
0 -
I've seen this 403 problem a lot; just left a comment. I think I found why, if you look at the record, the index lacks an entry name for the person for which you get the 403 error. See the image below. The record attaches without problem to Jane E Stieg, but not to her husband Robert Stieg in the line above. There is no entry for Robert Stieg in the index pane below; it skips from Mary J Buss to Jane E Stieg. This indexing error might be the source of the 403 problem. If so, there are a LOT of such errors in the 1950 census indexes.
2 -
I have a family in the 1950 census where one family member is clearly listed on the census, but the transcription for that line is missing. The missing person comes up in the hints/index, then returns "403 - record access denied". I've seen this happen in more than one family LRNY-V9M is one, LLMT-6FX is another.
0 -
Please see the Announcement on this subject:
https://community.familysearch.org/en/discussion/133029/1950-us-census-hint-error#latest
2 -
The 403 errors are clearly caused by numerous indexing errors in the 1950 census records, in which the name of the person is omitted. These errors occur for family members below the entry person, where the last name is indicated by a dash. The hint shows for that person in Research Help, but cannot be attached. The workaround is to find a person, hopefully within the family, whose name is indexed correctly, read the census page image to get the Residence information for the family members below whose names are omitted from the index, then manually create Residence events for those person. Very tedious, but at least you can find the addresses while you're doing that as they are never indexed.
In particularly, I note that the Wisconsin 1950 census is a real mess, with many names omitted. This needs to be reviewed posthaste as it really shoots holes in what was, I'm sure, a big effort.
0 -
@Mike357 it appears several examples (above) have been provided, please provide any update to the issue, or let us know if the issue has been referred. I've seen it suggested that one not add the 1949 residence field, but with the 403 error described, one is not even able to access the screen that allows this option. Thanks for the interest.
0 -
@Ottley BQ Did you read the announcement?
https://community.familysearch.org/en/discussion/133029/1950-us-census-hint-error#latest
1 -
Per my earlier post, another workaround for attaching these '403' error census records is to find the family member in the record whose name IS indexed correctly. Usually this is the Head of Household. This record will attach OK, and the Source Linker will then offer to attach all the other family members lacking names in the index (where does it get them from?). However, the Residence event is not offered in the Source Linker, perhaps because of this bug. You will have to go to each of the family members you attached the record to and manually enter a Residence event.
0 -
It's working now. THANKS to our SILENT Engineering folks.
1 -
@Jon W. Thomas it's sporadic. It's not on every hint from the 1950 census. It is not yet fixed.
0 -
@Áine Ní Donnghaile -- which browser are you using? I was thinking when it worked for my grandpa in Wisconsin, that I may have been using Firefox at the time (I use Chrome 99% of the time); not sure.
0 -
It's not browser dependent. Some records are accessible while others are not. I always verify trying with several browsers before I report a problem.
1 -
I have over 100 of these messages "We're unable to show this record to you" on the 1950 census hint so it can't be attached to the individual ... and continue to get new ones every day. Very discomforting.
I.E.
G61xytc
gqtbzmw
Ltqhp9f
L839zdj
should I list the other 100 individuals?
and on and on to 100 people with new ones being discovered daily
0 -
I concur with @Áine Ní Donnghaile. It is not browser dependent. In one family I'm working on I have 100's of individuals in the 1950 census. I am seeing record hints for all of them but I can see and attach only about 1 in 10 records.
Just now I am seeing the FEEDBACK tab on the Family Tree web interface, so I am using that to report some instances of this behavior.
1 -
When I get this error message that FamilySearch is not able to show me the 1950 census record, and I try to attach the same record to the same profile in the mobile app, I get this message:
Unable to load
Unable to load data from the server. Please try again later.
0 -
This is the error message I am getting now on the web interface:
We're unable to show this record to you.
This record can only be displayed on certain accounts. FamilySearch must honor the agreements we have with our partners, record owners, and internal policies.
1 -
Sadly, I STILL don't have the Feedback button in most browsers so that's not an option for me.
0 -
I have an update from engineering. They think they have identified and fixed the issue. They are currently running the 1950 record collection through the system to see if it corrects the records that are still having issues. This could take a few days as it is a large collection. Crossing fingers they have figured it out!
Sam 😉
2 -
I don't understand this restricted access to the 1950 census! Occasionally it is available to view, but most often, there is a message saying that viewing is restricted to certain accounts. When it first became available on FamilySearch, I was able to view the index and images and attach them as sources. Later, I tried to review some of the listings I had attached, but they had become restricted! A few days ago I was able to view and attach the 1950 listing for my parents' household for the first time. Previously it had been restricted. FamilySearch has given us little or no explanation for these restrictions, and continues to advertise the 1950 census as if it were widely available and unrestricted. This is very frustrating.
0 -
It was not restricted on purpose, @Southern Muse. The restriction is in error, and the engineers have been working to resolve. The 1950 census is a large and complex record set, indexed using a new method. There are glitches - not unexpected given the circumstances.
2 -
Occasionally, I can get past this 403 - Record access denied problem by going to a different member in the family, but only occasionally. Otherwise the error is extremely, and very frustratingly, utterly random. The 1950 census will attach to several families without the error, the next family errors. To make certain I have attached all record hints in my descendancy research I've dismissed the erroring 1950 hint. At least it's still attached to them in the dismissed hints. Sure hope they discover a solution soon!!!!!!
0 -
Why does FamilySearch keep giving me the 1950 U.S. Census to attach to Records only to take me to a page telling me I am not authorized to see it for this individual and cannot therefore attach it!!! WHAT??????
I have about a 50-50 chance of getting a 1950 U.S. Census source that is usable!!! What is going on ... worst source I have ever seen.
In addition, IF I get the source to open there is another 50-50 chance it has been indexed correctly. Names with no 1950 (or 1949) locations. Names that appear in the Census that are not indexed. Relationships that are not correct. It appears there was way too much rush in pushing out the 1950 Census, and too little Quality Control.
0 -
Thanks for the info that it is a bug. As of 1200 EST, 23 Nov, it is not resolved. Shame on FS for not widely communicating the known bug. Hopefully FS someday will learn not to push something out before rigorous testing.
0 -
There is - and has been for quite some time - an Announcement on the topic. No one reads the announcements, it seems.
1 -
Reading announcements, found after signing in, clicking the help icon, clicking community, clicking announcements, then scrolling down to find a topic sometimes pages deep, is non-intuitive. From comments,it appears that there is a problem with indexing the census; if so, opening it back up to allow us to help fix it is one possible solution. However, telling users 30 days ago that engineers are aware of the problem and are working to determine and fix the source of the problem, but then providing no update, no estimated expected resolution date, etc., is not keeping the user community informed. Posting (with link) a statement on the home page that there are problems with the 1950 census would be a good first step.
2 -
I understood that there was an agreement (possibly before you became Community Manager) that these announcements would be placed at the top of the relevant section - Search, in this example. You have adopted this practice yourself, by placing the "Code of Conduct" announcement under each category and @N Tychonievich has also placed announcements in this manner.
Okay, it makes sense to place these items under the dedicated category (of Announcements), but as @MLV2 states, this is "non-intuitive", except to those who are very familiar with the lay-out / functions of Community. I agree some users would still raise the same issues again, but I feel clearly placed announcements would be a help in reducing duplication of posts on the same issue.
Alternatively, a better way of addressing this would be to have a separately headed "Known Issues" category, which could have read-only access for ordinary members - i.e., inputs would require administrator status. Once an issue was fully resolved, an administrator could then remove the post.
2
