Latest Contributions by AdrianMarsden

We are moving our services from Desktop/Server to Pro/Portal.  Publishing in Pro 3.0 to Portal/Server 10.9 I have layers with queries like table2.field1 in ('01', '02', '04', '03') And table2.field2 IN ('01', '02', '03', '05', '04', '06', '07') And (table2.field3 IS NOT NULL Or table2.field3 IN ('AB', 'AC', 'AD', 'AD', 'RC')) Table2 is a Join on the primary key from table1 and is fully indexed. This works fine in Pro and Desktop and worked fine in Desktop published to Server 10.8 In the new world the layer draws slow and almost hits the 60 second time out when an ID task is sent via a web request. I have narrowed the issue to the OR part - and then ONLY when the SQL is looking at the related table.  When the SQL looks at just fields in the parent table or when there is no link, or when there is no 'OR'  everything works The data live in an Oracle 19C Enterprise database and the server is using matching 64bit client Any ideas?     ... View more

Hi We are new to publishing via Pro - we have avoided Pro as we can't really use it internally as we don't have GPUs on our virtual PCs/Server, but are in effect being forced to as we need to update, despite it being very painful to use. So - first attempt - got the service published - this is from Pro 2.9 and ArcGIS Server 10.8 - so not the newest, but I am sure this is a simple tick box I have missed. The layers all have a sub-selection of fields selected and many fields have aliases.  These appear OK in Pro But after publishing I get the full list - un-aliased. What have I missed? Cheers ACM ... View more

I've had this error on and off since moving from ArcIMS - cross site errors, but now I've hit something I simply cannot explain We have a server.  The server has 4 IIS sites, one of which is 'AGS' - hosting Portal and Server. The other 3 are all internal mapping sites. We use http across the board as I struggle to get certificates to include all the alternative names, plus it serves no real benefit in-house The 3 internal sites all have IP bindings set to specific IP addresses allocated to the server AGS is set to "All unallocated" There are 4 IP addresses allocated to this server, so it should only be picking up the one left over. As it is, it all works.  But I did hit issues when updating AGS, so I rolled back the change and investigated. As soon as I switch AGS to use the one remaining IP address - so the 'unallocated' one I get Access to XMLHttpRequest at 'http://<server name - not fully qualified>/server/rest/services/BaseMapZoomStack/MapServer?f=json&dpi=96&transparent=true&format=png8' from origin 'http://<out internal map name>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Somehow it would appear that the 'unallocated' setting in IIS isn't doing what it should.  In addition https://  <fully qualified server name>:443/portal/webadaptor 404s - with the physical path pointing to to folder structure of one of the mapping sites that has a allocated IP address - both AGS and the mapping website have https bound to 443. Removing the http binding from one of the other 3 sites (not all of them) makes things happy - as long as the AGS site is "all unassigned" Making https for AGS bind to the IP address it should be using gives another "resource cannot be found" message. Something is obviously wrong with the allocation, I have tried adding the server name into HOSTS along with the IP address it should be using but that didn't work I'm at a loss.  Until I resolve this I am relucatnat to upgrade AGS (currently on 10.6.1) as everytime I hit these issues.     ... View more