Technical Problem with England census.
Non LDS Familysearch users have always had access to England & Wales census Transcripts, but not original sheets. The other censuses still allow this.
Recently the 1871 England census has been unavailable from the Android App.
The option to access the census does not exist and if you click on a Task that links to the census you get this message.
I suspect there is a fault. I have tried doing what it says and clearing the cache. It makes no difference. It needs checking by your technical department but reporting to them just gets a reply to post it here. which is very frustrating.
Answers
-
I just checked the censuses and the Search option works and you can see transcripts. It just seems to not work when you click a Task linked to the 1871 census. This is from a few minutes ago. Also, certain censuses, 1871 and 1881 seem to be missing when searching a record from Sources/ Familysearch / Collections.
This on the Android App, Non LDS familysearch membership.
0 -
On recheck the Search option now finds the 1871 census and you can view transcripts from the App.
The problem seems Android App specific. Clicking a Task linking to the 1871 census returns message as above.
If you search from Sources / + / Familysearch / Collections it does not give options to search the England and Wales 1871 and 1881 censuses. They are not listed.
0 -
@kendoughty - Thank you for the update.
0 -
non-LDS users have in fact had (and should still have) access to original images of UK censuses at Family History Centers and Affiliate Libraries. But they have never had access from their home computers.
0 -
That is not the answer. Only the transcripts can be seen by non LDS users. I am quite aware of that.
The problem is accessing the 1871 and possibly the 1881 census from the Android App when clicking Tasks attached to Persons and via the Sources Search option.
This needs checking by the Mobile Devices Support team.
Searching via Collections from Sources on the App does not show these censuses as an option.
Clicking a Task linked to the 1871 census gives you this error report.
0 -
Please see further comments at https://community.familysearch.org/en/discussion/comment/424812#Comment_424812. As you will see, I have acknowledged the fact that your main issue is when trying to access these records via the App. Sorry that I am unable to offer any direct advice on this issue, but it could relate to the current "status" (availabilIty) of the records themselves (either through a computer or an App).
0 -
@kendoughty I have spent some time trying to replicate the issue you are seeing in the mobile app. I was able to find an ancestor with a hint for the 1861 & 1871 England censuses and they show up as expected on my Android phone. I included a screenshot. Can you tell me what version of the FamilySearch app you have? Also, which Android operating system do you have? I'm feeling like this issue might be specific to your phone. Have you tried to replicate on someone else's phone? I want to help you get to the bottom of this!
0 -
@Sam Sulser, what type of FS account were you using when trying to replicate Ken's problem? Try it with a public (non-LDS) account. I predict with near certainty that it will fail.
0 -
LOL @Julia Szent-Györgyi you are so right! I was so excited to find an ancestor that had these records as hints, I didn't change my account!! Ok, so I logged into my public account that has no attachment to me as a member. It was interesting to say the least. In the example ancestor I gave above, I could still see the 1861 census as a hint and it comes up to view like it should. However, the 1871 census no longer showed as a hint. Then I pulled up one of that ancestor's children. He was born after 1871 but has hints for 1881 & 1891. Both hints open as expected. I didn't get the error that @kendoughty is getting but it is odd that the 1871 hint no longer showed up on my public account. I found another ancestor with a hint to the 1871 census and again it did not show up as a hint on my public account on mobile. In researching this oddity, I found that there is a known issue with the 1871 census and it's viewability on public accounts. The engineers are working on this. I think this is what is wrong but I'm still not certain what the error messages are about. I never got any of those. The 1871 census just did not show up as a hint.
0 -
@Sam Sulser sam sulser This is what I get if I try to search via Historical Records, Collections for the 1871 England and Wales census.
No option to enter any details.
When I try to search from Sources for the person whose error image I sent previously, I don't even get an option for an 1871 census entry now.
I use public version. Android App on Samsung phone. Android 11, fully updated.
0 -
Attempted duplicating on public account Family Tree 4.4.3 (Android app - not same Android system version) and do not see the same result. I see the options for inputting search parameters (default: first/last name, place, year and/or More Options).
If you view app Help> About - which version of the app are you using ( I think it automatically updates - so expect you are on 4.4.3)?
What happens if you sign out (bottom of app menu) and sign back in (any difference)?
Perhaps you have some content filter blocking the Search (perhaps vpn or company phone)? What connection are you using (i am on wifi - no content filter running)?
0 -
Android 4.4 updated January 2022. No VPN. Private phone.
Signed out, cleared cache. Still the same on the 1871 census. Other censuses are fine. See the 1861 screen attached.
What about the ongoing,
known 1871 census problem that was given as the reason for this problem?
0 -
What type of connection? If on home wifi - do you have the same problem trying to access that 1871 census on desktop/laptop? It could be something is blocking/filtering content on the network (i was unable to duplicate - in Utah, USA)?
England and Wales Census 1871 for LB6D-4VD is not showing as attached when I view sources. Recent changes do not show that the source was removed. I do see the Jan 30 merge with 9VDT-GNY (maybe relevant?).
0 -
Additional. To confirm that the 1871 census does not even come up if you search Collections from Sources.
Both of these have 1871 census records attached that were connected when they were working. They do not even get the option to view it now.
0 -
Interesting. I am able to find 1871 census collection listed when Search Historical Records on Family Tree app.
But you are right - I do not find it in Sources of the person you referenced - LB6D-4VD. And I don't see that change in the Recent Changes - change log.
Because of your screenshots - I am suspecting you are connecting from a different country from myself (USA). Perhaps the country you are connecting from has different viewability of the 1871 census??
On person - MSRC-XD3 - I am able to see 1871 census attached as a source - but when selecting to view - I get:
"Something Went Wrong
Unfortunately, something went wrong and we are unable to display the record. Try refreshing the page, or come back later."
When viewing the 1871 collection I see that it was last updated this past Feb 18, 2022:
so yes, perhaps the recent changes have contributed to this issue. As far as what the recent changes were ... I don't know (FamilySearch Community member but not FamilySearch representative). But I think the licensing (contract) for 1871 census recently changed - so these issues could be related.
As far as how to workaround this issue:
I recommend you try searching England, Wales & Scotland 1871 Census at:
0 -
This needs to dealt with by a LDS representative? I have reported this for many weeks and have had irrelevant replies. I was told to raise it here, where I had more irrelevant replies and comments from people trying to be helpful. It has been corroborated by other users and has been mentioned by others on Facebook groups. I sent lots of emails, most with screenshots.
The 1871 census does not come up on a search of Familysearch from Sources and does not come up on Tasks on the Android App.
I was told that this was due to a known fault on the UK 1871 census, but it was not known when it would be rectified.
I am in England. Whether it is specific to the country I don't know, and only a technical person from the LDS can check this.
I have just checked on a Samsung Android tablet. Exactly the same symptoms.
No boxes to enter details from Historical Records/ Collections. No 1871 census come up on Sources, Familysearch, Collections. No Tasks show records from the 1871 census.
I can understand why it is still not working as the response to my reports has been frustrating at best, infuriating at worst, and I imagine anyone else who has tried to get something done probably just gave up.
0 -
You are correct - to get this specific issue investigated, confirmed or resolved further - would require a FamilySearch representative to follow through.
However, as a Community member I have no resources beyond troubleshooting - that I can resort to in attempting to narrowing this issue. Unfortunately, I could not duplicate the issue (of not being able to search 1871 census - I see the search available just fine - on both Android and Windows) with a public account - so it does appear to at least be narrowed to your connection to a different FamilySearch server or possibly relating to your connection. Currently when I check the attached 1871 census for person MSRC-XD3 - I do not get the above error either. Sorry I cannot duplicate that from USA. You indicate all your connections are having the same behavior - but this does not narrow the issue further. If others in your neighborhood but with a different network connection have the exact same issue - then it is probably the FamilySearch server being connected to (you may want to include references beyond facebook groups if this issue is corroborated). You might find some FamilySearch locality groups beneficial:
I have no idea whether there is some contractual restriction for accessing these records in UK - of which someone in these groups may be more informed (or a FamilySearch Representative here can check). I should mention all my responses are as a Community member not a FamilySearch representative - my attempts to duplicate/resolve/suggest a workaround for whatever the issue actually is - are strictly my own.
For others having problems but wishing to search or attach UK 1871 census to persons in the Tree - you can workaround this by using findmypast.com (subscription service). At least that appears to be a workaround ... Another possible workaround: try accessing these records at a nearby FamilySearch Family History Center or Affiliate Library.
0 -
Is there something wrong with you?
The problem I first reported you say you encountered! Why do you now say you didn't.
QUOTE from you -
"On person - MSRC-XD3 - I am able to see 1871 census attached as a source - but when selecting to view - I get:
"Something Went Wrong
Unfortunately, something went wrong and we are unable to display the record. Try refreshing the page, or come back later."
This what I have been trying to report for weeks! Is there someone who can actually look into this?
You are trying to be helpful but have not read my initial post.
My blood pressure and stress levels are sky high!
0 -
? There probably is something wrong with me ... but what it is I can't seem to figure out ...
Currently when I check the attached 1871 census for person MSRC-XD3 - I do not get the above error either. I do however get a new notice that the images are available at FHC/Affiliate Library or through findmypast (as mentioned) or through courtesy The National Archives, London, England.
? I think we are talking past each other and obviously you don't consider my attempts helpful. I'm sorry you cannot see what my attempts at help are indicating (that the issue is not exactly the same with a public connection on Android FamilySearch Family Tree app from USA - I'm not sure what else I could try to duplicate). Yes I got an error message about a record connected to a person you referenced - but not currently ... again not sure what else I missed in your initial post(s). I wish you well in your search.
1 -
Apologies. I have been experiencing this problem, the one you found, for many weeks. I sent emails and got ridiculous suggestions. When I rereported they fobbed me off by referring me here. I have made 16000 actions on Familysearch in the past year and am a genealogist with over 30 years experience. I have founded a family history society, written books and articles and also created six Facebook family history groups with 7000+ members. I know what I am doing. In fact I wrote a tutorial for the App, and promote its use.
The initial fault was
Sources search does not show the 1871 England census at all.
Clicking a task with an 1871 record gives the error you encountered.
The no access to 1871 census via Connections is fairly recent.
Why cannot a technical person look into this or give an update if there is an ongoing problem?
0 -
Please see my initial post.
0 -
I think all the FamilySearch technical people have been very busy over the past short while preparing for Rootstech. There is little FamilySearch employee representation here in Community and even less/non-existent technical employees.
Further - you are correct - there is not a great way of getting issues directly to the FamilySearch technical team IF a FamilySearch representative here in Community does not instigate that internal communication. I'm sorry your issue is not getting the technical response it deserves. This is something brought up here in Community from time to time - but I haven't seen a post from FamilySearch addressing a solution.
As far as the attempts at duplication:
Sources search does not show the 1871 England census at all. I could not duplicate. I do see 1871 UK census search capacity from the Android app and within the website on a public account. Therefore this is related to the FamilySearch server you are connecting to OR related to your connection to the Internet (this would need to be narrowed down to determine which is the case).
Clicking a task with an 1871 record gives the error you encountered. I did not duplicate - no hint with 1871 census available to test
The no access to 1871 census via Connections is fairly recent. Although I did get an error initially when selecting 1871 census source from a person to whom it is attached - I currently do not receive the error. Instead I get the notice about accessing the images at FHC/AL or findmypast.com.
Conclusion: From all of this and Community discussion that the FamilySearch contract for UK 1871 census was expiring (if I recall toward the beginning of the year) - I suspect any issues that one has with said census to be related to these contractual requirements. Further - because the initial error has changed to a notice of limited access - I suspect whatever changed to be related to these contractual requirements.
0 -
0
-
On the contract- the contract that has governed access to the 1841-1901 UK censuses from 2012 expired in November. In December the record custodian (TNA) told me no new contract had been signed yet, but "general terms and conditions of use" allowed FamilySearch to show images " in their library reading rooms". It is entirely possible that a new contract has been signed since- I'd imagine both parties would prefer the certainty of having a contract tailored to the particular circumstances rather than relying on generic T&Cs.
1 -
I would be inclined to accept that explanation if all England censuses were affected. It is only the 1871 and I get exactly the same problem accessing from the website.
Support gives no support at all.
0 -
Also, I use public Familysearch so I see no original sheets, only transcripts, which are quote adequate for my needs.
Most of my access is to help other people and introduce them to Familysearch. They can check originals in libraries etc. if they want to.
0 -
I've noticed, looking at the home page for each census collection, some subtle differences:
1851, 1881: The images and index are provided by FindMyPast.com
1841, 1861: This data has been provided by Findmypast.com.
1871: This data has been provided through a cooperative project with findmypast.com.
1891, 1901, 1911: [no mention of FMP]
A notable notable point from my email from TNA:
"The National Archives has no rights in any indexes or transcriptions created by Family Search. That information is their IP and they are free to do as they wish with it."
What I think may have happened is that since December FindMyPast have signed a deal with FS. It seems the terms of the deal vary slightly between the 1851/1881, 1841/1861 and 1871 censuses- probably due to who did/paid for the original digitizing and indexing of each census. FMP obviously wants to make life difficult for FS users (at least the non-LDS ones, since LDS users get a free automatic subscription with them), so that they give up and subscribe with them. FS or whoever legally owns the Index/Transcript data is free to set whatever rules it likes for accessing it, no matter how unusual they are. That could include blocking access to the 1871 census indexes but allowing access to the others.
1 -
In that case, why was I told on another thread, by a person who seemed to be a LDS rep, that he had spoken with their technical people and there was an ongoing fault with the 1871 census that they were working on, timescale unknown?
These problems started when they messed around with the App Search interface.
This now also has no option to search via a Spouse or parent name. They should have left it alone!
0 -
If you read my previous post you will see that I have made over 16000 "transactions" on Familysearch in the past year. That is why I notice these problems. I am not just a casual user. I try to promote use of Familysearch and the Apps via my family history society and six Facebook groups. Too many people criticise it. I check enquiries against Familysearch and give IDS of ancestors to people for them to check. As I do this I extend trees, add people, correct errors, merge, add photos and documents all in an effort to persuade people that Familysearch can provide excellent information and contacts, and there is no need to use paysites for basic English, and even worldwide research. If they want originals or fuller details I always suggest Findmypast as the best option.
0
