From: Nilanka on
I had the same issue and finally resolved after carefull testing. This is actually a error caused due to invalid permission settings. Be carefull when you add new lookup columns to lists. Check the users who are accessing the relevent list and and set permission before you add site columns as lookup fields. Also it's good to document permission settings and the use of lists within custom fileds and webparts. GOOD LUCK



metricfootballmicku wrote:

Site columns were added and those did not seem to cause an issue.
25-Nov-07

Site columns were added and those did not seem to cause an issue. I
have not had a chance to test, but I suspect it is *only* custom
lookups that cause the problem because of the association and the fact
that the user may or may not have access to the list the field is
using as a lookup.

The good news is it seems to be something can turn on and off without
any residual affects. The error pops up when it is on, but
immediately goes away once you remove the fields.

Previous Posts In This Thread:

On Friday, November 09, 2007 10:11 AM
dlozzi(remove-this wrote:

Cannot add user to WSS3
Howdy,

I have a WSS3 installation in AD Creation Mode. When I try to create a new
user WSS creates the account in AD and emails the user but errors and will
not add the user to the SharePoint site. If I create a user first in AD then
add them to the site I get the same error, but no email. The error below is
displayed on the web page

Exception Occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))

Below is from the diagnostic log

11/09/2007 10:05:01.51 w3wp.exe (0x0F24)
0x11AC Windows SharePoint Services General
837l Exception An unhandled exception occured. Watson will be invoked.

Event viewer has nothing!

I've done loads of searching on this and have nothing. Can you point me in
the right direction as to where I can start troubleshooting? I'll take
anything at this point!

Thanks a ton!!

--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net

On Tuesday, November 13, 2007 6:24 PM
callahan wrote:

David, I have set up several ADAC sharepoint farms, and have never had the
David, I have set up several ADAC sharepoint farms, and have never had the
error you are experiencing. I know it's been a couple of days since you
posted and you've gotten no response. And frankly, that's probably because
no one has come across this error (as you've discovered by the complete lack
of info online).

Obviously you haven't had sharepoint installed long if you can't
consistently add users. Have you considered doing a reinstall/repair?

-callahan
"David Lozzi" <dlozzi(remove-this)@delphi-ts.com> wrote in message
news:7E49D07F-1A13-4894-9B34-1E6AB02C844C(a)microsoft.com...

On Tuesday, November 13, 2007 6:43 PM
dlozzi(remove-this wrote:

You're right, there is only a handful of users in the system right now, but
You're right, there is only a handful of users in the system right now, but
trying to go live with it by Friday... I have a call with MS open and plan on
resolving tomorrow.


--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net


"callahan" wrote:

On Tuesday, November 13, 2007 7:46 PM
callahan wrote:

Cool. Please let us know what comes of it.
Cool. Please let us know what comes of it. You never know who might suffer
from the error next...

-callahan

On Wednesday, November 14, 2007 4:29 PM
dlozzi(remove-this wrote:

So, the cause is unknown to Microsoft but they know its an issue.
So, the cause is unknown to Microsoft but they know its an issue. Their "fix"
is to stsadm -o export each site, sub site and sub sub site and so on, delete
the site and then stsadm -o import each site, sub site and sub sub site and
so on. Then recreate/add all of the users and security permissions.

Nice eh? I'm not looking forward to this fix. Fortunatly, this current app
has about 16 sites and as many users. They are going live Friday with 1000+
users so the fix is necessary. I did ask if it's avoidable in the future, he
said that they don't know how it is caused so they can't fix it. Yeah, great
answer!

Anyway, I'm going to do some poking and see if I can find a better solution,
or write up my own script to automate the fix. I'll let you know what I come
up with.

--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net


"callahan" wrote:

On Wednesday, November 14, 2007 5:36 PM
callahan wrote:

Wow, it's a known issue, but they don't know what causes it and don't know how
Wow, it's a known issue, but they don't know what causes it and don't know
how to have you avoid it in the future? Makes you wonder how "known" it is.
Bummer.

Thanks for getting back to us though. Even if the fix is tedious, at least
there is one, for those who need it.
-callahan

"David Lozzi" <dlozzi(remove-this)@delphi-ts.com> wrote in message
news:A28C11B1-3948-40BC-B1EA-10D5EBBF27E3(a)microsoft.com...

On Wednesday, November 14, 2007 6:18 PM
dlozzi(remove-this wrote:

I'm now working on a windows app to iterate through the sites, export each of
I'm now working on a windows app to iterate through the sites, export each of
them, track user security, then after a deletion, iterate through all of the
sites and import them and reassign user permissions. Wish me luck!
--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net


"callahan" wrote:

On Wednesday, November 14, 2007 6:58 PM
callahan wrote:

Re: Cannot add user to WSS3
Cool. Good luck.
-callahan

On Friday, November 23, 2007 10:37 PM
callahan wrote:

That's a good thing to note.
That's a good thing to note. I mean, I've noticed that the user list is
just a list like any other, and therefore you should be able to add relevant
fields. Ironically though, I've never actually added any custom fields, and
haven't met anyone else who has either ('til you of course).

Tell me, did you happen to add any site columns? If so, did they cause any
problems, or only the lookups? Regardless, this is a good thing to know,
thanks for the information.

-callahan
<metricfootballmickus(a)gmail.com> wrote in message
news:00d8b5d4-af8f-4fa0-b6c3-f07c697bbb32(a)w28g2000hsf.googlegroups.com...

On Saturday, November 24, 2007 7:11 AM
metricfootballmicku wrote:

David,I've got the same exact issue you are facing.
David,

I've got the same exact issue you are facing. When doing a search, I
found another thread in which a person installed this hotfix:

http://www.microsoft.com/downloads/details.aspx?familyid=76fc2225-2802-46e5-a294-a842e3841877&displaylang=en&tm

and said that fixed things. Any chance you have not installed that
fix as well? I am really hoping that is the case as this is a pretty
nasty bug :(.

On Saturday, November 24, 2007 7:11 AM
metricfootballmicku wrote:

I may have a fix for you.
I may have a fix for you. I used SQL Profiler to see what the last
database call was before it would fail. For me, it was looking up the
fields associated with a user. It turns out that we had a couple
custom lookup fields we had added to our user list. Once I removed
those fields, everything started working again.

Sure hope that does it for you too... tell MS they owe you $250 :P

On Saturday, November 24, 2007 8:18 PM
callahan wrote:

Re: Cannot add user to WSS3
Makes sense. Good to know.
-callahan

On Sunday, November 25, 2007 5:24 PM
metricfootballmicku wrote:

Site columns were added and those did not seem to cause an issue.
Site columns were added and those did not seem to cause an issue. I
have not had a chance to test, but I suspect it is *only* custom
lookups that cause the problem because of the association and the fact
that the user may or may not have access to the list the field is
using as a lookup.

The good news is it seems to be something can turn on and off without
any residual affects. The error pops up when it is on, but
immediately goes away once you remove the fields.


Submitted via EggHeadCafe - Software Developer Portal of Choice
Use HTTP PUT Client to Upload Binary and Text Data
http://www.eggheadcafe.com/tutorials/aspnet/9a3baa60-a038-488c-a5a8-4eb0d49d899c/use-http-put-client-to-up.aspx