Author: Peter Hadikin <Peter_Hadikin AT BCIT DOT CA>
Date: Thu, 25 Jan 2001 14:30:54 -0800
Hello group, I am about ready to give up ... we have upgraded our Netware 5.x servers to either 4.1.1 or 4.1.2. It is not a pretty site. On both our production NDS tree and our test NDS tree we are e
Author: Peter Hadikin <Peter_Hadikin AT BCIT DOT CA>
Date: Thu, 25 Jan 2001 15:14:59 -0800
I did try this ... thought the same thing myself. The .pwd files tend to accumulate. Same results. No beer for that one. Next contestant please!! Take it easy, Peter "Remeta, Mark" <MRemeta AT SELIGM
Author: Scott Foley <sfoley AT NETDOCUMENTS DOT COM>
Date: Thu, 25 Jan 2001 16:38:57 -0700
I recall a similar problem that I had recently. I don't recall if I had to remove and recreate the client password, but I do remember some problems with the order that I loaded modules. I had to unlo
Author: "Forgosh, Seth" <sforgosh AT TIAA-CREF DOT ORG>
Date: Fri, 26 Jan 2001 07:34:19 -0500
Peter, When you log in, are you using a fully qualified NDS ID? I've found that if you don't, you will have this type of problem. For example, you might use .TSM.BACKUP.BCIT as your user ID. Note tha
Author: John Underdown <johnunderdown AT STI.SYNOVUS DOT COM>
Date: Fri, 26 Jan 2001 08:38:57 -0500
Peter, Try the following from Novell's Knowledge Base, Tecnical Information Document 2944976: -- -- SMS Group Object is corrupt improperly configured. SMS Group Object is corrupt improperly configure
Peter, We also had this problem. We are running a TSM 3.7.3 server on OS/390 our Netware servers work fine as long as we stay 4.11. Here is what our NOS engineer found. " A specific TSANDS is require
Peter, I think Seth may be on the right track. I've run into this many times as well. First, make darn sure the dsm (or whatever) ID had admin equivalency all the way through the tree structure, and
Author: Jeffery Carroll <Jeffery_Carroll AT AGFG DOT COM>
Date: Fri, 26 Jan 2001 18:33:11 -0600
We ran into EXACT same problem yesterday. Increasing the number available connections for the TSM/Novell ID in Nwadmin fixed it for us. We had an upgrade about a week ago, increasing number of client