Okay, I went for the easy target and missed. I guess the next questions to ask are whether or not the server has a replica of any partitions on it (the server we backup NDS on has a replica of all the partitions in our tree) and whether or not the netware user name that you are authenticating with has any kind of rights to those partitions (we use the admin user and password to authenticate tsm to the server and tree).
>>> [EMAIL PROTECTED] 6/2/2004 4:49:46 PM >>> Hi Joel, NETDB.nlm was already loaded when I checked. I have also tried reloading the modules (SMDR, TSANDS, TSAFS ...) but to no avail. I have looked in the archives of the list but only found something refering to an older NW install and an older TSM client. I was wondering if people running older versions of the eDir (like 7.x) are have a similar problem. This would help me eliminate the version of eDir as being the issue. Thanks all, Curt >>> [EMAIL PROTECTED] 05/31/2004 6:14:59 am >>> I believe NETDB.NLM needs to be loaded manually before the TSA's, or at least before the DSMC*. But you would not be able to backup regular files either if this was not loaded, I think.... Just a shot in the dark.... Joel Lovelien >>> [EMAIL PROTECTED] 5/28/2004 4:37:06 PM >>> Hi all, I've run into some issues while trying to back up a test box loaded with NW 6.5 running eDir 8.7.3. All I get are errors everytime I try to do either a scheduled or manual backup of the NDS. Current setup is: TSM Server v5.2.1.2 TSM Client for NW v5.2.2.9 (Mar 18th 04) NW v6.5 eDir v8.7.3 TSANDS.nlm v10551.61 SMDR.nlm v6.54 (Dec 1st 03) Using both TSAFS.nlm v6.50.06 (Dec 4th 03) TSA600.nlm v6.00.08 (Sep 11 03) The error that I'm coming across in the DSMERROR.LOG is: "ANS1876E Unable to connect to target service. Netware SMS return code = FFFFFFFF." Not too sure where to look from here. Has anyone come acrosss this before? Thanks Curt _______________________________________________ Curt Watts Network Analyst, Capilano College [EMAIL PROTECTED]
