Layers fail to load properly in Windows, but fine in iOS and Android

LindaKoch · ‎04-05-2017

I recently have discovered an issue with my deployment of Collector for Windows on HP tablets. My maps begin to load all background layers then a message comes on saying that 3 layers (the editable ones) are unavailable. Clicking the View button, displays the Layer Errors "the following layers are not accessible"]." when those layers are clicked, the message below the name says "the requested field was not found"

The maps work well in iOS and Android. Anyone have any ideas?

Anonymous User · ‎05-05-2017

I would set your ArcGIS Server logs to VERBOSE or DEBUG, then try to get an error while submitting edits while connected. If you think it is related to the internet, then I would test different connections and make sure your device is up to date

ChrisCzerwinski1 · ‎05-05-2017

Thanks for your time Dan. I'm going to test a bunch of stuff and try to pin point what fixes it. Hopefully Monday I'll have some answers to share. I suspect after a complete rebuild, things will be working as they were a week ago. This service layer has been through a pretty extensive beta test (trying to break it). Might need a fresh start.

We are still working on opening Port 7005 so that's also on my radar as a potential solution.

ChrisCzerwinski1 · ‎05-10-2017

So after a complete rebuild, things are working again as expected. I have a pretty simple database at this point, and plan to slowly add to it (range domains, subtypes, etc.), to see if any specific component breaks it again. Port 7005 is still seemingly closed, so we can partially rule that out. It would be nice to know what corrupted the application, but I'm happy to be able to take it offline with the windows tablet.

Thanks again for all your time on this.

RELAdmin · ‎05-25-2017

I have this exact issue - all layers load fine on web and android, but 1 layer will not load on my map in collector and windows. I cannot find any reason for this issue.

ChrisCzerwinski1 · ‎05-30-2017

I would try rebuilding the web service layer, and collector web map again. Not the ideal solution, but it worked for me.

AndrewSouthern · ‎06-06-2018

Same issue for me. Unfortunately rebuilding the feature service is not a viable option as it is being used in roughly 70 different web maps and dashboards.

Wondering if anyone who has experienced this issue remembers if the field they deleted or altered in some way was the first field in the table (besides ObjectID.) This is the case in my experience and I noticed while looking at the rest endpoint that the displayField is set to the field that was deleted, I'm guessing it's the first field in the table by default. I tried to "trick" Collector by adding the field back into the table with the same name, data type, etc. but to no avail. I also tried editing the JSON to change the displayField to another field, also to no avail.

Have already started a case with ESRI but since it looks like this problem with others wasn't resolved other than to rebuild the feature service I thought I would join the discussion and see if anyone else has had a similar experience.

Thanks.

KellyWright · ‎09-14-2018

I am experiencing this on our Surface Pro as well. We had not been using it for Collector because the camera is frankly terrible, but we are low on iPads so I thought I would give it a try. Our web map that feeds Collector works great on both iOS and Android, so I was surprised to see that 11 of our layers would not load on the Surface Pro.

These layers do have GNSS metadata fields as that is the entire point of this particular data collection (Lat/Long/Altitude/Horizontal Accuracy/Fix Time/Receiver ID). I am unwilling/unable to remove the metadata fields and re-publish.

As suggested above, I tried publishing a new Feature service just for the Surface Pro and creating a new web map . . . no go, same 11 layers are not accessible.

We host our data on our servers and use ArcGIS Server 10.3.

I have time constraints with this project that prohibit me from rebuilding the entire thing using Hosted Feature Layers on AGOL or calling Esri tech support for assistance (that according to this thread will not resolve the issue).

It's disappointing that this wasn't as plug'n'play as it is for iOS and Android. I'm curious to see what the end resolution is, but we will have to stop using the Surface Pro in the interim.

AndrewSouthern · ‎09-14-2018

Are your layers that are hosted http or https? I have run into problems when trying to use feature services hosted on our servers that are not https as that's what AGOL prefers (and what all hosted feature services are.) Since you are using server 10.3 maybe this is something to look at.

Also, do you happen to use many filters in the web maps? This is another issue entirely that I have run into with Collector for Windows. It seems like there's a limit to the amount of filter expressions a single layer can handle. However, when I have run into this issue I don't get the "Unable to access layer" error, the layer simply doesn't load.

I was at the UC earlier this summer and spoke with one of the Collector developers about the short comings I've found with the Windows version of the software compared to Android (I don't use iOS much.) He explained that support for the Windows version lags way behind that of Android and iOS, presumably because the demand for the other two platforms is so much greater. However, ESRI has heard enough complaints about the Windows short comings (and also the fact ESRI stopped developing Workforce for Windows completely) and that they will begin ramping up support. Doesn't do much for us now, I am bound to using Windows because the MDTs used by our Fire personnel are all Windows 10, but maybe there is hope for the future.

KellyWright · ‎01-07-2019

Hi Andrew, I am sorry it took me so long to reply but thank you for the information! You are correct, we were not using https at the time I encountered this issue. I have since upgraded our SSL (in part because of the upcoming TLS 1.2 requirements for AGOL) and updated all web maps using AGO Assistant to rewrite our service URLs with "https." I have not tried to use the SurfacePro since, but I will check again to see if this behavior now changes.

Thanks again!

Kelly Wright

StephanieRinguet · ‎02-21-2019

We are using Panasonic Toughpad that runs on Windows 10 and I experience same problem, one of my layer will not load. It works fine on Android and IOS, but on Windows Collector I get the error that my layer has invalid spatial reference, that the Wkid or Vertical Wkid is invalid. Other layers with exact same coordinate systems can be displayed fine. Hope that this issue is resolved as I only have access to Windows tablets!