As I said in old thread, I doubt what you did was resolution - and here is the proof.

Does this happened after starting NW or do you get this message after NW worked fine? When you check library properties do you library as enabled? Is the control path correct one?

To get more idea why nsrlcpd is gone one must check your logs. Also, check system messages to make sure there is no external influence to this. If Windows, check also for Dr. Watsons and on UNIX system if core exists. What version of NW are you using?

To add to Hrvoje's questions, how is your rape library connected to the host? SAN, SCSI ...?

HI,

But again the problem resolved , there was a problem with the host entry , the same resolution done , but i didnt know , before the host entry was in Small letters only after changing to Capital letter it has worked and the next day the same problem came , on that time i again changed to small letter and after changing it has worked fine , Even i didnt know the exact problem and exact resolution for this . But anyhow the problem got resolved and it is working fine for two days , kept in montoring in future the same problem exsits or not . Anyway thanks to all for your immediate solution .

Rajesh S

Thanks

The storage node server is SUSE Linux , in the inquire command i can see all the drive and the autochanger .

Rajesh S