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

STSADM command line to activate / deactivate publishing features

stsadm -o activatefeature -filename publishing\feature.xml -url -force

stsadm -o activatefeature -filename publishingresources\feature.xml -url -force

stsadm -o activatefeature -filename publishingSite\feature.xml -url -force (activating on site collection level)

stsadm -o activatefeature -filename publishingweb\feature.xml -url -force (activating on root site level)

stsadm -o activatefeature -filename publishinglayouts\feature.xml -url -force

stsadm -o activatefeature -filename navigation\feature.xml -url -force

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