|
POST
|
After running through this issue with Esri support we ended up having to unregister the existing relational and tile cache data stores, upgrade from 10.5.1 to 10.6.1, and then configure the new data store. We were never able to successfully re-register the tile cache data store, but it no longer was a dependency of our system. The following were the documented support steps. RECAP Running the configuration wizard in Firefox, user showed me where the error message occurs during the prerequisite check. Attempted to run the configuredatastore.sh to see if the error message is the same. Different error message "Attempt to configure the data store failed…Extended error message. The specified GIS Server site already has a managed data stored." Navigated to Server Manager and noted that there is registered Data Store that is not validating successfully. Ran the describedatastore.sh tool and received error stating that it is not initialized. Ran netstat -aon | grep 2443 and that port was listening, but running netstat -aon | grep 9876 and that port was not listening. User showed me that the Firewall is turned off completely. Informed user that we could temporarily unregister the Data Store and reconfigure the Data Store. Unregistered the Data Store and attempted to run the configuredatastore.sh. This was successful. Successfully configured the Tile Cache Data Store, but it does not show up in the Server Manager. Trying to unregister or register from the browser gives an extended error message. User informed that he will restore to a snapshot and attempt to run this again to see if he can get the Tile Cache to store. Will update me on the progress. Noted that in the syntax, only one "-" was referenced instead of two "--" for the stores option. RECAP #2 User rolled the Data Store back to 10.5.1. Unregistered both the relational and Tile Cache Data Store and began the upgrade process. Successfully registered through the configuredatastore.sh in the terminal, but only the relational works again. The Tile Cache returns the same error message. Ran netstat -aon | grep 29080 29081 and those ports were not listening. Verified that firewall is turned off and that there is no third-party anti-virus software. Mentioned that port 5968 relates to the couchdb folder relates specifically to the Tile Cache. User mentioned that they may not need the Tile Cache as they upgraded from 10.1-10.5.1 and there may be some clutter leftover. Temporarily disabling it and starting their services appears to have no affect; everything is still working just fine.
... View more
06-04-2019
03:04 PM
|
0
|
0
|
4404
|
|
POST
|
We are using an ArcGIS Online application to collect data. We are in Mountain Time (UTC -7) currently under daylight savings time (UTC -6). The date entered is 6/1/1903 12:00 AM; timestamp of -2101312800000 or 6/1/1903 6:00 AM UTC. Staff are using Edge and Firefox to enter and view data (image below of query result in Firefox). When viewed in Chrome (second image) the date is 5/31/1903 11:00 PM; still with a timestamp of -2101312800000 or 6/1/1903 6:00 AM UTC. The field in question was created on ArcGIS Online after the feature class was published and when combined with the UTC time is 6AM I do not believe the following post applies (Problem: ArcGIS Online pop-up windows and attribute tables display the date as a day earlier ). My assumption is AGOL in Chrome is not honoring daylight savings time and is subtracting 7 hours instead of 6. Oddly enough, the record edit dates are both returning the same datetime regardless of browser. Can someone out there with more insight into datetimes or AGOL provide any insight? The ironic thing is that we don't even care about the time, we just need date (but AGOL doesn't have just a date option) so staff are defaulting to 12AM during data entry, else we may never have noticed the inconsistency. Correction: ArcGIS Python API notes were removed from this post as it was not an error.
... View more
06-04-2019
01:31 PM
|
0
|
0
|
836
|
|
POST
|
Jake, Thanks much for the response. We have reviewed our system and meet all requirements. The only change from 10.5 to 10.6 are memory requirements. I assume you were asking us to verify requirements for SUSE Linux Enterprise Server 12 - Service Pack 2, and not suggesting we roll back to SLES12 SP2, as it was end of life March 31, 2018. With no subsequent security upgrades rolling back to SLES12 SP2 is not an option. The authorization wizard was run, and it is how we activated ArcGIS Server 10.6.1 with the new provisioning file. The patch notification tool was run, and while there are listed patches, I see nothing for Server or Portal that seems it would impact Data Store. If you are aware of specific patches that would impact the install please let us know what those would be. Does that address your suggestions? Adam
... View more
01-30-2019
12:46 PM
|
0
|
1
|
4404
|
|
POST
|
Attempting to upgrade ArcGIS Enterprise from 10.5.1 to 10.6.1 on Linux SLES 12 SP3. Upgrade has been successful for Portal/Web Adaptor and Server/Web Adaptor. When upgrading Data Store we received an exception (see attached) "com.esri.arcgis.datastore.common.DatastoreException: Invalid parameter (dsSettings)" for the Prerequisite Check. We rolled back to a pre-upgrade snapshot and removed all registered data stores before upgrading as a test. Same error. Has anyone seen this error and what it might indicate?
... View more
01-29-2019
07:47 PM
|
0
|
4
|
4871
|
|
POST
|
When I asked this question, I did not understand that user.esri_access is set up as a getter and a setter. To set you designate user.esri_access = True. The documentation provides guidance on this. It would save a step if enabling esri_access was included with user.update.
... View more
01-22-2019
09:45 AM
|
0
|
0
|
1266
|
|
POST
|
The api documentation suggest the esri_access function of the user class is a means of enabling/disabling esri access. In v 1.4.1 this is not functioning, perhaps because user.esri_access is defined twice. The first sets an attribute of the user which returns user_type. This appears to take priority over the second which is a function to set the user_type, as noted in the documentation. In addition user.update includes user_type=None in the function but does not include that parameter in the arguments. Can you clarify the future functionality for user.esri_access? And with that, is there a reason the ability to set user_type is not included as a parameter in user.update? Thanks.
... View more
05-30-2018
03:13 PM
|
0
|
1
|
1403
|
|
POST
|
From ESRI support: A HTTP dataset or an application when accessed through gallery, it enforces to pass the request over HTTPS. This behavior is found to be a case defect within the application and is logged as a bug. Following are the details of the bug: BUG ID: BUG-000109990 Synopsis: In Open data, the Gallery Guard enforces the applications or datasets to open over HTTPS even when the applications or datasets are over HTTP. Status: In Product Plan
... View more
05-22-2018
11:34 AM
|
0
|
0
|
805
|
|
POST
|
Trying to troubleshoot an http vs https problem on our Open Data page. We have shared a test site for troubleshooting. There is a page gallery for Hunting Applications with a web map application link to the Hunt Planner application hosted on our agency page. The problem is the link from the Open Data page redirects to an https url. On our Open Data site configuration the "Enforce HTTPS" option is set to "Off". If you search for the Hunt Planner item, the link works correctly. Our primary AGOL site has a security configuration of "Allow access to the organization through HTTPS only". Could this be impacting the Open Data site? What do we need to do to get these map application links to correctly point to an http address from Open Data?
... View more
05-11-2018
09:27 AM
|
0
|
1
|
1001
|
|
POST
|
Courtney, It was nice to meet you at the UC. As we discussed following up on any future issues I'm sending another orphan/duplicate record from OD. The Montana Lakes record is a document link so no specific url for the item on our OD site. It can be located via search on our current our legacy site: Search | Montana Fish, Wildlife & Parks Item id: 41ed181dc6124fa9a2955bcb127b4a9b; You will note the 'Lakes' search returns 7 records in the summary and the page json response, but there are only 6 listed. Testing on our new test OD site, shows this duplicate record in the list. There is only one item on our agol content list. If I unshare this item from our OpenData group, it will remove the valid record from our OD site after a short time but leave the orphan. Let me know if you need any additional information. Thanks again, Adam
... View more
08-18-2017
08:31 AM
|
0
|
0
|
3434
|
|
POST
|
All of our Open Data orphans have been resolved by ESRI support. All of our data visible on our OD site is through a single Open Data group on our AGOL site. Apparently the following steps removed the orphan layers: From the OD administration pages the OD Group was removed from the site. From AGOL the OD group was changed from Public to Private. These steps were then reversed. From AGOL the OD group was changed from Private to Public, and the group was added back to the OD site. Then on the OD site indexes were updated and the download cache reset.
... View more
02-20-2017
08:22 PM
|
1
|
0
|
3434
|
|
POST
|
Courtney Claessens , Just a heads up that our GIS manager has logged this issue as a ticket as of last week and we are communicating with ESRI support. The first group above "In Open Data group, but not on Open Data site" has been resolved. The second "On Open Data site, but not in Open Data group" has not and now includes an additional item.
... View more
02-13-2017
10:06 AM
|
1
|
0
|
3434
|
|
POST
|
Courtney, Our process is scripted so I can describe that it, but likely cannot point you to a specific point when this occurred. We (Bill DaigleLydiaBaileyBill Daigle) maintain feature classes in SDE. When edits occur the data manager will designate the layer be updated in all dependent locations, including AGOL as a hosted feature service. Very large items are loaded as document links that point back to our web server for download. The feature service upload process takes one of two paths, with all tasks being automated via api calls which mostly use github ArcREST api package functionality. The only exception is the full item upload via arcpy.UploadServiceDefinition. If the layer is new or has a schema change, the existing AGOL feature service is deleted and replaced. If the layer only has record level edits, the features on the existing AGOL hosted feature service are deleted and then new records inserted into that item. If errors occur in the second process, we revert back to the first full item replacement option. Items are shared with everyone and our OpenData group which contains all items to be displayed on our OpenData site. We are aware of issues with item replacement due to the object id being changed. However, this is lower priority since the feature service url does not change, and thus we haven't noted major negative impacts on map and apps pointing to those replaced feature service items. Following is a summary of our existing data issues related to inconsistencies between our OpenDataGroup and OpenDataSite. Count of items in each location; Items in our ODGroup that should be showing up in the ODSite; Items that are orphaned, not in our ODGroup nor on our AGOL site anymore, and should be removed from the ODSite. Our evaluations also picked up erroneous duplicate records over the last several days, but those appear to have been cleaned up or fixed as of this morning. In that case, a search for a specific record would show one result on screen, but list 2 results and show duplicates with the same item id when the returned json was evaluated. Thanks for your help, Adam ________________________ Open Data Site Items:133 Open Data Group Items:132 ________________________ In Open Data group, but not on Open Data site ____________ id: 991f5239cf814ec6b86628b9e490fddd name: AIS Watercraft Inspection Stations type: Feature Service url: https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FISH_AIS_INSPECTION_STATIONS/FeatureServer ____________ id: b938ee0d87a1480aa988109cb963e13b name: Montana Lakes type: Document Link url: http://gis.fwp.mt.gov/arcgis101/rest/directories/arcgisoutput/webResources/metadata/refrnc/lakes.htm ________________________ On Open Data site, but not in Open Data group ____________ ITEM ID NOT IN MTFWP ITEMS LIST id: 2b095b1f50074ad3803c7535804f50f9 name: Snowmobile Trails Program PDF Map Index type: ItemLayer url: https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FWPLND_WINTER_PDF_MAP_INDEX/FeatureServer/0 ____________ ITEM ID NOT IN MTFWP ITEMS LIST id: 3a7ccdc9db804845b126d5bcaaed32fe name: Winter Trails type: ItemLayer url: https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FWPLND_TRAILS_WINTER/FeatureServer/0 ____________ ITEM ID NOT IN MTFWP ITEMS LIST id: bbec615bc12446539758cee15a6868fe name: Montana Fish, Wildlife & Parks Warden Districts type: ItemLayer url: https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/ADMBND_RESPAREA_WARDEN/FeatureServer/0 ________________________
... View more
02-09-2017
08:21 AM
|
1
|
1
|
3434
|
|
POST
|
Courtney, I think we have the same problem on our site. We (bdaigle) are evaluating the discrepancy between the number of items in our agol open data group (n=130), the OD Site Manager summary (126) and data tab (136 datasets 132 items). It appears that this is a continuation of Kevin Dunlop issue of Phantom items in Open Data Beta . Is the current solution to still send you the list of these items for deletion? I assuming the bug is still being worked on by your engineering team?
... View more
02-02-2017
03:06 PM
|
1
|
5
|
3434
|
|
POST
|
Thanks for the information Kelly. We have been successful in updating content using the rest api without retaining an sd file... For now at least.
... View more
01-26-2017
09:43 AM
|
2
|
0
|
3162
|
|
POST
|
Kelly Gerrow it appears that your original answer may no longer be valid. The documentation About hosted layers—ArcGIS Online Help | ArcGIS indicates that "You cannot delete the service definition file until you delete the hosted feature layer." Can you revisit your answer to determine why this is? What functionality has been implemented that requires the sd file be maintained for the hosted feature layer? As of last weeks update to AGOL we cannot delete either shapefile or service definitions while the hosted feature layer exists. However, we can still send an api delete command to remove the service definition content item without error. We are now concerned that there will be lost functionality or errors that result from this deletion. Thanks - adamm Bill Daigle
... View more
12-23-2016
10:03 AM
|
1
|
6
|
17914
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 2 | 12-31-2025 01:10 PM | |
| 2 | 09-16-2025 09:23 AM | |
| 1 | 10-10-2025 12:10 PM | |
| 20 | 08-14-2025 04:17 PM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|