Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

"Reports to" link broken in SPS2003 after SQL2005 SP2 install

  Asked By: Noemi    Date: Sep 27    Category: Sharepoint    Views: 1114

Hopefully this post doesn't get buried in the forum before anyone
sees it. We're running an implementation of SPS2003/WSS2.0, with a
SQL Server 2005 backend. A few months ago, we upgraded the SQL
Server instance to SP2, which went very well, but one thing that we
just noticed is that the link between the "Direct Reports"
and "Reports to" fields seems to be broken/screwed up.

This only seems to be the case for users that are already in the
profile database; it seems to be fully functional for users that have
been added since the service pack upgrade. For instance, if you
browse to an existing user's MySite (existing meaning before the SP
upgrade) who isn't a Manager, and look at the "Reports To" field,
it's the actual domain username of the manager, and not the full name
(it shows domain\username, rather than John Doe). Similarly, that
same user does NOT show up in the manager's "Direct Reports" list.
The only way that I've found to fix it is to manually edit the
profile for that user and capitalize the domain name in the "Manager"
field (DOMAIN\username). Now, for users that were added after the
upgrade, there seems to be no problem whatsoever.

Is there something in SP2 for SQL 2005 that tweaks the data around
somehow for existing users? Is there some other hotfix that needs to
be applied? To me it seems very arduous and meticulous to just do it
manually for every single user in the profile database. If anyone
can point me in the right direction, please let me know at least
where to start.



2 Answers Found

Answer #1    Answered By: Dara Hobbs     Answered On: Sep 27

I saw it but this is a very specific issue so I'm not sure how many
people will have even experienced it, let alone know how to fix it.

Since it seems to be working for new users I wonder if you can't just
programmatically run thru all the user's in your profile database and
re-add the association...

Answer #2    Answered By: Abhinivesh Suvarna     Answered On: Sep 27

I think it's a very strange issue though. I may run a SQL
Profiler trace to see exactly what stored procedures get called when
a user profile is edited from the admin side. If I have any more
insight I'll post  it.