-603, no such attribute in DSTRACE

[Ben Lewis]

Just wanted to know if this is something I need to worry about.  I found one TID but it doesn't exactly "fit."

 

Here's the exact error from the dstrace screen:

 

DSARead failed, no such attribute (-603)

 

The TID is:  10015356

 

Thanks!

[Anders Gustafsson]

Ben Lewis,

> DSARead failed, no such attribute (-603)
>

That simply means that something asked for an attribute where there is
none, as in:

"Give me the faximile telephone number for Joe"

where Joe has none

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2195

[Edward van der Maas]

Ben Lewis wrote:

> Just wanted to know if this is something I need to worry about. I
> found one TID but it doesn't exactly "fit."
>
> Here's the exact error from the dstrace screen:
>
> DSARead failed, no such attribute (-603)

If nobody complains that something doesn't work then everything is
probably ok. 603 do happen, same for 601 (no such attribute)

--
Cheers,
Edward

[Niclas Ekstedt]

Ben Lewis,

Like my esteemed colleagues has already pointed out
it's most likely nuthin' to worry about. 603 and 601
errors are quite normal in DSTRace during normal operations.

A good rule of thumb are that as long as no one complains
about problems or these errors doesn't show up in DSRepair
during a Replica Synch Status check, it's nuthin' to worry about.

--
___________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Göteborg AB

Telindus. Change things your way
http://www.telindus.com/

[Andrew C Taubman]

Every time a user logins in who does not have a personal login script,
this message is generated when DS goes to check if there is or is not a
personal login script attribute on that user.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

[a...@novell.com]

As mentioned, fix what is broken. DSA is not a filter you should enable
in dstrace casually as it shows more than you will need most of the
time. Agent Buffers are the same way. Client buffers are the same way.
In these cases -601 and -603 are normal. They should be noted when a
client throws them as an error like when trying to login. In that case
-601 would mean you fumbled the username and/or context.

Good luck.

Ben Lewis wrote:
> Just wanted to know if this is something I need to worry about. I found
> one TID but it doesn't exactly "fit."
>
> Here's the exact error from the dstrace screen:
>
> DSARead failed, no such attribute (-603)

> <https://10.1.0.3:8009/nds/error?error=FFFFFDA5>
>
> The TID is: *10015356*
>
> Thanks!