Peter,
Try the following from Novell's Knowledge Base, Tecnical Information Document 2944976:
--------------------------------------------------------------------------------
SMS Group Object is corrupt improperly configured.
There may be circumstances where the SMS Group Object is created without the
administrator having the opportunity to define the Context.
Solutions
To recreate the object, do the following:
First, if TSA500 has been loaded, it will need to be unloaded. In some cases, SMDR may
have not loaded at all, but, if it is in memory, it will need to be unloaded before
executing SMDR NEW at the console. The configuration prompts for SMDR are as follows:
SMDR Configuration Screen
Default SMDR Group container context OU=MyOU.O=MyOrg
Press enter for using default context/enter the new container context
SMDR Group Context:
<Press enter for default or enter the desired context. for example, enter .o=MyOrg for
the Organization "MyOrg">
Default SMDR Context OU=MyOu.O=MyOrg
Press enter for using default context/enter the new context
SMDR Context: <press enter the second time for the default or typically, enter the
same context again>
Enter the user name(full context) that has managing rights
Example: .CN=Admin.OU=sms.O=MyOrgl
Username: .admin.MyOrg
Password: <enter the admin password>
SMDR will load with no messages.
--------------------------------------------------------------------------------
Make sure user .xxxxxxxx.yyyy is a member of the SMDR Group.
Good Luck,
John Underdown
-----Original Message-----
From: Peter Hadikin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 25, 2001 5:31 PM
To: [EMAIL PROTECTED]
Subject: Netware backups with 4.1.x ... help me ... I'm drowning!!
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 experiencing the
following problem. I have to say I am at a loss. I see nothing wrong
with the TSM install and config. The Netware boys assure me I should
have no problems logging into the tree ... yet, here I sit writing this
note.
Once I receive this error message, I am prompted for a login to the tree
and can login successfully with the same id & pw. I have some some
references to this same problem in past years but nothing recently.
Any, and I mean any suggestions could result in a free set of beers next
time that individual happens to be in the vicinity of Vancouver or I am
in their vicinity ... or, I suppose if we both happen to be in another
vicinity. Anybody from ADSM/TSM support or developement ... any
thoughts? As you can tell from my note, I am a poor, rattled and
desperate soul. Help me!
Oh yes, I have tried all sorts of different flavors of SMDR, TSA500,
TSANDS ... all with this same story. You can reach me at the top of the
Port Mann bridge ... I'm gonna jump, this time I really mean it! (ok ...
I'm only kidding but I COULD change my mind)
01/25/2001 07:05:52 ANS1874E Login denied to NetWare Target Service
Agent 'JOHNNY'.
01/25/2001 07:05:52 ANS1874E Login denied to NetWare Target Service
Agent 'JOHNNY'.
01/25/2001 07:06:00 ANS1880E TSA Connect error,
NWSMConnectToTargetService 'JOHNNY'
password file
'JOHNNY\SYS:TIVOLI/TSM/CLIENT/68f5fb04.PWD'.
Userid = '.xxxxxxxx.yyyy'
failed with cc = FFFDFFD7
------------------------------
