POST
|
Hi Moelsaket I haven't had the opportunity to test this for your exact scenarios, but with the latest version of Map Viewer in ArcGIS Enterprise 10.9.1 (i.e. formerly Map Viewer Beta) you can specify Custom Parameters when adding a layer from a URL (see Add layers from a URL). When you do this, the parameter is appended to all requests to the specified resource. So theoretically, you could add gdbVersion as the parameter and the named version as the value and it should target that version for ArcGIS Server requests. You can add/update custom parameters for layers added by other means (e.g. browsing layers) by opening the layer properties. As I said, I haven't been able to test this for your scenarios, so hopefully this is a solution or at least a starting point.
... View more
03-06-2022
04:31 AM
|
0
|
1
|
3615
|
POST
|
Also, this didn't cause me any issues, but at one point I had a mismatch on permissions between the items within Portal and the survey when viewed on the Survey123 website. i.e. my Portal said that everything was public, but Survey123 said that the form wasn't shared. However, I could still anonymously access the form.
... View more
02-23-2022
08:53 PM
|
0
|
3
|
1185
|
POST
|
Unfortunately the logs aren't all that revealing. The 500 error is somewhat expanded upon: {"error":{"code":500,"extendedCode":-2147467259,"message":"Unable to complete operation.","details":["Error: Unsupported request name."]}} But I don't see anything wrong with the payload. I've got a local 10.9 deployment and I set up a basic form using a feature service with enterprise geodatabase data and I tried everything to break it but it still works anonymously. As a troubleshooting step, I'd suggest creating a really basic feature service with one free text field and a form using Survey123's "Feature Service" initial XLSForm design. If you can get a public form working at this conceptual level, then it is likely something in your form/service that can be changed. If not, then it might be a bug.
... View more
02-23-2022
08:45 PM
|
0
|
4
|
1186
|
POST
|
No need to apologise for going to bed! Developer tools in your browser are usually launched by either pressing F12 or Ctrl+Shift+i - this is what it looks like in Edge: So what you need to before opening the developer tools is open the survey and complete it right up to the point before submission, then open the developer tools, then click submit. The Network and Console tabs on the dev tools will capture the activity that happened at the time of submission and may give some insight as to what went wrong. You can save these logs by right clicking on any of the entries and choosing Save as... Given that it looks like you've got the setup right, I'd also suggest raising this with your local Esri tech support - they'll be better placed to diagnose, confirm if this is a bug or known issue etc.
... View more
02-23-2022
01:16 PM
|
0
|
6
|
1197
|
POST
|
Well that all looks pretty good... Going back to what happens on submission, could you please run the developer tools in your browser while submitting so that you can capture network and console entries? If you don't want to go through the trouble of sanitizing them to post here then you can PM them to me if you like.
... View more
02-22-2022
08:47 PM
|
0
|
8
|
1578
|
POST
|
Hi Heather Firstly, I'd strongly suggest that you get in touch with your local support provider, and backup your database. Preserve incremental backups if possible, and take a snapshot that doesn't compromise the ability to do point in time restoration. Regarding what the repair tool does, this is from old sde command line documentation, so it is likely to be reasonably consistent with what the geoprocessing tool does now. The repair rules for the delta tables are as follows: Records in the Adds table that reference nonexistent states are deleted. Records in the Deletes table that reference nonexistent states are deleted. When multiple versions of a record are present in the same state, all but the latest record is deleted. When the same feature in the Adds or Base table is deleted multiple times in the same state, all but the latest delete entry is removed. Hope the repair goes well and it solves your issue!
... View more
02-22-2022
08:31 PM
|
1
|
0
|
5256
|
POST
|
There's nothing showing under layers or tables - can you navigate to any of the layer IDs? i.e. add /0 or /1 etc. to the FeatureServer URL?
... View more
02-22-2022
03:46 PM
|
0
|
10
|
1584
|
POST
|
Thanks for the updates Kristin. The sharing all looks good there. What happens if you open the rest endpoint for the feature service in a private/incognito tab without signing in? Can you access it and see the editing operations like Apply Edits, Add Features etc.?
... View more
02-22-2022
02:32 PM
|
0
|
12
|
1590
|
POST
|
Hi Kristin That should work if you've shared the feature service and the survey to everyone. Something to check is whether the portal items for both the feature layer and the map image layer created from publishing the service are shared to everyone - with feature access being a capability of a map service, it is necessary to share both portal items. Hope this helps! Craig Edit: While I've seen issues with this in the past, I have verified that having different permissions on the map image layer and the feature layer shouldn't be an issue in this instance.
... View more
02-21-2022
06:30 PM
|
0
|
15
|
1612
|
POST
|
Hi Moelsaket I don't believe that is possible, but you can create a basic Experience Builder app and include the Branch Version Management widget which will allow users to switch versions. There's a useful video here which shows you how to configure the widget - Manage Your Branch Versions with ArcGIS Experience Builder Hope this is useful! Craig
... View more
02-21-2022
06:15 PM
|
1
|
4
|
3662
|
POST
|
Hey Heather You could try running the Diagnose Version Metadata and Diagnose Version Tables geoprocessing tools to see if there are any inconsistencies. There are corresponding repair tools in the Geodatabase Administration toolset if you do happen to find any issues, but make sure you take full backups before executing either of those tools. Craig
... View more
02-21-2022
05:50 PM
|
2
|
2
|
5278
|
POST
|
Hi Matthew I've seen similar behaviour to this on my local ArcGIS Enterprise deployment in earlier versions. I never quite nailed exactly what was happening, but I always suspected it was one of the following: Accessing portal before server/data store had started; or Changes to hostname after machine restart and/or enabling/disabling VPN If the machine that you're referring to isn't on some sort of availability schedule (i.e. Enterprise is always running) then you can probably rule out #1. On a server, #2 might be a problem if you have multiple DNS entries or network interface cards; there's some documentation for configuring Enterprise components for this scenario: Installing Portal for ArcGIS—Portal for ArcGIS | Documentation for ArcGIS Enterprise Configure ArcGIS Server in advanced scenarios—ArcGIS Server | Documentation for ArcGIS Enterprise Create a data store—ArcGIS Enterprise | Documentation for ArcGIS Enterprise Does the server have multiple DNS entries and/or NICs?
... View more
10-19-2021
04:24 PM
|
0
|
1
|
2563
|
POST
|
This might be easier for your local support to work through, but a couple of things... That is the server name. I just went to that address, and I get a windows server IIS splash screen. Do you get any HTTPS errors? Are you using Chrome? In Pro, Projects tab > Portals, I am signed into two portals, one is arcgis.com, and the other is to the blacked out address, with "/portal/" appended to the end. So just to confirm, when you use your ArcGIS Portal in a browser, you go to an address like https://portal.domain.com/portal - is this different to the blacked out address? e.g. it is something like https://servername01.domain.com/portal instead? If so, you should try deleting that portal from Pro and adding the other one.
... View more
03-21-2021
05:04 PM
|
0
|
4
|
6050
|
POST
|
Hey Anneka You should log this with your local support provider, then you'll get updates on resolution timeframes etc. Craig
... View more
03-21-2021
04:23 PM
|
1
|
0
|
3036
|
POST
|
For all of the ArcGIS Enterprise components, the data (content, logs, services, caches, databases etc.) is all written to directories outside of the installation path, and this will grow as your usage of ArcGIS Enterprise grows - there's no real cap on how large they could become. By default these directories are c:\arcgisportal, c:\arcgisserver, and c:\arcgisdatastore, but you can (and should) change them to another drive (or a network file share for HA, noting that some of these directories must still live on the local machine) as part of the installation. Your 100GB per machine on the D-drive more than covers this for a clean installation, but it's nearly impossible to tell you how quickly you'll use this up, other than to say that tile caches could eat away at the ArcGIS Server's disk space very quickly if you're using them. There are some log files which are written to the installation directories, so while they won't grow as rapidly as the data directories, it would be incorrect to say that they don't grow at all, just not significantly. The minimum requirements listed in the support documentation should more than cover this. You can install the ArcGIS Enterprise components to another drive if required - usually this done more out of organizational policy to segregate programs/data from the OS drive, but as stated above, the installation directories shouldn't grow that much. Definitely create the data directories on D-drive though, this is a good practice.
... View more
03-21-2021
04:20 PM
|
4
|
0
|
6933
|
Title | Kudos | Posted |
---|---|---|
1 | 02-22-2022 08:31 PM | |
2 | 02-21-2022 05:50 PM | |
1 | 02-21-2022 06:15 PM | |
1 | 03-08-2021 07:13 PM | |
1 | 03-21-2021 04:23 PM |
Online Status |
Offline
|
Date Last Visited |
Wednesday
|