nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

bug? (ERROR 001170: The reduced study area polygon is too small for analysis.)

RoyceSimpson

I've got several mxd's that I'm publishing with all their layers off by default and get the below error. The services publish anyway but are stopped. I simply start them and they are good to go.

I would be great not to get this error though.

Executing (Publish Service Definition): PublishServiceDefinition ... # 
{"buildInitialCache":false}
Start Time: Fri Oct 26 14:42:39 2012
Validating publish options.
Connecting to the server.
Getting basic item metadata for service definition upload.
Getting server information (server folders, data stores, etc.).
Extracting manifiest from uploaded service definition.
Validating service definition.
Determining service's input folder name.
Attempt to find service's input folder.
Creating the service.
ERROR 001170: The reduced study area polygon is too small for analysis.
Failed to execute (UploadServiceDefinition).
Failed at Fri Oct 26 14:42:41 2012 (Elapsed Time: 3.00 seconds)

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

PF1

Executing (Publish Service Definition): PublishServiceDefinition ... # 
{"buildInitialCache":false}
Start Time: Fri Oct 26 14:42:39 2012
Validating publish options.
Connecting to the server.
Getting basic item metadata for service definition upload.
Getting server information (server folders, data stores, etc.).
Extracting manifiest from uploaded service definition.
Validating service definition.
Determining service's input folder name.
Attempt to find service's input folder.
Creating the service.
ERROR 001170: The reduced study area polygon is too small for analysis.
Failed to execute (UploadServiceDefinition).
Failed at Fri Oct 26 14:42:41 2012 (Elapsed Time: 3.00 seconds)

We ran into this same issue today. Real small mapping service. Its got about 20 GIS features (20 rows all are point geometry type) that are stored in a FDGB on a fileshare. Data is registered with the server (not copying). This is a distributed GIS Site with 2 load balanced web-adaptors, and 4 GIS servers (2 clusters with 2 servers each). Administration is disabled at the web-adaptors and we are publishing from one of the servers in the GIS site. restarting (stopping/starting) the Publishing Tools GP service did not fix it.

I've got 3 other mapping services that are all about the same size and they all worked just fine.

Anyone else with this issue??

BrettElliot

I'm also getting the same error.

We have a 4 machine site (web adaptor, 2 gis servers and a staging server). I'm guessing this is a 10.1 bug that has to do with multiple machine clusters... there seems to be a few of them with this version of ArcServer.

Deleting the service and republishing the service seems to be a work-around.

If anyone from ESRI could chime it, it would be appreciated!

MattRohlf1

I'm getting the same error with many of my services on 10.2.

We're also running a multiple machine cluster -- two GIS servers with no Web Adaptor installed yet. I've noticed that the problem persists even if I shut down one of the servers, though.

DeirdreRaftery

Did anyone get a fix for this? Currently having the same problem with ArcGIS Server 10.2.

Multi-Machine deployment with 2 AGS machines and no Web Adapter.

Thanks

AntonioSergio

Hi,

I had the same problem today in a multiple machine 10.2 cluster environment...two GIS Servers and one web adaptor,

my workaround for that situation was to save the MXD with a smaller extent instead of the Full Extent and then publish the MXD ,

Regards,

António Sérgio

HusseinNasser

We ran into this bug recently, ArcGIS Server 10.1 SP1. Similar to most of the Server configurations in this thread, we do have two GIS Server machines.

We managed to get fix this by removing one of the machines from the Server Site Manager (Site->machines->hit the X button next to one of the machines). Then we simply run the publishing again, after it was succeeded, we joined the machine back to the site.

A workaround to get you up and running until Esri fix it or provide the cause of the problem.

JohnGardner

I experienced the same error.

Resolved by changing the scale from 15mil to 24k.

DavidMuthami1

Experienced the same error today-16th Aug. 2014

Resolved by changing data frame coordinate system from a local coordinate system (LO25) to web mercator auxilliary sphere.

JamesMonty1

Thought I would add my two cents in case anyone from ESRI looks in on this post.

Ran into this issue for the first time after publishing many other services successfully using 10.2.1

Like others, the error comes up when publishing to our production site with multiple servers. However, our development cluster also has 2 machines, and I can publish to that with no problem. Another difference is that we are publishing image services rather than map services from an MXD. Services are already in Web Mercator, so that isn't the issue.

As others have experienced, the service does eventually start up and run as expected, but some explanation of the error message would be nice. Has anyone who has submitted a ticket ever heard anything definitive?

Jim

SarahNoakes1

I've had this today too. I'm running desktop 10.2.2 publishing to server 10.3, but I've been doing that all week with no issues. It would be nice to get a more meaningful error message...

Deleting the original map service and republishing worked for me.

Sarah Noakes

Cornwall Council

JeremiahGlascock1

Sarah,

I am having the same issue as you.... I'm trying to publish from desktop 10.2.1 to server 10.3 but its not even creating the service. I still get the error. It takes roughly 30 minutes just to get the error. ArcGIS Server logs do not say anything... no warnings or severe errors and we only have one machine so i am apprehensive to delete it out as mentioned above. I have created new MXDs with the scale set at 10k and that did not help either. It would be great to know if there is a solution. I think I'll log a ticket with ESRI Support.

SarahNoakes1

Hi Jeremiah,

I have a call open with ESRI UK and they are discussing the issue with ESRI Inc. I'll report back when I have a resolution.

For me the error is intermittent - I can republish a map service several times and then every now and then I get the error. We have two servers in our cluster, and the configuration store is on a third separate file server. The issue seems to have something to do with ArcGIS Server not being able to get a lock on the files in the config store when it tries to delete and rename them.

Yesterday I tried removing one of the servers, and temporarily moved the config store locally to the remaining server. The issue still recurred intermittently.

Sarah Noakes

Cornwall Council

I am in the process of building our Enterprise GIS Server site, and have been doing a lot of testing of various environments and software versions since months(!). This is one of the errors we come across frequently. I have strong evidence that this is a problem caused by network issues. If you have other information please share, but I would bet that nobody subscribed to this thread has had this error with a single-machine site where config-store and server-directories are stored locally on the machine that runs ArcGIS Server - unless of course you were working with tiny extents or something that would make the "reduced study area that is too small for analysis" message an accurate and true description of the problem. If you did, please share that information too, (because then I'll have to revise my hypothesis.) Thank you!

deleted-user-ugCMpXci8bn5

I am having this same problem when I run a Python script to create map services on ArcGIS for Server 10.2. I can manually publish a service from the same mxd on the same server. This error is causing my script to end prematurely. Has anyone found a solution? Is anyone from ESRI reading this? Thanks,

I have seen this using 10.3 as well.

deleted-user-ugCMpXci8bn5

I should also mention that the services created before the error is thrown appear to be on and working, but the Python script fails on the error and subsequent services are not created. Also, all of my layers are turned off by default.

BrunoMendes

I've had this issue and both config-store and server-directories are on a shared folder.

I did'nt give much attention to the problem because it starts and works as expected.

We are now using version 10.3.

ErnestoCarreras3

I am experiencing the same issue with a multi-site GIS server configuration with no Web Adaptor. The only difference is that I am publishing a Geolocator service.

001170 : The reduced study area polygon is too small for analysis.

@Esri

AlexanderBykov

Same problem.

Use 10.3 multi-site ArcGIS.

Anonymous User

We've been running into the same issue. Multi-machine site, Python script for publishing services moving from dev to test to production, ArcGIS Desktop 10.2.2 and ArcGIS Server 10.3 with Web Adaptor.

deleted-user-ugCMpXci8bn5

I changes some parameters in my Python script, and now I can run it in 64-bit. These seems to have eliminated my particular problem; I am no longer getting this error.

ErnestoCarreras3

My issue should be fixed with http://support.esri.com/en/downloads/patches-servicepacks/view/productid/160/metaid/2186

AndrewBrown

For those of you having issues with multi machine sites on remote shares. If they are storage area networks with SMB , you might be experiencing OpportunisticLocking as described in this ESRI support article.

My problems were solved by dropping a machine out of each site, then I could publish.

I was running dual , 2-machine environments at 10.2.1 on Windows 2012 and I received the reduced study errors, as well as packaging succeeded but publishing failed.

40391 - Packaging succeeded, but publishing failed. ERROR 001369: Failed to create the service

dcm888gis

Same error yesterday as well:

ERROR 001170: The reduced study area polygon is too small for analysis. Failed to execute (UploadServiceDefinition).

Using python script to publish services. ArcGIS Server 10.3.

The service actually published and started without any problems despite this error message.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.