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