Arcgis Server 10.1 Ecp Crack
Stephany Tousley
Is it the Datastore or the ArcGIS Server that's doing the heavy lifting when serving up Hosted Feature Services to the Portal? I'm analysing the performance of our system, and looking at ways of spreading the load across our available machines. I read an article that said that the ArcGIS Server ArcSOC for a Hosted Feature Service is just a lightweight REST endpoint and the datastore does the hard work. But I'm not too sure about that.
It's a mix. If you consider a traditional map service, then (in dedicated instances), publishing a service will create an ArcSOC.exe and start consuming memory. If you start using it and max instances are higher than 1 then it may create more ArcSOC.exe's, and this starts to consume an increasing but linear amount of memory. The CPU loading is dependent on how often it's called. The memory usage relates to the fact that it needs to 'make an image' from the data. The internal workflow will be something like:
Clearly, this is a gross simplification. In a hosted feature service, the burn layers step is replaced by 'format data' (JSON/PBF). The manipulation of the text (data) is a much lighter weight computational operation. Importantly it doesn't need a SOC for every service instance. In effect a server that is only used for hosting services needs much less memory than a traditional ArcGIS Server.
In terms of which is doing most, then the Data Store will be doing the data heavy lift, with the Hosting Server doing the conversion to JSON/PBF. Obviously, if a little bit of data is requested then neither has a high workload, but as larger amounts of data re requested then both start to ramp up.
I think it would be fair to say that both are working in tandem. The data stores workload would be somewhat comparable to an Enterprise Geodatabase, but a specific hosting server will need less resources than a traditional ArcGIS Server. Many of my smaller clients run Enterprise Portal, Hosting Server, and Data Store (the Base Deployment) on a single machine, and then traditional server roles on individual machines as required.
The issue we are having is we have reinstalled the web adaptor for an Image server and provided a new web adaptor name. e.g. server1 > Imageserver. This works and is accessible when applying the webadaptor name to the end of the our enterprise URL.
The issues start when trying to add this newly applied web adapted server as a 'federated' server. The dialogue we receive back is 'Error - server is already federated'. We have tried unfederating this server via portal manager and also the server manager to no avail.
you should not unfederate your ArcGIS Server because when you federate to the same ArcGIS server again all the items in ArcGIS Server will be re-added with new itemid's and this causes havoc to permissions links etc.
Hi Henry. Thanks for the reply. I following the link towards the end of your comment and I was able to successfully unregister the federated server. So thankyou. I have now been able to add the server as federated again. I'm now having an issue where the hosting server won't validate the server managed database when validating. Any ideas as to why this may be?
Hi @ArranGIS, the datastore is probably still reverencing the old url all you do is re-register it.
Go to _url.co.za/webadaptor_name/manager/site.html then datastore and click on the x for relational and tile cache if present.
I opened the keycode files and noticed they were different. I had, at one time, arcgis server loaded on these virtual machines but because of some unknown problem causing it to not work anymore I had to uninstall and remove all traces of ArcGIS Server but must have forgotten to remove these keycode files. That's usually the case with ArcGIS Server software, it'll just spontaneously stop working. Anyway, I deleted the keycode files and re-activated using the same license file. Same error as before so I checked the files and noticed the codes in the new keycode files were still different. So I just removed the keycode file from the second machine and copied and pasted the keycode from the first machine so they would be exact.
I had this same issue and it was infuriating. I was trying to join a second machine to our existing site and I received this error message late at night as I was trying to do this during non-production hours (and this was after a couple of months of troubleshooting with Esri support on why I wasn't able to add a second machine to our site, un-related to the license issue though).
I was in a similar situation as you. I had a VM where I previously installed server and attempted to join it to our site. Part of the troubleshooting process (again, not for the license issue) was to un-install and re-install server. So that's what I did, but even though I used the same authorization file, it still wouldn't like the authorization file. I had to do a complete un-install and remove all evidence of any Esri files in the Program Files directory. Then finally do a fresh installation and it accepted the authorization file at that point.
Check and make sure that keycodes is not the one that is getting updated when applying the authorization number. If that is not the case then please reply to this and we can then delve deeper into this to see what may be going on.
For anyone that comes across this issue when joining a server to an existing ArcGIS Server site, one of the reasons the license error appears is because the time zones of the two machines do not match, so this may be something else to check on the two servers.
I am currently running three environments (development, acceptance, production) of ArcGIS Enterprise 10.6.1 on Windows 2012 servers (Portal and Server are federated) and I am experiencing an issue (only on the acceptance environment) where all of our web services within ArcGIS Server are shown with a status of "Stopping".
In the ArcGIS Server logs, two big error codes appear after each attempt to restart the ArcGIS Server windows service. The error codes are 6550 (failed to start the server machine) and 7365 (error while starting AppServer). I began my troubleshooting by restarting the ArcGIS Server windows service. After that didn't fix the issue, I rebooted the entire server (didn't fix the issue). After that, I went through and checked multiple things including verifying that the windows account running ArcGIS Server has the correct folder permissions set, verifying that I have a valid licenses to run ArcGIS Server, verifying that the acceptance environment is configured the same as the development and production environments, and verifying that the acceptance environment has the same ArcGIS Enterprise patches installed as the other environments.
I will note that this behavior occurred after some recent windows patches were installed on that server. When comparing the timestamp of the errors appearing in the ArcGIS Server logs to the timestamp of the installation of the windows patches on the acceptance server, they are very similar (same day). This leads me to believe that the recent windows patches had some affect on ArcGIS Server. The odd thing is that the same windows patches were installed on the development and production environments with no issues arising after installation. I contacted ESRI support and all they can tell me to do is to attempt to uninstall the windows patches to see if it corrects the issues or uninstall/reinstall ArcGIS Server in that environment. I would rather not have to uninstall/reinstall ArcGIS Server due to possible issues that might arise from our federation with Portal. This is the first time I have ever experienced this behavior in any version of ArcGIS Enterprise. Does anyone have any other suggestions for things I can try?
After working with ESRI tech support for several weeks, we finally found a solution. It appears that one of our custom geoprocessing services (geometric network trace) was causing the issue with all of the services showing as Stopping. We believe the service became corrupted some how. Below are the general steps I followed to fix the issue (if you need more details let me know):
That was one of the first workflows I tried and it did not work. I have tried it a few times on that server and nothing changes. I will also mention when I log into the ArcGIS Server Administrator and go to machines --> machineName --> status I see that the configured state is set to STOPPED and the real time state is set to STARTED. I went back to the machine page and clicked on the start operation. It ran for several minutes and nothing happened so I stopped it. I then went back to the machine page and clicked on the stop operation and then tried the start operation again. This time it ran and both the configured state and the real time state were set to STARTED. But when I went to ArcGIS Server Manager and tried to load the services page, it never loaded and none of the services were working (tried accessing web apps using those services). Not sure if this info matters, but I figured it wouldn't hurt to share.
05f2edc126