Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Portal Server 2003 list issue?

  Asked By: Ganesh    Date: Jul 17    Category: Sharepoint    Views: 956

Can anybody tell me why a list item would not include the created by
and modified by?

We have an internal for sale bulletin board and we have a mystery user
who keeps posting inappropriate sale items. We need to know what user
is posting the items, but the created by and modified is not stamping.



16 Answers Found

Answer #1    Answered By: Vinay Thakur     Answered On: Jul 17

I agree with you! Its been one of the things I have asked MSFT to render
in WSS but the audit trail while captured and exposed via an API is only
surfaced in teh MOSS product!

Answer #2    Answered By: Lynn Mann     Answered On: Jul 17

Your saing that even when you modify settings and columns, open the
default view, and then check the created by and modified by columns
to show in the default view that these fields are all blank? By
default the created by and modified by don't show up the in the
defalt view. You have to un-hide them.

Answer #3    Answered By: Damini Dande     Answered On: Jul 17

Below is a test post: Notice at the
bottom it list  the user who created and modified (SharePoint inserts
this). The problem I am trying to solve is someone has found a way
to post and the created by and modified is BLANK.
Item: test2
Seller: test2
Start Date: 3/12/2007
End Date: 5/11/2007
Description: dddd
Contact Info: sssss
Status: For Sale

//************* Below the by is usually always populated except for
// for this bad apple who is posting crap on our network. I have a
// that if this individual is caught he will be terminated.
Created at 3/12/2007 1:29 PM by Kiosk User XXX-XXXX
Last modified at 3/12/2007 1:29 PM by Kiosk User XXX-XXXX

Let me know if you need more to go on.

Answer #4    Answered By: Irving Hurley     Answered On: Jul 17

I have never seen this behavior before. Are you 100% sure you don't
have an active directory account somewhere with this name? I would
go through you site administration and ensure that only the correct
groups and users have access and that the people you expect are
within those groups. I will do some research on this later on today.

Answer #5    Answered By: Lalit Bhattacharya     Answered On: Jul 17

It sounds like they may have cleared their "Display Name" setting from
their user record in that site collection. That's the only way I know
of that would cause "Blank" created by/modified by metadata to be
associated to the items.

You could programmatically enumerate those items, and for the ones where
Created By/Modified by are blank, use the associated UserID to then go
back to the site collection users list  to find out who it is. I don't
think it would be that difficult to do. If you'd like, I'll try to
take a stab at creating something fairly crude but workable in a couple
of days, but first I want to ensure that specifically what you are
seeing, is in fact, just "Blank" created by/modified by

So, it looks like a need from SPS2003, WSS

Answer #6    Answered By: Gwendolyn Acosta     Answered On: Jul 17

If it is the display name being blank then read my post on "Portal
Alerts Not Working" the code posted there will repopulate display
names and the email address within active directory.

Answer #7    Answered By: Kyle Hernandez     Answered On: Jul 17

You are right that the issue  stems from users permissioned in a site
collection via a group, and the first time they visit the site, their
display name Is not stored in the UserInfo table as it is in AD.

Your code assumes that the environment is absolutely a Portal server
installation, and not just WSS. I do understand that Moojjoo is running
Portal, so if he is using profiles, and they are up to date it would
work, but also see:

SharePoint Account Management using SPUserUtil - Part 6 - Synchronizing
Display Names and Email Addresses with Active Directory


I do like the fact that you provide an option to update from the
Profiles rather than going straight to AD.

Answer #8    Answered By: Kedar Phule     Answered On: Jul 17

But this issue  is not customized code. This
is a standard customized list  within Portal Server 2003.

I keep seeing the mention of SITE, which belongs to Windows
SharePoint Services 2.0 and this list was created on PORTAL SERVER
not Windows SharePoint Services.

I keep seeing messages about AD and the profiles stored in Portal
Server. If this is the issue the next time the BAD APPLE post a BAD
Listing we will run the profile tool to update and hopefully expose

I am STILL OPEN TO other solutions.

Answer #9    Answered By: Chanel Gaines     Answered On: Jul 17

We understand that your issue  is not with customized code, we are just
offering sample code that can help to resolve your issue with the
customized list.

A SITE belongs to BOTH WSS 2.0 and Portal Server. A Portal server  and
it's areas are in a single "Site Collection" Portal Server 2003 is
build on TOP of Windows SharePoint Services, so when we speak of things
such as the SITE database, it refers to Portal Server as well.

Answer #10    Answered By: Timmy Whitney     Answered On: Jul 17

Thanks for the info on the SITE
refers to Portal Server. I have always referred to AREAS as Portal
Server and SITES and Windows SharePoint Services to reduce confusion
to end users.

Thanks also for the sample code.

Do you recommend that I perform a full Import on the Profile
Database if the individual posts another rude comment on the board?

Answer #11    Answered By: Harihar Sonnad     Answered On: Jul 17

That leads to a whole discussion of what a "SITE" is vs a "WEB" and that
portal "Areas" are supported via WSS backing "Subwebs" of a single site

If you refer to a "Site" as a WSS Team site whether it be the root web
(Site) of a site collection or a subweb (subsite) of a site collection
and that a portal  Area is not like a normal WSS team site, please
continue to do so if it helps reduce confusion

Sometimes it can confuse people more when you try to explain what's
really going on under the covers

Importing another complete import of the Profile database isn't going to
solve this problem from what I can tell. It sounds like your KIOSK
servers are probably using Anonymous access to get add comments? If so,
it should be showing "Anonymous"

Probably best to wait for it to happen again, then some data can be
collected to find out what is really going on

Answer #12    Answered By: Deven Gajjar     Answered On: Jul 17

If these Kiosks are allowing users to get into your portal  you most
likely have something like ALL NT Authneticated Users added to
contributor for the "area" that you are talking about. This is a
really bad practice as your probably seeing. Try and gain access to
one of these kiosks and see what username and machine name they are
using. This is most likely your problem.

It sounds like you might need to revise how your active directory
structure is setup and move all active employees into a specific
group. Then remove the all nt authenticated users from sites
(portal and WSSS) and replace with the AD group for active employees.

Answer #13    Answered By: Latisha Schneider     Answered On: Jul 17

A developers nightmare in the work place. The
company I am employeed with has KIOSKs which are locked down but
anybody can use the machine without requiring login. Tell me that is
not a security issue????

Answer #14    Answered By: Nora Maxwell     Answered On: Jul 17

I want to restate that the issue  is with an SharePoint Portal 2003

We have a list  setup that allows employees to post items. As soon as
you post an itea an end user can click on the item to VIEW ITEM.

******************EXAMPLE LIST ITEM**************************
Item: test2
Seller: test2
Start Date: 3/12/2007
End Date: 5/11/2007
Description: dddd
Contact Info: ssss
Status: For Sale

Created at 3/12/2007 1:29 PM by <***Kiosk User 999-1716***>
Last modified at 3/12/2007 1:29 PM by <***Kiosk User 999-1716***>
******************EXAMPLE LIST ITEM**************************

The area enclosed in <*** ***> is what is BLANK...

Unfortunatly our PR department has deleted the listings and I cannot
perform any other research. I have instructed them to not delete it
next time until I can look into the issue. I will be following your
advice to recreate the issue.

Answer #15    Answered By: Corina Duran     Answered On: Jul 17

We totally understand that this is with Portal 2003, and an area list.

An area list  is just a "WSS" list

Answer #16    Answered By: Irving Hurley     Answered On: Jul 17

You need to add these columns from Modify Columns and Settings by editing the
default view of the custom list.

Didn't find what you were looking for? Find more on Portal Server 2003 list issue? Or get search suggestion and latest updates.