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

Did anyone ever figure out the unlucky 7 error 001272? We upgraded to 10.5.1 after years of being software constrained. The MXD is heavily riddled with definition queries. I hope definition queries were not the cause.

JacobMaggard

I have just encountered this issue when re-publishing a service that has been in use for over a year.

The detective work / differences:

I added some new bathymetry layers to this large group layer.

I published (overwrite) yesterday with all the data coming from a known / registered database source (RO user, SDE). As we know, a 2GB raster shouldn't be housed in SDE, but I do this when I have one piece of a 91 FC dataset that is a raster. I digress. The publishing worked, but I thought the bathy was a tad slow -- and I wanted to relieve some workload from my SQL Server over time.

So, today, I re-pathed the bathy layers to the RW user (which isn't registered, on purpose) to get ArcGIS Server to copy the files local (as they don't change). I have some modulus queries on the contours (e.g. 100 ft in one layer and 500 ft in another). These are in SQL Server SDE snytax (obviously).

My guess is that when copying local to the ArcGIS Server (FGDB), the def query conversion isn't being made or isn't being made correctly.

I know how to workaround from here, but I hope this helps someone.

-Jake

www.setld.com

Sean, Thank you for the suggestion. Unfortunately, this is as close to the root as I can get, I suppose I could try shortening the table names, but if that is my problem this avenue is doomed before I start, as this isn't the production version.

Avinash, Thank you. However, I don't think that is my problem, the query is straight out of the ArcMap Definition Query Builder. That said, thanks for sharing as its good to know that, if I ever get that type of error though that the services is that particular.

SeanDingman

For us, this was a path length limitation that caused all of the problems. In my case, when I wrote the draft service to a directory closer to the root, the errors disappeared.

Anonymous User

Hello,

Previously we have also faced similar type of issue but in different category after publishing of service map services is not visible in in arc map its due to != keyword used in mxd to we replaced the query according to ArcMap supported query and its got resolved.

Try to correct query

I have ArcMap 10.2.0.3348. I can't update beyond that due to a secondary software requirement.

This definition query issue appears to still be a problem. Here is my simple definition based upon the joined table column.

BlinkHistory.dbo.Blink_History_7Day.Blink_Count >= 6

ERROR 001272 7 7 7

I can see the data I'm querying perfectly in ArcMap. Any ideas?

Anonymous User

I'm also experiencing this issue on ArcGIS 10.3.1. On Oracle 12c.

MladenSimic2

I have the same issue with 10.2.2.

The problem was because I had fc and standalone table joined using the option "Join data based on a predefined relationship class." Joining data using the option "Join attributes from a table" solved the problem.

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.

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.

CassandraGray

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.

Beauty! Worked at a client site where we're severely hampered with permissions, etc. at 10.2.1. Thank you!!

BrianLocke

I had the same problem, changed by DB connection Props from DB authentication to OS authentication and worked for me.

MirceaUngurean

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 worked for me. It is really nice workaround for such a nasty problem.

AzizaParveen2

Using service definition file worked for me

My definition query didn't even use any geometry field, the query was based on a attribute field. I am using 10.2.

SeanDingman

I fought with this for a while over the weekend and installed the SP1, but it still didn't work. I believe that it has to do with the permissions to the cache folder (e.g., C:\Users\<user>\AppData\Local\Esri\Desktop10.1\Staging). If I change the path of this folder or run ArcGIS for Desktop as administrator, everything works fine.

MatthewFletcher

I have 10.1 installed on my desktop computer, ran into this error (which directed me to this forum 🙂 ). Logged onto our GIS Server running 10.2, the service published with no problems.

AlexanderBaker

I had the same issue with the SHAPE_Area field changing to SHAPE.STArea() field when moving feature class from a file geodatabase to SDE. When sourcing my data in the Local Government General Purpose Template to the newly copied feature classes in SDE with the SHAPE.STArea() field name, Drawing Errors occurred based on the Syntax being different.

This only occurred with feature classes that had definition queries using the SHAPE_Area fields.

If you change your definition expression to Ex. SHAPE.STArea() > 6000 instead of "SHAPE.STArea()" > 6000 / WITHOUT QUOTES
it works. No more drawing errors.

Hope this helps.

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.

MichaelRobb

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

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

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.

.... 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

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.

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

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.

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.

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.

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.

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?

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?

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.

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?