1. The system cannot find the file specified (path_to_file)(path_to_file)
i The error message is reported during a restore activity.
ii. The error message is reported when starting a retire storage process.
2. The system cannot find the file specified. (path\_dirdesc) (path\_dirdesc)
This error might be reported by DS-System during processes like: Autonomic Healing, System Admin, Synchronization - etc, in the following scenarios:
- _dirdesc file is missing completely from the DS-System storage
- _diredesc file exists on the DS-System storage but the link to the file doesn't exist
3. The system cannot find the file specified. (data\1\1\36\31\1\1\3\6.1302202937) (data\1\1\36\31\1\1\3\6.1302202937)
The warning error message is reported from DS-Client Event log when doing restore of files. This warning error message can be seen also on the DS-System/DS-Operator event log. But can browse the data path (reported in the warning error) and can restore directly from the DS-System
4. The system cannot find the file specified. (J:\xx\x\reg.ds) (J:\xx\x\reg.ds)
The error is reported when doing an import of the initial backup on the DS-System.
5. The system cannot find the file specified: (the name of *_diff.dmp, diffirental database dump)
The error is reported when recovering a DS-Client database
6. The system cannot find the file specified. Software\Microsoft\Windows NT\CurrentVersion\ProfileList\hex-hex-hex\ProfileImagePath (1))
The error is reported in DS-Client and the following corresponding error is reported in Windows Event log:
Volume Shadow Copy Service error: Unexpected error VSS_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a new session. The most common cause is that the number of parallel backup has exceeded the maximum supported limit.
7. The system cannot find the file specified. (\\CLS\E$\Exchange Server\bin\store.exe GetFileVersionInfo)
Is reported during a process to create Exchange 2007 cluster backup
1. i. DS-Client requests online files that do not exist on DS-System ( during restore DS-Client uses the info available in dsclient database which might not be up to date, one reason for such discrepancies might be that an old dsclient database backup has been used to re-built DS-Client application ).
ii. There are orphaned links located on the storage location to be retired.
2. This error is most likely to appear after Disaster Recovery scenarios. _dirdesc file can be found on the DS-System storage at Backup Set Level, Share Level, or Directory Level. It contains information like Backup Set/Directory synchronized or not, Backup Set/Directory type, Backup Set/Directory/Share name etc.
3. DS-System is using snapshot when doing the restore.
4. The import of an initial backup cannot find reg.ds in sub directory.
5. Weekly admin performes a full dump of the database and it will try to find diff.dmp file. If Daily Admin has never been run, then it will fails to find diff.dmp file. And Weekly Admin is not sure whether the diff.tmp were deleted or weren't created. So it shows this message.
6. Multiple backup sessions running in this server and as a result when one snapshot is taken and before being transmitted to the DS-System, another snapshot was taken which overwrites the one from previous session.
7. A windows cluster name is used instead of Exchange cluster name (virtual node). During Exchange cluster installation, a windows cluster is created first and then during the actual exchange installation, the user will be prompted to create Exchange cluster name (Virtual node).
1. i.a. Run a system based synchronization to update the DS-Client database with the actual files layout available on DS-System side.
i.b. If the error points to a path that does not contain the strings 'pub', 'acc' or 'cln' the solution is to run autonomic healing with 'Force DR Scan' option on the backup set reporting the error ( the backup set can be identified via DS-Operator > Setup > Storage Path Converter). If the error points to a path containing the strings 'pub', 'acc' or 'cln', there are broken library links. In order to fix such links a DR scan for libraries (only) must be run. The steps are available under the FAQ section, ID 370.