"...Another way to make your data available to all GIS server machines is to use the operating system tools to share the directory in which the data is stored. Shared directories are commonly referred to with Universal Naming Convention (UNC) paths, which contain the name of the server (for example, \\myServer\data). When you use UNC paths to reference your data, all GIS server machines will look to the correct machine for the data.
If you store your GIS resources in shared directories, remember that all data source paths within the resource must also use UNC paths or relative paths. For example, if your map document contains layers from three feature classes, the paths to those feature classes must be UNC or relative paths.
Remember:
Although shared network folders are convenient for referencing data, they require network traffic and can introduce performance bottlenecks that would not otherwise exist when accessing the data through local paths..."
"...You should be aware of your operating system's security mechanisms and hierarchies. For example, if you are working from a shared directory in Windows, you will have to give the ArcGIS Server account share permissions for the folder, then you will have to switch to the Security tab of the folder properties and grant NTFS (file) permissions to the ArcGIS Server account for the folder. If you do not grant both types of permissions (share and file), you will not be able to access the resource, since the operating system gives precedence to the more restrictive of the two..."
Jamal,
My thought is that many of these messages are not helpful and are simply symptoms of a mixture of ArcGIS Server bugs and user configuration errors. 10.1, which should have been called 11.0 from an ArcGIS Server perspective, was a massive architecture change and I think that we are going to have to work through all these issues.
I think that the best way to do that is to file incidents with ESRI support. The forums are great for users helping other users but it seems clear that ESRI does not file bugs based on these discussions. There are some exceptions to this, e.g. Chris Fox, but they are exceptions and not the norm.
I recently reported the problem that you can't take the parcel sample from the tutorial data and publish it from one of the Windows public folders without getting the "base table definition error":
#NIM089194 Parcel Fabric data publishing from C:\Users\Public\Documents folder will return error "Server instance is started with errors. The base table definition string is invalid".
In this case there is no permission problem. I think that it is simply a bug in ArcGIS Server. What is the bug? I haven't a clue and I don't have the bandwidth to try to figure it out:(
In another case, I saw this error and it was a configuration bug.
ESRI support also informed me of the following:
#NIM082970 The error, "The base table definition string "MyLayer" is invalid" is vague. The error should indicate that permissions have not been granted to the geodatabase folder.
But we already know that this error is not always related to user permission problems because public folders are well.... public.
Jamal,
If were not able to fix this issue this is what I figured -
I had this same error publishing the map service to AGS 10.1 and a warning was also given after analyzing the map document (which we tend to ignore) -
"Layer is being published with custom class extension. "
If you experienced similar warning make sure the necessary class extensions applied on the feature classes are installed on your machine.
Once I installed these the map document was published successfully.
Error I got - The base table definition string "Conductor" is invalid.
Thanks!