SPL Request 0xB103

Patrick Farrell

unread,

May 29, 2009, 7:53:40 PM5/29/09

to

18:35:54 7F8 SPL Request (Get Other Status) [0xB103]:
cn=pfarrell,ou=IT,o=TPG - Requested Userid not found in directory

I upgraded to Messenger 2 today since I finally got around to it, just
to enable presence.. I finally got that working. I am however seeing
that error. Seeing as how I do in fact exist in the tree, that's funny.
There is a host object and it is associated properly under the general
properties.

As far as I can tell, everything works fine, messaging, chat rooms,
presence.

One TID I saw said there's no known reason for it and that the only cure
is to remove all messenger objects, kill the folders and reinstall the
messenger application on the server (Netware 6.5 SP7 fyi).

Should I just write this off as cosmetic and ignore it?

Craig Johnson

unread,

May 30, 2009, 12:13:41 AM5/30/09

to

Any chance your user ID was created with NWADMIN? Does it have a
UniqueID property?

Craig Johnson
Novell Support Connection SysOp

Patrick Farrell

unread,

May 30, 2009, 12:57:56 AM5/30/09

to

I can guarantee you mine was created with nwadmin since I put the
network in starting with Netware 4 :P

I do have UniqueID. I ran a script years ago to assign them to
everyone. I just double checked to make sure and I do have one.

Craig Johnson

unread,

May 30, 2009, 1:55:49 AM5/30/09

to

Does messenger work for your ID?

I saw TID 10094732. Not much help...

Is the error happening only on that one user ID, as far as you know?

Weird...

Patrick Farrell

unread,

May 31, 2009, 7:56:15 PM5/31/09

to

It works fine for me. I did the upgrade Friday night and I was the only
one logged in. I logged another test user in and didn't see the message
for that user. I'll have to see what happens Monday when people start
using it.

Patrick Farrell

unread,

May 31, 2009, 8:15:17 PM5/31/09

to

On a whim I just logged in to check as some people log in over the
weekends. I am seeing it for other users. As far as I can tell however
everything works fine.

Markus Ernst

unread,

Jun 2, 2009, 7:36:18 AM6/2/09

to

Hello

We have the same error, but no problem with it. As mentined in TID, we have removed all messenger objects in eDir an made a fresh
installation. The error was back after a while. If more users are logged, than the erros comes more often.
It looks cosmetic.

regards
Markus

Patrick Farrell

unread,

Jun 2, 2009, 4:13:37 PM6/2/09

to

Markus Ernst wrote:
> Hello
>
> We have the same error, but no problem with it. As mentined in TID, we have removed all messenger objects in eDir an made a fresh
> installation. The error was back after a while. If more users are logged, than the erros comes more often.
> It looks cosmetic.
>
> regards
> Markus

I see them for every user. There's no problem on the user side that
anyone can see so I'm content to leave it alone as I'm the only one that
sees the error and everything appears to work fine.

Patrick Farrell

unread,

Nov 17, 2009, 2:20:15 PM11/17/09

to

jlgib wrote:
>
> I'm sure you are no longer looking at this thread, but just wanted to
> let you all know we are having the same error - but everything appears
> to be working. Hopefully, it really is cosmetic.
>

Are you sure enough to bet money on that? :p

Craig

unread,

Jan 14, 2010, 8:21:24 PM1/14/10

to

You will even read this comment.

:)

"Patrick Farrell" <pfar...@packereng.com> wrote in message
news:PHCMm.3644$K62....@kovat.provo.novell.com...

Sami Kapanen

unread,

Mar 1, 2010, 8:36:34 AM3/1/10

to

Craig wrote:
> You will even read this comment.
>
> :)

I certainly will ;P

We have rather new GWIM 204 OES2 installation here, and logfiles are
filling up by these B103 and B106 errors..

-sk

Patrick Farrell

unread,

Mar 1, 2010, 3:01:01 PM3/1/10

to

On 1/14/2010 7:21 PM, Craig wrote:
> You will even read this comment.
>
> :)
>

I read it :)

I'm amazed at all the cool solutions posts touting the benefits of a
product that Novell has put zero effort into in recent years.... When
did 2.04 ship? Probably a year or so at this point.