Latest Contributions by JordanKing3

嘿,伙计们,我们试图发布MXD很大(60mb) and associated SD file (10mb) to ArcGIS Server and we keep getting a failed error after around 30 minutes or so. For context, we have a 10.6.1 AGS, which is federated. The service we are trying to publish has a lot of layers in it (over 100) and has an associated pre-built cache, which sits on a mapped network drive. We've tried to publish it through ArcGIS Desktop and also by uploading the SD file to the Server Manager and on both occasions we get this same log results after around 30 minutes of waiting for the publishing to complete: Token Renewal Failed (No credentials available). 10014 Core server call to create service failed (/admin/createService). 23850 Failed to create the service.: Token renewal failed (No credentials available). 23836 Token renewal failed (No credentials available). 100104 Error executing tool: Publish Service Definition – Failed to execute (Publish Service Definition). 20010 Apologies, I am not able to copy the full log. The numbers to the right are the associated error code. I'm guessing the token it grabs before it publishes may have a 30 minute expiry time and for some reason it is unable to get another one? Does anyone have any advice for publishing large services? or know if there are any other workaround to get around what we are experiencing? Cheers, Jordan ... View more

Hi All, We have a HA Portal site, with a multi-machine Federated ArcGIS Server. The Portal and ArcGIS Server both have two Web Adaptors and Load Balancers in front of the WAs. IWA has been configured in IIS according to this technical article. If we browse to our Portal through the load balancer, e.g. 'https://lb.domain.com/portal/home', IWA works with no issues and we are authenticated. However, if we browse directly to either one of the Portal Web Adaptors, e.g. 'https://wa1.domain.com/portal/home' we are always prompted for login credentials and even if we enter the correct credentials, we never seem to get authenticated. Likewise, when we browse to a single ArcGIS Server, through Web Adaptor, or even directly to the server itself through 'https://server1.domain.com:6443/arcgis/manager', we are always prompted for authentication. However, if we go through the ArcGIS Server load balancer, e.g. 'https://lb2.domain.com/arcgis/manager' IWA works as expected and we get straight in. We can't seem to pinpoint what might be preventing us from doing this. We're wondering if it potentially is the federated server URL and admin URL are both set to 'https://lb2.domain.com/arcgis', therefore if we go to anything other than that Portal doesn't accept it. Typically, these issues aren't really a problem because all of our users are going through the load balancers and as such, are authenticating with IWA as expected. Where we have ran into issues is when we upgrade our ArcGIS Servers and the steps are to: un-install the Web Adaptors, then upgrade Servers, then Continue Server Upgrade using 'https://server1.domain.com:6443/arcgis/manager. Because of this, we can never authenticate with Portal at this step and always receive an Unauthorized Access message at the Server Manager. As previously mentioned, once we re-install both Web Adaptors and access it through the LB it all works again, but we dont believe the Servers have properly upgraded because we never see the Continue Server Upgrade step. Any advice on this would be great, are there settings with how we have federated we should be changing etc? Cheers, Jordan ... View more