Latest Contributions by RandallWilliams

OK. I've seen cases where the keycodes file has expired line-items that can cause issues like this. Besides the line for Portal for ArcGIS, are there any other products or extensions that may have expired listed in the keycodes file? ... View more

If I recall correctly, there's an additional license needed from Erdas to run image services sourced from .ecw files. There's not a license restriction from the Desktop side, but there is from the GIS Server side. That said, the error you're showing is not the error I'd expect if this were a license issue. ... View more

Also, ArcGIS Enterprise isn't tied to the ArcGIS Desktop license manager. Do you have a perpetual or term license? It may be that the license has expired. Check down in \\program files (x86)\esri\license10.x\sysgen - there should be a 'keycodes' file. Open it with notepad and the expiration date should be noted. Was your portal working previously? ... View more

Logical cores, but memory is your primary limiting factor. Processor generally comes into play more with GP than with Mapping Services. Honestly, there's not a well defined answer here that's going to fit for every use case - it depends on: a. The resources available on the GIS Server machine - both memory and processor b. The type of services you're running (Map/Feature or GP or Image or...?) c. Virtual memory and desktop heap allocation etc The following documentation goes into depth: http://www.wiki.gis.com/wiki/index.php/Capacity_Planning_Tool http://www.wiki.gis.com/wiki/index.php/Server_Software_Performance ... View more

What's the virtual memory allocation on this machine? Is it Windows managed, or set to a specific value? ... View more

Hi, There's not really a good way to do this with the GIS Server. If other client applications are still configured to consume the service (even if the service doesn't exist), the GIS server will still receive those requests and generate an error. You COULD handle this with other technologies - for instance, you could configure a web application filter to prevent these queries from reaching your GIS Server, or you could configure a reverse proxy (or use IIS with ARR) with a specific directive for this specific deleted service to route requests elsewhere. Otherwise, you'd have to handle this at the web app side by removing references to the service in the client applications, which can be challenging when services are public and you don't have a good way of knowing or contacting whoever owns those client apps to ask that the invalid references be removed. ... View more

Esri employs frame-busting technology on forms where logins can be passed to prevent a security vulnerability called 'Phishing by frames'. There's not a user controlled method to update this configuration. ... View more

Scott is correct, this is expected (to an extent). Any client application that makes a request to a service that doesn't exist will cause this message to appear. This is logged as: 9503 Service ''{0}'' not found. Check if the service exists and is started. That said, there's an issue (BUG-000090837) requesting to change this logging level from 'Severe' to 'Warning'. Questions: a. Is this GIS Server public? If so, google might be crawling your site. b. You mention .mxds - is that the only way your users consume these services? It's likely that even without a 'use' connection that the desktop client will reach out. If you're curious, you can test will an intercepting proxy like Fiddler. ... View more

There's not a hard limit to Server per-se, but there can be a limit depending on the environment. Also, the number of services isn't really the question - the issue is the number of service instances that are spun up (default is Min 1 Max 2). That's why you can publish and start more services if you stop some of the existing ones. There's two ways to approach this situation. One is to alter your service design, the other is to alter the environment.  I'm not sure what your end goal is, but personally, in terms of organization, I'd create a map document, say, for 'birds'. In that map document, I'd create sublayers for different species of birds. Then in your application, you can reference the individual feature layers as you need them. You may already be doing something similar, and this will result in a lower number of service instances running on your machine. I'd then have services for 'birds', 'monkeys', 'snakes', or whatever. Outside of map design, I've seen two distinct environment issues come into play when publishing a large number of services to ArcGIS for Server.  First, I'd check your virtual memory settings - ensure it's set to 'Windows managed' Hamstrung virtual memory can affect the amount of physical memory Windows can allocate to processes. Sedcond, you may also want to check out this KB, it discusses the impact of the non-interactive desktop heap has on the number of services you can publish to a Windows machine.  Finally, building up your stack and leveraging Portal for ArcGIS along with the ArcGIS Data Store will allow you to publish potentially thousands of feature layers without the overhead that ArcObjects based map services bring. Hope that helps! ... View more

I typically refrain from running much as local system because that's a highly privileged account. Do you see any errors in your windows event logs? ... View more

Is this issue specific to the local service account (.\ArcGIS), or does it happen with other accounts?  Are there other services that run on this machine that use the .\ArcGIS account? I'd check to see if some GPO is getting enforced. To do that, while ArcGIS for Server is running, log onto this machine, open a CMD prompt as an admin, and run gpupdate /force. If that causes these logon failures, then it seems likely that this issue is compounded by some GPO. This is less an ArcGIS Server issue and more a Windows issue. The windows event logs should help to provide additional context. ... View more

Hmmm...personally, I wouldn't do this in PROD. If you have to, I'd download and host this API in house in your shop. Most current web servers set CORS headers by default. I'd set those headers in the web.config on the root of your web server. " A public demo of CORS Anywhere is available at https://cors-anywhere.herokuapp.com. This server is only provided so that you can easily and quickly try out CORS Anywhere. To ensure that the service stays available to everyone, the number of requests per period is limited, except for requests from some explicitly whitelisted origins. If you expect lots of traffic, please host your own instance of CORS Anywhere, and make sure that the CORS Anywhere server only whitelists your site to prevent others from using your instance of CORS Anywhere as an open proxy." ... View more

Backups I'd handle via SQL server, but there are some solid python scripts out there to help with the geodatabase maintenance tasks you mention. Check this one out for instance. ... View more