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; } } }

ERROR 001272: Analyzer errors were encountered (codes = 7).

AlanToms

Hello folks,

When trying to publish a map service am I get the followin error, ERROR 001272: Analyzer errors were encountered (codes = 7). I have been able to track the issue to the definition query. If a layer's defintion query has SHAPE.STLength() or SHAPE.STArea() in the query it will throw the error, but those are valid queries created using the Query Builder. I have been unable to find details about ERROR 001272. Any suggestions for a soltion?

Thakn you
Alan

Find more posts tagged with

Accepted answers

All comments

JenniferRoberts

Any chance does your mxd or this layer have a spatial view, I am having a similar problem and am wondering if you cannot publish a spatial view to ArcSever. My service which is getting this error is currently published in 10 and we are trying to now publish it in 10.1

BubbaHey

Try adding quotes on the text field values in the definition query.

AlanToms

It is not a spatial view.

Adding quotes does not work as the quotes are incorrect syntax and this isnt a text value; I tried it anyways and it threw a bad SQL message.

tms2000

Had the same error with a definition query on SHAPE.area > 15. Removed the query and the service published fine.

AlanToms

Had the same error with a definition query on SHAPE.area > 15. Removed the query and the service published fine.

Yes, but I need to have the definition query. I'll think I'll put a ticket in with Esri Support.

JenniferRoberts

Hello folks,

When trying to publish a map service am I get the followin error, ERROR 001272: Analyzer errors were encountered (codes = 7). I have been able to track the issue to the definition query. If a layer's defintion query has SHAPE.STLength() or SHAPE.STArea() in the query it will throw the error, but those are valid queries created using the Query Builder. I have been unable to find details about ERROR 001272. Any suggestions for a soltion?

Thakn you
Alan

We have the same problem (anyone trying to publish community mapping mxd's will!) I have heard from ESRI that the problem with a definition query on the shape.area/length that this is a bug. We are going to do some testing to see if we change the layer to a query layer if the same error will persist. Will let you know how we make out but it is something you might want to try. 🙂

AledJones

Yes, but I need to have the definition query. I'll think I'll put a ticket in with Esri Support.

Hi Alan,

Have ESRI support replied yet? I've taken one of our servers offline to perform the upgrade and now I can't carry on due to this issue.

Regards,

Aled

AlanToms

Hello,

ESRI is aware of the problem. Bug NIM082764: Analyzer error 00007: Layer's definition query is invalid is appearing when publishing unexpectedly when publishing enterprise data with a definition expression based on the geometry fields.

Alan

AledJones

Hello,

ESRI is aware of the problem. Bug NIM082764: Analyzer error 00007: Layer's definition query is invalid is appearing when publishing unexpectedly when publishing enterprise data with a definition expression based on the geometry fields.

Alan

Hi,

Thanks for your reply. I couldn't find any reference to 'NIM082764' but I did find this one 'NIM083369' - I suppose the only possible solution is to duplicate the area fields?

Aled

AledJones

Hi,

Thanks for your reply. I couldn't find any reference to 'NIM082764' but I did find this one 'NIM083369' - I suppose the only possible solution is to duplicate the area fields?

Aled

For anyone stuck on this problem, duplicating the area field worked for me and I've been able to publish the service.

KarlMagnusson

I'm having the same problem. Have anyone find esri's bug report for this problem?

/Karl M Växjö - Sweden

Anonymous User

This NIM - NIM083369 - Analyzer error 00007: Layer's definition query is invalid appears when publishing enterprise data with a definition expression based on the geometry fields such as ORASPATIAL.States.AREA fields.

has been addressed in ArcGIS 10.1 SP1.

http://downloads.esri.com/support/downloads/other_/189810.1_SP1_Announcement.pdf

ArcGIS 10.1 SP1 for Server is available from the Customer Care Portal - http://customers.esri.com. Please refer to the link below:
http://support.esri.com/en/downloads/patches-servicepacks/view/productid/189/metaid/1913

DuaneTreadon

Hi all,

My background is in using GIS for analytic processes and all on one machine. I now find myself in the exciting world of servers and enterprise database models. We have adopted the LGIM structure to populate with our data. Currently I am working on learning how to publish map services. I seem to do great on simple maps I've created as suggested by tutorials with no errors produced. However I am having trouble with the above mentioned error when I try and publish the General Purpose base map provided as part of the LGIM.

I am using ArcAdvance 10.1 and Advance Server 10.1. Both have SP1 installed but I still get the error. Is there something with the LGIM or base maps provided that I need to do before publishing out as a map service?

Sorry if this is a newbie question, just getting into learning this side of GIS.

Thanks for the assistance.

DT

nizarsalih

I am trying to publish Local Gov Community map and General Purpose Basemap in 10.1 SP1 but still having Error 001272: Analyzer errors were encountered (codes = 7,7,7,...7). What else could possibly cause this error beside queries based on geometry field, which according to the previous post got resolved in SP1. Did anyone successfully publish Community map after upgrading to SP1?
Thank you,
Nizar

DuaneTreadon

I am trying to publish Local Gov Community map and General Purpose Basemap in 10.1 SP1 but still having Error 001272: Analyzer errors were encountered (codes = 7,7,7,...7). What else could possibly cause this error beside queries based on geometry field, which according to the previous post got resolved in SP1. Did anyone successfully publish Community map after upgrading to SP1?
Thank you,
Nizar

We are still having problems with ours. It will publish only if we remove the definition queries that used SHAPE.STLength or SHAPE.STArea. The funny thing to me is that you can use these fields with no problems in label SQL processes.

Peter_von_Minden

I am experiencing the exact same issue when using the .AREA field in a definition query. It seems to be localised to my PC though. I have SP1 installed and so do my colleagues but when I try and publish it on my PC, I am the only one to get the error. I have re-installed ArcGIS 10.1 and the service pack but it still happens.

Anyone else found the same thing with other PC's being able to publish?

HusenKang

Anyone has the solution for this issue?

I got SP1 installed and getting this error when trying to publish a map service.
In the MXD, there are some layers using Shape.STLength() in the query definition.

DuaneTreadon

Anyone has the solution for this issue?

I got SP1 installed and getting this error when trying to publish a map service.
In the MXD, there are some layers using Shape.STLength() in the query definition.

We are still having the problem also. Even with SPs installed on both serer and desktop. Our GIS Systems Administrator seems to think it has to do with SQL Server and how it names things. Anyone else think of this angle?

DuaneTreadon

This NIM - NIM083369 - Analyzer error 00007: Layer's definition query is invalid appears when publishing enterprise data with a definition expression based on the geometry fields such as ORASPATIAL.States.AREA fields.

has been addressed in ArcGIS 10.1 SP1.

http://downloads.esri.com/support/downloads/other_/189810.1_SP1_Announcement.pdf

ArcGIS 10.1 SP1 for Server is available from the Customer Care Portal - http://customers.esri.com. Please refer to the link below:
http://support.esri.com/en/downloads/patches-servicepacks/view/productid/189/metaid/1913

Apparently it has not been fixed for everyone with release of SP1. Any additional help that can be provided?

Peter_von_Minden

After contacting ESRI, we were told to completely uninstall ArcGIS 10.1 from my PC and any associated elements. Then we were told to remove any residual registry hives left over and to delete any residual folders in C:/Program Files ... After doing all that, I reinstalled my ArcGIS components but still got the same error.

Whilst the above suggestion didn't work for me, it may be useful to some of you. This bug is very strange to me as I can successfully publish the same mxd on my colleagues PC who has the same components, operating system and service pack.

DuaneTreadon

After contacting ESRI, we were told to completely uninstall ArcGIS 10.1 from my PC and any associated elements. Then we were told to remove any residual registry hives left over and to delete any residual folders in C:/Program Files ... After doing all that, I reinstalled my ArcGIS components but still got the same error.

Whilst the above suggestion didn't work for me, it may be useful to some of you. This bug is very strange to me as I can successfully publish the same mxd on my colleagues PC who has the same components, operating system and service pack.

Wow that's a lot do to. Funny the definition query works with no issues in ArcMap. It only shows itself when the map is being published as a web service. Our GIS Systems Administrator believes it has to do with SQL Server and how it names things.

Peter_von_Minden

Wow that's a lot do to. Funny the definition query works with no issues in ArcMap. It only shows itself when the map is being published as a web service. Our GIS Systems Administrator believes it has to do with SQL Server and how it names things.

We use Oracle but if it was a DB issue, then it should be happening on all our PC's. If I hear any more from ESRI, I will pass on to you all.

HusenKang

It works for me if I publish it this way. In the Share as Service windows selects option 'Save a service definition file'.
Then, selecting the option 'No available connection'. Then choose the location where you want to save the definition file.
Use ArcCatalog to browse to the just created definition file and right click and select 'Publish as a Service'.

Hope this workaround also works for you guys.

DuaneTreadon

It works for me if I publish it this way. In the Share as Service windows selects option 'Save a service definition file'.
Then, selecting the option 'No available connection'. Then choose the location where you want to save the definition file.
Use ArcCatalog to browse to the just created definition file and right click and select 'Publish as a Service'.

Hope this workaround also works for you guys.

Sorry I missed this follow up post, was out for vacation during the holidays. This is a great tip. I just published a small sample map as a test and your method worked for me. No errors when I published from the definition file. I am going to try on one of the provided base maps next. Thanks for sharing.

DT

Peter_von_Minden

It works for me if I publish it this way. In the Share as Service windows selects option 'Save a service definition file'.
Then, selecting the option 'No available connection'. Then choose the location where you want to save the definition file.
Use ArcCatalog to browse to the just created definition file and right click and select 'Publish as a Service'.

Hope this workaround also works for you guys.

Just tried this and it works a treat. Thank you for the suggestion.

DuaneTreadon

.... I am going to try on one of the provided base maps next. Thanks for sharing.

DT

Having no issues with publishing the LGIM basemaps now using this tip. Again thanks!!! Great find on a work around.

JT

BrianNemec

I just tested this out on my Server 2012 running 10.1sp1 and I get that same code. I did try saving the service as an SD and then publishing that and this seemed to work. It looks like ESRI needs to address this issue again and let us know what the status of it is.

MichaelRobb

The SP1 Server side does not fix the issue.

Though the workaround discussed works, I do not like how the workaround works as selecting 'no connection' merely means the data is exported OUT of the SDE into a registered database created by the service and copied to ArcServer.
This means more datasets to maintain and not a good streamline of updating SDE datasets which would not pass to the service.

Is there not a fix for this at all ESRI?

ServicePublishingResult.png

MichaelRobb

This is properly addressed and no longer an issue with any shape.ST () in expressions in arc10.2!

MikeLouwrens

It works for me if I publish it this way. In the Share as Service windows selects option 'Save a service definition file'.
Then, selecting the option 'No available connection'. Then choose the location where you want to save the definition file.
Use ArcCatalog to browse to the just created definition file and right click and select 'Publish as a Service'.

Hope this workaround also works for you guys.

This solution worked for me also.

Cheers,
Mike.

RachelFrischeisen

Husen Kang wrote:

It works for me if I publish it this way. In the Share as Service windows selects option 'Save a service definition file'.
Then, selecting the option 'No available connection'. Then choose the location where you want to save the definition file.
Use ArcCatalog to browse to the just created definition file and right click and select 'Publish as a Service'.

Hope this workaround also works for you guys.

We were receiving the same error message (except ours said "codes = 3") when attempting to publish a service pulling data from a registered Data Store (we are at Server 10.2.2). Even though the ArcGIS Server account had full share/NTFS permissions on the data store directory, we could not publish from Desktop.

After we spent a good 3 hours with tech support (his only suggestion was allowing data to be copied to the server - thanks, but no thanks), this was the only feasible workaround we could find. Thank you for the suggestion and here's hoping that ESRI will do something to address the fact that Data Stores in Server 10.2 simply do not function like they should.

HusenKang

Glad I can help. I am still using 10.1 here. I was hoping the problem would have been fixed at 10.2.

I also find publishing directly to ArcGIS Server takes longer than publishing via SD file.

Not sure if others experience the same.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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