An error occurred modifying an attribute value. Invalid name (db2a)

Mike Finnegan

unread,

Apr 29, 2009, 2:54:14 PM4/29/09

to

I have Netware 6.5 SP7 and Groupwise SP6 I used Consoleone when I tried
to create a user named Allison I got the Groupwise error message An
error occurred modifying an attribute value. Invalid name (db2a). I
create another user Sharon right after that with no problems. I have
deleted and recreated Allison several times with the same result. I even
tried adding a character to her name. She does have the same last name
as a current user and I added a letter to that with the same result.

Could the user name be stuck in GroupWise somewhere or what could cause
this error?

Uwe Buckesfeld

unread,

Apr 30, 2009, 12:05:30 AM4/30/09

to

On 04/29/2009 Mike Finnegan wrote:
> Invalid name (db2a)

Does TID 2947044 ring a bell?
Else try disassociating the GW account from the eDir account, wait a minute or two, reassociate and try again.

Uwe

Mike Finnegan

unread,

Apr 30, 2009, 10:31:49 AM4/30/09

to

Thanks for the reply.

The TID does not apply to my situation. As to your suggestion the
GroupWise account never gets created. The person in question has the
same last name as a current user and when I tried to create the new user
I got an error. I tried to modify the last name by adding the first
character to the end of the last name but the users first name triggered
the error. I had to use Alice instead of Allison and with the added
character to the last name it worked. It seems that the name Allison is
stuck somewhere and needs removed. I'm not sure of how to do that.

Uwe Buckesfeld

unread,

Apr 30, 2009, 2:10:10 PM4/30/09

to

* Mike

if it were already taken, the error would be "duplicate entry" or some such. Anyway, double check for any object with the same name, could be a distribution list, a nickname, a gateway alias maybe.

Uwe

Mike Finnegan

unread,

Apr 30, 2009, 3:51:06 PM4/30/09

to

Thanks Uwe,

The new person had the same last name as somebody which caused the
initial error. After that just using the first name which is unique and
not duplicated caused the for mentioned error. I even modified the last
name and the first name still triggers it. Something got whacked from
the first time. When I changed the name from Allison to Alice and used
the same modified last name it worked so the unique first name seems
tied up somewhere because it was associated with a duplicate last name.
How can that be fixed?

Uwe Buckesfeld

unread,

May 1, 2009, 6:21:42 AM5/1/09

to

Mike,

I'd delete the GW account completely and recreate a new one which is definitely not a duplicate. The error may occur when you rename the faulty account, but it should definitely not appear if you create a new account with a unique name.

Uwe

Mike Finnegan

unread,

May 1, 2009, 2:43:09 PM5/1/09

to

The problem is that it was created in Netware but not GroupWise. I did
delete it in Netware. It seems retained in GroupWise some how but I
can't see it their using consoleone.

Uwe Buckesfeld

unread,

May 2, 2009, 6:48:37 AM5/2/09

to

If it is in the database, you can see it in C1. Switch to Groupwise view, and connect to secondary domains.
If you really have a "ghost" account, rebuild the domain(s) and PO(s).

Uwe

Dave Parkes

unread,

Sep 27, 2009, 5:11:50 PM9/27/09

to

Well spotted - however, using 'All' as a mailbox ID is still dangerous,
see TID 10100737

Cheers Dave

--
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/