But I got a way to avoid the error , that is keeping the fiddler running when publishing the service,then the service will be published succeded.nan zhang.
Hi all,
I got the same issue when publishing map service to AGS 10.2.2 , not to Portal or Online.
I found it come from the tool "Upload Service Definition". Tracking this, I found the .sd file was created but can't be copied to server. The file be deleted immediately after born.
Before I can publishing map service to AGS 10.2.2 successfully.
Thanks
I am having this same issue right now. I recently just upgraded to 10.2.1 and each time I try to publish a map service to ArcGIS online I get the error "Packaging succeeded, but publishing failed". However, when another person in my office publishes (who is still on 10.1) to arc gis online, they have no issues. Is this a bug with 10.2.1?
We had been experiencing the same issue recently when moving to 10.2.1. We found a fix for this issue. The path for your portal or ArcGIS Online account needs to be set within the ArcGIS Administrator.
Open the ArcGIS administrator, open the advanced configuration window. Then open Manage Portal Connections and add the address for your AGOL organization or your internal portal. Once the connection is added, select it and Connect. Click Ok through all of the dialog boxes. Now try publishing your services. This fixed the issue for us; hopefully it can help someone else out.
I have a subscription for AGOL for Organizations. Usually, I don't have too much trouble updating a feature service, but I have to delete, then create the service all over again. I have never successfully overwritten a feature service. I'm trying to update a feature service used in many maps, but now I have not been successful. The Results window shows a generic 999999 error. The original feature service was created in ArcMap (10.1), from a polygon feature class. When deleting and attempting to upload from ArcMap failed, I tried uploading a shapefile. The service definition uploads, but it can't be published because the "feature service already exists". But the feature service has been deleted and it doesn't show up in my Contents and it doesn't show up in my services folder. Any idea how I can delete this ghostly feature service?
Barbara, this isn't necessarily a solution for finding the "ghostly feature service", but if you do have to create a new service and just need to update the URL in your maps, check out ArcGIS Online Assistant Just log in with your user/pass...leave the default location, the log in should bring you to your Org account. There are several tasks you can perform under "I want to..."
Until you find a solution to your ghost service problem, this might be a work around. This is a Esri/ago-assistant · GitHub project....I'm not involved, but have used the app successfully in the past. But, I would recommend using the git hub page so you know more about it.
I was having the same problem, and found a workaround that may offer a clue to the source of the problem.
In the GP Results, I reran the Stage Service step separately, then checked to be sure the SD file existed. Then I reran the Upload Service Definition separately, first checking the box to Override Sharing Properties. Presto, I have a hosted service.
Jill Halchin
National Park Service
Savannaha, thank you so much for noting this fix. I had tried everything else but your fix worked for me just like you said. What is really wierd though is that no one else in my organisation had to add the organisation URL to get publishing to work - I guess I was just the lucky one.
Cheers,
Paul
I had the same problem with ArcMap 10.2.2 just now - sometimes the Fiddler option worked, but none of the other suggestions above helped.
I finally managed to upload the service from within ArcGIS Online: I first staged the service with ArcMap, then logged into AGOL (in browser), go to My Content, choose Add Item and select the saved service definition. You can select to publish the SD as a service immediately. This worked.
After a bit more experience with publishing services, I'm seeing what appears to be inconsistencies from day to day, even using the same database and mxd. Sometimes I get a quick, clean publish, but other times I have to resort to a workaround. And it doesn't seem to be related to the number of features or the size of the service.
At this point, I suspect that my problems, anyway, are due to variations in our network speeds or changes that IT is continually making to firewalls, etc. Overall high internet traffic, or something happening on the Esri/Amazon side may be a factor sometimes, too. So frustrating when results are inconsistent.
I have also intermittently experience the same problem. Sometimes I can publish no problems other times I get the "Failed to execute (uploadServiceDefinition)" message. The only work around that I have found that works for me is closing down ArcMap and reopening and then republish. Most of the time I can republish after the first reopening of ArcMap. I admit this is an annoying work around.
However, I agree with Jill I also suspect the issues are due to variations in network speeds etc.
THANK YOU!!! GRACIAS!!! MERCI!!!
By just simply adding a new connection using HTTPS instead of HTTP did the trick.
Our issue was only happening when running ArcMAP in Citrix.
JReyes
To summarize what Savannaha explained, you want the three connections in your Manage Portal Connections.
http://www.arcgis.com
https://www.arcgis.com
https://(your organization portal).arcgis.com
I have the same problem to publish a feature service. If you have XTools pro 16.0 on your computer, you must uninstall this version, because with the 16.0 it is impossible tu publish something (I don't know why) !
If you can get ArcGIS Pro, do it. It is 64-bit and was born to do web. It's still a toddler in many ways, awkward for day to day data managment and digitizing, but it can publish! Fast. Consistently. You can overwrite services that were published from ArcMap in many cases. The only caveat is a bug that I just ran into: if you keep hosted services in an AGOL folder with spaces in the folder name, overwriting will fail. So be sure that your folder names don't have spaces. Seriously, even if you don't to anything else with Pro, try it for publishing.
There is a fix for this - Support | XTools Pro
I have an MXD that points at a single point file with about 80 records stored in a FGDB that I had published to a folder in ArcGIS Online and subsequently overwrote without problems. I did this once a month for 6 months without issues. I tried to overwrite it the other day and got the packaging succeeded but publishing failed 99999 error. The logs showed nothing, that generic code isn't helpful, if you're reading this far down you know the drill. I was trying anything I could to get it to publish, I had moved it to the root and that didn't work. I deleted the service and the SD, didn't work. I renamed the service when I re-published, didn't work. I renamed the MXD to be completely different than any service name and published with that name, didn't work. Even had Fiddler running. I finally got the crazy idea to run my MXD through the MXD Doctor. After I did that, it worked, it published. The MXD was 1.3 MB before (bloated by re-saving), and after the "treatment" it was 66 KB. I don't know if the planets aligned perfectly or there was divine intervention, or our network magically uncluttered itself to allow outbound data, but it worked. I am going to test this the next time I have this error with this and reply back. I can't with any certainty say this solves this issue, but it may be worth trying. Just my two pennies, hopefully it's helpful. Again, I had deleted the service and SD so this was a straight publish to the root, not an overwrite of the old service in the folder. Oh yea, I was publishing from within ArcGIS Desktop 10.3.1, Advanced License, 64bit PC, 8GB RAM, and 1GB network speed, and Symantec Endpoint AV software I can't disable.
Peter,
Do you know what the fix that is? The link just takes me to their main support page and I can't find anything regarding the issue on their site.
Thanks!
No fix from XTools yet as far as I am aware. I have just unistalled XTools and it works again.
Cheers.
I tried many of the of recommendations - Like Kevin - with no success.
MXD Doctor provided the solution for my situation.
With ArcGIS Desktop 10.2.2
My team contacted XTools and this was their reply. Hope it helps (works for us):
"This is a known issue in the recent XTools Pro 16.0. The problem is caused by the Selection Manager tool which uses layer extensions and adds GUIDs for the map layers and that seems to be unsupported on the ArcGIS Online (ArcGIS for Server) side, even if you don't use this tool.
We are working on the ways to address and fix the issue in the next update. Meanwhile, if you experience this problem there is no need to uninstall XTools Pro. It is known to help if you simply select to store relative pathnames to data sources for your map document. If this does not help in your case you can try to unregister the Selection Manager component in XTools Pro. For your convenience, you can download a package with a couple of .reg files at: https://xtools.pro/media/4862/sm_regunreg.zip One can be used to unregister Selection Manager and another to register it back. This is for the default installation path and can be modified as required."
I'm running ArcGIS Desktop 10.3.1 and am having the same issue. I was able to publish successfully earlier this week, was unable to publish several tiled feature layers last night/this morning, able to publish a feature layer this afternoon, and then unable to publish afterwards. Any quick assistance would be appreciated as this is related to an active project.
I should note that I've tried running this in ArcGIS Pro as well as ArcMap and have still had the same error
Having the identical problem in 10.3 as you. Just started. But trying to publish feature service. Had published earlier the same data but now the error. Cant publish anything. Frustrating!
Jason, I opened up and published a layer this morning with no problem. I'm not sure what happened, but maybe it was on the server side? If I have issues again in the future, or if I figure out what happened, I'll come back to this thread.
Well, it looks like I am having the same issue again. No idea what is wrong still. This time I was trying to publish a tiled layer as opposed to a feature access layer earlier.
I've encountered this error occasionally with different map packages given to me by individuals, for publishing to ArcGIS Online. Each situation has been a case of something peculiar about the package the AO didn't like, and I've been able to publish the contents of a finicky package using one of the following methods:
1) delete extraneous layers you don't need to publish
2) if Step 1 doesn't work, divide a map package containing feature layers and tile layers into one file for the former and one for the latter, and publish each to a feature service or tile service accordingly
3) as a last resort, rebuild the map package by importing the layers into a new file
Hi Barbara,
I am too facing the same problem. Did you find a solution to this problem?
I struggled with this error all day and tried many of the above methods with no success.
Finally I went and made an entirely new file gdb and imported in the features I was previously trying to publish. The old file gdb I had been using had some layers that had successfully published in a different mxd. I'm not sure if having those published layers in the same gdb with the unpublished ones I was trying to publish caused it to be 'locked', so that's why the new file gdb was created. Still didn't seem to work, so I just dragged those layers from my polished mxd (symbols, layers, scale dependencies) into a fresh untitled mxd and was able to successfully publish from there.
This was also after specifying the correct Portal URL in Administrator, although when I published that first map service it wasn't set so I'm not sure if that made a difference.
It's incredibly frustrating that this error seems to be so common (and judging from this thread, has been common for 5 years) and has so many solutions and workarounds but the messages in the Geoprocessing window after it fails are utterly useless.
I spent HOURS troubleshooting this issue, and uninstalling XTools Pro 16.0 fixed it. I NEVER would have figured that out without your comment. Thank so much!
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
