ArcGIS Pro 2.3 will not publish services

[EricEagle]

I'm testing ArcGIS Pro 2.3 currently within a 10.6.1 Enterprise environment.  I have found that 2.3 will fail to publish any services.  The log simply says, error publishing service (all the other staging/etc succeeds).

I get that a server upgrade will sometimes require client upgrades.  But for a new client not to be compatible with a server instance only one revision behind - this is new to me.

Does 2.3 require the 10.7 Enterprise pre-release in order to publish hosted services?

[MichaelVolz]

Philip Heede of ESRI addressed this question in the following thread:

ArcGIS Pro Publish Services To ArcGIS Server 

You will see his comment on p.8 as this is a popular thread.

Philip says "I can't say for certain, but at this time the expectation is that this will require ArcGIS Server 10.7 alongside ArcGIS Pro 2.3. I doubt that we will be able to support publishing to older ArcGIS Server releases."

[EricEagle]

I am not trying to publish directly to ArcGIS Server - just creating a regular web map / web layer via Portal.  The linked comment relates to directly publishing to ArcGIS Server, bypassing Portal.

[EricEagle]

Answering my own question.  So apparently, opening a 2.2.x project in 2.3, and attempting to publish, will not work.  Creating a new project in 2.3, and publishing web layers/maps via 10.6.1 Portal/Enterprise as hosted service does work.

[MichaelVolz]

So the implication of this discovery is that you will need to recreate all your projects from previous Pro versions in 2.3 in order to keep your publishing workflows intact.  For shops with lots of services published from previous versions of Pro (pre 2.3), this could be a substantial amount of work.

Would the webmaps that were hitting the previous pre 2.3 services need to be rebuilt as well as configurations such as pop-ups would no longer work?

[SusanTran]

Hi Eric,

Pro 2.3 supports publishing hosted web layers to 10.6.1 Enterprise and does not require 10.7 Enterprise.  Re-authoring maps from earlier versions of Pro in 2.3 should not be required.  Unfortunately, it appears that you're encountering a bug.  I'd like to work with you to investigate this problem and will direct message you for more information. 

Thanks,
Susan

[JillHalchin]

I encountered a similar problem last November. After installing Pro 2.2.3,  I was unable to publish any of the map in one project.  But I could publish from a second project.  The portal had been upgraded to 10.6.  I tried all sorts of experiments, including a new project with all new maps.  If finally resorted to publishing from ArcMap.

This morning, I uninstalled Pro 2.2.3 and installed Pro 2.3 for a fresh start.  I tried publishing from the existing project, but again, failure.  Since you can now start Pro without a template, I tried that. New map, added the data, presto, it published! 

It doesn't look to me like a Pro-Portal version compatibility issue. You can continue using an older project with newer versions of Pro.  I think the original project was corrupted. The replacement was based on the original, so it must have inherited the problem. 

Hopefully that makes sense.

[JillHalchin]

Update on my previous.  I continue to have problems publishing to our portal from Pro.  But I don't think that it's a corrupt file issue after all.  Publishing from Pro is inconsistent, sometimes it works, sometimes not.  New projects, old projects, new service, overwriting a service - I never know what will work and what won't.  A couple of years ago, ArcMap wouldn't work for publishing, so I switched to Pro for services.  Now Pro won't publish a lot of the time, but ArcMap will.  This is a huge time-waster.  Every 6 months or so I have to re-create maps, services,  web maps and applications because I've had to change the publishing workflow depending on which software is acting  up.

[ThomasColson]

Jill Halchin‌ we're standing up a new Portal instance that is specifically targeting, and resolving, the publishing hosted feature services issues folks are having. IT just released it for testing yesterday. Stay tuned. However, the issues are not Pro or Map related, it's the data store and lack of hardware resources is the issue. 

[JillHalchin]

Thanks!