For whatever reason I have been getting a failure to publish error when publishing to portal. I can publish to AGOL just fine. I've been on numerous calls with Esri customer service as well as pulling in outside sql help to play around and look for what may be the problem. No one can find anything. A waste to pay this much money and not be able to use the service.
@Laura this is a question rather than an idea I'm guessing?
Long shot, but have you tried adding the same data to a brand new pro project in a brand new map and publishing that? It might at least rule a few things out.
@David_Brooks Yes, still does not work
Hi @Laura,
I’m sending this brief message to let you know I’ve moved your recent post 'Cannot publish to portal' from our ArcGIS Ideas area to the ArcGIS Enterprise Portal Questions board where it’s more likely to be seen and responded to by members who can help.
All the best!
What are you trying to publish as an item?
Are you publishing from Pro or through the website?
Are you getting any messages in the Portal and/or Server logs?
A layer from a database in SQL through Pro. I can publish when it is from a database I just created.
Is your SQL database registered on your ArcGIS Server as a Datastore?
yes, and it validates
There are some very slight differences in the connection properties between what you have in the data store configuration and what the logs are telling us. The datastore has the server names in upper case while in the logs it's lowercase. In the datastore we see that the INSTANCE=sde:sqlserver:MCGSSS02.
You've said that this all validates, which is great!
The instance in the logs is using a Instance="DSID=guid" reference instead of the above. I wonder if it cannot resolve to this. Personally, I like things to be 'clean'. I'd create a new data store entry with the same info as the logs (i.e. with the DSID entry) and see if you can get that to validate. That will tell us a bit more then.
An issue here is that a lot of people will use a sde file to create the data store, but then they have variations of that file that they use in different map documents. Sometimes they are close enough that it doesn't get picked up during publishing as a new datastore entry. But there's sufficient differences in there that the publishing will fail.
I was also reminded of another thing, but this only applies if you're using dedicated instances. You may want to try publishing the service with a min instance value of 0. It may publish, you can then try and increase the min instances to 1 (or more) after publishing and see if you can get it to work that way. It was something we did way back when, but may just work....
How do I go about changing that? I always use an sde connection path.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
