I received the Cannot have "mixed" data stores with a feature or geocode service message today when I tried to publish a 10.2.2 feature service with data updates enabled. My map document only has one layer and that layer's data source is an ArcSDE Enterprise Geodatabase. I found that the issue was an image element that was added to the layout to display a logo on printed maps. ArcMap must package up the image and upload it to the server just as it would any layer source data that is not registered with the server. Once I deleted the image element from the layout I was able to publish my feature service.
Jay
Jay, thanks for posting this comment. I just experienced the same error today, running 10.2.2. I never would have guessed to delete the image elements in the layout window, but after I did this, it published successfully!
Brendan
You are the man Jay. This has been perplexing me so much over the last week...
Yep, this was exactly my problem too. I would never of guessed that the images in the Layout window would cause this!
Jay,
How did you discover the solution to this problem? I scoured through the documentation on Feature Services and couldn't find the answer.
Thanks for posting this solution.
This issue still exists in 10.5 where it presents, in my case, as "ERROR 1369: Failed to create the service" in ArcMap.
The server log shows "Failed to create the service.: Invalid service definition. Cannot have "mixed" data stores with a feature service"
Removing images from the layout window does resolve the problem. The problem only occurs when "Feature Access" for the service is ticked as one of the Capabilities.
If you've removed everything from the map document except for data that all resides within the same database, I'd open a new arcmap session and drag the layers from map doc 'a' into new map doc 'b', then attempt to republish. Sometimes map documents hold onto old data references when they shouldn't.
I had a different problem. I built a mapping service in Portal to show how the app would look. Just wanted to show and get feed back from future users. I built it in a file DB so i could make changes easier. Well, when it came time to actually go into production with a feature service, I imported it into my SDE DB and changed the source on the Map document. That through my error. The advice to create a new map document with new data source was correct. Once I did that, all was well.
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.