A cached service layer in your map or scene is in a different projection than the map or scene being shared. The best solution depends on what you are sharing and if the service layer is your basemap.
- Web maps require a basemap. All cached service layers in the map must use the same tiling scheme as the basemap and the map must be in the same projection as the basemap.
- Global web scenes require a basemap that uses either ArcGIS Online/Bing Maps/Google Maps or the WGS84 Geographic Coordinate System, Version 2 tiling schemes. All cached service layers in the map must use the same tiling scheme as the basemap.
- Local web scenes do not require a basemap. If you have a basemap or a cached service as your scene's elevation source, all cached service layers in the map must use the same tiling scheme as the basemap or elevation source and the scene must be in the projection of the basemap and elevation source.
- If the service layer is acting as your basemap, use the provided default solution to automatically change the projection of your map or scene to match the projection of your basemap.
- Alternatively, use the provided solution to open the map properties to manually change the projection of your map or scene. For more information on setting the projection of your map or scene, see Specify a coordinate system.
- Remove the service layer from the map or scene.
If the service layer triggering the analyzer is serving as the map's basemap and you are sharing a web map or global web scene, do not remove it. It is required to define the map's tiling scheme and spatial reference.
Cached service layers are required to be in the projection of the scene or map. This can be because the service layer is acting as the basemap and is used to define the projection of the map or scene once shared or because the service cannot be re-projected in the viewer.