Many people including myself seem to forget there is a ‘folder’ content type in WSS / MOSS. The main reasons to use folders has always been performance issues for me & for archiving data in certain scenrios, but a big thing is that by using folders you can assign custom views that specifically are only available for the folder(s) that you specify.
However when considering using folders in your Information Architechture consider the following that you do not appear to be able to do:
- attach workflow to folders via UI
- move folders via UI
- move folders via explorer view without losing your metadata
- have version history on folders
- show folders in data view rollups
- CQWP won’t be able to surface all your data in folders – need to test to confirm this
Written by peter.stilgoe on July 2nd, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
Grant rights via a special personalization services permissions link from the SSP Admin UI. Specific rights can be granted to different components:
http://server:port/ssp/admin/_layouts/ManageServicePermissions.aspx
Written by peter.stilgoe on June 30th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
When you create a content database in Sharepoint through the central admin it is created with the following characteristics:
Recovery Model: FULL
Auto growth: 1mb
Log file growth: 10%
The one we are concerned with here is the Auto growth being set to 1mb. This means is we upload a 50mb file, the Db has to grow 50 x 1mb which causes performance issues. Also if a database auto grow occurs whilst being used by end users all web sites inside that site collection will stop while the database allocates more space. Also you will be pretty much guaranteed to get database fragmentation.
Its better to create your content databases manually and set the size you expect it to grow to from the outset. Then set a quota in Sharepoint so that the DB cant grow any more once it hits the size limit.
Note: if you do create via SQL ensure the DB settings are Latin1_General_CI_AS_KS_WS
Written by peter.stilgoe on June 19th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
When performing a search the search results page would display & then any link clicked thereafter, whether an actual search result or another menu item would take 20 – 30 seconds to load.
The problem was that our web front end servers didnt have access to the internet & they were trying to display external federated search results. If you are experiencing this check your WFE’s have external access, if they do not go into your federated seach settings & set it to return results from the local index & not from an external provider ie MSN, Google etc.
Written by peter.stilgoe on April 8th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
When clicking ‘Search Settings’ within your shared services provider you get the following error:
“Authentication failed because the remote party has closed the transport stream”
This appears to be caused by the SSL certificate, you can fix it by creating a new SSL cert using the IIS 6 resource kit & using SelfSSL
IIS6 resource kit
Command to run: Selfssl /s:(IIS ID of the Office Server Web Services site) /v:(length of validity for the certificate in days – I opted for 5000)
This then replaced the existing certificate with the newly created SelfSSL certificate and Search Settings now worked.
There is also a MOSS KB Article here: Authentication failed because the remote party has closed the transport stream
Written by peter.stilgoe on March 19th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
Search broken after installing the MOSS infrastructure update? Can no longer access any of the search settings in the Shared Services Provider?
The answer lies in the MS Document “Planning and Deploying Service Pack 1 for Microsoft Office SharePoint Server 2007 in a Multi-server Environment”
To ensure that you have the correct permissions to install the software update and run the SharePoint Products and Technologies Configuration Wizard, we recommend that you add the account for the SharePoint Central Administration v3 application pool identity to the Administrators group on each of the local Web servers and application servers and then log on by using that account.
Written by peter.stilgoe on March 18th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
By inluding html in your calculated column formulas you can turbo charge your lists in Sharepoint, see:
Using HTML in calculated columns
Adding traffic light system to Sharepoint lists
Written by peter.stilgoe on March 4th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
If youre not already using JQuery in your Sharepoint environment Im sure you will be in someway in the future, to get you started heres some useful links:
JQuery at EndUserSharepoint
50 JQuery examples
37 more JQuery examples
Written by peter.stilgoe on March 3rd, 2009 with no comments.
Read more articles on JQuery and Moss / Sharepoint / WSS.
Step By Step – Hide the Quick Launch Bar in MOSS 2007:
1 Browse to the home page of a WSS Team Site as a Web Designer or Administrator
2 From the Modify Shared Page smart-menu, choose Add Web Parts and then Browse.
3 Put a Content Editor Web Part on the bottom of the Right Web Part Zone.
4 From the new Web Part’s smart-menu, choose Modify Shared Web Part.
5 Choose the Source Editor… button on the resulting tool pane.
6 Enter:
<style>
.ms-quicklaunch
{
display:none;
}
.ms-navframe
{
display: none;
}
</style>
7 Choose the Save button.
8 In the tool pane, expand the Appearance category and alter the title to read “Hide Quick Launch Bar”.
9 Still in the tool pane, scroll down and choose None from the Frame Style dropdown.
10 At the bottom of the tool pane, choose the OK button.
Written by peter.stilgoe on February 20th, 2009 with no comments.
Read more articles on Moss / Sharepoint / WSS.
