Saturday, April 30, 2011

MOSS 2007 User Profile AD Sync Issue

Background:
  • User Profile Import Schedule was not running as per configured Schedules
  • We have to manually run the Incremental crawl which pulled the users from different ADs.
  • Profile Synchronization, Quick Profile Synchronization Jobs were running successfully.
  • There were totally 90000 profiles, pulled from different domains.
Problem:
  • Imported User profile details (changes) were not getting published to the web applications.
  • We were able to see the changes in SSP database in “UserProfileValue“table.
  • On the other hand when we removed the user from site and added him back the changes are reflected in the web application.
Resolution:
Ran following commands to get rid of this issue
stsadm -o sync -listolddatabases
Resulted in number of GUIDs, so ran following command to delete those GUIDs
stsadm -o sync -deleteolddatabases
And then
stsadm -o sync
To check connection between AD and MOSS ran following command
stsadm -o getproperty -propertyname peoplepicker-searchadforests
If its resulted in NO, then we have to set connection between AD and MOSS using following command
stsadm –o setproperty –pn peoplepicker-searchadforests –pv

After that rechecked behavior using stsadm -o sync -listolddatabases and did not get any GUIDs and after that ran Full import which resolved the issues.
Please let me know in case of any questions.

Display SharePoint site user with only user name (without domain name)


Click on the arrow besides Welcome domain name \ user name and then click on My Settings

There are following options Account , Name, etc.

Check Name option, if it will show you Domain name \ user name then you has to change the display name in user’s AD attributes because this information is directly fetched from AD via SSP.

After change in Display name in AD attributes recheck user profile properties under SSP user
profiles and properties


Please let me know in case of any queries

Wednesday, April 20, 2011

How to: Export a Discussion topic List item (SharePoint 2007) to excel or PDF ?

Here is  some tricky way to achieve this GOAL

When you reply to a discussion it changes to Flat view and redirected to flat.aspx page.
So to export discussion topic in excel you have to manually change the URL from flat.aspx to allitems.aspx.

I.e. to enable export to spreadsheet option URL should behttp://siteURL/Lists/discussionname/allitems.aspx

Else to export from “Flat view”  try following steps.


·         Open Excel

·         Click on DATA tab

·         Select from Web option

·         Then in URL provide the URL with http://siteURL/Lists/discussionname/flat.aspx

·         This will open a page with Allitems.aspx in pop up and then you can select (arrows) to insert required data to excel.

·         And from Excel you can easily export to PDF

Wednesday, April 13, 2011

Upgrade WSS 2.0 (with MSDE DBs) to WSS 3.0


One of my friends was in process to upgrade his WSS 2.0 to WSS 3.0 but the main challenge was he was using WSS 2.0 with MSDE database so in place upgrade will not be helping him.
To achieve the goal we have followed below steps.

  • Copied all .mdf and .ldf files to new SQL server ( SQL 2005 )

  • Restored all DBs from .mdf and .ldf which had created new content DBs on SQL 2005 machine

  • Installed WSS 3.0 and connected it to SQL 2005

  • Created dummy sites and attached all the DBs using STSADM command - 

    stsadm -o addcontentdb -url URL NAME –dn DB NAME- one by one to sites and we got all our old sites up and running.

'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater

Issue:
'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater


Environment:
Windows XP

Microsoft Office 2010
IE8


Resolution:

Office 2010 is supposed to *better* work with SharePoint Server 2010 or SharePoint Foundation. But it is also backward compatible. Install the feature - Windows SharePoint Services Support - and it should work for version 2, WSS 3.0 and Foundation or Server 2010.

SharePoint content database monitoring tools

I found some very good SharePoint Content DB monitoring third party tools.
These are some
SharePoint content database monitoring tools to alert administrators if the content database size gets low/full
SharePoint Monitoring Toolkit Executive Overview
SharePoint Monitoring ToolKit for System Center Operations Manager 2007

Wednesday, April 6, 2011

Create folder in Wiki Page Library

By default there isn’t any option to create a folder inside Wiki Page Library, please find following figure.The only option available is New Wiki Page.

Also it is not possible to enable content type and then get a folder option. This is something tricky to create a folder inside Wiki Page Library.

Open the Wiki Page Library in Windows Explorer , make sure there isn't any option for Explorer view or there isn't any option under actions  menu.


Create or copy windows folders inside it and come back to Wiki Library in browser and refresh the page.
Here you will get folder created in Wiki Page Library.

Hope this will be helpful.

Tuesday, April 5, 2011

Lookup column gives "#" symbol when export to spreadsheet


Issue:
There are 3 lookup columns, when I export this list to spreadsheet these lookup fields export with #;ID attached to them, and I got "testdata#;15"  instead of "testdata" I get
Resolution:
It was resolved after unmarking check-box for "Allow Multiple Values" for that lookup column under column settings

Friday, April 1, 2011

The column name you have entered is already in use or reserved. Chooseanother name

One of the users changed the default content type “Title” to “Item Title” and when he tried to pull it back it gave an error – “The column name you have entered is already in use or reserved. Choose another name”

After modifying default name to custom name he realized that “Title” name had been changed to all over sites because on site all lists / libraries were inherited from parent content type. As a farm admin I even tried with no luck and got the same error.

I googled the issue and very quickly found resolution on – http://blog.weareon.net/fix-for-the-column-name-that-you-entered-is-already-in-use-or-reserved-choose-another-name/

There is a small JavaScript we have to run in browser which clears all the values in the forbidden column collection array and gives you a confirmation

And after running following JavaScript I got rid of that issue.

javascript:g_FieldName={};alert(‘Successfully cleared forbidden columns’);