I am working with ArcGIS server 10.6, web Adaptor, and Portal.
I have been trying to solve this error message I get every time I try to publish a new service. The service is packaged but not published in my portal.
I checked the status of the publishing tools they are all started.
The log messages are quite vague.
I saw many threads about patches, and previous versions of ArcGIS server. I did apply the patch, restarted everything but still the same result. I tried to repair the server. Same results.
It's like the server and portal do not talk to each other anymore.
If someone has any idea, I am interested.
Solved! Go to Solution.
The "Bad syntax" error is typically happening due to information being provided in the connection. Make sure when you make the connection in ArcMap, use the either the ServiceURL or Admin URL via HTTPS (https://webadaptorname/arcgis or https://servername:6443/arcgis) and you will want to provide Portal login credentials. If these issues continue, I would highly suggest having a support case created!
Can you please tell us if you are able to publish a simple service definition file (.sd) via ArcGIS Server Manager page? Does it publish the service correctly?
Also is your Server federated with Portal? If it is, please check to see if they are still federated by validating via Portal admin end point and or Arcgis Server end point.
Thank you for taking the time to answer.
1/ The ArcGIS Manager page does not open. It turns for ever and nothing happens.
2/ I tried the https://webadaptor.domain.com/arcgis/portaladmin/federation/servers/validate?f=json and it returns an error "Token required".
When we installed Portal, webAdaptor, datastore and the server, we only got one certificate. There is no certificate on the portal machine. Is it a problem?
Could you please provide us with how your federation between Portal and ArcGIS Server was completed? Example: ServicesURL = https://webadaptorname/server, AdminURL = https://AGShostname:6443/arcgis. (going to portaladmin, federation, servers, click on the server listed)
Also if you go to ArcGIS Servers admin API (https://webadaptor/server/admin or https://AGShostname:6443/arcgis/admin) security, config, you should see the federation properties here. Does the PortalURL match the URL you use to access Portal?
If we can't get to ArcGIS Server Manager this can sometimes mean three things. One is we are using a URL that is not the ServicesURL and this will cause the please wait page until it eventually times out and takes you to a ArcGIS Server Manager login screen (which in a federated environment we should never see). Second is the URL that Portal is configured to use is not what the federation has been configured with. Third is there could be an issue with the Portal's PublicURL (web adaptor URL or webcontexturl, if set).
When federated and attempting to access ArcGIS Server Manager, it should re-direct to the Portal's PublicURL, If this URL is not accessible or has not been properly setup for the federation to use it, we will get a continuous loading page. This could all tie into why we have issues publishing.
Sorry for the delay in replying. I was trying to find solutions as well.
1/ We installed ArcGIS Server and a webadaptor on the same machine, then Portal on a second machine. Through the url portal https://machinename:7443/arcgis/ we created the portal account, then we installed a webadaptor:
We federated the server and the portal via https://servername:6443/arcgis/admin. The security config is http/https.
We added the server in the portal account service url is in http and admin url is in https. I was wondering if with a proxy, the webadaptor is necessary or not and could be slowing things down.
2/ If I go to the security config https://AGShostname:6443/arcgis/admin I only see http/https, authentication tier: GIS server +. I do not see any URL.
3/ If I go to the portal admin under federation the servername:6443 is seen as hosted server, but shouldn't it be federated server?
4/ Also in the portal admin if I try to validate, even unfederate the server it turns forever and nothing happens. Same if I try from the portal account. I cannot validate it although the URL is the good one, I cannot add another server (it's telling me federation is disabled) and I cannot delete it.
Here is where I am now.
No worries!! Thank you for getting back with more information though. What you are seeing within the ArcGIS Server admin security config page is strange. If we are properly federated with Portal, we should not be seeing GIS Server authentication, we should be seeing Portal as the authentication mode. We should also be seeing Portal/Server based URL's in the Portal properties.
It sounds like your Portal believes it is federated, but the ArcGIS Server does not believe it is federated. This would explain why you can't validate or unfederate the ArcGIS Server because it can't properly communicate with Portal. We would need to manually unfederate your Portal and ArcGIS Server. You can accomplish this by accessing https://portalmachine:7443/sharing/rest, login in the top right, click Portals, Self, scroll all the way to the bottom of the page, click on Servers, Click on the Server ID listed (should be only one option) and then Unregister Server, Unregister. This should remove the federation from Portals side. Since ArcGIS Server appears to already be unfederated, you shouldn't need to mess with it.
When you re-federated your Portal and ArcGIS Server, make sure your ServicesURL is the ArcGIS Server web adaptor (or reverse proxy URL) and your AdminURL is your https://arcgisserver:6443/arcgis (or web adaptor URL).
Please reach in and have a case created if you are unsure about the workflow. I will try to own it and work with you on this.
Ok I followed your workflow and re-federated my server and my portal. That part went fine. I made sure the ServicesURL and AdminURL were the good ones. It seems it also solved the connection issues that I had before. It was extremely slow to connect to the portal and open anything.
Now I got a message saying that "the servicesURL couldn't be validated with "http://servername.arcgis/rest/info". If ServicesURL is a proxy url verify it is accessible for all clients". I am not sure what this means exactly.
I also try to add a connection to the server to publish services and I got another error message: "proxy server got bad address from remote server".
I am glad that cleared up some of our issues. The new error we are seeing could be tied to the certificate being used by the web adaptor (443 binding in IIS) or some resolving issues with the ArcGIS Server Services URL with Portal. Did you end up federating using the Reverse Proxy URL or the web adaptor? Also you listed http://servername/arcgis, did we federated using HTTPS or HTTP?
1/ I federated with the web adaptor.
2/ The config is http/https.
3/ I checked IIS: on the ArcGIS Server machine there is no binding to port 443. There is a binding on the Portal machine.