Hi,
Ok, the next thing we can try is to enable logging. To enable logging you'll need to make a small change in a text file within the ArcGIS Runtime local server directory. At Beta 2 you need to do this manually, but we have since created a much more user/developer-friendly GUI app to do this.
#. Open Windows Explorer
[the following steps assume you're on a 64-bit machine - for 32-bit drop the x86, etc]
#. Browse to "C:\Program Files (x86)\ArcGIS SDKs\WPF10.1\ArcGISRuntime10.1\LocalServer64\bin"
#. Find the arcgisruntime.json file and open in a text editor.
#. Change the following:
"logging" : false,
#. To:
"logging" : true,
#. Save and exit.
#. Now when you run your application the local server will be creating log files in %temp%\ArcGISRuntimeLogs (e.g. C:\Users\mbranscomb\AppData\Local\Temp\ArcGISRuntimeLogs).
#. you can open the log file in a text editor to see if there are any clues to the problem.
If there's nothing useful in the logs, then to confirm that the MPK is definitely pointing to the correct we'll need to dive a little deeper. So I'd like you to check the following please:
#. Browse to the exploded packages in my documents (e.g. C:\Users\mbranscomb\Documents\ArcGIS\Packages).
#. Find the directory with the same name as your MPK (e.g. ch_test5)
#. Browse to ...\ch_test5\v101
#. Use 7-zip to extract the files from the MSD file (e.g. extract ch_test5.msd to a new folder ch_test5.msd)
#. Browse to ...\ch_test5\layers
#. Open the xml file for one of the layers of your data in a text editor (e.g. myFeatureLayer.xml)
#. Look for the <WorkspaceConnectionString> tag.
#. This should contain a path like "DATABASE=V:\Data\..\ch5\ch_test5.gdb".
#. This will confirm that the packaging process is correctly using the virtual / mapped drive for the externally referenced drive.
If the path in the msd file looks ok then it should be behaving fine. If none of that helps - can you put together a reproducer app with data? I could test this by simply creating the same virtual /mapped drive here.
Cheers
Mike