Hi, after the last update received in Survey123 connect (3.14.256), several Survey form's item details are not accessible in our organization. Please see the screenshot below.
Hi @UğurBaranSarıbaş
This issue has now been resolved and the Survey123 website has been updated to 3.14, with the noted issue above now resolved. Please test with you surveys again.
Regards,
Phil.
Thanks all. We are investigating this issue. We are going to roll back momentarily to 3.13 until we can test a fix with 3.14.
Your issue is likely separate from what this post is referring to. If the issue persists, I'd recommend starting a new thread.
Something to check quickly would be security settings:
I received this error message today after I updated a survey and published it. I can see the survey in the Survey123 app on my phone. I am able to use the survey on my phone and submit a record, but I cannot open it on the desktop, I just get the error message.
Same issue is popping up in 3.18.
BUG-00160874 offers the following workaround.
· Move the note or text question below the select_one question.
· Change the appearance of the begin group question to compact, field-list, or leave appearance as blank.
See Esri's Technical Support page:
https://support.esri.com/en-us/bug/when-a-survey-contains-a-group-with-the-tablelist-appea-bug-000160874
Sure do. BUG-000160874
Thank you for posting this. I encountered this same bug on 1 of my forms. I appreciate you taking the time to write it up, even if it's different from the original bug. Do you have the bug #?
Hello,
I had this pop up yesterday with two surveys. After some troubleshooting, I found a bug: A group with table-list appearance AND a non-select_one/select_multiple question (e.g., a note or text) as the first element inside that table-list causes the survey to give this error. The survey is still visible and accessible in Portal (and I would assume AGO).
This bug has been logged with Esri, and a fix will (presumably) be worked on and deployed sometime in the future.
EDIT: For clarification, this comment is in response to another more recent comment. The original reason this particular thread was started was for a different bug which has long since been resolved. However, the error message is generic, so there are many reasons why you could be seeing "The survey is not accessible or does not exist."
EDIT2: Logged as BUG-000160874
Still having this error as of August on Connect v3.18.123! Anyone have a workaround besides contacting support?
I don't recall what I did to work around this. I did not log a case with Esri Canada. I checked and I don't see a repeat of the error message on any of the surveys that I currently have access to.
Can you see them in Survey123 Connect?
We are seeing this behavior after publishing an update from 3.17. Anyone have any luck with esri support? @KurtSargent1 @FionaTaylor
I would suggest contacting Esri support.
The issue discussed here occurred when Esri updated from 3.13 > 3.14. The issue affected most users, and resulted in a rollback to 3.13 and subsequent update/fix to 3.14 to resolve the issue. This specific issue has been resolved for a while now.
There was a recent[ish] update from 3.16 > 3.17 which may have caused an issue for you.
While not helpful (I apologize), I personally have not experienced the issue described here, and all of my surveys are working properly. I would guess that if this was caused by 3.17, it isn't as far reaching as the previous issue.
Me as well, March 9, 2023
This thread suggests the issue has resolved, but I'm getting the same error on just one survey, now in March 2023. Can anyone suggest a solution?
I am facing also the same issue as per the belwo screenshot. Any updates in this regard?
Hi @Anonymous User ,
Thanks for your reply, everything works fine now.
Baran
Looks like I am back up and running. Reports are sending as normal again.
Hi @ShelbyZelonisRoberson,
Hi @Katie_Clark,
Is there any update? Our service and clients are being heavily affected. how did upgrade the system without a proper test?
Agreed -- this is a really, really, really big deal for us. We have a public-facing application that fails if a report can't be generated.
Thanks for the info, but we are unable to generate reports even after the rollback. This is a big operational problem for our agency and we really need to be able to give everyone a timeline for when it will be working again. Is there any update?
Same here. Reports still cannot be generated.
On a good note though, I can at least access the data tab in the web browser again for the affected surveys.
Still having issues with report generation across the board after the roll back.
Same issue here. Any timeline for a fix?
@JamesTedrick @IsmaelChivite Any updates on a fix here? or timeline on one?
I am having an issue with the update as well, on iPhone and iPads. I can load my surveys but the data is not pulling into inboxed forms.
You are getting it on the same group ID we are - an esri created group for ArcGIS Online vector basemaps. Makes me think that ESRI's servers hosting those basemaps are the source of the CORS problems, not our portals.
Seems like that may be the legacy vector basemaps as well, although I don't think it's due to anything we have configured.Update: The failing request also fails with cURL, which would not be affected by CORS.
I get that error in Chrome:
But I get CORS in Firefox:
Some more insight into our issue. As others have mentioned, the console shows a CORS error but our CORS settings are completely open. Also if you watch the network traffic while attempting to open a survey detail page, you can see many successful requests and a single failed request. CORS issues wouldn't allow some requests to succeed and others fail in this manner.I dug into the failed request. It's the `/search` endpoint searching for the ArcGIS Online Vector Basemap group, as its url exists via our Portal:
Wondering what other people are seeing in their network traffic.
Same here. Seems like this is on Esri's end. Just got off the phone with support. They are still trying to figure this out.Edits:
Just to toss this out there. Support had me try adding "Access-Control-Allow-Origin" to IIS. This actually made the problem a little worse so I removed it.
Also, as others have mentioned, this is almost at random. I have surveys I created back-to-back that are almost identical. Some work. Some don't. Republishing doesn't help either, so the issue is something tied to the surveys.
I published with Connect only. I used 3.13 until today when I updated to 3.14, but no change.
Seems like we need to wait on Esri to publish a fix.
Yikes! I'm glad I saw this post, because I was about to update....hopefully Esri can shed some light on this soon?
@JamesTedrick @IsmaelChivite Is Esri aware of this issue?
Same here.
Same issue being seen with our Teams. Across multiple portals. Problem is systemic (mostly) across survey's published prior to the Survey123 update yesterday. New survey's published today behave as expected. No changes w/respect to origins or CORS settings on our end.
Also received this issue today on multiple environments, both locally and on client environments. I have published from Connect Version 3.13.249. Tested surveys on version 10.8.1 as well as 10.9.1 of ArcGIS Enterprise.
Also tested with CORS enabled and disabled on IIS, as well as Portal Allowed Origins defined. Unfortunately none of the above has resolved the issue.
Seeing the same issue internally. Many surveys across multiple owners. Getting CORS/header errors in chrome: whenever trying to view a survey through survey123.arcgis.com
Same issue here. Republishing the surveys does not help. Console shows CORS errors, but there is nothing that has changed on our Portal end in the last 24 hours.
Also, when trying to access the item directly from Portal rather than the Survey123 site, we get a slightly different error, stating the .webform file is missing.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
