Select to view content in your preferred language

Serving Mosaic Dataset (Image extension) from NFS mounted directory

1483
2
08-20-2012 03:29 PM
TomWhitenack
New Contributor
So I have an Image mosaic with about 4TB of imagery stored on a NFS mounted disc.  I only have read only access to the images, but I've created mosaic datasets on the ArcGIS server machine, registered as a data store directory containing the filegeodatabase with the mosaic dataset and served it.  It seems to function fine when viewing the Overview images, but as soon as you cross the threshhold to where the raw data should display (accessed via NFS mount), it goes blank.  This same configuration worked in ArcGIS Server 10, btw. 

I've tried adding the NFS mount location as a datastore, but I get the error "Invalid folder location. Unable to access this location." 

Any suggestions welcome. 

Thanks,
Tom
Tags (2)
0 Kudos
2 Replies
JeffreySwain
Esri Regular Contributor
So you can see the source rasters correctly when creating the mosaic dataset and generating the overviews, but cannot when you attempt to publish them?  Is that correct?  Have you registered the 'data store' with ArcGIS Server?  Also how are you accessing the data?  A good test is to use the path used when creating the mosaic dataset in Windows Explorer from the Server machine.  If that machine cannot recognize that path, then you will have to modify the path so that the machine can see it.  It has been my experience that different networks and operating systems are more tolerant of '$' shares and paths with spaces and characters.
0 Kudos
TomWhitenack
New Contributor
I was not unable to create a datastore using the web-interface, since I assume it's trying to grant permissions to the arcgis user, it would fail because it's not a windows machine I'm mounting and there is no arcgis user there.  The permissions to this folder are setup based on the machine I'm connecting from.  What I did to work around this was to manually add the datastore to the /arcgisserver/config-store/data/argis-dataspace.xml file.  So it seems to be fixed now.

Thanks for your help.

Tom
0 Kudos