Latest Contributions by JYI

‎12-04-2019

Exactly the same error.

‎12-04-2019

I am trying to set DEBUG, however, I got stuck with "Save", i.e., cannot Save. the reason is that Is there a solution to fix this error? thanks.

‎01-15-2019

Final Solution: The reason why the collaboration failed is that inside a Portal VM, the other Portal url is not accessible. The two Portal urls have to be recognized inside Portal VMs. In our case, Portal and Web Adaptor are on the same VM.

‎12-22-2018

Thanks all for help. The final solution is: " . There are 2 causes of 502 Gateway errors SSL certificate on the server being proxied is not trusted Fix is to import the certificate into the trusted cert store – can be done using Internet explorer or PowerShell The request timeout in IIS needs to be adjusted In IIS Manager, right click on the site and go to Manage Web Site -> Advanced Settings. In there, under Connection Limits you should see Connection Time-out. "

‎12-18-2018

I just tried to deploy the wildcard certificate to the trusted certificate store on each machine, bind the certificate to the port 443 on the load balancer and two web adaptors, and then import the certificate through sslcertificates -> importExistingServerCertificate on each portal and server machines, still got the same issue: Federated server and Hosting Sever cannot be valid at the same time. The data store is always valid at this moment. Could you explain more on this "When I've seen the 502 error in Azure, it was because I hadn't mapped the internal DNS to the external URL correctly. "? I would like to know the solution to it. Thanks.

‎12-18-2018

I am trying to find the logs in ArcGIS server for Data store validation. Nothing there for data store validation. The version is 10.6.1. People are saying this is SSL certificate issue as the errors are more related to 502 Bad Gateway?

‎12-18-2018

Yes, I have checked each time if the Relational Data Store is valid in ArcGIS Server, before federating a server and adding the hosting server. Same thing happened to the Relational data store though, that it is not stable either. Not each time it shows valid.

‎12-18-2018

The error: 502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server. No, there are no errors with the machine names. I used the registered public server url to federate.

‎12-17-2018

We have followed arcgis-powershell-dsc/BaseDeployment-MultiMachine.json at master · Esri/arcgis-powershell-dsc · GitHub to deploy the high available system in Azure. The system consists of 2 Web Adaptors, 2 Portal for ArcGIS, 2 ArcGIS Server, one ArcGIS Data Store, and One ARR 3.0 load balancer. The system is up and running. The wild card SSL certificate is installed on the Load Balancer. The public url registered with the certificate works well. There is a problem with this federated server and hosting server though. Every time I can only make either Federated Server or Hosting server available, not both. I.e., once the server is federated successfully, I then choose this server as the Hosting Server and then Save, it will throw 502 Bad Gateway error and the Hosting Server cannot be added. To fix this, I go into Portal admin -> Federation -> Servers -> select the federated server -> Update the server role to be Hosting Server -> Update server, now the hosting server is good and the federated server becomes not valid anymore! If I remove the Hosting Server from Portal, i.e., change the Hosting Server to be No Hosting Server, then the Federated server becomes valid again. From the surface, the issue seems just that the Federated Server and the Hosting Server cannot be valid at the same time. Any ideas? Thanks!

‎11-02-2018

Hi, I am trying to collaborate two 10.6.1 Portals, one on Azure and one on AWS. The collaboration is initiated on the Azure Portal. AWS Portal can only Send Content to the Portal on Azure. On AWS Portal: On Azure Portal: The wild card certificates on the two Portal are the same. The error message: "A scheduled collaboration configuration synchronization job has failed for collaboration with name 'null'" is in both Portal Log. Can anybody explain what is wrong here?

‎09-21-2018

Hope you have solved your problem. If not, this is my solution as I cannot add our WMS layer either in the way you did. But I am able to add it from:

‎09-21-2018

Hi Jonathan, I am having exactly the same issue with Dean. We have setup Portal 10.6.1 on both Azure and AWS cloud. On our Azure Cloud, when I tried to add the WMS layer, I got "Service '' does not exist or is inaccessible" error. On our AWS Cloud, our WMS layer works fine inside the Server where Portal is located, as the WMS layer is only authorized to Portal's IP address. Now we want to use ESRI's Portal build in Proxy Restricting the portal's proxy capability—Portal for ArcGIS (10.6) | ArcGIS Enterprise to make WMS layer available to the users. So far it does not work, I cannot get the link as yours: https://portal.domain.com/portal/sharing/proxy?https://data.gov.au/geoserver/qld-state-electoral-boundaries-psma-administrative-boundaries/wms?SERVICE=WMS&REQUEST=GetCapabilities, i.e., there is no proxy added. My first question to you is: how did you configure to use Proxy in Portal? Second, you mentioned "hit the Get Layers button", where is the "Get Layers" button? Third, why in Azure, the WMS layer cannot be added? Thanks, JYI

‎09-06-2018

Solution: ...... for kmz in arcpy.ListFiles("*.km*"): print("CONVERTING: {0}".format(os.path.join(arcpy.env.workspace, kmz))) kmzFile = os.path.join(arcpy.env.workspace, kmz) arcpy.KMLToLayer_conversion(kmzFile, out_location)

‎09-06-2018

Yes, it is correct: CONVERTING: C:\Work\Google_MASHUP\AdministrativeBoundary\ParkTest\Dinosaur.kmz

‎09-06-2018

Hi, I am writing some standalone code following the link KML To Layer—Conversion toolbox | ArcGIS Desktop (KMLToLayer example 2 (stand-alone script)) to try to convert a list of .KMZ files to .lyrx files, using ArcGIS Pro license. The sample .kmz file I used is attached. It can be opened from Google Earth. My testing code is as simple as this: import arcpy import os # Set workspace (where all the KMZs are) arcpy.env.workspace = r"C:\Work\Google_MASHUP\AdministrativeBoundary\ParkTest" # Set local variables and location for the consolidated file geodatabase out_location = r"C:\Work\ArcGIS_Layers_From_KMZ" # Convert all KMZ and KML files found in the current workspace for kmz in arcpy.ListFiles("*.km*"): print("CONVERTING: {0}".format(os.path.join(arcpy.env.workspace, kmz))) arcpy.KMLToLayer_conversion(kmz, out_location) I got the error: arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid. ERROR 000732: Input KML File: Dataset Dinosaur.kmz does not exist or is not supported Failed to execute (KMLToLayer). The printed result is: CONVERTING: C:\Work\Google_MASHUP\AdministrativeBoundary\ParkTest\Dinosaur.kmz, which is correct. I am able to use the Geoprocessing tool KML to Layer directly from ArcGIS Pro window to convert the .KMZ successfully but not from the above code. Also, using the same code, with ArcGIS Server License, I am able to run it successfully. Could anybody give the suggestions on this error? Thanks JYI

Online Status	Offline
Date Last Visited	‎07-10-2023 04:04 PM

My Ideas

Latest Contributions by JYI

Re: Webgisdr: Export operation failed. Method argument cannot be null

Re: Webgisdr: Export operation failed. Method argument cannot be null

Re: A scheduled collaboration configuration synchronization job has failed for collaboration with name 'null',

Re: High availability Portal/Server in Azure with Federated and Hosting server issues

Re: High availability Portal/Server in Azure with Federated and Hosting server issues

Re: High availability Portal/Server in Azure with Federated and Hosting server issues

Re: High availability Portal/Server in Azure with Federated and Hosting server issues

Re: High availability Portal/Server in Azure with Federated and Hosting server issues

High availability Portal/Server in Azure with Federated and Hosting server issues

A scheduled collaboration configuration synchronization job has failed for collaboration with name 'null',

Re: Adding WMS in Portal and ArcGIS Pro

Re: Adding WMS in Portal and ArcGIS Pro

Re: Python standalone script using ArcGIS Pro license

Re: Python standalone script using ArcGIS Pro license

Python standalone script using ArcGIS Pro license

Dashboards in enterprise 10.9.1: "Too many active ...

Re: Azure App Gateway WAF ruleset

Re: Azure App Gateway WAF ruleset

Re: Signout portal from web app builder app

Re: High availability Portal/Server in Azure with ...