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 001270: Consolidating the data failed.

YimanSong

I got this error when I try to publish a tiled map service to ArcGIS Online through ArcMap. Does anyone know why?

Najděte více příspěvků označených jako

Accepted answers

All comments

JoanneParkinson

Hello Yiman,

The message you received indicates the data and any additional resource could not be packaged.

There is a help topic associated with the message you received:

'>http://resources.arcgis.com/en/help/main/10.1/index.html#//00vp0000002r001270

What type of data does the .mxd you are trying to publish contain?

Does the length of the path to your data, staging folder or server name exceed the operating system limit?

Thanks,

Joanne Parkinson
Esri Software Product Engineer

YimanSong

I was trying to use the data straight from our SDE. Is it a bad practice?

JoanneParkinson

It is okay to publish hosted services using data from an enterprise geodatabase. If paths lengths don�??t exceed operating system limits, the issue may be with the data.

StevenMoore1

Hi Yiman,

Have you created a portal connection to your organizational site using the ArcGIS Administrator?

You can check this by launching the ArcGIS Administrator, clicking Advanced, then Manage Portal Connections. Do you see a URL to your site in addition to 'http://www.arcgis.com' ?

If not, click 'Add', type the URL to your site, and then click 'Connect'. Also keep in mind that if you have SSL enabled on your site, the URL you add will need to use HTTPS instead of HTTP.

MatthewKelso

This error has been plaguing me in recent weeks when trying to upload data to ArcGIS Online through the Desktop 10.1 interface. It is clear that this is being used in ways other than described on the help file:

http://resources.arcgis.com/en/help/main/10.1/index.html#//00vp0000002r001270

I'm not sure if it is related to too many layers being uploaded at once, transparency or other settings or what, but there is something in the data that triggers this error that has nothing to do with the length of the path.

The work-around is to upload the data through the online interface, but of course, that is much more time-consuming.

WillSchulte

I've been getting the same error message when trying to publish a map service from an mxd onto ArcGIS Online. The mxd only contains a raster dataset from a GDB. I've tried shortening the path names, as is suggest in the help topic but I still can't get it to work. Any insight would be greatly appreciated.

Will

RobWaller

Got this error today as well, in my case is was low disk space on the machine that publishing from that caused the issue. Once freed up enough space it published.

JosephSegretto__GISP

I also received this error. It was very frustrating. I did some troubleshooting for a while trying to figure out what was going on. I decided to try switching to the Advanced license and the error disappeared. I was able to publish the tiled map service.

WillSchulte

I figured out I had the same problem as Rob. The drive where my staging folder was located had low disk space so it wouldn't work. I changed the location of the staging folder to a drive with more space and it worked.

You can do this in desktop by clicking Customize > ArcMap options > Sharing. There it lets you choose the location of the staging folder. I think it works best when the folder path is short so I just used F:/Temp and it published from then on.

KeG

I'm getting this error now too. I'm publishing a gp tool with a py script. My data is an empty gdb that i'm only using to get a schema into one of my gp tools.
I'm telling it not to move data. But it still busts with this error.

BenAller

I just got this error too. I published a map document as a service about 2 months ago without any major problems. This morning I attempted to republish the same map document with no changes except for editing capabilities. The error shows up, and I retry a couple times and get the same error msg. Then after read this thread, I went back and tried again to publish and it worked. The only thing I did differently was to preview the service first. Got me.....

TracyBusby

I was told that the service does not like versioned SDE. Best to export to personal or file geodb before publishing.:cool:

Can anyone help me with a viewshed analysis?

JasonLyon

this error came out of the blue yesterday, have tried changing the staging folder with no help, cleaned out more storage space - no solution.
Can not overwrite an existing service, nor can I publish new service.
Very frustrating.

GIS-Cambria

I'm having the same problems with this error. I'm trying to publish to ArcGIS Online, using 10.2. I've changed the staging folder, etc.

MikeMinamiP1

There are a few possible reasons why consolidation fails. These are the most common reasons we have seen.

Low disk space. Change your staging path.
License doesn�??t support copying data. For example, you try and consolidate (which is copying) data like a network or a terrain and you don�??t have the appropriate license level.

Thanks,

Mike

SorrenMills

Seen this happening several times and on several different systems for no apparent reason. Just lately, it has started occurring on a system that was previously working a week ago, so now I have a bunch of map services published that I can't overwrite nor create new services.

1. I have Advanced license level
2. I have over 50GB on both C and D drives - switching the staging folder to either makes no difference.
3. Tried renaming path names etc. but no luck.

Strangely, I have 3 MXDs that publish fine and 3 that refuse to. I can't see any differences to indicate why some work and some don't.

AlisonFletcher

Could I be getting this error if my dataset were too large?

DonPritt

Yeah me too, this sucks be time for a subscription account, I'm dead in the water....
Worked fine last time and now this feature service is completely gone, I have basically a blank web map now online, management will be impressed.
Hopefully next week something miraculous will occur and I'll be able to publish my services from ArcMAP.
I tried everything, file size didn't matter, although I had to do nothing before, map analysis was clean before upload attempt....maybe its a Friday the 13th thing.

sucks.pdf

DonPritt

Well.....it worked first thing this morning, was able to upload feature services directly from my MXD, it took a while but it cleared.
Don't know why it didn't Friday, I changed nothing except for the time and day, only thing I can assume on my end is maybe it had something to do with the network, my internet connection speed or AGOL web site was being flooded with requests around that time....whatever, I'm happy for now.

MuryadiOey

I had the same error when I tried to publish feature service using python, below here is my script that I modified from
http://gis.stackexchange.com/questions/61057/overwrite-existing-map-service-in-arcgis-server-10-1-through-arcpy
can someone give enlighten to me? if I comment out this part "Change service type from map service to feature service" it worked.

import arcpy
import xml.dom.minidom as DOM

#define local variables
# wrkspc        mxd document directory
# mxdName       mxd document name
# con           ArcGIS Server Catalog path
# service       service name (include service direcotry)
# summary       service summary
# tags          services tags

wrkspc = 'C:/test/'
mxdName = 'sample.mxd'
con = 'GIS Servers/arcgis on localhost_6080 (admin)'
service = 'MyMapService'
summary = 'Population Density by County'
tags = 'county, counties, population, density, census'

mapDoc = arcpy.mapping.MapDocument(wrkspc + mxdName)
sddraft = wrkspc + service + '.sddraft'
sd = wrkspc + service + '.sd'

# create service definition draft
analysis = arcpy.mapping.CreateMapSDDraft(mapDoc, sddraft, service, 'ARCGIS_SERVER',
                                          con, True, None, summary, tags)

# set service type to esriServiceDefinitionType_Replacement
newType = 'esriServiceDefinitionType_Replacement'
xml = sddraft
doc = DOM.parse(xml)
descriptions = doc.getElementsByTagName('Type')
for desc in descriptions:
    if desc.parentNode.tagName == 'SVCManifest':
        if desc.hasChildNodes():
            desc.firstChild.data = newType

tagsState = doc.getElementsByTagName('State')
for tagState in tagsState:
    if tagState.parentNode.tagName == 'SVCManifest':
        if tagState.hasChildNodes():
            tagState.firstChild.data = "esriSDState_Published"

### Change service type from map service to feature service
typeNames = doc.getElementsByTagName('TypeName')
for typeName in typeNames:
    if typeName.firstChild.data == "MapServer":
        print "FeatureServer"
        typeName.firstChild.data = "FeatureServer"

outXml = xml
f = open(outXml, 'w')
doc.writexml( f )
f.close()

# stage and upload the service if the sddraft analysis did not contain errors
if analysis['errors'] == {}:
    # Execute StageService
    arcpy.StageService_server(sddraft, sd)
    # Execute UploadServiceDefinition
    arcpy.UploadServiceDefinition_server(sd, con)
else:
    # if the sddraft analysis contained errors, display them
    print analysis['errors']

JuliaGalindo

Hi,

I got the same error, but in my case I was using a FGDB with a schematic dataset. Although, I was not using the schematic data, it seemed to be the problem. So I used a copy of the feature class I was interested of in another FGDB and there was no problem.

AzizaParveen1_0-1751044929737.png

AnthonyJonesRSK_0-1751045009091.png

AnthonyJonesRSK_1-1751045151585.png

PaulStephenson

I also received the error. After a bundle of troubleshooting I found in my case it was a feature class that participated in two relationship classes. One or both of them were tripping the error. When I used an exported copy of that data w/no relationships, it pushed through. The mxd was a Local Gov Basemap for 10.2 template for which I had plugged the data into based on the sample...

MattKelso

I got this error again, after several months of not seeing it. In this case, I was able to isolate the problem. I had a manually set quantitative distribution for one of my layers (i.e., not quantile or Jenks). This apparently also can trigger the "Consolidating the data failed" error.

More useful error messages would be...useful.

FrankRoberts

I was also wracking my brain, and figured out I had a dbf file attached to my mxd. Once I removed that the error went away.

Hope it helps someone!

IngaPlayle

I was also wracking my brain, and figured out I had a dbf file attached to my mxd. Once I removed that the error went away.

Hope it helps someone!

Thanks Frank! You helped me. I had the error, checked for dbfs and found I had some csvs in the mxd. Once I removed them the service published.

I appreciate the time you took to write your solution on the forum.

Cheers,
Inga

DonaldLund

If you are using any shapefiles that you named using hyphens it will bork the process and produce this error. If you are publishing from ArcMap, right click each layer, select properties, select the source tab, and check the shapefile name. If you lost your mind and decided hyphens were easier to type than underscores, like I did (hopefully it was temporary insanity), export the layer, rename it using underscores, add it to the map, and remove the original.

EricElder

We found the error to be related to a file (tif) that had a file attribute of AT. The problem was the T portion, which refers to "Temporary." To remove the temporary portion we ran a PowerShell script:

PS C:\> Get-childitem \Data -recurse | ForEach-Object -process {if (($_.attributes -band 0x100) -eq 0x100) {$_.attributes = ($_.attributes -band 0xFEFF)}}

This script removes the temporary from all files in the folder. Here is the link to the PowerShell solution:

Attrib - Edit file attributes | Windows CMD | SS64.com‌

jessemaps

I had the same error when attempting to publish from a shapefile data source that had # symbols in the attribute names. Just changing the field aliases didn't help - I had to move all the attributes to new fields without # symbols in the name and delete the old fields and then it worked.

RichardJansen

Just today i found out that the use of a 9.3 personal database gives the same error. Converting your database to the newest version in catalog solves the problem.

I hope this helps some of you.

BrianJBaldwin

I saved my MXD, closed it, reopened, and then it published...not sure what the issue is either.

GeorgeVernardos

Did you ever find out what caused it in your case? I am stuck on this for weeks now...

PeterFennell

Same situation here. Left the map open overnight, came in the next day to publish and error. Saved the map, closed it, immediately reopen and published without error. Had to be a network hiccup or something.

NayrahIslamovic

Thanks Frank for the tip... I had the same issue as Inga! And as soon as they were removed it uploaded!

mbeierle

I got this error as well and scrolled through this thread looking for a resolution. It seemed that I had renamed a feature classes attachments and relationship class and it was not happy with me. After blowing it away and re-enabling attachments, I was able to publish with no errors. Also, I was publishing as a hosted feature service on ArcGIS Portal, not ArcGIS Online.

LarryMasters

Thanks for the wisdom Frank. A colleague had built a map and wanted it published. I had no idea a dbf file was there until I read your post. Thanks-a-ton.

Anonymous User

Do you know how I could do this on ArcPro? Still new to navigating around in there. Thanks!

Headshot.jpg

AmberShows

That's what worked for me as well, thanks Will Schulte.

LauraGillespie1

Thank you for posting, or I would have never figured out my issue.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Přihlásit se
Registrovat

Rychlé odkazy

Všechny komunity
Nedávné příspěvky
Sledovaný obsah
Pomoc komunity

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