The server or storage agent can recover from some failures by requesting access to different volumes. If there is a directory definition problem, this message may be displayed multiple times during retries with different volumes. The directory names associated with the device class definition in the server should be checked for correctness in the number and names of directory entries.

The permissions associated with newly created files should be checked to ensure the server and storage agent can write to newly created files. Depending on the system, a mask value may need to be adjusted. The system error or event log should be checked for indications of hardware or software errors from file systems.

For a remotely mounted file system, ensure that the remote file system is mounted and useable to the storage agent. The file system should be checked to ensure that sufficient space is available. While the server checks space, multiple device classes or servers using the same file system can cause the server's space checking to underestimate available space.

For storage agents, PATH definitions for each of the FILE drives should be checked to ensure that the number of directories in the PATH definition matches the number in the server's device class definition and that directories exist and are accessible to servers and storage agents accessing server directories via their own path names. For example, if the server has the following definition:

DEFINE DEVCLASS FILE DEVTYPE=FILE DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a storage agent has the following PATH definition: DEFINE PATH STA FILE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE DIR=X:\DIR1,X:\DIR2 then system STA must have drive X set to access directory L:\FILECLASS on the server so that directories DIR1 and DIR2 correspond to the correct destinations on the storage agent and that the number of directories match between the PATH and the DEVCLASS definitions.