How to easily move / copy list items from one sharepoint list to another
By peter.stilgoe
This method is only available for those running MOSS 2007:
1) Create your blank destination list where you want to move the list items to. If you have a list already setup to accommodate the data you can skip this step.
2) Now goto Site Actions –> Manage Content & Structure
3) Navigate to your source list & select all the items you wish to move or copy
4) Now click on actions & select move or copy
5) Now you will be prompted to choose your destination list, choose this & click OK.
Now your list items will be copied / moved to your destination list whilst retaining all the metadata etc.
More From pstilgoe
Search results return wrong url for list items 1_.000 etc
By peter.stilgoe
When performing searches on MOSS / Sharepoint your list items return invalid URL’s ie.
http://test-server/contacts/lists/contacts/1_.000 or 2_.000 or 3_.000 and so on.
This problem is being caused by our document imaging software from Knowledgelake, during the installation it adds some meta data mappings in the SSP.
To fix this go into your SSP –> Search Settings –> Meta data property mappings and edit the property called ‘path’
The first mapping is the cause of the problem ‘ows_ItemURL(Text)’
Remove this entry.
Reset all crawled content.
Now perform a Full Crawl & list items will now be returned with the correct url’s.
More From pstilgoe
SharePoint Analyzer: Diagnostic Tool for Best Practices
By peter.stilgoe
Bamboo Solutions latest offering appears to be a very useful free tool enabling you to quickly analyse you Sharepoint/MOSS environment right down to patch level:
SharePoint Analyzer is a powerful FREE diagnostic tool to quickly discover the configuration of any SharePoint installation and a critical component for anyone who is looking to incorporate Best Practices into their SharePoint deployment.
Uncover Critical Information about your SharePoint Farm:
• The entire farm topology, from Web applications all the way down to individual lists
• Server information, including patches and updates
• Information on databases that are being used as part of your SharePoint deployment
• Solutions and features that have been deployed, displayed per Web App and Site Collection
• Services and their status
• Information about Bamboo products that are used in your farm
Bamboo Solutions Sharepoint Analyzer
Also there is something similar over at CodePlex Sharepoint Inspector
I have not used either products yet so as always thoroughly test in your test environment before moving to production.
More From pstilgoe
How to get verbose/detailed error messages from your MOSS / WSS servers
By peter.stilgoe
In the ‘web.config’ file of your SharePoint web application, edit the following two entries:
1) Turn custom errors off:
Change the value from “On” to “Off” in a development or staging environment, or to “RemoteOnly” if you have to troubleshoot an issue in a production environment.
2) Enable CallStack & AllowPageLevelTrace
To make the CallStack visible, set the value to “true” also set the AllowPageLevelTrace value to “true”
Note: changing the web.config will cause SharePoint to restart the whole web application immediately after saving.
More From pstilgoe
WSS / MOSS Capacity Planning Tool
By peter.stilgoe
All SharePoint Architects should take a good look at this free tool and use it to first estimate what would be required to support a new production environment and second to assist with the forecasting changes to the production environment.
Download the main program here: System Center Capacity Planner 2007
Download the MOSS / WSS template here: Sharepoint Template
More From pstilgoe
Contacts Management Template by default returns all names beginning with the letter R
By peter.stilgoe
If you have downloaded & installed the Contact Management template from Microsoft you will have noticed for some reason it by default returns all names beginnning with ‘R’
You’l be pleased to know this is easily fixed by editing: http://MYSERVER/contacts/Results.aspx in Sharepoint Designer.
The list of contacts is provided by a Data View web part which contains the following line:
Remove the letter ‘r’ and refresh your page, now no contacts will show up by default.
More From pstilgoe
SSP vs Web Application vs Site Collection vs Site
By peter.stilgoe
Web application
Every Web application is an IIS Web site, so it has it’s own URL (6).
A Web application is for administration of the SharePoint configuration.
When you create a Web application, you make a new IIS Web site(called application pool in IIS), and install WSS 3.0 components in that Web site. This makes it possible for the IIS Web site to store, run, and manage site collecitons.
A Web application is essentially an empty shell with an associated URL. You need a Web application to make a site collection (1).
You need a Site collection and sites to be able to show anything to a user. Each web application can host many Site collections.
Every web application(7):
Runs as a separate IIS website,
Has its own URL,
Has its own content database,
Can have its own authentication method,
Reasons to use more than one Web application on a SharePoint farm:
Because a Web application is actually a website in IIS you have a strict separation of the runtime environment. So if e.g. a webpart gets implemented in http://sandbox1.ourcompany.com and it takes the entire IIS site down then still another Webapplication at http://sandbox2.ourcompany.com remains running and is not affected (Runs as a separate IIS website).
Total size is becoming to large to do backup in reasonable time (Has its own content database),
You have more than one sort of public on this machine: e.g. an external site for the entire world to see, and an intranet (Has its own URL, Has its own content database, Can have its own auth. method).
As a means to separate the users it is not a very good one though from a security point of view(8).
You are stuck to using at least three Web applications: one for Central Administration (for configuring SharePoint itself), one for the SSP- Share Service Provider, and one for the user(-s community). When you make another webapplication we are always referring to the latter: for the users. If you use My Site, be advised to use a separate Web application for that too.
Site Collection
A Site collection is geared towards the company, the people using sharepoint.
A Site collection is a top level site. Sort of like the root in a directoy. You can fill it with both document libraries ‘n such, and from here you can make (sub-)sites, as many levels deep as you like.
Typically you give a site collection to a business process (like sales), or if you are less well organized you give one department a site collection (running into problems when you reorganize).
It is possible to have the contents of a Site Collection stored in a dedicated database. The main reason to do so is you can backup/restore in a reasonable timeframe. Do NOT create a site with a dedicated sitecollection and database for performance reasons, as many databases do not scale well(9).
It is not obvious how to set the contents of a site collection to a certain database however. Of a web application it is.
A bit about jargon:
Either talk about TLS-Top Level Site and subsites, or about site collection and subsites.
Developers often refer to these as the root web and subwebs.
A bit annoying: for programmers the jargon is a bit different from the people doing installing and maintenance.
WFE
A Web Front End is a piece of hardware, it runs the MOSS server that provides the user interface. At the back end it talks with the SQL server where all content is stored. There can be multiple WFE (as well as SQL servers).
SSP – Shared Services Provider
An SSP is to help administrators to keep administration (as much as possible) in ONE place and not on every server.
Suppose you have a webfarm with more than one WFE. Suppose you want to change some setting on team sites, wikis blogs, collaboration or publishing in a general sense. These settings are NOT stored in the database but locally on the WFE itself. So if you change it on one WFE, you must change it on every WFE. SSP does that for you: you change your settings in one place only, and SSP changes all the appropriate settings on the appropriate servers for you.
In other words: An SSP is a collection of farm services (such as profiles, search, audiences, scopes, alerts, BDC, Excel services and usage reporting) that are made available and consumed by the associated Web applications and site collections (3).
A Web application hosting site collections needs to be associated to a SSP: therefore, SSP should be created prior to creating other web aplications(5).
A server farm has at least one SSP. To host the SSP, a web application is required.
The SSP needs at least one Web site for hosting its administraion Web pages. Micosoft recommends a minimum to use two IIS Web sites: one for the SSP pages and another one for the My Site hosting pages(2).
You can have multiple SSP’s on one server farm and even one SSP for multiple farms. Unless you have very good reasons, just stick to one SSP for every server farm.
If you need more than one index server you must use a different SSP for each index server(4).
Application (-server)
In MOSS Jargon an application server is either a MOSS search, index or Excel server.
It has nothing to do with applications in a general sense as we understand them.
WFE, SSP, Web application, Site Collection, site
A WFE (Web Front End) is the hardware, running bits of MOSS.
Because you can have more than one WFE the SSP (Shared Service Provider) helps you out configuring many settings on all of ‘m even though you do it in only one place.
If you have more than one Web application: all webapplications run on every WFE. You cannot distribute webapplications over the various WFE. It would negate the idea of redundancy and load balancing.
The rest has a hierarchical connection:
You need a Web application to run any site collection.
A web application can have multiple site collections.
A site collection can contain many sites, and finally sites can contain many sites, many levels deep.
Every site can contain many lists such as document libraries.
Every list can contain many items, but there are practical limits.
The source for this excellent overview: SSP, Web Application, Site Collection, Sites
More From pstilgoe
Customising sharepoint list forms
By peter.stilgoe
You’re using a custom list as a form to collect data which is made simple in Sharepoint / MOSS as it automatically creates the form for you as you add the required fields / columns to your lists. This is OK but quite alot of the time you find yourself needing more flexibilty with your forms ie. adding notes in between fields, adding navigation & links etc. You’l be pleased to know if you have a copy of Sharepoint Designer this is relatively straightforward to achieve:
1) Open your site in SharePoint Designer.
2) Browse to your newly created list and open the NewForm.aspx web form.
3) Make a copy of this form by going File –> Save As and giving it a new name ie. ‘NewForm-test.aspx’
4) Highlight the ‘default List Form’ Web Part on the page & hit delete.
5) Click Insert > SharePoint Controls > Custom List Form.
6) In the List or Document Library Form box, select the appropriate list, content type and type of form.
7) Click OK and a new Data Form Web Part is added with the controls representing all the fields from the list.
Apply the customisations you require ie. adding in text boxes, adding links etc etc.
9) Now save the form & when you’re happy with it update your links to point to the new form.
More From pstilgoe
How to remove the ‘Phonetic’ fields from your contact forms in Sharepoint / MOSS
By peter.stilgoe
To stop these from displaying in your ‘Contact Forms’ you need to edit your ‘Contact’ content type at Site Collection Level here:
http://site/_layouts/mngctype.aspx
Now you can go through and set the ‘Phonetic’ columns to hidden so they no longer display in your contact forms. I believe the ‘Phonetic’ columns are for Asian support.
More From pstilgoe
K2 Blackpoint recommended specifications
By peter.stilgoe
Computer and Processor Minimum: Server with processor speed of 2.5 gigahertz (GHz) or higher
Recommended: Dual processor, 3 GHz or higher
*32-bit and 64-bit support
Memory Minimum: 1 gigabyte (GB) RAM
Recommended: 2 GB recommended*
*Farm deployment requires 2 GB RAM; 4 GB recommended for SQL and K2 Server
Hard Disk 3 GB of available hard disk
Display 1024×768 or higher resolution monitor
Connection 100 megabits per second (Mbps) connection speed required for farm deployment
56 kilobits per second (Kbps) required for client to server connection
Email Notifications Internet Simple Mail Transfer Protocol/Post Office Protocol 3 (SMTP/POP3)
or
Internet Message Access Protocol 4 (IMAP4)
or
MAPI-compliant messaging software
NOTE: If you are installing a single server environment, it is recommended that you have more RAM and a larger processor in order to have acceptable performance. If you are separating out the components onto multiple tiers, those tiers should be sized appropriately based on usage and performance requirements.
More From pstilgoe
How widely used is SharePoint with Corporate users?
By peter.stilgoe
“Today at the Microsoft Office SharePoint Conference 2008, Microsoft Chairman Bill Gates noted that SharePoint is one of the fastest growing products in the company’s history, having reached the milestone of a US $1billion-dollar business with 100 million licenses sold, and growth of more than 50 percent in the second quarter of the current fiscal year”.
“A recent report by IDC found that 61 percent of users surveyed said they were deploying SharePoint enterprise-wide. Another 28 percent of those using SharePoint in departments today are expected to expand usage to the enterprise within the next 12 months”. [source: Microsoft; IDC]
“Bill Gates showed in terms of growth in revenue, growth in adoption — 100 million users, that’s a phenomenal number. Another number is three-quarters of the Fortune 100 now have SharePoint. That’s just a very impressive number, people seeing the impact that it can have in their businesses, how they do business; just very, very gratifying for us”
[source: Kurt DelBene, Sr Vice President, Microsoft Office Business Platform Group]
More From pstilgoe
How to add Blackberry support for MOSS 2007 & Infopath Forms
By peter.stilgoe
You can add Blackberry support by adding some information to a “compat.browser” file found in the “App_Browsers” folder inside the Sharepoint virtual directory.
Read the post here for the code
More From pstilgoe
Document Management & ECM – Quick facts & figures
By peter.stilgoe
1. Companies spend $20 in labour to file a document, $120 in labour to find a misfiled document, and $220 in labour to reproduce a lost document.
2. 7.5 percent of all documents get lost; 3 percent of the remainder get misfiled.
3. Professionals spend 5 – 15 percent of their time reading information, but up to 50 percent looking for it.
4. The average document photocopied 19 times.
5. There are over 4 trillion paper documents in the U.S. alone and they are growing at a rate of 22% per year (PricewaterhouseCoopers).
6. Corporate users received an average of 18 megabytes (MB) of e-mail per day in 2007; E-mail is expected to grow to over 28 MB per day by 2011.
7. Users send and receive an average of 133 e-mail messages per day (Radicati Group).
8. A single FAX machine costs $6,200 per year (Captaris); the average time to manually FAX a document is 8 minutes.
9. The average cost to send a package via courier service is between $8 and $15.
10. The cost of office space has increased 19% (Office Space Across the World 2008).
More From pstilgoe
MOSS search results all return with the IE document icon and not their correct icon
By peter.stilgoe
That is until we do an iisreset & then they all display with their correct icons, very odd.
Will post more when worked out whats going on !



November 28th, 2008
