RPC errors Event ID: 1049 appear on RSA and RMS Server, together with "Internal error: Unable to create file" Event ID: 1048 errors on RMS server. This may also be seen with "Mapping Conflict" Event ID: 1060.
| Article:TECH17033 | | | Created: 2001-01-13 | | | Updated: 2010-01-13 | | | Article URL http://www.symantec.com/docs/TECH17033 |
Problem
RPC errors Event ID: 1049 appear on RSA and RMS Server, together with "Internal error: Unable to create file" Event ID: 1048 errors on RMS server. This may also be seen with "Mapping Conflict" Event ID: 1060.
Error
Event ID 1049: Job 'jobname' on pair 'pair_name' is disconnected. Cancelling the job on this pair. : No RPC binding has been established
Solution
The combination of the errors reported by VERITAS Storage
Replicator Event Id's: 1049 (Figure 1), 1048 (Figure 2) and 1060 (Figure 3) are
caused when the path name of files replicated to a target directory exceed 260
characters in length. The limit set by Windows NT/2000 for any path name is 260
characters. VERITAS Storage Replicator is not able to work beyond these limits.
To avoid this problem, reduce the length of the paths which contain files that are to be replicated. Even if the length of the path name on the source is less than 259 characters, the length may increase when added to the appropriate "replica" directory on the target.
Figure 1
Figure 2
Figure 3
To avoid this problem, reduce the length of the paths which contain files that are to be replicated. Even if the length of the path name on the source is less than 259 characters, the length may increase when added to the appropriate "replica" directory on the target.
Figure 1
Figure 2
Figure 3
|
|
Related Articles
Legacy ID
241874
Article URL http://www.symantec.com/docs/TECH17033
Terms of use for this information are found in Legal Notices
Thank you.