WEBGISDR migration and broken mosaic datasets in file geodatabases

[WarrenMedernach]

I am attempting to deploy a webgisdr backup of our current environment to a new environment with the ultimate goal of migrating our 2 machine (hosting and image server) 10.9.1 deployment to 11.3 following this guide.  I now have a 95% functioning new 10.9.1 deployment with our data restored.

I say 95% because I have some published Mosaic Datasets as Map Image Layers, where the Mosaic Dataset resides in a File Geodatabase located on a shared folder that is registered as a Data Store.  The source files  for the mosaics reside in object storage in Azure. The shared folder Data Store successfully validates in the new deployment as do all other Data Stores from the original deployment. All of these layers that are referencing a Mosaic Dataset in a File GDB are not working.  The debug logs have not provided much insight, and simply state: Could not find service. Service may be stopped or it may not be configured.

Any suggestions or ideas where I might look to try to get this resolved?

[JakeSkinner]

Hi @WarrenMedernach if you right-click on the Mosaic Dataset > Modify > Repair Broken Data Source Path, are there any reported broken paths?

[WarrenMedernach]

Thanks Jake.  I figured it shouldn't have been anything related to actual mosaic itself as it's working fine on the 'live' system, it just wasn't working on the replicated system accessing the exact same data.  It turned out to be a permission issue for the arcgis service account on some of the server system folders after the deployment.  It all seems to be working fine now.