Issue : Publish Map Service have Layer datasource with mulitiple schema

[SreejithSreenivasan]

Error while publishing the Map Service, Map document layers are  pointing to multiple database schema.
ArcGIS Pro 3.2.2 & ArcGIS server 11.1
Is it mandatory all the layer source geodatabase should be from single database schema?

[MichaelVolz]

Can you provide a screenshot of the error message?

[SreejithSreenivasan]

Please find the error message given below.It is saying to check second sde connection feature classes are exists on the server.Please note that ..I could able to register both connection in the arcgis server and able to publish as a seperate Map services.But If I try to put the layers in single Map, getting the follwoing error message.

"Failed to create the service.: Updating the server connection string for layer xyzxyzx failed. Attempted connection string was ENCRYPTED_PASSWORD_UTF8=00022e686a6468932456674274c337553524337686f31634d6c616c536868534a312b5a38346e5172487677787a6e383d2a00;ENCRYPTED_PASSWORD=00022e684351234467a336867466c452b616745851893657a666d4a5a336a3775742f76734f5757er474b737a7a703838453d2a00;SERVER=xyzxy;INSTANCE="DSID=9b469a91-4c91-4fa0-90d2-d491084625b9";DBCLIENT=oracle;DB_CONNECTION_PROPERTIES=xyzxyz;PROJECT_INSTANCE=sde;USER=xyzxy;VERSION=SDE.DEFAULT;AUTHENTICATION_MODE=DBMS. Table name is xyzx.xyzxy. Please verify the data exists on the server."

[Eugene_Adkins · Accepted solution]

Unfortunately, you cannot publish a map service with data from multiple sources. Here’s some ESRI documentation.

The solution would be to publish two different services (or more depending upon the number of sources) and then join/add/bring these feature services together on your online or portal side in a web map. Another solution would be to create a single source containing all your data (or add the missing data to an existing source) so you could publish a singular map service.

Hope this helps.

[MichaelVolz · Accepted solution]

Do you have a business requirement where the data in the service will be getting edited through the service?  That would make this more complex.

If just read-only access through the service, can you create an account where the user has read-only access to all the data so this user account can be used when publishing the service instead of 2 different accounts that get explicit access to each schema?