FAQ: Microsoft Windows SharePoint Services

FAQ: Microsoft Windows SharePoint Services

FAQ: Microsoft Windows SharePoint Services

This is version 21 of a FAQ that was initially intended for those people with experience of STS 1.0 who are moving to or considering moving to WSS. These people should ignore section O. People completely new to the product can also study it with advantage and *should* (once) read section O.

Please note that this WSS FAQ contains little on 'Programming' WSS. Readers more interested in that are recommended to have a look at Ian Morrish's WSS

Demo site at www.wssdemo.com

.

The FAQ is still very much a work-in-progess. Amendments and additions to the text are being made at regular intervals (other work permitting) - posting of the text version to the newsgroup microsoft.public.sharepoint.windowsservices has now been abandoned but notice of the availability of a new PDF version will given there.

A PDF edition of the latest version (as posted to the newsgroup) is available at this site

(Useful Documents). The wss.collutions.com site text usually contains quite a bit of newer information than the PDF version. However the PDF file is printable !

The initial sections of this FAQ are almost the same as those in the STS 1.0 newsgroup

FAQ, which should make it easier for people who have used that FAQ to follow the changes listed here. New sections have been added for items that require longer answers than the STS 1.0 FAQ generally had. Earlier questions in each section compare the two products - later questions don't bother.

Finally, as always, a FAQ relies on contributions and corrections from other members of this newsgroup. Please post such contributions and corrections to either the newsgroup or a hotmail address I have set up for such mail ( [email protected]

). Note however that requests for help sent to this address will be ignored and should be posted only to the newsgroup.

Thanks to Jorgen Johanson of Norway for supplying some excellent material between version 8 and 9. Thanks also to various Microsoft people for their excellent support in the official beta newsgroups some attributed parts of which can be seen in the text below. Thanks too to the many people who, by posting answers in the newsgroups and giving me permission to use these answers here, have helped the

SharePoint community by making this information more widely available.

Finally what you will not find. You'll find nothing about SharePoint Portal Server 2003

(although most of the items below will also apply to Windows SharePoint Services within SPS 2003). As stated above you'll also find very little code. Code sections tend to be only added here if I understand the code myself (which cuts down the selection drastically) .

1

Note that SharePoint Portal Server has it's own excellent FAQ at www.spsfaq.com

maintained by Stephen Cummins which of course these days is concentrating more and more on SPS 2003.

Mike Walsh,Helsinki,Finland

(blog at http://mikeswss.blogg.de/ which was started on 9th Feb 2003 following e-mail requests)

2

New since version 20

III.18.2 How can I increase the timeout for a web part?

III.51.2 How do I index .rtf files?

III.51.3 How do I index XML files?

III.64.2 I am getting ’#50070: Unable to connect to the database WSSConfigDB on

SqlServer”.What’s my problem?

III.65 How can I stop users from adding content when I don’t want them to?

III.66 How do I create Multiple Workspace Site Definitions?

III.67 How can I make it possible for anonymous users to save their survey responses?

III.68 I’m getting ”Server Error in’/<application name> Application” – what’s my problem?

III.69 How do I edit Link List URLs in Datasheet View?

III.70 How can I enable anonymous users to add, delete or edit files in document libraries?

III.71 How do I see which web parts I am using in a page?

III.72 What code do I need to access an Oracle database?

III.73 In an Issues List, how do I set alerts so that I get an alert only when something is changed in a post assigned to me?

III.74 How do I apply a theme that was created outside my environment?

III.75 We need to specify default.aspx when accessing our WSS sites. What’s the problem?

III.76 When I try to upload a file I get “Form validation error”. What might the problem be?

IV.6.9 How do I hide default site templates?

IV.14 How do I remove the entries for web parts in the Virtual Server gallery BUT keep the web parts?

IV.15 How do I get the logged on user’s display name into a basic page?

IV.16 How do I remove ”Upload Multiple Documents”?

VII.4.1 SPS 2003 and WSS Training – SharePoint Experts Boot Camps

VII.4.2 SPS 2003 and WSS Training – SharePoint Summits

VII.4.3 SPS 2003 and WSS Training – SkillSolve (UK)

VII.5.3 WSS Products - iOra for Microsoft SharePoint

VII.5.4 WSS Products - Workflow Accelerator for SharePoint Technologies

VII.5.5 WSS Products – My Workplace for Outlook

VII.6.1 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003 Unleashed

VII.6.2 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003 : Planning,

Design and Implmentation

VII.6.3 SPS 2003 and WSS Books – Microsoft SharePoint Products and Technologies

Resource Kit

VII.6.4 SPS 2003 and WSS Books – Microsoft SharePoint: Building Office 2003

Solutions

3

Amended since version 20

I.7.1 The basic search function

II.10.2 Why should I perhaps not install WSS to a domain controller?

III.6.4 "Upgrading" from WSS to SPS 2003

III.12.4 Is there any way to have the web part title wrap if it's wider than the column it's in?

III.18.1 What is the default time before a user receives a session timeout error? How do I amend this default? (renumbered)

III.36 How do I transfer a lot of documents to WSS?

III.40 How can a user change his/her password in WSS?

III.50 What workflow approval possibilities are available ?

III.51.1 How do I index OneNote files? (renumbered)

III.54 I cannot import from Excel 2003 to WSS. What's the problem and solution?

III.64.1 I am getting "#50070: Unable to connect to the database STS_Config?". What's my problem? (renumbered)

IV.5 How can I apply new (whole-site) Themes? (renamed)

Removed since version 20

Mike Walsh (WSS/STS MVP), Helsinki, Finland

4

Contents

O. Introduction to Windows SharePoint Services

I. General

I.1 What are the Operating Systems Requirements?

I.2 What is the Relationship to SharePoint Portal Server 2.0?

I.3 What is the Relationship to Office?

I.4 What is the Relationship to FrontPage?

I.5 What is the Relationship to MSDE and SQL Server?

I.6 What is the Usage of MSDE and SQL Server?

I.7 How does the The Search Function work?

I.7.1 The basic search function

I.7.2 Adding file types to the indexing routines needed for the search

I.7.3 Can you tell me how an SQL Search is performed ?

I.7.4 Which things are covered by SQL Searching ?

I.7.5 Why are SQL search results grouped in sets of only five items ?

I.7.6 How do I ensure that .pdf files are included in the Search function?

I.7.7 What is the scope of a search?

I.8 What are Virtual Servers?

I.9.1 How does Version Control work?

I.9.2 When is a new version created ?

I.9.3 Can I restrict the number of versions ?

I.10 How are the Help files organized?

I.11 Which Languages are available?

I.12 What can you tell me about Document Libraries?

I.12.1 Document Library - Content

I.12.2.1 Document Library - Alerts - Subscribing to

I.12.2.2 Document Library - Alerts - Amending the text

I.12.2.3 Document Library - Alerts - Rights needed

I.12.2.4 Document Library - Alerts - Can an Administrator create Alerts for others?

I.12.3 File Types you can't upload

I.13 What can you tell me about Lists?

I.13.1 Lists - Content

I.13.2 Lists - Attachments

I.13.3 Lists - Limits in the number of fields per list

I.13.4 Lists - Limits in the size of fields per list

I.13.5 Lists - What graphics formats are supported for Thumbnail creation in a Picture

Library?

I.14 What Browsers are supported?

I.14.1 Supported Browsers - General Information

I.14.2 Supported Browsers - Web Parts

I.15 Can I amend Error and other System Messages?

I.16 Do I see Different views of the information for different users?

I.17 How does WSS use Web Parts ?

5

I.18 How does WSS handle Roles?

I.19 What limits are there for the number of sites for particular set-ups?

I.20.1 What doesn't work when using Office XP?

I.20.2 What doesn't work when using Office 2000?

I.21 How do I find out about the usage of my site ?

I.22.1 What are the differences between standalone WSS and the WSS in SBS 2003?

I.22.2 What are the differences between standalone WSS and the WSS in Project Server

2003?

II. Installation

II.1 On what Media is the product delivered?

II.2 What are the Licensing requirements?

II.3 Are there any Differences in basic installation procedures?

II.4 Where are files located?

II.5 What are the URLs of sites; subwebs etc.?

II.6 Can I install WSS on a server running other applications?

II.7.1 Can I run WSS under VMWare?

II.7.2 Can I run WSS under MS Virtual Server?

II.8 How can I access my WSS Server from XP Pro?

II.9 Is there anything extra I should be aware of if I have upgraded my server from Win

2K Server to Win 2003 Server?

II.10 WSS and Domain Controllers

II.10.1 Can I install WSS to a domain controller?

II.10.2 Why should I perhaps not install WSS to a domain controller?

II.11 Too large documents

II.11.1 My multiple document uploads are failing because they are too large. What's the solution?

II.11.2 My uploads of (single) very large documents are failing. What is the problem?

II.11.3 My packaging of a large WSS site in FP 2003 is failing. What's my problem?

II.12 How do I enable Session State?

II.13 After installing WSS I get "cannot to the configuration database" when trying to access WSS. What is the solution?

II.14 Where do I get the language packs for the WSS Beta2 Tech Refresh?

II.15 Can you install Class Server and WSS on the same server?

II.16 Can I migrate STS 1.0 sites that have customized schema files to WSS?

II.17.1 How do I install WSS so that WMSDE is located at a non-default location?

(Single server)

II.17.2 How do I install WSS to use an existing copy of SQL Server instead of WMSDE?

(Single server)

III. Administration

III.1 How do I change Time and Date styles?

III.2 Are there any Differences in Authorization?

III.2.1 Authorization - Are there differences with anonymous access ?

6

III.2.2 Authorization - Are there differences in the kinds of user that can be allocated to a site?

III.2.3 Authorization - Are there differences in the specification of a local (server) user?

III.2.4 Authorization - Are there differences in the specification of a domain user?

III.3 When do I run Server Health?

III.4 What can you tell me about Logging?

III.5 What are the rules for Naming Sites and Document Libraries?

III.5.1 Relation to directory names

III.5.2 Forbidden characters

III.5.3 How can I change a site name?

III.6 What can you tell me about Migration?

III.6.1 Site Migration from STS to WSS

III.6.2 List Migration from WSS to WSS

III.6.3 Site Migration from WSS to WSS

III.6.4 "Upgrading" from WSS to SPS 2003

III.7.1 How do I 'check out' and 'check in' a document in WSS?

III.8 Can I provide the same content to both an Intranet and an Extranet Site?

III.9 I've forgotten which port I need to use when I administer my site. What is my administration port number ?

III.10 I am getting an error saying that I need to remove FrontPage Server Extensions or

SharePoint Team Services 1.0. How do I do this ?

III.11.1 How do I list the sites in a Virtual Server?

III.11.2 How do I list all the subwebs in a site?

III.11.3 How do I delete a Meeting Workplace?

III.12.1 Where can I get Web Parts from ?

III.12.2 How do I remove a web part ?

III.12.3 A web capture web part that accesses information from an external site requires action from me. How can I avoid this?

III.12.4 Is there any way to have the web part title wrap if it's wider than the column it's in?

III.12.5 What is the difference in using the Page Viewer Web Part to display web pages and using the Web Capture Web Part?

III.13 How can I make a field read-only?

III.14 I can't customize any lists (but I can make other site changes). What is my problem?

III.15 What are the minimum rights a user needs in order to be able to create a Personal

View?

III.16 I get a proxy server error when I try to import a Web Part. But I don't have a proxy server. What's the solution?

III.17 How do I integrate IM icons into WSS?

III.18.1 What is the default time before a user receives a session timeout error? How do I amend this default?

III.18.2 How can I increase the timeout for a web part?

III.19 What do I have to do to make it possible for a user to be able to use FTP to upload documents to a document library ?

7

III.20 Is it possible to specify the maximum number of versions of a document in a document library?

III.21 I get ""HTTPException (0x80004005) Debugging is not supported under current trust level settings". What do I need to do to activate debugging?

III.22 Does WSS support Digest Authentication or Advanced Digest Authentication?

III.23 I get "Server Error in 'uddi' Application". How do I solve this?

III.24 I get "Access Denied" or "Cannot Complete This Action" when accessing a WSS site. What might be my problem?

III.25.1 Why am I being prompted for Authentication many times when I open an Office document in WSS?

III.25.2 Why are my domain users continually prompted for name/password?

III.26 My log files aren't being stored where I specified. What's going on?

III.27 I can't edit pictures in the Picture Library - what's the problem?

III.28 How can I tell if WSS is in AD Account Creation Mode?

III.29 What third-party Virus tools are available for WSS?

III.30 Search isn't working - what could be the reason?

III.31 Why do I have to re-enter my credentials after using the site for a while?

III.32 Why aren't changes I've made in the base template propogating?

III.33.1 I can't run smigrate locally on my server - what might be my problem?

III.33.2 How do I use smigrate to move sites with spaces in their names?

III.33.3 What is the difference between using smigrate to backup a site and using stsadm?

III.34 I can never get the formulas in a Calculated Field right. Where can I get Help with this?

III.35 How do I restrict access to a document library?

III.36 How do I transfer a lot of documents to WSS?

III.37 After upgrading from WMSDE to SQL Server 2K I can't install SP3 and Search doesn't work. Why?

III.38 How do I restore a (WSS) SQL Server backup to *another* server?

III.39 I get "Can not add the user because a user with that name already exists." How do I add the user?

III.40 How can a user change his/her password in WSS?

III.41 Why can't I synchronize certain properties between a WSS document library and

Microsoft Word?

III.42.1 I have added a list template to the list template library but it is not available to my

Create. What's the problem?

III.42.2 I can't find how to add a list from a list template to my site. Can you help?

III.43 Why can't I specify anonymous access to my WSS web site? (It's greyed/grayed out)

III.44 I get "Data Source does not contain valid XML Data" when adding a WSS List with Data View. What's my problem?

III.45 I've just installed a third-party web part, but it's not listed on my site. What's the problem?

III.46 How can I recover individual documents to my WSS site?

III.47 Why can't I see the link for "Manage Access Requests" in my top-level admin?

III.48 How do I add a Back button to my WSS Menu Bar?

III.49 Are there any other filter parameters for a List View than [Me] and [Today]?

8

III.50 What workflow approval possibilities are available ?

III.51.1 How do I index OneNote files?

III.51.2 How do I index .rtf files?

III.51.3 How do I index XML files?

III.52 I need to recreate my site utilizing a new site architecture. How can I do this without deleting all of the sites?

III.53 How do I programmatically upload a document?

III.54 I cannot import from Excel 2003 to WSS. What's the problem and solution?

III.55.1 Alerts aren't working even if the Timer Service is running. What might be wrong?

III.55.2 Can an Administrator create Alerts for others?

III.56 How do I avoid seeing an old document version after doing Edit in MS Word?

III.57 How can I get OCR Indexing of TIFFs in WSS?

III.58 I have several hundred web parts. Browsing and clicking Next takes forever. How can I get to a web part quicker?

III.59 How can I make the link between Web Part Connections a dropdown list rather than the standard radio buttons?

III.60 How can I make text in a Multiple Line Field Type a Hyperlink?

III.61 How do I prevent users from Editing my WSS sites with FrontPage?

III.62 How can I enable Outlook to see a WSS workspace as a valid repository for shared attachments?

III.63 How can a user be automatically e-mailed that a task has been assigned to him/her?

III.64.1 I am getting "#50070: Unable to connect to the database STS_Config?". What's my problem?

III.64.2 I am getting ’#50070: Unable to connect to the database WSSConfigDB on

SqlServer”.What’s my problem?

III.65 How can I stop users from adding content when I don’t want them to?

III.66 How do I create Multiple Workspace Site Definitions?

III.67 How can I make it possible for anonymous users to save their survey responses?

III.68 I’m getting ”Server Error in’/<application name> Application” – what’s my problem?

III.69 How do I edit Link List URLs in Datasheet View?

III.70 How can I enable anonymous users to add, delete or edit files in document libraries?

III.71 How do I see which web parts I am using in a page?

III.72 What code do I need to access an Oracle database?

III.73 In an Issues List, how do I set alerts so that I get an alert only when something is changed in a post assigned to me?

III.74 How do I apply a theme that was created outside my environment?

III.75 We need to specify default.aspx when accessing our WSS sites. What’s the problem?

III.76 When I try to upload a file I get “Form validation error”. What might the problem be?

9

IV. Basic Customization

IV.1 How do I customize the Quick Launch section of the main page?

IV.2 How do I customize the main section (centre/right) of the main page?

IV.2.1 General Customization of the main section

IV.2.2 Customizing the look of Document Libraries in the main section

IV.3 How do I add Icons?

IV.4 How can I add Images?

IV.5 How can I apply new (whole-site) Themes?

IV.6 How can I create and use New Templates?

IV.6.1 How do I create a Template?

IV.6.2 How do I make a template available globally?

IV.6.3 How do I view the templates I have in a global catalog?

IV.6.4 How do I create a new site on a virtual server with a particular template?

IV.6.5 I have created a template from a site where roles were defined. How can I preserve the roles when I create a site using this template?

IV.6.6 What is the maximum size for a site template ?

IV.6.7 What is the maximum size for a list template ?

IV.6.8 How do I remove a list template?

IV.6.9 How do I hide default site templates?

IV.7 How do I build into a WSS web page the contents of another Web Site ?

IV.8 WSS unlike SPS 2003 doesn't have "My Site". Can I simulate this in WSS?

IV.9 How do I add Hyperlinks to an Announcements List?

IV.10 How do I remove the Sharepoint toolbar (new/edit/delete item) from dispform.aspx of a list?

IV.11 How do I set "Overwrite existing file" off by default?

IV.12 How do I make only database rows with different keys visible in a WSS web part?

IV.13 How do I use the Search Form from the default page on another page?

IV.14 How do I remove the entries for web parts in the Virtual Server gallery BUT keep the web parts?

IV.15 How do I get the logged on user’s display name into a basic page?

IV.16 How do I remove ”Upload Multiple Documents”?

10

V. Interaction with Office Products (details)

V.1 How does Outlook interact with WSS?

V.1.1 Outlook Interaction - Contacts

V.1.2 Outlook Interaction - Attachments

V.1.3 Outlook Interaction - Meetings

V.1.3.1 Outlook Interaction – Meetings - From Outlook

V.1.3.2 Outlook Interaction – Meetings - From WSS

V.1.4 Outlook Interaction - Saving E-mail messages and attachments in WSS

V.1.4.1 Outlook Interaction - Saving only E-mail messages in WSS

V.1.4.2 Outlook Interaction - Saving only E-mail attachments in WSS

V.1.4.3 Outlook Interaction - Saving both E-mail messages and attachments in WSS

V.2 How does Word interact with WSS?

V.2.1 Word Interaction - General interaction (New document; Edit Document etc.)

V.2.2 Word Interaction - Propogation of Word Properties

V.3 How does Excel interact with WSS?

V.4 How does Access interact with WSS?

V.5 How does InfoPath integrate with WSS?

V.5.1 InfoPath Interaction - Can I create a drop-down control on an InfoPath form that gets it's values from a SharePoint List if online or saved in a form if off-line ?

V.5.2 InfoPath Interaction - Can InfoPath forms be used both to add data to a WSS list

(forms library) and to reference data from an existing list?

V.5.3 InfoPath Interaction - Can InfoPath publish to Sharepoint, but NOT require

InfoPath to edit the form?

VI. Tutorials

VI.1 How do I synchronize Contacts?

VI.2 Details on Templates

VI.3 Customizing the Home Page

VI.4 Using Web Part Connections

VI.5 The Data View Web Part in Front Page 2003

VI.6 The Form Web Part

VI.7 How to save a Document Library as a template that with content is greater than 10

MB in size

VI.8 The Company Web in SBS 2003

11

VII Documents and Web Sites

VII.1.1 General Documents

VII.1.2 Web Part Documents

VII.1.3 Some IIS 6.0 Documents (and tools)

VII.2 Web Sites

VII.3 Web Hosting for STS/WSS sites

VII.4.1 SPS 2003 and WSS Training – SharePoint Experts Boot Camps

VII.4.2 SPS 2003 and WSS Training – SharePoint Summits

VII.4.3 SPS 2003 and WSS Training – SkillSolve (UK)

VII.5 WSS Products

VII.5.1 WSS Products - SmartLibrary

VII.5.2 WSS Products - Scene7 for SharePoint Portal Server 2003

VII.5.3 WSS Products - iOra for Microsoft SharePoint

VII.5.4 WSS Products - Workflow Accelerator for SharePoint Technologies

VII.5.5 WSS Products – My Workplace for Outlook

VII.6.1 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003 Unleashed

VII.6.2 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003 : Planning,

Design and Implmentation

VII.6.3 SPS 2003 and WSS Books – Microsoft SharePoint Products and Technologies

Resource Kit

VII.6.4 SPS 2003 and WSS Books – Microsoft SharePoint: Building Office 2003

Solutions

12

O. Introduction to Windows SharePoint Services

I have received mail saying that it would be useful if newcomers to Windows SharePoint

Services (WSS) (i.e. those who have not used the predecessor product SharePoint Team

Services (STS)) were to receive some background information on the product. So here it is. This is of course my own opinion and based on things I have heard as well as my own experience both with the STS and WSS products and with my acquired experience through writing the STS and now the WSS newsgroup FAQs. (The historical intro has been written based on what MS people have said in newsgroups and presentations)

The history of STS in brief is that a group inside Microsoft decided to create a portal site that would cover the main needs of a workgroup or small department (maybe the original intent was just for their department, I don't know). The software was built on the basis of

(but extending) FrontPage Server Extensions because these were Office group people.

The software was implemented in one (or more?) departments and by word-of-mouth spread through Microsoft like wildfire. Previously outside consultants had been employed to create "local" web sites; these took much longer to implement; required more maintenance; and of course cost more than this new internally-made portal.

At some point this internal product was converted into a named product called SharePoint

Team Services - one of those cases where it was felt that adding a product to an existing

"family" was a good idea, although STS had little to do with the existing enterprise product SharePoint Portal Server (SPS).

What was the reason that the use of what was to become STS spread so quickly within

Microsoft ?

-------

1. It was a ready-made site that could be implemented in hours and would run out-of-thebox on normal-sized PCs, yet could be customized and extended for the use of larger groups.

2. It contained mini versions of most of the things that a small department or workgroup would need.

3. Adding users to the site and giving them rights was simple.

Ready-made site / Extended

STS could be installed on a single server and in it's minimum version included the use of

MSDE. SQL server 7.0 and SQL Server 2000 were optional database systems for the single-server version but could also be used as database systems for the dual server version (one server for the site and documents; the other for the database).

13

Mini Versions

In addition to the key document library and custom library functions (for storing and organizing documents), there were also Information Board(s); Discussion Board(s); and

Contact List(s)

[FAQ writer's note: my sites rarely used these and concentrated on the document storage aspect - reckoning that the ability to locate documents was more important than recreating things that could be done in Outlook]

Authentication

There were two kinds of users - domain users, who just needed to be specified to the site

(or particular area of the site) and local users (who when created within STS would be created as users local to the STS server AND would be given rights to the STS web site.

Subwebs could either have the same rights as the higher-level site or could be defined as having their own users.

---------

Now what about WSS ?

One of the recommended uses for STS was for a project group.

The project would form; the project leader would ask the STS administrator to create a web site for the project and the project would post all its (external) source documents and

(internal) papers to the web site. It would use the site for internal Project announcements and would perhaps (if people were located over a wide area) would use the discussion function. Nice and easy.

The main problem from the point of view of the administrator was that while creating a standard site was easy; most project groups wanted customization when they ordered the site from him/her and this customization often mean both FP UI-look changes but also changes to the standard templates. With only one set of templates per server this often caused problems - many project groups could use the same server from the server load point of view but the one set of templates per server meant that changes made for one group spread to other groups (usually when they added subwebs).

With WSS a lot of these problems disappear. a) the project group now generates its own WSS site

[The first meeting of the project group is announced and participants are listed. On sending, the project leader is asked if he/she wants to create a WSS site for the project; if yes, the list of participants to the meeting are given rights to the site.]

14

b) on generation of the WSS site, a number of different templates can be selected from. c) creation (by the administrator) of new templates is much easier than before.

(Similar things happen with a Document Workspace)

There are of course many improvements to the user interface; to the fields that can be used in libraries and the way lists can be output; much much greater extensibility etc. etc.

But for me the key thing to remember is that WSS builds on a product that was so usable that its use spread throughout a major software company without any official encouragement to use it. WSS is just more of the same - a low cost and quick way to create web sites that are genuinely useful to their users yet need little maintenance from administrators.

Now on to the rest of the FAQ where I hope that you'll get some useful answers on how

WSS works in detail.

15

I. General

I.1 What are the Operating Systems Requirements?

Unlike STS 1.0 which worked on several operating systems - even if it in production tended to be installed on a Windows 2K Server variant, WSS will only work on .Net

Server and in particular all versions of .Net Server except the Web Edition.

Jorgon Johanson of Norway send me however a lot of detail on using WSS with the Web

Edition including the following.

'According to Microsoft WSS will run on the Web Edition, but there are two catches

Catch 1 - The Web Edition can NOT host the database.

"You must use the remotesql=yes parameter to install Windows SharePoint Services Beta

2 on Windows Server 2003, Web Edition. For more information about installing

Windows SharePoint Services Beta 2 to work with Microsoft SQL Server 2000, see

Remote SQL Server Deployment."

Catch 2 - The Web Edition may be difficult to get hold of.

"It (The Web Edition) will only be distributed through selected partner channels and will not be available for retail. Service providers should visit the Microsoft Service Providers

Web site for more information."'

I.2 What is the Relationship to SharePoint Portal Server 2.0?

SharePoint Portal Server (SPS) 1.0 and SharePoint Team Services (STS) 1.0 were two separate products that confusingly shared the same name and had limited interaction (and that, only in one direction after both Service Pack 1's came out when SPS could also include information stored in STS in its searches).

SPS 2.0 is built on top of WSS. As such it now adds additional functionality rather than it being a completely separate product.

Here is a list of the extra functionality in SPS 2.0 as provided in the SPS newsgroup by

James Edelen

Enterprise Search (multiple content sources)

Audiences

User Profiles

My Site

Farm Scaling

Enterprise Application Integration Framework / Single Sign-on

Central Site Manageability

16

Areas (Taxonomy for Documents, sites, etc.) and as I didn't know what "Taxonomy" meant either, I looked it up - "classification, especially in biology" (Concise Oxford)

I.3 What is the Relationship to Office?

STS 1.0 had certain functions (such as Open Document) that relied on the presence of

Office XP in the client workstation. However most functionality was available to Office

2K (and Office 97?) users.

Users of Office who didn't have STS 1.0 installed had full Office functionality available.

With WSS *administrator* functions are only available to users with Office 2003 installed on their clients. Thus for instance FrontPage 2003 is essential for site amendments.

Users of Office 2003 get full functionality only if they have WSS installed.

One part of full functionality is the opening up in for instance Excel of a WSS Document

Workspace where documents from selected WSS document libraries are listed; can be amended and additional documents can be uploaded to them from within Excel.

Note: See also section V where this Office / WSS relationship is dealt with in detail

I.4 What is the Relationship to FrontPage?

Just as FrontPage XP could be used for a certain amount of basic customization with STS

1.0, so FrontPage 2003 can be used for similar customization with WSS.

The use of back versions of FP is not possible in connection with a WSS site.

In STS 1.0 it was dangerous to amend certain of the template and similar files with FP. It is unknown (but likely) whether this is the case with WSS.

I.5 What is the Relationship to MSDE and SQL Server?

STS 1.0 used as default MSDE 1.0 and also worked with both SQL Server 7.0 and 2K.

WSS uses as default MSDE 2K and ONLY works with SQL Server 2K not 7.0.

Note that in order for SQL Server 2K to work on a Windows 2003 Server it (SQL Server) must use Service Pack 3 or later.

Note also that some functionality (see below I.7) is not available with MSDE 2K.

17

Note: A little known fact is that the version of MSDE used with WSS (called "WMSDE") is not the same version of MSDE as that used by SPS v2.

WMSDE, whose use is restricted to Windows Components (in this case WSS), has a different product code in which the 5 concurrent users (then a slowdown in performance) limit from MSDE 1.0 has been removed as has the 2GB limit in the size of the database that was also present in MSDE 1.0.

Both these limits are still contained within the MSDE version that is used by SPS v2.

Finally, note (**SPS v2 only**) that if you are installing onto a Domain Controller,

MSDE is not available as an option.

I.6 What is the Usage of MSDE and SQL Server?

STS 1.0 stored documents in the File system while the database contained information on the location of the documents.

WSS stores documents in the database.

I.7 How does the Search Function work?

I.7.1 The basic search function

In STS 1.0 the search function (as provided by MS) searched only in documents.

In WSS the built-in search function now searches on the contents of both documents and lists.

In STS 1.0 the search function was always available no matter what database was used.

In WSS the search function is no longer available for sites with MSDE 2K unless they also have SPS 2.0 (SharePoint Portal Server 2.0) installed.

(The options are SQL Server searching or SPS 2.0 searching. SPS 2.0 searching works where the WSS database is either SQL Server 2K or MSDE 2K; SQL Server searching works only where the WSS database is SQL Server 2K. MS recommend SPS 2.0 searching for very large sites)

Note:

Ian Morrish

has developed a solution for being able to search a single SharePoint list. See http://www.wssdemo.com/pages/search.aspx for this.

18

I.7.2 Adding file types to the indexing routines needed for the search

In STS 1.0 adding file types to the indexing routines required very difficult adjustments.

The only company which provided a routine for this was Adobe who provided a routine that both added an icon for .pdf files (as IV.2) and added .pdf files to the types covered by the search. Otherwise the only option was to allow indexing of *all* file types.

(Recently a Visio filter - untested by this user - has become available from Microsoft for searching Visio files).

In WSS indexing is SQL Searching or SPS Searching (see I.7.1). Details on file types covered and how to add additional file types will be available later.

I.7.3 Can you tell me how an SQL Search is performed ?

When you search WSS sites with SQL Searching, the search is performed by using a

FREETEXT statement.

Using FREETEXT allows searching by intent; all terms are 'stemmed' or in other words the query looks for all inflectional forms of each query term.

For instance, if you query for "swim", the query also returns results including "swam";

"swimming", and so on.

If you want more information on what is possible using FREETEXT look at SQL Books

Online.

(Thanks to Jerry Orman who provided the basic information in this text)

I.7.4 Which things are covered by SQL Searching ?

Full information is in the Admin Guide. Here are some basic facts

Searched

List items

Documents

Lists

Possibly searched

File types other than .doc, .xls, .ppt, .txt, and .htm

These need customized SQL Search search filters to be included in searches.

Not searched

19

Non-text list fields (such as currency, number, lookup, Yes/No)

Attachments to lists

File Properties used by Office 2003 documents (such as "Author" and "Company")

Survey Lists

Hidden Lists

Other things you can't do

Boolean searches

Display the number of matching items

(Thanks again to Jerry Orman for pointing out the Admin Guide and giving the above in a different form)

I.7.5 Why are SQL search results grouped in sets of only five items?

The search results page is divided into two sections - list items and document items.

This is to avoid a situation in which only documents are selected by a search (because of the number of times the search word appears in a document).

Because there are thus potentially a number of list items AND a number of document items selected it was decided that the most suitable number of list items and documents per page would be five (each) - i.e a possible total of ten.

I.7.6 How do I ensure that .pdf files are included in the Search function?

The first step would be to ensure that .pdf files are included in the list of acceptable file types (see I.12.3 File Types you can't upload) as otherwise you won't have any .pdf files in your WSS system that you can index.

Secondly, you should add the Adobe IFilter to the server running the copy of the database that WSS is using.

This IFilter can be found on the Adobe site and is an .exe file that automatically sets up your site to be able to index .pdf files.

Finally you should be aware that .pdf files are only indexed that are added to your WSS site after the Adobe IFilter has been installed. In order to get round this problem you should re-upload the files that were on the site before the Adobe IFilter.

(although see below * )

(Thanks to Bobby Ma for this final piece of the puzzle)

20

There's also a Microsoft article on SQL Server Full-Text Indexing with the Adobe IFilter that might be useful. http://support.microsoft.com/default.aspx?scid=kb;en-us;323040

Note the following address for the Adobe IFilter which might prove successful when http downloads aren't ftp://ftp.adobe.com/pub/adobe/acrobat/win/all/ or http://www.adobe.com/support/salesdocs/1043a.htm

which is the latest (24 Nov 2003) working Adobe http link.

*

Ian Morrish

posted the following comment

I have seen it mentioned that if you already have PDF files in a document library and then add the Adobe iFilter you have to re-add the documents to the library before they will be indexed. Fortunately this is not true. SQL Server has some system stored procedures to manage indexing.

Use SQL Query Analyser to run the following command (after installing your iFilter)

USE Name_of_your_WSS_content_db

EXEC sp_fulltext_catalog 'ix_STS_servername_xxxxxx', 'rebuild'

You will find the correct string for 'ix_STS_servername_xxxxxx' by using SQL Server

Enterprise Manager. Expand the WSS content database and click on Full-TextCatalogs.

No restart of any services was required for me to be able to search on PDF contents.

I.7.7 What is the scope of a search?

Search in WSS is scoped to a site (what in STS was a "subweb").

So if you do a search on a Main Site, it will return results only from the top level Site and not from any lower-level sites that are under it in the structure.

(Adapted from a message from Iyaz)

21

I.8 What are Virtual Servers?

In STS 1.0 Virtual Servers could either be created by specifying a new TCP-IP address or by the use of (Front Page) host headers.

In STS 1.0 all Virtual sites retained the look and feel etc. of the main site as defined in the single set of templates for that STS installation.

In WSS it is easier to define Virtual Servers. It is also possible for each virtual site to have several main WSS sites (and naturally below them several subwebs).

In WSS a Virtual site can be configured differently to the main site (and to other Virtual

Sites).

I.9.1 How does Version Control work?

STS 1.0 had "version control". It wasn't. It simply meant a *very basic* read-only function that most site administrators turned off. In order to have true versioning of documents, administrators needed to buy and install Visual Source Safe (which worked well with STS 1.0)

WSS now does have true version control - that is both versioning and check-in/check-out.

I.9.2 When is a new version created?

Unfortunately (in my opinion) a new version of a document is created every time

*anything* changes in connection with the document.

In other words if you have an attribute for the document that changes its value from

"Windows" to "Windows 2003" then a new version of the document is created.

Versions thus do not only reflect changes to the text of the document.

Note too that if you update several lines in Datasheet View you can in fact cause more versions than you expect.

If you amend all the fields in one line (record), then it seems you create one new version.

If however you first use copy/paste for the same field (column) in several lines (records) and then repeat this method for another field, you create more than one version for each of the records you've amended.

Thanks to Thierry Masson for pointing this out.

Lars Burk sent me this clarification on how versioning in Word (for instance) works. I this case there is only one new version per session.

22

Once a Word (or in fact any other office file) file is opened in edit mode from a document library, a new session is opened. Upon the first "save" action, a new version appears in the document library. Until the session of the MS application is finally closed all "save" actions do not create new versions of the particular document. Only the new "edited time stamp" increases accordingly.

I.9.3 Can I restrict the number of versions?

No.

The number of versions just goes up and up !

If you want to control the number, the only way at present is to delete versions you don't want to keep.

I.10 How are the Help files organized?

STS 1.0 had very basic Help files provided by Microsoft.

WSS allows the administrator (and others, if he/she so desires) to both amend the existing help files and add new ones (see *).

Unlike the help file supplied with beta-1 which was just as basic as that provided with

STS 1.0, the WSS RTM help file contains some good text (some of which seems to have been borrowed from early versions of this FAQ!).

* The existing help files are Copyrighted by Microsoft.

Initial feedback from Microsoft during the Beta process was that it is likely that additional links (to own help files) may be allowed from the main Microsoft help page but that no other changes may be made to the Microsoft-provided help files.

If taken to this extreme, this would greatly reduce the additional functionality of allowing users to amend and add their own help files.

However as yet, no change in this restrictive policy has been indicated by Microsoft.

23

I.11 Which Languages are available?

On an STS 1.0 Server only one language was possible (one per server).

On an WSS Server several languages are possible (one per site).

STS 1.0 was available for the same languages as WSS see below (minus Hindi ? - the list produced in August 6 2001 does not include Hindi) with the same languages being fully translated.

WSS is available for the following languages

- fully translated (="Localized"):

Arabic; Czech; Danish; Dutch; English (British, US); Chinese (HK, Simple, Traditional);

Finnish; French; German; Greek; Hebrew; Hungarian; Italian; Japanese; Korean;

Norwegian; Polish; Portuguese (Brazilian, Portugal); Russian; Spanish; Swedish; Thai;

Turkish

- not translated but local language(s) may be used (="Enabled"):

Bulgarian; Croatian; Estonian; Hindi (with Indic); Latvian; Lithuanian; Romanian;

Serbian; Slovak; Slovenian; Ukrainian

"Enabled" has been described as follows - "When a site is enabled, the UI is in English.

Anywhere a user can enter text in the interface of an STS site will allow the user to input the enabled language." Or, I suppose, you can use the alphabet of your language.

I.12 What can you tell me about Document Libraries?

I.12.1 Document Library - Content

In STS 1.0, a Document Library consisted of one (folder-)level of documents. The appearance of sub-folders was simulated by the use of Views where the types of documents were divided up into groups on the basis of the contents of one or more

(custom) fields.

In WSS, Views are still available just as in STS 1.0, but in addition it is now possible to also have sub-folders of a document library. The document library maintainer can thus use either or both techniques whichever is more suitable for the particular type of documents.

(A two-level off-line copy of a web site for instance would be very suited to the subfolder technique for instance. A set of documents from different sources would perhaps suit more the View approach)

24

In WSS Views also incorporate new options such as

Group By

Totals

Styles

Folders

In particular Group By could be used as a further way of simulating sub-folders.

I.12.2.1 Document Library - Alerts - Subscribing to

In STS 1.0 it was possible for a user to subscribe to a document library so that he/she would be notified whenever a change was made to the document library.

In WSS it is possible to subscribe to documents and thus receive notifications at document level.

I.12.2.2 Document Library - Alerts - Amending the text

In STS 1.0 it was not possible to amend the text of Alerts because they were a .DLL file.

In WSS it is possible to modify the content and format of Alerts about changes to list items.

You do this by customizing XML files in the ...\Template\XML directory.

(For full details see the WSS SDK under the heading "Customizing the Message Text for

Alerts")

I.12.2.3 Document Library – Alerts – Rights needed

This is hidden away in the Alerts section of the Admin Guide, but has been asked in the newsgroup so is quoted here.

A user must have the View Items right (included in the Contributor site group by default) to sign up for alerts.

I.12.2.4 Document Library – Alerts – Can an Administrator create Alerts for others?

In the product as delivered by Microsoft, the only people who can create Alerts are the people for whom the Alert is intended.

So Administrators can not create Alerts for anyone other than themselves.

Jan Tielens

has however created a (free) web part that allows Administrators to create

Alerts for other people.

25

You'll find it at http://weblogs.asp.net/jan/archive/2004/02/12/72079.aspx

I.12.3 Document Library - File Types you can't upload

In STS 1.0 you could upload to a document library any file you liked. This obviously had the drawback that you could upload a script (say) and by clicking on it start it carrying out its functions. The usual way round this was for the Administrator to request that such

"dangerous" file types (scripts, exes etc.) should be zipped and then the zip file uploaded to the document library.

In WSS there is a set (long) list of file types that can not be uploaded to a document library.

This file () can of course be amended by the administrator - usually I suspect to reduce the list of restricted file types rather than to increase the number. As I wrote enough the default list is *very* long.

The file is ....60/CONFIG/DOCEXTFL.XML

To change the list of non-uploadable files you can either amend the file itself (and probably do IISRestart to make it work) or you can use the User Interface as follows (the example being removing chm files from the list).

1. Open SharePoint Central Administration

2. Under Security Configuration, click Manage blocked file types

3. Remove the line for CHM and click OK

Note: If you are migrating a site that contains documents which are blocked by WSS, these documents will not be migrated to the new server.

I.13 What can you tell me about Lists?

I.13.1 Lists - Content

In STS 1.0, the List consisted of the data you entered into it. This data could not be formatted per item but only per List. (i.e. you could specify for all the items in the list that the field XXX should be 'Ariel Bold 14 Red', but you couldn't specify that a particular item should contain somewhere 'Ariel Bold 14 Red' text.

In WSS, the data entered for a particular item can be formatted (even individual words or groups of words).

26

Note: This only works for Lists but not for Document Libraries and also only works there for Multi-line fields.

I.13.2 Lists - Attachments

In STS 1.0 no attachments were possible. The nearest you could come to this was to move a document to a document library and - having created a new Hyperlink field for the list - add a link to this document.

In WSS attachments to an item in a List are supported.

Note: Attachments are not searched unless SPS Search is being used.

Note2: Attachments are not supported in Document Libraries; Picture Libraries and

Surveys.

I.13.3 Lists - Limits in the number of fields per list

Limits on the number of fields in a list in STS 1.0 are unknown to this author.

The limits in WSS for lists are as follows

There is a maximum of 64 text fields per list. Text fields are fields of the following types

"single line of text"

"Choice"

"Hyperlink" (each takes up 2 text fields in the database)

"Picture" (each takes up 2 text fields in the database)

Note that Multiline Text fields are not text fields in the above sense.

Other limits per field type per list are as follows (note that similarly to text fields, number-type fields (Number and Currency) are restricted to 32 *in total* per list)

Multiline text fields - 32

Number or Currency Fields - 32

Date/Time Fields - 16

Lookup Fields - 16

Yes/No Fields - 16

Calculated Fields - 8

The number of fields possible for Document Libraries are slightly different because of the pre-defined fields for a standard document library (in brackets below). Removing these pre-definded fields from the above figures give the following limits

27

Text Fields - 57 (5)

Multiline text fields - 31 (1)

Number or Currency Fields - 32

Date/Time Fields - 16

Lookup Fields - 16

Yes/No Fields - 16

Calculated Fields - 8

(Information courtesy of Jerry Orman - text by the FAQ writer)

Note: Roughly this information is now contained in KB 823555. (Aug 22 2003)

I.13.4 Lists - Limits in the size of fields per list

A single-line field is by default 255 characters in length.

A multi-line field is **in a document library** by default 255 characters in length.

A multi-line field in **any other list type** has no such limit (one correspondent had over 5000 characters in such a field).

A Choice field of type check box (i.e. multi-choice) has a maximum of 255 characters in the sum of the names of the choices.

[The difference between the character limits in two kinds of fields was explained by Gabe

Bratton thus

"The reason there is a 255 character limit for Multiline Text Fields in Document Libraries is that the OLE property stream doesn't support more than 255 characters. Having more than 255 characters would cause problems demoting properties into documents."

Thanks to him, and to Thierry Masson for asking why.]

28

I.13.5 Lists - What graphics formats are supported for Thumbnail creation in a Picture

Library?

This is actually the subject of KB article 822259 and is added here in brief (and alphabetical!) form.

.bmp

.dib

.emf

.gif

.jfif

.jpe

.jpeg

.jpg

.png

.tif

.tiff

.wmf

.xbm

I.14 What Browsers are supported?

I.14.1 Supported Browsers - General Information

In STS 1.0 there were problems accessing STS sites from Macs and by users using

Netscape browsers.

I'm vague on the details but I seem to remember that in addition to the need to use Basic

Authentication there was also some loss of features (i.e. some things didn't work). In addition some older versions of IE didn't work entirely satisfactorily.

In WSS I've been told that (and this is a direct quote from inside MS - with my thanks to the sender)

"Any Windows, Macintosh®, or UNIX client can use Windows SharePoint Services ... features, providing the client runs the following software:

Microsoft Internet Explorer 5.01 or later (best results with Microsoft Internet Explorer

5.5 or later),

Microsoft Internet Explorer 5.2 or later for Macintosh, or Netscape Navigator version 6.2 or later

29

So we're including Mac and Unix running IE 5.01 or later and NS 6.2 or later."

Note: Linux Mozilla is not a supported Client browser. However Mozilla 1.4 is based on

Netscape 6.2 and thus does seem to work.

Note 2: Both Mozilla 1.4 and some late Netscape versions have difficulties rendering the menu line of this (FAQ) WSS-based site. This has been passed on as a potential bug to

Microsoft.

Note 3: Following a comment from one correspondent that the latest version of Opera works, I received the following additional information from another correspondent.

Depends on what you consider "works" I've been using Mozilla (Firebird/Firefox and it's derivate K-Meleon) now for more than a year as default browser and a lot, but not all, features of SharePoint (no matter if WSS or SPS) work.

However, all the features which rely on client-side ActiveX of course don't work

(Personal Menu, Document Library Explorer view, Datasheet Views, Linking to

Outlook/Excel/Access).

The really sad thing is that several features are blocked on purpose for Netscape/Mozilla

(including Firebird/Firefox and K-Meleon). One I am suffering from is the grouped view expand/collapse option where the code explicitely says to exit if the browser is Netscape

(or Mozilla, which is the same codebase). I wish the developers would have been more focused on following the Internet standards for XHTML, DHTML, CSS and JavaScript instead of only looking into the proprietary IE stuff .

Pretty much the same applies to Opera (just checked my site with Opera 7.23).

I.14.2 Supported Browsers - Web Parts

According to a seminar given by MS on Web Parts, the full Web Part experience is available to users of IE 6.0 and 5.5 and Netscape 6 and 7 only.

30

I.15 Can I amend Error and other System Messages?

In STS 1.0 a common request was to have the ability to amend error and other systems messages such as the message informing someone that they an amendment has been made. Usually in STS 1.0 the answer was that such messages were hard-coded and could not be changed.

In WSS Error messages are still hard-coded. Most of them are stored in the fpext.msg file which is not editable.

(space left for system messages info)

I.16 Do I see Different views of the information for different users?

In STS 1.0 all users, irrespective of their WSS roles (Browser, Author etc.), saw the same web pages. This meant that even Browser users were allowed to see Site Settings and change parameters BUT were then not allowed to save their changes because of incorrect authorization levels. This led to confusion and help requests to the administrator.

One workaround used was to hide the link to Site Settings behind a graphic image on the page on the assumption that only people who knew this link was there would bother to click on the graphic image and if anyone without rights did so by chance - Tough!

In WSS all users irrespective of their STS roles still see the same web pages with all the above consequences and workaround possibilities.

Note that there is one exception to this rule. A user can – in addition to the standard pages also see *their own* pages through specifying “Personal View”.

In a *Portal Server* installation you can create "audiences" and then you can target portal site content for viewing by one or more specific audiences. (The default audience being

'all portal users'). However this will apply only to the Portal Server part of the site and not to any WSS sites created in a Portal Server system.

I.17 How does WSS use Web Parts ?

In STS 1.0 Web Parts could not be used. Their use was restricted to SharePoint Portal

Server (SPS) 1.0 only

In WSS Web Parts are an integral part of the product.

(for more detailed information, look at sections VI.3 Customizing the Home Page and

VI.4 Using Web Part Connections below)

Note: SPSv1 web parts need to be converted before they can be used in WSS (or SPSv2)- see the "MS Articles" section of this FAQ for a link to a Microsoft white paper on this.

31

I.18 How does WSS handle Roles?

In STS 1.0 there were five default Roles - Browser, Contributor, Author, Advanced

Author and Administrator. These were predefined rights from the same list of total rights for the site and by default as you moved up the scale you had the same rights plus more.

This list was divided into three main categories - Web Design Rights; Team Contributor

Rights and Web Administration Rights.

By default no user except the Administrator had rights to any of the options in the Web

Administration Rights section and to those parts of the "Web Design Rights" section that were indeed Web Design Rights.

There was also very little difference between a Browser; and Author and an Advanced

Author (again by default) with an Author in addition to the functions available to a

Browser being able to create/update/delete HTML pages and directories; and the

Advanced Author on top of that being able to "Design Lists" (Create and customize lists)

In WSS there is a much clearer set of main categories and greater differences between the different standard roles.

There are still five categories of default roles but these have changed in character.

- The Guest role has no equivalent in STS. Users with this role can only read *specific* lists and documents when specially given permission to do so.

- The Reader role is equivalent to the former Browser role and can only view items; document; discussion comments and pages in a Web Site (although strangely can also

Create a Web Site using Self-Service Site Creation).

- The Contributor Role is roughly equivalent to the former Author role (but has also rights to amend the users own Personal View [this function was not available in STS at all].

- The Web Designer Role lies between that of the STS Advanced Author role and the

STS Administrator role with a greatly extended ability to amend the content of a web site.

- The Administrator Role as before has full control of the site (all selections are specified)

In addition to the change of roles there are now clearer definitions of individual rights.

For instance in STS one selection was Create/Edit/Update HTML Pages. This is now three different selections Add; Edit; Delete. Similarly in STS there was one selection for

Create/Rename/Remove a subweb. This is now two different selections (Create and

Manage). There are now two different selections for the right to a) apply a theme or borders and b) apply a style sheet.

32

In addition the division of the list into List Rights; Site Rights; and Personal Rights is much clearer than the STS divisions (see above).

I.19 What limits are there for the number of sites for particular set-ups?

The Administration Guide recommends the use of SQL Server rather than MSDE if you are supporting more than 10 “active and large Web sites”.

For more than 1,000 sites, the same source suggests installing SQL Server on a separate server.

[The next level would be a couple of Web Servers and a Couple of SQL Servers. The

Admin Guide does not indicate at which point such a configuration would be necessary.]

I.20.1 What doesn't work when using Office XP?

Neither of the following are visible and available for use

- multiple file upload

- datasheet view

None of the new interactions with Office products such as

- Creation of Meeting Workplaces in connection with an Outlook Calendar "Create

Meeting" action

- Creation of Document Workspaces when saving a document in Word/Excel

- Saving of an Outlook attachment in WSS so that for instance people opening the attachment after a change has been made to it see the new version

- Synchronization (see section VI for more details of this)

Andrew Couch also gave me this information -

Office 2003 seems to be required to for a user presence context menu to appear. With

Office 2003, when you hover over a user name in a SPS/WSS list column, a menu is available which allows you to send a message, schedule a meeting, add the user to your contacts, make an IM call (if installed) etc. If you have Office XP, this menu is not available and the user name is simply a hyperlink to the users shared profile view.

John Miller added that

Presence context menus are available with Office XP if you have Windows messenger installed (Not .NET Messenger)

33

I continue to be grateful for more additions!

Note that there is a new (August 2003) paper from Microsoft called “Good, Better, Best:

Windows SharePoint Services Integration with Microsoft Office” which includes a table with a cross-reference of what works with Office 2000; Office XP and Office 2003 respectively.

See the "MS Articles" section in this FAQ for the current link to that.

I.20.2 What doesn't work when using Office 2000?

(this is a work in progress)

All the restrictions from Office XP (see I.20.1) plus -

- Edit in Microsoft Word / Excel

(Thus with Office 2000 and earlier you need to open the document in WSS; Save it to your hard disk; amend it locally and then upload it under the same name back to WSS.)

Note that there is a new (August 2003) paper from Microsoft called “Good, Better, Best:

Windows SharePoint Services Integration with Microsoft Office” which includes a table with a cross-reference of what works with Office 2000; Office XP and Office 2003 respectively.

See the "MS Articles" section in this FAQ for the current link to that.

I.21 How do I find out about the usage of my site ?

In STS 1.0 usage of a site was obtained through the use of Front Page.

In WSS you need to first set "usage processing" and then you can set usage processing using the User Interface of WSS.

(Site Settings / Site Administration / 'View site and usage data' in the Management and

Statistics section).

There are a couple of things that the user needs to be aware of. a. You will not start seeing usage results until the day after you turn usage processing on. b. If a virtual server is added *after* usage processing is set, usage processing will not be enable for that virtual server.

34

In order to get usage processing in that situation, you need to

(i) Go to the LogUsage.aspx page and re-apply the settings or

(ii) set the start time for the particular virtual server with stsadm.exe -o setproperty -pn job-usage-analysis -pv ""daily between HH:MM:SS and

HH:MM:SS"" -url <URL to virtual server>

(one line)

Note: For those who - like me - can't find where to even say that you want usage processing, the reason is that you are looking in the wrong place. You'll have to go to the server. Once there go to -

Start / All Programs / Administrative Tools / SharePoint Central Administration and in the 'Component Configuration' section select "Configure usage analysis processing"

I.22.1 What are the differences between standalone WSS and the WSS in SBS 2003?

Many thanks to

Dustin Miller

for supplying this.

The differences are -

New list types

Fax Library

Create a fax library to view and store incoming faxes. This library displays the fax number, time received, and number of pages.

Help Desk

Create a help desk list to offer users an easy way to submit requests for technical help.

Your network administrator can choose to be alerted by e-mail when requests are submitted or modified.

These are implemented as list template files, and not as new list definitions in

ONET.XML with their own SCHEMA.XML.

35

Default lists available on the "default site":

Archived Documents (doclib)

General Documents (doclib)

Incoming Faxes (faxlib)

Presentations (doclib)

Projects (doclib)

Our Photos (piclib)

Announcements (announcements)

Help Desk (help desk)

Links (links)

Vacation Calendar (events)

General Discussion (discussion)

I.22.2 What are the differences between standalone WSS and the WSS in Project

Server 2003?

(More information gratefully accepted)

The Template used by Project Server 2003 has the following additions compared to standalone WSS.

Additional Customized Lists

Issues

Risks

36

II. Installation

II.1 On what Media is the product shipping?

STS 1.0 was available on the extended Office XP (with FP) and on the FP XP CDROMs.

WSS is available as a free download to the Windows 2003 Server Operating System.

(For the link see this FAQ's "MS Articles" section via the "Useful Documents" menu item)

II.2 What are the Licensing requirements?

Licensing is as always something that should be checked with Microsoft.

As usual each part of the puzzle needs to be licensed seperately.

So a) standard licensing for Windows 2003 Server (and upwards) b) standard licensing for SQL Server (if this is used) and *presumably* free use of

MSDE if this is used. c) WSS supplied as a free download.

Again: these are a best guess only. To be sure, ask Microsoft.

II.3 Are there any differences in basic installation procedures?

STS 1.0 a. If no database system was installed on the STS server - MSDE 1.0 was installed. b. If SQL Server (7.0 or 2K) was installed on the STS server prior to installing STS 1.0 - no new database system was installed and the STS databases were created in the existing db system. c. If the user wanted to use a database on a remote server he/she used the /nd parameter on installation and no database was created or used on the STS 1.0 server.

WSS a. If no database system is installed on the WSS server - MSDE 2K is installed. (Unless your server is a Domain Controller in which case this is not an option)

37

b. If SQL Server 2K is installed on the WSS server prior to installing WSS - a second instance of "SQL" is installed for the WSS databases. This "second instance of SQL" is in fact MSDE 2K not SQL Server 2K.

If the user wants the existing SQL Server 2K to be used for WSS he/she needs to follow the procedures for SQL Server on a remote server (c). c. If the user wants to use a database on a remote server he/she must install from the command line and use the remotesql=yes parameter and no database is created or used on the WSS server.

II.4 Where are the files located?

In STS 1.0 there were four main sets of files a. Templates - on the same drive as the operating system

It should be noted that only the standard templates are stored here. Information on all amendments to these standard templates are stored in the database. b. IIS Metabase - %SYSTEMROOT%\SYSTEM32\INETSRV\Metabase.bin c. Documents - default: under InetPub\wwwroot otherwise where specified in the file system d. Databases - located where you specified on installing the database

In WSS there are three main sets of files a. Templates - on the same drive as the operating system in a *similar* location to STS

1.0 b. IIS Metabase - %SYSTEMROOT%\SYSTEM32\INETSRV\ (containing

MBSchema.xml; Metabase.xml; MBSchema.bin.00000000h; and (for the benefit of older programs that look for it) a dummy file called Metabase.bin)

[History files are stored at %SYSTEMROOT%\SYSTEM32\INETSRV\History] c. Databases (include documents) - located where you specified the databases would be when you installed the database

Note: Because different sites can have different templates, some templates are stored per server and others stored per site.

There are thus both different templates to STS 1.0 and these are in some cases stored at different levels in the file system.

38

Note2: The Metabase file is no longer binary but is a plain XML file that can be edited.

II.5 What are the URL's of sites, subwebs, etc.?

a. The Main Site located at http://<servername> b. Document Libraries created in the main site located at http://<servername>/<doclibname> c. Subwebs to the mainsite located at http://<servername>/<subwebname> d. Document Workspaces created while in the main site located at http://<servername>/<docworkspacename>

(Document Workspaces created while in a subweb to a main site are located at http://<servername>/<subwebname>/<docworkspacename>) e. Meeting Workspaces created while in the main site located at http://<servername>/meetings/Meeting1; http://<servername>/meetings/Meeting2 etc.

Note: From the above URLs you can see that from the URL alone it is impossible to tell whether you are looking at a Document Library; a Subweb or a Document Workspace.

Meeting Workspaces however have their own page with a list of all Meeting Places - namely http://<servername>/meetings

Note 2: The total list of the above Subwebs; Document Workspaces; and whether or not there are any Meeting Places can be obtained by going within the Main Site to "Site

Settings" followed by "Manage Subwebs". In order to obtain the full list of Meeting

Workspaces you need to click on http://<servername>/meetings in the list. This item is not present in the list of "Subwebs" if no Meeting Workspaces have been created. Note that this "total list" does not include Document Libraries.

39

An alternative method to get all the above (but still no Document Libraries) listed is to go to Site Settings / Site Administration and in the Site Collection Administration section access 'View Subweb List'. In this case all the meeting places are listed as well as the

Subwebs; and Document Workspaces. This listing also includes the listing of document workspaces within subwebs.

One way to get a list of Document Libraries is to go to 'Site Settings' and within the

Customization section, access "Modify Site Content". This gives a list of all Lists and

Document Libraries. Another way is to select "Document and Lists" in the menu line.

Lower-level sites can be listed in various ways (Thanks to Jorgon Johanson for this)

Site Settings

Go to Site Administration

Management and Statistics: Manage sites and workspaces

- or -

Site Settings

Go to Site Administration

Site Collection Administration: View site hierarchy

They can also be listed in several places in SharePoint Central Administration.

Useful Tip: Because the URL is (as above) non-indicative of whether the 'site' in question is a subweb / meeting place / document workspace etc., it is even more important than before to use a good name in the Title - this "Subweb Title" is listed alongside the URL name when "Manage Subwebs" is selected. f. Lower-level sites these are located at http://<servername>/sites/<lowerlevelsite> g. Document Libraries created in the lower-level site located at http://<servername>/sites/<lowerlevelsite1>/<doclibname> h. Subwebs to the lower-level site located at http://<servername>/sites/<lowerlevelsite>/<subwebname> i. Document Workspaces created while in the lower-level site located at http://<servername>/sites/<lowerlevelsite>/<docworkspacename>

(Document Workspaces created while in a subweb to a main site are located at http://<servername>/sites/<lowerlevelsite>/<subwebname>/<docworkspacename>)

40

j. Meeting Workspaces created while in the level site located at http://<servername>/sites/<lowerlevelsite>/meetings/Meeting1; http://<servername>/sites/<lowerlevelsite>/meetings/Meeting2 etc.

The same notes apply to lower lever sites as to the main site (With the exception of the possibility of listing from the Site Collection Administration section because this applies only to the Main Site).

II.6 Can I install WSS on a server running other applications?

The Define Managed Paths feature is targeted at this kind of scenario.

You use Define Managed Paths to exclude the URLs of the existing application(s) from being processed by the WSS ISAPI filter.

The definition can be changed in the section of WSS where you specify Virtual Server settings.

II.7.1 Can I run WSS under VMWare?

Windows 2003 Server only runs under VMWare Workstation 3 if USB is disabled.

Note that this is not officially supported

Windows 2003 Server also runs under VM Workstation 4, on which platform people have also had WSS (as part of SPS 2.0) running successfully.

(Thanks to David McKenzie for the Workstation 3 update)

II.7.2 Can I run WSS under Microsoft Virtual Server?

Yes. The compiler of this FAQ has had good experiences with Windows 2003 Server running Microsoft Virtual Server (pre-release=acquired version) and WSS with several

XPPro clients within MS Virtual Server able to access the WSS system via IE 6.0.

This worked satisfactorily on a PC with 256 MB of main memory and one P IV 1,5 processor (the memory only allowed one XP Pro session to be open at a time). It also worked - but not satisfactorily - on a portable with 256MB of main memory and a PIII

800MHz processor.

(It now works much better on a PIV 2,5M notebook with 1 GB of memory - but does that surprise anyone?)

41

For anyone who is considering this, I assign between 192 and 256 MB to each virtual machine and am thus able to run three main VMs at the same time (with others in Saved

State ready for instant revival)

I have in fact six VMs - XP Pro with Visual Studio .Net; XP Pro with Office 2003; XP

Pro with Office XP; Win 2003 with WSS; Win 2K with STS and Win 2003 with SPSv2.

II.8 How can I access my WSS Server from XP Pro ?

Note: This section is here purely because the compiler had trouble finding how to do this.

It is of course the same as how to access any Windows 2003 Server from XP Pro.

Handling possible Security Problems caused by doing this this way are up to the reader.

Windows 2003 Server comes with 'Remote Desktop for Administration' switched off.

Switch it on with (on the server with Administration Rights)

Start

Control Panel

System

Remote

Click the box marked 'Allow Users to connect remotely to your computer'

OK

Then if you haven't already done so, you have to set up XP Pro to be able to make a

'Remote Desktop Connection'.

(On the workstation)

Start

All Programs

Accessories

Communications

Remote Desktop Connection

Select Options write in name of server (works best for me) etc.

II.9 Is there anything extra I should be aware of if I have upgraded my server from

Win 2K Server to Win 2003 Server?

Before you install WSS you should check two things a. That in IIS the "Run WWW Service in IIS 5.0 isolation mode" check box is cleared. b. That FrontPage 2000 Server Extensions are not running on the virtual server at port 80.

42

Note: b. would happen by default if the server had been upgraded from Windows 2000 to

Windows 2003.

II.10 WSS and Domain Controllers

II.10.1 Can I install WSS to a domain controller?

Yes.

It's unclear as to whether this is a recommended method or not.

Certainly Microsoft have stated that WSS will be able to install (it's version of) MSDE on a domian controller and that this is in fact the way Small Business Server 2003 will ship with WSS configured.

In any case there is one clear rule to follow. Always install IIS after the server has been promoted to a Domain Controller role. (Otherwise following installation there will be authentication problems).

Note: SPS v2.0 can also be installed to a domain controller but in this case MSDE is not an option

II.10.2 Why should I perhaps not install WSS to a domain controller?

1. Because Active Directory Account Creation mode is not supported.

2.

(SPS v2 only)

Because the option of using MSDE as your database is no longer available.

Note to 1:

Ian Morrish

says that although Active Directory Account Creation mode is not supported, it does work *provided that you specify the Domain Administrator as the app pool account (for both admin & content during setup)*.

His site at http://www.wssdemo.com

apparently runs in this mode and does have a DC

(and SQL Server) on the same server as WSS.

II.11 Too large documents

II.11.1 My multiple document uploads are failing because they are too large. What's the solution?

The default value for the "Upload Limit", which is what controls the total size of documents you can upload at one time, is set to a (in my opinion) far too low 50MB. In order to increase the size do the following.

43

On the Server (under Administrative Tools) click on "SharePoint Central Administration"

"Configure Virtual Server Settings"

"Default Site"

"Virtual Server Default Settings"

"Maximum Upload Size"

Specify a larger figure than the standard 50. I use 300.

----------------

Another possibility is that you have specified quotas that would be exceeded by the transfer.

To amend the existing quota values do the following

On the Server (under Administrative Tools) click on "SharePoint Central Administration"

In the Section "Component Configuration" click on "Manage Quotas and Locks"

(Thanks to Emmanuel Bouvier for the suggestion to add this alternative problem)

II.11.2 My uploads of (single) very large documents are failing. What is the problem?

WSS has problems when adding large documents. Problems seem to start at a document size of > 70MB and with documents over 100MB almost always being rejected.

II.11.3 My packaging of a large WSS site in FP 2003 is failing. What's my problem?

There is limit in the size of a WSS site that can be packaged with FP 2003.

This limit is ca 125MB.

II.12 How do I enable Session State?

You can enable session state by uncommenting the following line in the web.config

<!--

<add name="Session" type="System.Web.SessionState.SessionStateModule"/>

-->

In addition you need to set the <pages> enableSessionState attribute to true.

44

Note: Quoted from a comment by Gabe Bratton - if anyone can add more information such as where the web.config and the enableSessionState attribute are, please send mail to me at [email protected]!

II.13 After installing WSS I get "cannot to the configuration database" when trying to access WSS. What is the solution?

The most likely explanation is that after installing WSS, you amended the name of your server.

The WSS database has already been created using the name your server had when you installed WSS. So now when you try to access WSS using the new name of the server, you will be able to access the server but not be able to access the database and thus you will get this message.

The simplest way to correct this problem is to re-name your server back to the name it had when you installed WSS.

-------------

Knowledge Base article 823287 also has a different explanation. (Although a) is similar)

According to that article this happens if one of the following three conditions are true. a) The SQL database is not running b) IIS is configured to run in IIS 5.0 isolation mode c) The account that is used by the application pool does not have the required permissions to the SQL Server database.

For more information, please go to http://support.microsoft.com/?kbid=823287

(It may be that later versions of this KB include my original reason above as d))

II.14 Where do I get the language packs for the WSS Beta2 Tech Refresh ?

The latest link is listed in the MS Articles section of this FAQ (via the Useful Documents

Menu Line)

45

II.15 Can you install Class Server and WSS on the same server?

Yes.

But you then need to install WSS to a location other than the default virtual server because Class Server can only use the Default Web Site in IIS.

Full details of this are in KB 821501 (18th June 2003)

(included in the FAQ to make this information searchable)

II.16 Can I migrate STS 1.0 sites that have customized schema files to WSS?

Here is the detailed answer

Krams

received from

Troy Starr

.

I'm afraid that we don't support migrating STS 1.0 sites that are based on customized schema files. Our recomendation for this scenario is to backup your STS 1.0 site as usual and then edit the FWP files that smigrate generates to convert your custom list types to their closest STS v1 built-in list types.

For example:

1. Use smigrate to backup each individual STS v1 site.

Example syntax: smigrate -w http://v1server/site -e -f site.fwp

2. Use a Cabinet decompression utility such as EXTRACT to decompress all of the files out of the FWP file. You can get the EXTRACT utility from the Microsoft CAB SDK at: http://msdn.microsoft.com/library/en-us/dncabsdk/html/cabdl.asp

, although any utility that can decompress CAB files will suffice.

Example syntax: EXTRACT /A /E site.fwp /L c:\files

3. Browse to the "files" folder and open the manifest.xml file.

46

4. Change any custom list type entries to built-in list type entries. For example, to turn the custom list type into a Links list type, change:

<List Name="some name" Title="some title" BaseType="0" Type="500" Url="some url" Version="1"> to

<List Name="some name" Title="some title" BaseType="0" Type="103" Url="some url" Version="1">

5. Save your changes.

6. Use a Cabinet compression utility such as CABARC to compress all of the files in the

"files" folder into a FWP file. You can get the CABARC utility from the Microsoft CAB

SDK at: http://msdn.microsoft.com/library/en-us/dncabsdk/html/cabdl.asp

, although any utility that can generate CAB files will suffice.

Example syntax: CABARC N fixed_site.fwp c:\files\*.*

7. Use smigrate to restore the fixed FWP file to a WSS v2 site.

Example syntax: smigrate -r -w http://wss/site -f fixed_site.fwp

Note that each site has its own manifest file. If you don't use the "-e" switch with smigrate during the backup, then smigrate will also backup all of the sites below the one you specify. If that happens, you will need to alter the manifest file for each site in the

FWP below the one you specified. You can find the manifest files for a site's immediate child sites listed in the "<Subwebs>" section in the manifest file.

If you've created custom field types as well, then you will need to modify the manifest file to similarly convert them into the standard STS v1 field types.

II.17.1 How do I install WSS so that WMSDE is located at a non-default location?

(Single server)

This is in the Admin Guide but has been asked so many times, it's worth adding here.

You use the /datadir parameter - for instance setupsts.exe /datadir="d:\program files\wmsdedata \\" ;

47

(The above is the Admin Guide example - there is more detail in the deployment scenarios section)

II.17.2 How do I install WSS to use an existing copy of SQL Server instead of

WMSDE? (Single server)

This too is in the Admin Guide in the Single Server Deployment part of the Deployment

Scenarios section.

The short answer is to use the remotesql=yes parameter so setupsts.exe remotesql=yes

Again the Admin Guide has this in more detail.

48

III. Administration

III.1 How do I change Time and Date styles?

In STS 1.0 a common request was to have the date set to "European" i.e. DD/MM/YY or

"Swedish" i.e. YY/MM/DD instead of the STS 1.0 standard US date MM/DD/YY. This and the change to a 24 hour clock were only possible outside STS at the operating system level. These settings were thus valid for all the sites located on the server.

In WSS it is possible to set "Regional Settings" in Site Settings / Site Administration where there are selections for Locale (which presumably includes date format); Sorting order; Time Zone and Time Format (12/24 hour clock). These settings are valid for *the site* which means that a single server can run sites which are operating in different time zones and with different language 'styles' (for want of a better word).

III.2 Are there any differences in Authorization?

see "I.16 Do I see Different views of the information for different users?" (Both STS 1.0 and WSS show identical web pages to users irrespective of their roles.)

There seems to be much more granularity (options) when defining the rights of normal users.

III.2.1 Authorization - Are there differences with anonymous access?

In STS v 1.0 it was sufficient to specify using the STS UI that you wanted to allow anonymous access to a web or sub web.

In WSS it is necessary to both specify anonymous access in the WSS UI for the web / subweb but also to allow anonymous access in IIS.

Details: a) IIS

Goto IIS MMC, right click on the Default Web Site (or the virtual server you have extended as a WSS site), properties, click on the security tab, click on the edit button of

Authentication and Access control and enable Anonymous access. b) WSS

Site Settings

Site Administration

Top Site Administration (omit if already at Top Site)

Manage Anonymous Access.

49

III.2.2 Authorization - Are there differences in the kinds of user that can be allocated to a site?

In STS v 1.0 there were two kinds of users - domain users, who used their domain names and passwords; and local users, who were defined on the STS server as a user with a password specifically for that server.

In WSS there are three kinds of users. In addition to the above two kinds, there can also be active directory users. [More needed]

III.2.3 Authorization - Are there differences in the specification of a local (server) user?

In STS v 1.0 it was possible in the STS UI to specify the name and password of a local user. This happened in this form the first time this user was assigned to any STS web

/subweb on the same server and caused the user to be created on the server as well as being given rights to the STS web. (When you gave rights to a user for other webs/subwebs on the same server, you specified the user as <server-name>\username and didn't specify a password).

In WSS it is necessary to create the user on the WSS server first (specifying a password).

Only following this is it possible to give this user rights to a WSS web/subweb. In this case it is sufficient to specify just the user name (i.e. no longer <servername>/username).

III.2.4 Authorization - Are there differences in the specification of a domain user?

In STS v 1.0 a domain user was specified for a web/subweb by writing domainname\username and not specifying a password. This applied both the first time the domain user had access to part of a site and to all other times.

In STS v 1.0 it was also possible to specify a domain user even when the workstation itself was not part of the domain. In this case when accessing the STS site from such a workstation it was necessary to enter domainname\username and password in the login box.

In WSS a domain user is still specified for a web/subweb by writing domainname\username and not specifying a password.

In contrast to the situation with STS, this can now only be done from a workstation that is part of the domain in question as before being given rights to a WSS site, all users are checked to see if they exist (and no login function is included in this routine).

50

III.3 When do I run Server Health?

STS 1.0 had the "Server Health" function which was intended to make sure that the data on the file system and the data in the STS database were in sync.

WSS uses the WSS database for all the data that was previously located in two locations and thus there is no longer a need for the "Server Health" function in WSS.

III.4 What can you tell me about Logging?

STS 1.0 had logging to C:\WINNT\system32\LogFiles\W3SVC1 (and W3SVC2,

W3SVC3 etc.)

WSS has (RTM) a configurable registry key that you can set to control how verbose the logging is.

Critical events will be logged to the application log in the event viewer.

The stsadm.exe comman line utility uses a log file called stsadm.log which is stored in the temp directory of the person running this utility.

The log for the w3wp process (w3wp.log) is stored in the windows temp directory.

III.5 What are the rules for Naming Sites and Document Libraries?

III.5.1 Relation to directory names

In STS 1.0 the name of a subweb was automatically the physical name of the directory.

The same applied to document libraries.

In WSS you need to specify both the subweb / doc lib name and its "physical" name separately. They may still be the same but don't have to be.

III.5.2 Forbidden characters

In WSS Site Names may not contain the following characters.

\ / : * ? " < > | # { } % & <TAB>"

In addition site names may not begin with underscore "_" as this is reserved.

Finally, here is the WSS invalid character set (which I would guess means for the names of files that you upload to WSS)

" # % & * : < > ? \ { | } ~

51

III.5.3 How can I change a site name?

(This answer is specifically for SPS 2.0 but should also apply for a WSS installation with different addresses - i.e. http://server and http://server/subsite)

Site collections like http://server/sites/teamsite cannot be renamed.

Subsites like http://server/sites/teamsite/subsite can be renamed by opening the site in

FrontPage by going to Tools, Site Settings and changing the Web Name:.

Where the site is a site collection, you have a couple of options

1. Create a new site with a new name but do not apply a template and use smigrate.exe to migrate the original site to the new site. This option does not preserve security.

2. Use stsadm.exe -o backup/restore to backup the site and restore it to a new name.

After restoring you can delete the original site. This option is full fidelity and does preserve security.

III.6 What can you tell me about Migration?

III.6.1 Site Migration from STS to WSS

To upgrade from STS v1 to Windows SharePoint Services you will have to use the smigrate.exe command line utility to first backup the STS v1 site, then restore it to a new

WSS site that has no template applied.

Instructions for doing this are in the Windows SharePoint Services Admin Guide at http://www.microsoft.com/downloads/details.aspx?FamilyID=a637eff6-8224-4b19-a6a4-

3e33fa13d230&displaylang=en

(Revised for RTM on October 4th 2003)

In the admin guide find the primary topic Backup and Migration and the instructions for using smigrate are in Migrating and Upgrading Web Sites.

It is required that you apply Office XP SP 1 and SP 2 to your STS v1 server. You can get these from here, http://office.microsoft.com/productupdates/mainCatalog.aspx.

Once your STS v1 server is updated to SP 2 you will need to apply a QFE patch to it from

52

http://download.microsoft.com/download/d/1/3/d1335281-d1d8-4f58-afc2c6871e6d694f/OWS1002.exe.

This is described in the WSS readme file (the link to this is at http://wss.collutions.com/Lists/MS%20Articles/Grouped%20by%20Category.aspx). The patch makes it possible for smigrate.exe to get as much data from your v1 site as possible.

Common issues:

1. When you create a new WSS site to restore a STS v1 site, do not apply a template to the site. When you get to the template picker page do not apply a template.

2. After applying the QFE patch to your v1 server you may need to upgrade your web sites. This is done using the owsadm.exe command line utility. On your STS v1 server you can upgrade all of your v1 sites by running owsadm.exe -o upgrade -p all

(after having in a command line session negotiated your way to \program files\common files\microsoft shared\web server extensions\50\bin)

(above instructions from Gabe Bratton in a beta newsgroup)

-----

Also note that when using the -u and -pw passwords with smigrate, you may get an error message

"You are not authorized to perform the current operation"

In this case please refer to Knowledge Base article 828210 for an explanation and workaround.

III.6.2 List Migration from WSS to WSS

In WSS it is possible to transfer a list between WSS Team Sites using the 'List Template' feature.

Here is the detail.

1. Browse to your WSS site

2. Click Shared Documents, Modify settings and columns

3. Click Save document library as template

4. Name the file documents.fwp and make Template Title Documents (for example)

[Tech Refresh = (probably) .stp]

5. Optionally choose to include content (which is any documents in your document library)

6. Click OK

53

Once you have made the list into a template you can copy the template to another team site.

1. Browse to your WSS site

2. Click Site Settings, Go to site administration, and click Manage list template gallery

3. Right click on the link for Documents and click Save target as (to your file system)

Now you can go to another team site, and upload the template into that sites template gallery. After the new template is uploaded you can click Create from the navigation of the team site and create a new document library from the template you uploaded.

(above instructions from Gabe Bratton in a beta newsgroup)

Note: According to Henrik Andersson this no longer works **with Beta-2 templates** after the Beta-2 Technical Refresh. Beta-2 templates no longer are listed in the Manage

List Template Gallery (above second section 2). This seems to be because templates are now stored as .stp files and amending the Beta-2 templates from .fwp to .stp seems to correct it.

III.6.3 Site Migration from WSS to WSS

The following is quoted directly from Jerry Orman's response to a question from me.

For details of the smigrate program itself, please refer to the item III.6.1 (Site Migration from STS to WSS)

"You can use smigrate to move a v2 site to another v2 site.

The limitation is that you have to use the same build of WSS on both of the servers. So you can't smigrate a Beta 2 .fwp file to a Beta 2 Technical Refresh server.

In order to migrate the site you would need to:

1. Install the build of WSS that you guys used to smigrate the site originally on a server.

So if you guys were running Beta 2, install Beta 2 of WSS on a different server.

2. Use smigrate on this server (the beta 2 server) to restore the site (.fwp file) to this server.

3. Upgrade WSS on the server to the Beta 2 Tech Refresh build.

4. Smigrate the site to a .fwp file from the upgraded server

5. Then use smigrate to move the site.

54

Thanks as always to Jerry.

Note that the question he was answering concerned using smigrate to upgrade from beta-

2 to Beta-2 Tech Refresh.

The key parts of the general answer are the first two paragraphs of his reply (in the web site version in red).

-----

Also note that when using the -u and -pw passwords with smigrate, you may get an error message

"You are not authorized to perform the current operation"

In this case please refer to Knowledge Base article 828210 for an explanation and workaround.

III.6.4 "Upgrading" from WSS to SPS 2003

Microsoft have a (long) Knowledge Base paper on this at http://support.microsoft.com/default.aspx?scid=kb;en-us;824877

(August 27 2003)

It should be noted that the procedure listed does not work for WSS installations that use

Host Header mode or Active Directory mode.

So avoid both of these if you think that you will later be "upgrading" to SPS 2003.

III.7.1 How do I 'check out' and 'check in' a document in WSS?

WSS makes this process both clear and easy to do. The steps are as follows

Open a document library; click on the arrow at the right of the document name; click on

Check Out.

Then Open the document; amend it; save.

Then click on the arrow at the right of the document name; click on Check In.

Fill in comments as to why... OK.

55

III.7.2 How does locking work in WSS? (What are the two kinds of check-out?)

Here is some text from Iyaz explaining this better than I could.

SharePoint supports two kinds of check-out:

Long term check out

This is the explicit check out .

This holds a lock on the document whether you have it open for edit or not.

Short term check out

You get this feature implicitly.

If you open a document for editing, you get a short term lock on the document to prevent other people from editing the doc while you are.

The Office client applications refresh this lock periodically as long as you keep the document open. Once you close the document, your short term check out is released.

III.8 Can I provide the same content to both an Intranet and an Extranet Site?

This is mentioned (*) in the Administration Guide.

* (The previous text of "well covered" has been amended following comments that this is not included in the (download) .chm file - but check the Admin Guide out anyway, it may have been updated by the time you read this)

The key details follow.

- One virtual server is configured with Integrated Windows Authentication and an internal address

- The other virtual server is configured with a different authentication type (probably

Basic Authentication + SSL) and an external address.

Both these point to the same content.

-------------

To confuse us the SharepointTSAdmin.chm (Ed: RTM version of Admin guide not yet checked to see if identical) expands on this by saying that the two virtual servers must be *on separate boxes*

56

This is in fact not the case.

Ed Lee using instructions he got from "Sabre Lighter" did so by following the instructions in the SPS Administrators Guide.

Security > Portal and Site Security > Managing Anonymous Access Settings.

One of his virtual servers uses Windows Integrated Authentication and the other uses

Basic. (as above).

This also worked well for another newsgroup member. (On receiving just the above instructions from Ed)

III.9 I've forgotten which port I need to use when I administer my site. What is my administration port number ?

Unlike STS 1.0 which always used the same administration port number, WSS generates a random port number as the administration port.

If you are not happy with the random number, you use the following command line command to alter it (to 1234) stsadmin.exe -o -setadminport -p 1234

III.10 I am getting an error saying that I need to remove FrontPage Server

Extensions or SharePoint Team Services 1.0. How do I do this?

This might happen when you install WSS or when you try to extend a virtual server.

The error message (which is very long) starts with "Setup has detected that FrontPage

Server Extensions or SharePoint Team Services 1.0 is installed on the default virtual server. These must be removed ...."

To solve this,

Either a) Remove FP 20002 Server Extensions from the virtual server (if they are present)

Start / Administrative Tools / Microsoft SharePoint Administrator.

57

On the Server Administration Page for FP SE 2002

Administration / Uninstall FrontPage Server Extensions 2002 / Full Uninstall=Yes

Or

(If they are not present)

You need to delete the hidden folder _vti_pvt\service.cnf in the content directory of the virtual server

(Information from the betaplace site)

Note: 'Removing FrontPage 2002 Server Extensions' is now the subject of KB 823378

(22 Aug 2003)

III.11.1 How do I list the sites in a Virtual Server?

You can't do this via the WSS User Interface.

Instead you have to go to the following directory on your server (X: = boot drive, typically C:) and run stsadm.exe

Directory: X:\Program Files\Common Files\Microsoft Shared\Web Server

Extensions\60\BIN

Command: stsadm -o enumsites -url http://servername

III.11.2 How do I list all the subwebs in a site?

This is possible via the User Interface.

(while in Top-level site)

Site Settings

Go to Site Administration

(in Site Collection Administration)

View Site Hierarchy

III.11.3 How do I delete a Meeting Workplace?

You browse to the (Meeting Workplace) site and -

1. Click 'Modify This Workspace', select Site Settings

58

2. Click 'Go to Site Administration'

3. Click 'Delete this Site'

III.12.1 Where can I get Web Parts from?

Microsoft provides in addition to the standard web parts that come with WSS a set of

Web Parts for Office components.

These (which are at present WebParts for Datasheet; PivotChart; PivotTable; PivotView;

Spreadsheet; QuickQuote and webCapture) and are installed on the server can be found at http://www.microsoft.com/downloads/details.aspx?familyid=38be67a5-2056-46a1-84b1-

337ffb549c5c&displaylang=en

The client Office web components download which might be needed to view some web parts if Office 2003 is not installed on the client is at http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-

97a5-e0fd290d4b76&DisplayLang=en

--------

Tim Heuer has several web parts (some chargeable at reasonable prices, others free) at http://www.timheuer.com/stuff.htm

At the time of writing (7.2003) these are

Workspace Explorer ("provides an out-of-the-box function for quickly viewing the hierarchy of a site collection")

RSS Feed Reader (free)

Flash Movie Viewer (free)

Doc Lib Utils

However, for an up-to-date listing of WebParts, please go to Hitesh Seth's web page http://hiteshseth.com/webparts

(Which appeared almost simultaneously with the posting of the above text)

59

III.12.2 How do I remove a web part

- At the top level of a site, go to Site Settings

- In Administration click on "Go to Site Administration"

- In Site Collection Gallery click on "Manage Web Part Gallery"

- Edit the part you want to remove

- Click on the menu item "Delete"

Note: This procedure is only possible when you are the top level site

Note 2: There is a different procedure for SharePoint Portal Server

III.12.3 A web capture web part that accesses information from an external site requires action from me. How can I avoid this?

I am using a Web Capture part that gets information from news.bbc.co.uk. Every time I access the page containing this web part, a message box comes up with the following text

"This page is accessing information that is not under its control. This poses a security risk. Do you want to continue?"

On Pressing OK, the part refreshes correctly.

However I want to avoid having to press OK every time I access the page. This is how to do it.

In Internet Explorer select Tools from the Menu line. Then

Internet Options

Security with Local Intranet selected click on 'Custom Level'

In the Miscellaneous section change the value of 'Access Data Sources Across Domains' from Prompt to Enable

(Thanks to John Dougherty for asking a question that had been annoying me for weeks; thanks too to David McKenzie for supplying the answer)

Warning: Any effects on your sites/clients security caused by amending this security item in IE are your problem.

60

III.12.4 Is there any way to have the web part title wrap if it's wider than the column it's in?

No

III.12.5 What is the difference in using the Page Viewer Web Part to display web pages and using the Web Capture Web Part?

The Page View Web Part comes with the product, so why did the Office team (in their

Office Web Parts and Comonents package - see the download in the MS Articles section of this FAQ) produce a Web Capture Web Part that did the same thing I wondered

(aloud).

The answer is that in addition to showing (as does the Page Viewer part) the entire web page, the Web Capture part allows you to select a part of the web page and only this will then appear in the web part.

(The sections you are allowed to select are marked with a small yellow sign that changes to green when you select it)

David McKenzie warned however that this selection continues to work only if the originating web page is not re-designed in any way.

"In reality, the implimentation builds a table of elements from the source page; and when that page's design is altered, the table entry no longer points to the desired element."

Note: Theoretically the Web Capture part should refresh automatically too. Well it hasn't when I've used it! [It does refresh when you leave the page it is on and then go back.]

III.13 How can I make a field read-only?

You can't.

However for a standard field at least you can use the following workaround from Jerry

Orman.

This consists of removing the field from the EditForm.aspx page - and thus by not seeing it, you can't edit it.

The example he uses is the Title field in a document library which always appears in the

Edit page even if you have created your own field to store the Document's name.

His text then continues -

1. Open the site in FrontPage 2003.

61

2. Navigate to the EditForm.aspx file for the list you want to modify (in this example a document library).

3. Right-click the list.

4. Select Customize SharePoint List Form.

You will now get icons with question marks for the various parts of the form. Each of these icons represent a control on the form in CAML.

For the document library example, the last icon on the top row has the following code :

<ows:Field name="Title">

5. Remove the question mark for this code.

6. Save the page.

The Title field will no longer appear on the EditForm page.

III.14 I can't customize any lists (but I can make other site changes). What is my problem?

There seems to be a link between turning off the ability for users to "Manage Personal

Views" and this problem.

Despite the name, turning off "Manage Personal Views" (in Beta-2 Refresh, at least) also stops even the Administrator making any changes to even site-wide Lists.

The solution is therefore to turn "Manage Personal Views" back on.

1. SharePoint Central Administration

2. Configure Virtual Server

3. My Site

4. Manage User Rights for Virtual Server

5. Re-check the "Manage Personal Views" checkbox.

Thanks to "Tom" for spelling this out.

III.15 What are the minimum rights a user needs in order to be able to create a

Personal View?

The minimum rights needed to create and update a personal view of a web part page are

1. View Items

2. View Pages

62

3. Add/Remove Private Web Parts

4. Update Personal Web Parts

The Contributor group has for instance all these rights in its default (out of the box) configuration.

Note: (SPS v2 only) The main page of an SPS portal can not be personalized. (However, the 'My Site' feature is only available for SPS v2 and not WSS)

(Thanks to Jerry Orman for sending the message on which this item is based.)

III.16 I get a proxy server error when I try to import a Web Part. But I don't have a proxy server. What's the solution?

The error that was received when trying to import (Click on the Content Link) a web part from the Microsoft Web Part Gallery was

"An error occured while importing a Web Part ... (URL) .. . This error may be due to the current dashboard proxy server setting .....

The answer was to go to the Command Line and -

1. cd \program files\sharePoint Portal server\bin

(The location of proxycfg.exe)

2. proxycfg -d -p fake_proxy:80 "*;<local>

Then the following occurs -

Updating proxy settings

Current WinHttp proxy settings under ... (Registry key) ..

Flags = PROXY_TYPE_DIRECT | PROXY_TYPE_PROXY

Proxy Server = fake_proxy:80

Bypass List =*;<local>

(Thanks to Chip Willis who posted both the question and the answer (!) )

III.17 How do I integrate IM icons into WSS?

The integration of IM icons is one of the features of WSS that only applies to users with

Office 2003.

Office 2003 includes IM icons and functions in its standard installation.

63

However in order for WSS to use these icons/functions it is also necessary to make modifications to WSS.

1. On the SharePoint Central Administration page, under Virtual Server

Configuration, click Configure virtual server settings.

2. On the Virtual Server List page, click the name of the virtual server you want to configure.

3. Under Virtual Server Management, click Virtual server general settings.

4. In the Person Name Smart Tag and Presence Settings section, next to

Enable Person Name smart tag and Online Status for members, select Yes.

Thanks to Eric Legault for providing this extract from the Administrator Guide.

In case those of you without IM and/or Office 2003 are wondering how this works, here's an extract from Kurt Sanders

"If I am logged into IM and change my status to "Busy", the icon on the portal changes to match that icon used in the IM product" - i.e. not only is Kurt listed with icon as a member of a site but the icon now changes to Busy.

Note: The above applies also to SPS v2.

III.18.1 What is the default time before a user receives a session timeout error? How do I amend this default?

The time-out that causes the message

"The security validation for this page has timed out. Click Back in your Web browser, refresh the page, and try your operation again" is configurable.

Start / Administrative Tools / SharePoint Central Administration / Configure Virtual

Server Settings /virtual server name / click Virtual Server General Settings.

-On this page locate the Web Page Security Validation section.

The default should be 30 minutes.

Amend the default as required.

64

Note1: When the user clicks on the Back in the browser (as suggested in the error message), you receive the same error again. It requires you to click the Home link and retry.

Note2: Even if you do the refresh to resubmit you likely will lose what data you added on the refresh. After the refresh though it is possible to add the data to the form and resubmit.

(This FAQ item uses information from a message from Mike Denman and a reply from

Gabe Bratton. The FAQ maintainer is solely repsonsible for his interpretation above of the Q+A)

III.18.2 How can I increase the timeout for a web part?

Web parts using things like filters may time out.

In order to avoid this a parameter setting in web.config needs to be amended.

<WebPartWorkItem Timeout="nnnnn" />

Thanks to

Robert Winger

for providing this.

III.19 What do I have to do to make it possible for a user to be able to use FTP to upload documents to a document library?

You can't.

There is no support for FTP in these (SPS v2 and WSS) generations of the Sharepoint products.

III.20 Is it possible to specify the maximum number of versions of a document in a document library?

No. (WSS and SPS v2)

This is being considered for later versions.

III.21 I get ""HTTPException (0x80004005) Debugging is not supported under current trust level settings". What do I need to do to activate debugging?

This problem arises when running DotNet web applications on the same machine where

WSS has been installed and where debug has not been set to "false".

Here is the solution as posted by 'Pica'

65

You need to customise the web.config file either in "c:\Inetpub\wwwroot\" for all the application or the web.config file in your application directory.

Add the following line to your web.config in your application directory

<trust level="WSS_Medium" originUrl="" /> or

<trust level="Full" originUrl="" />

OR edit the line in the wwwroot\webconfig File.

The default setting for the level is "WSS_Minimal" which is not sufficient to debug your applications. Change this setting to at least "WSS_Medium" or "Full". ("Full" might be needed for applications that access Active Directory for instance - comment from Andre

Perusse)

In addition, this document might help: http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnspts/html/sharepoint_NorthwindWebParts.asp

(Section: Specifying a Trust Level in the Web.config File)

Many thanks to Pica for providing the question and the detailed answer.

III.22 Does WSS support Digest Authentication or Advanced Digest

Authentication?

No.

Please see KB article 823279.

(included in the FAQ to get this brief info in the PDF edition)

[and I haven't a clue what they are either ...]

III.23 I get "Server Error in 'uddi' Application". How do I solve this?

This is the subject of KB article 826785 and it may occur when WSS was installed on a computer that has UDDI Services installed.

The workaround is to amend the UDDI Web.config file (see the KB for details)

(included in the FAQ to get this brief info in the PDF edition)

66

III.24 I get "Access Denied" or "Cannot Complete This Action" when accessing a

WSS site. What might be my problem?

This is the subject of KB 823278 (27 Aug 2003)

This occurs if you delete a user account in Windows and then re-create it using the same name.

The same user name is not accepted in WSS as being the same user that was given access rights to WSS.

Please refer to the KB article for how to deal with this situation.

(included in the FAQ to get this brief info in the PDF edition)

III.25.1 Why am I being prompted for Authentication many times when I open an

Office document in WSS?

This is covered in KB 823553.

When you give up and finally press Cancel, the document then appears as read-only.

This can occur if the WSS directory security uses anonymous access as its authentication method.

The fix in KB 823553 (see there) stops the prompting for Authentication, but documents are still opened in read-only mode.

(included in the FAQ to get this brief info in the PDF edition)

III.25.2 Why are my domain users continually prompted for name/password?

One reason for this might be their IE settings

Go to Tools/Internet Options/Security/Custom Level

In the Security Settings dialog, scroll to the bottom and make sure that 'Automatic logon only in Intranet Zone' is chosen.

(thanks to 'Teresa')

III.26 My log files aren't being stored where I specified. What's going on?

This is covered in KB 823506.

67

You've specified a path for the logfiles that is more than 100 characters long and WSS has truncated it to 100 characters. (I.e. stick to 100 chars or less!)

There's not much more in the KB itself.

(included in the FAQ to get this brief info in the PDF edition)

III.27 I can't edit pictures in the Picture Library - what's the problem?

This is KB 826784.

Either you don't have Office Picture Manager installed (or a similar WSS-compatible control) or (if you have) you haven't configured your browser to support ActiveX

Controls.

The KB has details of how to install Office Picture Manager and how to change your

Local Internet zone settings.

(included in the FAQ to get this brief info in the PDF edition)

III.28 How can I tell if WSS is in AD Account Creation Mode?

This is covered in detail in KB 823507.

The solution uses a parameter of the stsadm.exe tool (createadaccounts) that is not listed in the WSS help or in the Admin Guide.

The article is dated Aug 26th 2003, please see it for further details.

(included in the FAQ to get this brief info in the PDF edition)

III.29 What third-party Virus tools are available for WSS?

Microsoft provides a list of its partners at http://directory.partners.extranet.microsoft.com/AdvSearchResults.aspx?sharepoint=4

This at the time of writing (10.03) lists three products, two of which specify WSS (Sybari and Network Associates).

68

III.30 Search isn't working - what could be the reason?

Assuming you are running SQL Server 2K because search doesn't work in WSS using

MSDE, here are some ideas.

Although in SQL Server 2000 by default the Full-Text Search (FTS) components are installed and the MSSearch service is setup and marked to auto-start and run under the

LocalSystem account, it is possible that these default settings have been changed.

So check them.

Also check if there are any MSSearch errors in the Application Log.

And of course in SharePoint Central Administration, make sure that the checkbox for

"Enable Full Text Search and Index Component" is selected.

Thanks to John Kane and Iyaz.

P.S. If search still isn't working. A final attempt could be to re-install the Full-Text-

Search component of SQL Server. This has helped at least one person to move on.

(Thanks to "Steve" for this)

III.31 Why do I have to re-enter my credentials after using the site for a while?

Thanks to Jeff Lynch for the following (edited) text -

WSS "sites" issue a non-persistant cookie (in the user's browser) that is used for

"authentication" purposes.

In the WSS "Central Administration" site you can set the timeout by selecting "Virtual

Server General Settings" and changing the "Web Page Security Validation" value.

The default value is 30 minutes.

After the elapse of this time period the user is automatically logged off the site and must re-enter his/her credentials.

III.32 Why aren't changes I've made in the base template propogating?

One possible reason for propogation to not happen was supplied by Tim Heuer. (edited)

FrontPage editing has great UI capabilities, but does "break" the tie between the original base template that the site derived from. Any edits made to the site or page using

Frontpage make that site/page a "non-ghosted" site/page,

69

This means that if you change the underlying base template, none of the changes will propogate to sites/pages that were (earlier) modified in Frontpage".

III.33.1 I can't run smigrate locally on my server - what might be my problem?

One cause for this is that you have IE installed in the Internet Explorer Enhanced

Security Configuration.

You can solve the problem by either a) removing the Internet Explorer Enhanced Security Configuration or (better) b) running smigrate with the -u and -pw parameters so that you can specify both the

DOMAIN\User and passwprd of the account that should be used to perform the migration.

(Thanks to both David McKenzie and Troy Starr)

III.33.2 How do I use smigrate to move sites with spaces in their names?

The smigrate utility does no work with websites with one or more spaces in their names.

So for instance smigrate -w http://server/foo bar -f c:\foo bar.fwp does not work.

Instead use double quotes for names with spaces.

Thus smigrate -w "http://server/foo bar" -f "c:\foo bar.fwp" will work.

(Thanks to Iyaz)

70

III.33.3 What is the difference between using smigrate to backup a site and using stsadm?

There is a difference in granularity.

Here's (edited slightly) Iyaz's take on this.

Stsadm backups up an entire site collection and restores only as a site collection.

Smigrate can be used to just backup one site or subsite and then be used to restore to another site.

Smigrate does not migrate permissions though.

Smigrate also does not migrate personal customizations (i.e. does not migrate your

Personal View on the Home Page).

III.34 I can never get the formulas in a Calculated Field right. Where can I get Help with this?

This tip come from Gary A. Bushey and is something I at least hadn't noticed and could turn out to be very useful.

When you add a Calculated Column you have an section in the centre of the screen called

"Optional Settings for Colum". In that section you'll see a link for "show me more information".

Initially, this looks a complete waste of time, but go to the 'Calculated' entry at the bottom and then select the "About Computed and Calculated Columns" link.

That's a big improvement as are some (but not all) of the links at the bottom of that section. (Gary mentions in particular the 'Functions' link)

III.35 How do I restrict access to a document library?

This is simple when you know how!

- Open the document library

- Modify Settings and Columns

- Change Permissions for this document library

The default is that the roles Reader, Contributor and Web Designer (plus Administrator) with rights to the site have access to all document libraries.

71

These three roles (not Administrator) are listed at this stage.

- Remove them

- Add the users you want to have access

- Give them the rights you want them to have

- Go Back to Document Library

Now everyone accessing this Document Library will need to specify an approved name and password to do so

III.36 How do I transfer a lot of documents to WSS?

There are various methods of doing the copying

WSS UI - multiple documents; Copying from hard disk folder to Explorer View in WSS;

Copying from directory to directory (using the Net Use view of the WSS doc lib);

Copying to the doc lib as defined in My Network Places.

Two riders:

1. WSS doesn't seem to be happy to get a lot of documents (in size) at one go. The default is 50MB and problems may start at 100-200 MB per upload (and there's always a problem with single files that are in the 70MB - 100MB range).

2. If you have additional fields in your document library (which is a useful way to go - for Source; Category; TransferDate etc.) and these have default values, the files that are uploaded to the doc lib while those values are the defaults will get those values in those fields.

So a useful tip is to specify defaults; upload the files that match those defaults; change the defaults; upload those files etc. This can often save a lot of time later.

Watch out too for the Upload Document function where it seems you can specify values when uploading Multiple Documents. It will not take the values you specify there but will take the default values you have specified in the doc lib itself.

Note: The default value for the upload size of a batch of files is 50MB. Thus, when the default is used, even single files greater than 50MB in size can not be added to the site.

In order to change the default, you need to do the following

72

Go to the server and then

Administrative Tools

SharePoint Central Administration

Configure Virtual Server Settings

<Select the site you want to configure>

Virtual Server General Settings

Max Uploads Size

III.37 After upgrading from WMSDE to SQL Server 2K I can't install SP3 and

Search doesn't work. Why?

The symptoms of this are that when you try to install the Service Pack 3 of SQL Server

2K - after having upgraded in place from WMSDE to SQL Server 2K - this doesn't work because it says that SP3 is already installed. Installing SP3 is however necessary in this case in order to get WSS Search to work.

The reason for this is that WMSDE that is installed as default with WSS is already at SP3 level. Thus when this is upgraded to SQL Server 2K, SQL Server thinks it too is already at SP3 level and refuses to perform the SQL Server 2K SP3 installation.

The solution is to install SQL Server 2K SP3a, this - despite theoretically not being needed if you already have SP3 - is as far as SQL Server is concerned not SP3 and thus will install.

(Thanks to Christoph Vogt for researching this and posting the facts behind this text in the newsgroup)

III.38 How do I restore a (WSS) SQL Server backup to *another* server?

Note: restoring to the same server is covered in the Admin Guide. Here are some detailed suggestions from Iyaz as to how to restore to a new site (which Steven from New Zealand found solved this problem)

1) On the Backup server(standby or whatever you are calling) extend the virtual server as a WSS site.

2) Restore the backup of content database to the backup server.

3) Using the WSS Admin UI, go to the Virtual Server you have extended-Manage content database and remove the database. Then using the same UI now add the restored database.

4) This will populate the config databases for you with the right information(please note you do not have to restore the config database to the Backup Server)

73

5) Please note that the Content App Pool account of this backup server must have the same account that you have been using for the Productions erver. If not then using SQL queries you need to change the DBO owner of the restored database to the one you are using (the Admin guide gives you a query on how-to do this)

6) Once added now you will be able to browse to the site you want and restore the documents from there or do a stsadm backup and restore an entire site collection the

Production server.

Many thanks to Iyaz !

Note: There was also a case where someone only wanted to move the config and content databases. In this case Iyaz had the following additional advice for him

"You need to just restore them to the SQL Server you want. Make sure that the DBO owner for this is the same as your App Pool accounts. Using the WSS Admin UI then set the configuration database server and then set the default content database server."

III.39 I get "Can not add the user because a user with that name already exists."

How do I add the user?

Go to

- Site Settings

- Site Administration

Under Site Collection Administrator

- View Site Collection user information and delete the user from there.

Then add the user back.

(Thanks to Iyaz for this)

74

III.40 How can a user change his/her password in WSS?

[I haven't tested this solution myself and I am not sure in which cases it applies - more info gratefully received - but given that this question is asked quite often here's two approaches.]

Use the built-in IIE5/6 password change feature? You just need to add a new virtual directory to IIS (e.g. named "iisadmpwd") and point it to

"c"\windows\system32inetsrv\iisadmpwd". Then make sure to exclude it in the "Managed

Paths" section.

[You can find the Managed Paths section as follows - Start/All Programs/Administrative

Tools/SharePoint Central Administration/(Virtual Server Configuration)Configure virtual server settings. On the Virtual Server List page, select the virtual server you want to configure. On the Virtual Server Settings page,(Virtual Server Management) Define managed paths.]

If you don't like the UI just tweak the .ASP files as you like (e.g. I removed the bold header) and then put it into a Content Viewer Web Part using a URL like this:

" http://YourServer/iisadmpwd/aexp4.asp

".

Thanks to

Dave Colbeck

for the above main text. (Well actually

Jeremy Rammalaere

who seems to have written it first). Thanks too to

Christian Holthe

for the suggestion to include where the Managed paths section is.

(Note that .asp files are probably not allowed to be uploaded to your site. Remove them from the banned list by following WSS FAQ item I.12.3)

Note:

"Doug"

points out that

if you are using WSS in Active Directory Account Creation mode all users will see a

"Change Password" link on the user information page (_layouts/1033/userdisp.aspx) which allows them to manage their password (enter old, enter new and confirm new password dialog).

Administrators also have the ability to set a users password through this UI (enter new and confirm new password).

Or in other words the original procedure (above) is only necessary if you are NOT using

Active Directory Account Creation mode.

75

III.41 Why can't I synchronize certain properties between a WSS document library and Microsoft Word?

Background: If you create a new field in a WSS document library then that field also becomes a property of the Word Document itself.

There are however two different cases (and three different results)

A. The field name you use is also the name of a standard Word Property

A.1. The field name is listed in the Summary Box of the Word menu Item (File)

Properties (and is not the Title field)

(Fields Subject, Author, Manager, Company, Category, Keywords, Comments Hyperlink

Base)

In this case there is no synchronization and if you create a field in a WSS document library called "Subject" it's contents will appear in a Word Property called Subject0 and the Subject Word Property will not have changed.

A.2 The field Title (from the Summary Box) and all other names of standard Word properties that are not listed in the Summary Box.

In this case there is synchronization.

B. The field name you use is NOT the name of a standard Word Property.

In this case there is synchronization.

The above text is loosely based on information provided in the newsgroup by Iyaz

(thanks Iyaz!) BUT the interpretation and possible inaccuracies are solely mine.

III.42.1 I have added a list template to the list template library but it is not available to my Create. What's the problem?

If you create a list template in (say) a site based on a Meeting Template, the list template can only be used when creating a list in another site based on a Meeting Template.

Thus if you are in a normal Site your list template from a site based on a Meeting template will not be listed under Create.

76

III.42.2 I can't find how to add a list from a list template to my site. Can you help?

(I added this because I went round in circles trying to do this - when you know where to go it's simple)

Go to the site (i.e. sub-site or old name subweb) where you want the list to appear.

- Modify This Workspace

- Site Settings

- Modify Site Content

- Create New Content

The list template you need should be listed under Lists or Customs Lists (if not check

III.42.1 to see if that applies).

Select the one you want; give it a name and OK.

The list is now included in your site under the new name.

III.43 Why can't I specify anonymous access to my WSS web site? (It's greyed/grayed out)

You need to first enable Anonymous on the Virtual Server using the IIS MMC.

Only when this is done is setting anonymous access a selectable option.

III.44 I get "Data Source does not contain valid XML Data" when adding a WSS

List with Data View. What's my problem?

One possible cause of this error is that the list schema is no longer valid.

One example of this would be that Lookup fields reference lists that no longer exist.

(Thanks to Colin Bowern)

77

III.45 I've just installed a third-party web part, but it's not listed on my site. What's the problem?

Some webparts from third-party suppliers (usually the ones that cost money) include installers that also ensure that their web part is (after installation) automatically visible in your list of web parts (after doing Add a Web Part + Browse) typically in the "Virtual

Server Gallery".

Others such as the free RSS Feed Reader from

Tim Heuer

( http://www.timheuer.com/stuff.htm

) need a bit of extra work .

[All the following takes place on the WSS server]

Once the standard installation has been completed, open a Command Prompt and go to c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN and run the following command line exe stsadm.exe -o addwppack -filename <filename> -globalinstall

Here the tricky thing is that you do NOT specify as file name the *dwp file but instead specify the .cab file (in the case of the Tim Heuer file something like

TimHeuer.SharePoint.WebParts.Rss.cab in place of <filename> - I was lazy and copied the file to the BIN directory first).

After that it might also be a good idea to do an IIS Restart.

[One way to do this is to go to Administrative Tools / Computer Management / Select

'Internet Information Services (IIS)' in 'Services and Applications' / Right Click and 'All

Tasks' / Restart IIS]

Now when you Modify My Page in your Client and do Add WebPart / Browse, these new webpart(s) should be listed in Virtual Server Gallery and you can use them just as you use webparts from Microsoft.

Finally there are parts that come without any form of installation package such as those from

Jan Thielens (http://weblogs.asp.net/jan/Rss.aspx

)

and

Patrick

Tisseghem(

http://radio.weblogs.com/0126624/rss.xml) that need to be installed completely by hand.

Here is an example of Jan's installation instructions

78

To install these web parts: copy the DLL into the BIN folder (or put it in the GAC), copy the DWP files in the WPCATALOG folder and add the following line to the

SafeControls section of the Web.Config:

<SafeControl Assembly="Leadit.SharePoint.Essentials, Version=1.1.0.0,

Culture=neutral, PublicKeyToken=6f708acd0ffbe583"

Namespace="Leadit.SharePoint.Essentials" TypeName="*" Safe="True" />

In order for you to be able to do this you need the following information about the paths used by default for these three items (for a single standard WSS site)

a) bin subfolder

c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN

b) wpcatalog

c:\Inetpub\wwwroot\wpcatalog

c) web.config

c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\CONFIG

StopPress: Jan’s web parts are now packaged!

III.46 How can I recover individual documents to my WSS site?

For this you need to be using a backup product with document-level backup and restore.

Most established backup companies are working on such products but have not yet released them.

The one company that seems possibly (make your own investigation) to have achieved this is a SharePoint migration company that also says it has backup tools with documentlevel etc. capabilities.

This company's information page (issued Jan 2004) is at http://www.avepoint.com/website/product.html where it should be noted that the backup tools are only specified for SPS 2001 and SPS

2003 despite WSS being mentioned earlier on the page in another context.

79

[The above information will be revised as and when more information about this and other backup products becomes available. Mike]

III.47 Why can't I see the link for "Manage Access Requests" in my top-level admin?

This function is not available when the site is in AD Account creation mode.

III.48 How do I add a Back button to my WSS Menu Bar?

This request came from an administrator whose users "had difficulty" in finding the browser's Back button when in WSS.

Siegfried Weber provided an answer that did not rely on local server access but which only (probably) works with IE browsers.

"Add a new link to your navigation bar, name it "Back" and add the following as URL: javascript:history.back();

III.49 Are there any other filter parameters for a List View than [Me] and [Today]?

No, but there is a workaround.

Create a calculated field. There you will have access to a wide range of functions. Then use this calculated field in your View.

Example:

You want to show all tasks where [Begin] date is within one month of the current date.

1. Create a calculated column [BeginOneMonthAgo] = [Begin] - 30

2. Create a View with a filter that applies to the [BeginOneMonthAgo] field -

[BeginOneMonthAgo] less than [Today]

Thanks to Bogdan Chernyachuk for this example.

80

III.50 What workflow approval possibilities are available?

WSS provides basic approval facilities.

This basic one-step approval process can be extended by Document library event handlers. For more information on this see http://msdn.microsoft.com/library/default.asp?url=/library/enus/spptsdk/html/tsptDocLibEvents.asp

Finally, various third-party companies already offer or are working on various levels of workflow support. These include

CorasWorks

http://www.corassolutions.com/default.aspx

FlowBuilder and WorkFlow Engine (DataLan)

http://www.sharepointstuff.com/_wsn/page3.html

K2.net 2003

http://www.k2workflow.com/Default.aspx?d=1

SMART Workflow

http://www.lmrsolutions.com/products_workflow.asp

SmartLibrary v1.1 (Nintex)

http://www.nintex.com/Product-SmartLibrary.aspx

and

Teamplate Workflow Wizard for Microsoft SharePoint Products and Technologies

( http://www.teamplate.com/internal/product/sharepointworkflowwizard.asp

Thanks to

Doug Peterman

for providing the impulse for this FAQ item and most of the information.

81

Thanks also to

Tariq Al Ayad

for adding two more to the original list.

III.51.1 How do I index OneNote files?

1. Install OneNote on the WSS Server.

2. Setup WSS to index .one files.

(The IFilter will be installed when you install the OneNote application on the server)

Thanks to James Edelen !

III.51.2 How do I index .rtf files?

Note: This solution uses a file from the SharePoint Portal Server *2001* Resource Kit. I haven't tested it myself yet, but

Jon Smith

who provided the following information reports that it is working fine in his early tests.

Download the rtf filter file

from here http://www.microsoft.com/sharepoint/server/techinfo/reskit/rtf_filter.asp

and then do the following steps.

Installation:

1. Add rtffilt.dll to your system

Copy rtffilt.dll to WINNT\System32 on the operating system drive of the computer running SharePoint Portal Server.

2. Register rtffilt.dll a) Click Start, point to Programs, point to Accessories, and then click Command Prompt. b) At the command prompt, type Cd /d %windir%\system32, and then press ENTER to navigate to WINNT\System32 on the operating system drive. c) Type regsvr32 rtffilt.dll, and then press ENTER. d) Click OK to close the message.

82

e) Exit Command Prompt.

3. Restart the Microsoft Search (MSSearch) service a) Click Start, point to Programs, point to Administrative Tools, and then click Services. b) Right-click Microsoft Search, and then click Restart.

Thanks to Jon Smith for providing the above information!

III.51.3 How do I index XML files?

There's an XML Filter available at http://www.quilogic.cc/ifilter.htm

(Price in May 2004 $99 / single machine - +20% tax if you are in EU).

(Thanks to

Michael Greth

for finding this company)

III.52 I need to recreate my site utilizing a new site architecture. How can I do this without deleting all of the sites?

Adam Macaulay provided the following detail but with the following rider "You are not going to be able to overwrite a template which is already in place unless you do a restore".

1) Create a Site Templates of your expected Root Site and your Sub Site that you eventually want to have setup, make sure to include data.

2) Add your root site template to the Global Catalog via stsadm -o addtemplate -title "TEMPLATETITLE" -filename FilenameLocation

(one line)

3) Create a new top-level site under a managed path "/sites" which will be a dummy site for you to create a backup from.

4) Use the template you loaded into your global catalog for the root site.

5) Re-add any users you had at the old site, so they will, should, carry over into your subsite.

83

6) Add the subsite template you created earlier to your site template gallery in the new site.

7) Check everything and make sure you are getting everything you wanted.

8) Backup the new site via stsadm -o backup -url http://url/sites/newsite -filename filenamelocation -overwrite\

(one line)

9) Backup your old site just in case you need data or setup information stsadm -o backup -url http://url/ -filename filenamelocation -ovewrite

(one line)

9) Restore to your current URL stsadm -o backup -url http://url/ -filename filenamelocation -overwrite

(one line)

10) Check everything.

Adam added the following -

Note: This procedure should only take about 30 minutes to 1 hour to complete.

Some items to note,

- Security will not be carried over in your template if you your new site doesn't have users added already.

- You will need to be cautious as you will need to try your best to keep the site structure intact when you create your new site collection for which you will create a backup from and restore over your old site.

- If anything fails keeping a backup of your old site for restoration if necessary is a good idea.

84

III.53 How do I programmatically upload a document?

Here is some code from

Adriaan

.

//Load the local file into a stream

FileStream stream = File.OpenRead(@"c:\test.doc"); byte[] content = new byte[stream.Length];

//Read the file into a byte array stream.Read(content,0,(int)stream.Length); stream.Close();

//name of the document when saved in the libary string fileName = "test.doc" mySiteCollection = new SPSite(" http://Localhost ");

//Grab the rootSite myWeb = mySiteCollection.RootWeb;

//Get the folder that should store the document folder = myWeb.Folders["MyFolder"];

//Upload the File

SPFile myFile = folder.Files.Add(fileName,content);

//Check in the file

myFile.CheckIn("Check in the file");

III.54 I cannot import from Excel 2003 to WSS. What's the problem and solution?

The user had the following problem

When I attempt to import an Excel 2003, I invariably receive the following error message after selecting the range of the sheet with the import data: "cannot connect to the server at this time. Your list cannot be published."

According to

Iyaz

, this is a known problem with WSS systems that are running in AD mode.

The solution - as supplied in the same thread by

"Ben"

was

1. Bring the sheet in to a top level site

85

2. Save as a template

3. Add to sub-site.

as the reason for the problem is that in this mode importing to a sub-site is not possible.

If this doesn't help, consider push instead of pull - i.e. try going in the opposite direction -

'publishing' the list from Excel 2003 to the WSS (sub) site.

The following Microsoft Office Online Training pages might be useful to you for this.

Lists I: How to use lists in Excel 2003 - http://office.microsoft.com/training/training.aspx?AssetID=RC010801391033&CTT=1&

Origin=EC010229841033&QueryID=pIL5v0hw40

Lists II: Publish Excel 2003 lists to a SharePoint site - http://office.microsoft.com/training/training.aspx?AssetID=RC010916061033&CTT=1&

Origin=EC010229841033&QueryID=pIL5v0hw40

Thanks to

Jim Duncan

for this alternative suggestion !

III.55.1 Alerts aren't working even if the Timer Service is running. What might be wrong?

[This is the first posting related to Alerts - I'll add more when they come in a FAQ-type form.]

This particular problem was explained (in my words) as follows

When people sign up for an Alert, they receive the E-Mail confirmed they are signed up, but they never receive any Alerts.

Doug commented as follows

Alerts cannot be processed if the account that the SharePoint Timer Service is running under does not have access to the content database.

In my experience the symptoms were identical - I did get immediate notification that the alert was set up (and it was), but no alerts actually processed as expected. As soon as I granted access in the content database to the account that the sptimer service was running under I was flooded with about 250 alerts.

86

Note: This also might be a reason for a Usage Analysis processing job not to work.

III.55.2 Can an Administrator create Alerts for others?

Please see I.12.2.4. where this is answered fully.

III.56 How do I avoid seeing an old document version after doing Edit in MS Word

?

The answer to this question applies also to similar cases where an earlier version of a document is still being displayed.

Erik Johnson

pointed out that

In IE, go to Tools, Internet Options. Under Temporary Internet files, click the button for

Settings. Check for newer versions of stored pages: Every visit to the page.

might help.

David McKenzie

, however, noted that this workaround might affect users negatively in other ways and should therefore only be regarded as a workaround.

(In particular he notes that users on slower connections will notice degradation in sharepoint page loads)

III.57 How can I get OCR Indexing of TIFFs in WSS?

Gregg Smith

sent me the following solution to this WSS problem. The text has been edited by me and I - not Gregg am responsible for any errors in it.

SharePoint Portal Server 2003 gives users the ability to search on the content of faxes and other TIFF type documents via OCR.

Windows SharePoint Services can have this ability as well by installing a tool from the

Microsoft Office 2003 suite on the WSS server.

Carry out a custom installation of Office. This will present the menus you need. Deselect all other options except the 'Microsoft Office Document Imaging' which is under Office

Tools.

87

Make sure the component is fully installed and not only specified as "On First Use".

With the addition of this Indexing Assistant, when WSS finds TIFF files it will have MDI perform OCR on the document and build that information into the Full-Text Index for later retrieval.

The OCR runs in your Default System Language Setting but this can be changed.

With the completed setup you should now be able to search for, and find, text inside TIFF and MDI files. When testing be sure to allow enough time for WSS to update/rebuild the

Full-Text Indexes.

Check with your Microsoft Licensing Rep. to see if/how this will effect your licenses as per your lic. agreement.

(Mike: It is very possible that you will need to assign a license of Office to the WSS server - be warned.)

III.58 I have several hundred web parts. Browsing and clicking Next takes forever.

How can I get to a web part quicker?

The question actually was

If you have 500 lists and the one you want to add is at the end, you have to click the Next link 50 times.

Is there a workaround for this?

The answer is simple when you know how

I personally Search for the web part instead of browse... goes a lot faster than next, next, next..

Thanks to

MDS

for this answer.

88

III.59 How can I make the link between Web Part Connections a dropdown list rather than the standard radio buttons?

When you create a web part connection, the originating part (i.e. the one where you make the selection) changes to a radio button list.

"Jeff"

asked whether a dropdown list would be possible and

John Jansen

sprang into action with the following FrontPage 2003 solution.

If you change to using a Data View Web Part using FrontPage 2003 then you have the ability to use any view style and fire connections. One of the view styles is a dropdown list, so you could do it pretty easily.

There is a bit of trick with using the dropdown style, though, because the connections wizard does not know how to create an onchange event.

If you want to pursue that, here are the steps:

1. Insert two Data Views of your data.

2. Select one of the Data Views, choose Style from the Data View Details taskpane.

3. Choose the drop-down box style from the list of styles, click OK.

4. Right click this Data View, choose Web Part connections.

5. Connect to the other Data View as you would normally.

6. Go into Code View.

7. Look for the <a target="_self"> code that looks similar to this (usually, it would be the first <a> tag in the page) and copy the entire block for the first XSL:ATTRIBUTE (see below):

<a target="_self">

<!-- NOTE: start copying here -->

<xsl:attribute xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="href"><xsl:variable name="cursel">dvt_curselkey={<xsl:value-of select="$CurrentRowKey"/>}</xsl:variable><xsl:variable xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="fields">@ID=<xsl:value-of select="ddwrt:ConnEncode(string(@ID))"/></xsl:variable>javascript:<xsl:value

89

-of select="ddwrt:GenFireConnection(concat('99d2bb39-f973-482c-a0ca-e49b56eae72d

*',$fields),string($cursel))"></xsl:value-of></xsl:attribute>

<!-- NOTE: end copying here-->

<xsl:attribute name="style"><xsl:if test="$CurrentRowKey =

$dvt_curselkey">font-weight: bold;</xsl:if></xsl:attribute>

<xsl:value-of select="@Title"/>

</a>

8. Look for the code for the <option> tag. It should be right above the <a> tag.

9. Paste in the section of code you copied above.

10. Change the name="href" part to name="value". At this point, you should have something like this:

<option style="display:{$GroupStyle}">

<xsl:attribute xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="value"><xsl:variable name="cursel">dvt_curselkey={<xsl:value-of select="$CurrentRowKey"/>}</xsl:variable><xsl:variable xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="fields">@ID=<xsl:value-of select="ddwrt:ConnEncode(string(@ID))"/></xsl:variable>javascript:<xsl:value

-of select="ddwrt:GenFireConnection(concat('99d2bb39-f973-482c-a0ca-e49b56eae72d

*',$fields),string($cursel))"></xsl:value-of></xsl:attribute>

<a target="_self">

<xsl:attribute xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="href"><xsl:variable name="cursel">dvt_curselkey={<xsl:value-of select="$CurrentRowKey"/>}</xsl:variable><xsl:variable xmlns:xsl="http://www.w3.org/1999/XSL/Transform" name="fields">@ID=<xsl:value-of select="ddwrt:ConnEncode(string(@ID))"/></xsl:variable>javascript:<xsl:value

-of select="ddwrt:GenFireConnection(concat('99d2bb39-f973-482c-a0ca-e49b56eae72d

*',$fields),string($cursel))"></xsl:value-of></xsl:attribute>

<xsl:attribute name="style"><xsl:if test="$CurrentRowKey =

$dvt_curselkey">font-weight: bold;</xsl:if></xsl:attribute>

<xsl:value-of select="@Title"/>

90

</a>

</option>

11. Look for the <select> tag for the drop down. It should look something like:

<select name="ID" size="1">

12. Add an onchange event handler for the tag, as follows:

<select name="ID" size="1" onchange="eval(this.options.value)">

Now when you change the value your drop-down, your connection should fire.

III.60 How can I make text in a Multiple Line Field Type a Hyperlink?

In the standard form of a Multiple Line field type where you have allowed formatting, it is only possible to specify first the name of a link and then the link itself - i.e. there is no hyperlink function in the menu line.

Keith Holt

asked if it would be possible to make text link to a URL rather than having to specify the URL.

Iyaz

supplied the following fix with additions from

Jeff

.

Open your site in FrontPage 2003

Navigate to the list folder under the site menu,

(On the left) Expand the list folder,

Right click the relevant List file

Choose Properties

Select the Field where you want to include a hyperlink

Click Modify

Check the box to allow hyperlinks in the field.

91

Then, your rich text toolbar will suddenly have a hyperlink button added to it:-)

Thanks to both

Keith

for the question and

Iyaz+Jeff

for the answer.

III.61 How do I prevent users from Editing my WSS sites with FrontPage?

The papers explaining this are for SPS 2003 but can be used for WSS too.

Iyaz

said that there will be a WSS-specific document someday but that for the moment the following two papers cover this theme. http://support.microsoft.com/?id=831612 http://www.microsoft.com/technet/prodtechnol/office/office2003/maintain/fp03sps.mspx

Eric

also confirmed the suitability for WSS with this text

The same thing applies to WSS. Just add the proper attributes to the ONET.XML project element. I have tested this and it seems to work.

However, beware... clients can also connect using FrontPage 2002 and hose their sites up real good. Microsoft told me there's no way to prevent this other than to tell them not to do it.

III.62 How can I enable Outlook to see a WSS workspace as a valid repository for shared attachments?

This is the message being shown in a pop-up when using Outlook 2003

Microsoft Office Outlook:

Shared attachments are not available for this location. You may not have permission to access the location, it may not be a trusted site, or it may be unavailable.

Here is the solution from

Skip Shean

Open a browser, go to your WSS site.

Tools --> Internet Options --> Security Tab

Select Trusted Sites

Click the "Sites..." button

Uncheck the "Require server verification (https:) for all sites in this zone.

92

Put your domain in the "Add this web site to the zone:" field like: http://*.yourdomain.com

III.63 How can a user be automatically e-mailed that a task has been assigned to him/her?

PD

was using a Task List when he discovered that it was impossible for e-mails to be sent automatically to users to inform them that a task had been assigned to them.

Michael Reinhart

supplied the answer -

Buld your list using the "Issues" list template instead of the Task template.

You will find that that functionality is included.

(The setting is in the list's General Settings.)

Thanks Michael!

III.64.1 I am getting "#50070: Unable to connect to the database STS_Config?".

What's my problem?

This seems to occur only with the WSS implementation of SBS 2003.

The following text comes from

Susan Bradley

via an anonymous SBS newsgroup member.

It has been added here because just this question has been asked in the WSS newsgroup a couple of times already.

“Based on my research, this problem could be caused because the SharePoint Timer

Service failed to contact the SharePoint database while the SBS is rebooting. In SBS

2003, the SharePoint Timer Services is used to send notifications and performs scheduled tasks of WSS. It needs to access the SharePoint database when starting.

Since the Veritas Backup exec software is installed on the server box and several backup exec related services have started during the reboot, these services could cause the

SharePoint database from being mounted in a timely manner, thus, causing the problem to occur.

I reproduced this problem in my test machine.

93

After the MSSQL$SHAREPOINT service has stopped, this error message will be logged in the application log. You may now try to manually start this service to see if the problem will still occur.

1. Start-->Run-->Type 'services.msc' (without the quotation marks) and press Enter.

2. In the Services console, stop the 'SharePoint Timer Services'. Check the status of the

'MSSQL$SHAREPOINT' service, make sure it has been started and then restart the

'SharePoint Timer Services'. The problem should be resolved.

If there is no problem with the manually service startup, we can set a service dependent of the SharePoint Timer Service. Please try the following steps:

1. Start-->Run-->Type 'Regedit' (without the quotation marks) and press Enter.

2. In the registry editor, navigate to the following registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

3. Right-click the blank area in the right panel, click 'New'-->'Multi-String Value'.

4. Input the value name 'DependOnService' (without the quotation marks) and then double-click the newly created value. In the value data area, type

'MSSQL$SHAREPOINT' and click 'OK'.

5. Close the registry editor and reboot the server box.“

III.64.2 I am getting ’#50070: Unable to connect to the database WSSConfigDB on

SqlServer”.What’s my problem?

The full message is

"#50070: Unable to connect to the database WSSConfigDB on SqlsServer. Check the database connection information and make sure that the database server is running.

The answer from

Iyaz

was

You will see this if the Sharepoint Timer Service is not running in the same account as the WSS Admin App Pool account.

Make sure they are the same.

94

Thanks again,

Iyaz

!

III.65 How can I stop users from adding content when I don’t want them to?

We've all had them, users who continue to work with your application long after you've requested that they go home.

Here's how to make sure they don't amend anything.

Thanks to

Thom Robbins

for blogging on this - even though it's in the WSS UI it's not easy to find.

Here are the details

On the WSS Server:

1. Start / SharePoint Server Administrator

2. Portal Size and Server Configuration section / "configure site quotas and locks from the Virtual Server list page"

3. Manage Quotas section / "Manage site collection quotas and locks"

4. Specify your site name / Click View Data

5. Specify either a. Adding content prevented (Disables file upload capability within WSS and SPS sites) or b. No Access (Disables access to the entire site)

If you want to see this in glorious technicolor with screen prints, Thom's blog item is at http://radio.weblogs.com/0131777/2004/04/09.html#a111

III.66 How do I create Multiple Workspace Site Definitions?

In the case of Meeting Workspaces the template ID is hard-coded to be a value of 2.

This means that you can only have one Meeting Workspace Site Definition because you can only have one Meeting Workspace template where ID=2

(This answer is based on one from

Iyaz

- thanks to him and hopefully I got it right)

95

III.67 How can I make it possible for anonymous users to save their survey responses?

Anonymous users of a site that allows anonymous access can access a Survey but can not save their surveys.

In order for this to be possible, you need to go to the permission settings for the survey.

There in the left-hand-column you'll find an option for anonymous users.

Here you need to set View, Add and Edit permissions.

Thanks to an anonymous "

Mike

" for supplyng this answer.

III.68 I’m getting ”Server Error in’/<application name> Application” – what’s my problem?

One reason for this message is that you are running an application (for instance an

ASP.NET application) on your WSS server.

In order for this to work you need to exclude the path used by this application from being processed by WSS.

You do this by adding an Exclude Path for the Virtual Server - so:

- SharePoint Central Administration

- Configure Virtual Server Settings

- specify the virtual server (perhaps the default web server)

- Define managed paths

Thanks to

Eugene Jenihov

for supplying this answer.

(Oddly enough although the need for an exclude path is well-known, this error message isn't.)

96

Note that there has also been a message from

Hari Nayarayan

with more on installing

an ASP.NET application on a WSS Server.

"The easy solution is to install WSS in a separate Virtual server.

If you really want to make your ASP.NET app to work in the same Virtual server as

WSS, you have to do the following.

1) Exclude your ASP.NET app's path within WSS

(Mike: as above)

2) Do the following changes to your ASP.NET app's web.config file under <system.web> tag.

<httpHandlers><clear /><add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0,

Culture=neutral,

PublicKeyToken=b03f5f7f11d50a3a"/></httpHandlers><httpModules><add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule"/><add name="Session" type="System.Web.SessionState.SessionStateModule"/></httpModules><!-- Enable

Session for the pages in your application --><pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="true" /><trust level="Full" originUrl="" />

3) Your app may be using some features within your ASP.NET app, that requires some additional modules to be added to your app's web.conf

Thanks

Hari

!

97

III.69 How do I edit Link List URLs in Datasheet View?

Datasheet View is very useful for making quick bulk changes to a List. But if you have a

Link List, you'll find that it is impossible to edit either the Name or the Address part of a

URL field in Datasheet View. Instead to do this you have to go to Standard View and open each item separately.

So the answer to the FAQ question is - You can't.

But there is a workaround that has been kindly supplied (here in severely edited and amended form) by

Rohan Cragg

that is worth using if you have a lot of these URLs to

edit.

A typical scenario is that you have a list of Names and you need to add the http addresses for each name. Ideally you would copy the Names in one go into the Datasheet View of a

Link List and add for each name the http address. But this doesn't work.

So Rohan's (amended) suggestion is that you start by creating an empty Excel spreadsheet. You then copy your list of names to column A; and write the appropriate http addresses in column B (using the usual Excel copy techniques to save writing the same 'text' over and over again.

Then you in Column C create a formula that looks something like this

=HYPERLINK(A1,B1)

["something like" because in my case with a Finnish locality and despite my use of US

Excel, I needed to write =HYPERLINK(A1;B1) for this to work]

Having then copied this formula to the rest of the column, you now have in column C a set of "URL"-style fields that you can copy in Excel and then paste into the URL field of a WSS Link Library.

Thus saving (for long lists) an awful lot of time for a relatively small additional set-up time.

Thanks to

Rohan Cragg

for the idea of using Excel and HYPERLINK. As always when I edit supplied material, mistakes in the text here are mine.

98

III.70 How can I enable anonymous users to add, delete or edit files in document libraries?

You can't.

The answer - as supplied by

Iyaz

- is that you can't do this for Document Libraries, Form

Libraries or Picture Libraries.

It is only possible for List items to be added, deleted and edited anonymously.

Thanks Iyaz !

III.71 How do I see which web parts I am using in a page?

Add

?contents=1

to the end of the address of the page.

So for instance

http://wmxx0001/Product%20WebPages/Exchange.aspx?contents=1

Thanks to

Patrick Tisseghem

for blogging on this and to

Steve Clarke

for improving on his solution.

III.72 What code do I need to access an Oracle database?

It's quite straightforward to access SQL Server databases from FP 2003's Data View function, but, although supported, accessing Oracle databases is more difficult.

Here is some text provided by "Steve" (who has done this) followed by guidelines provided earlier by David Mackenzie - you'll find those below in Italic Black.

---------

1. Install the Oracle Client onto the SharePoint server.

2. Reboot the server.

3. Either alter the C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\CONFIG\wss_mediumtrust.config file or alter your

C:\Inetpub\wwwroot\web.config file.

Add the following to the wss_mediumtrust.config file:

99

Under the <SecurityClasses> node enter

<SecurityClass Name="OleDbPermission"

Description="System.Data.OleDb.OleDbPermission, System.Data,

Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>

Locate the <trust> node in the web.config and ensure that it reads as follows:

<trust level="WSS_Medium" originUrl="" />

OR

Forget the wss_mediumtrust.config file and just locate the <trust> node in the web.config and ensure that it reads as follows:

<trust level="Full" originUrl="" />

4. Reset IIS either in the console or use iisreset at a command prompt.

5. Write your code, I suggest using the OleDb objects.

EXAMPLE:

'Setup your connection string...you can put it in the Sub, or make it a Const, or put it in the Web.config file, whatever you like.

Dim strConn as String =

"Provider=OraOLEDB.Oracle.1;Password=<your password>;Persist Security

Info=True;User ID=<your id>;Data Source=<your datasource>"

'Construct your Query or use a SPROC, again whatever you like.

Dim strSQL As String = "SELECT * FROM Table1"

'Create the connection object.

Dim oConn As OleDbConnection = New OleDbConnection(strConn)

'Create and use a command object, best practice.

Dim oCmd As OleDbCommand = New OleDbCommand(oConn)

'Use it in a dataset, datareader or whatever...I'm using a dataset for example only.

Dim oDs As Dataset = New Dataset

Dim oDa As OleDbDataAdapter

100

'I like With because it cuts down on keystrokes when you start adding parameters and such, and I read somewhere that it actually gives you a slight performance boost

With oCmd

.CommandType = CommandType.Text

.Connection = oConn

End With

oDa = New OleDbDataAdapter(oCmd)

oDa.Fill(oDs)

Do something with the dataset here...

'Clean up those objects

oDa.Dispose

oCmd.Dispose

oConn.Dispose

------------

Here is the text that started him off (kindly provided by

David Mackenzie)

.

Try

'#1: setup the database connection info oraConn = New OracleConnection(connectionString) oraCmd = New OracleCommand

'#2: query information oraCmd.CommandType = CommandType.Text oraCmd.CommandText = "SELECT ..."

'#3: the OracleCommand object needs to be associated with an active connection oraConn.Open() oraCmd.Connection = oraConn oraDA = New OracleDataAdapter(oraCmd)

'executes the query information set at #2: myDataSet = New DataSet mydatagrid = New DataGrid newColumn = New BoundColumn

'Define grid columns

...

Controls.Add(mydatagrid)

' you can access the data via myDataSet.Tables(0) using the row index.

' this data can also be bound to a DataGrid with this syntax:

101

oraDA.Fill(myDataSet) mydatagrid.DataSource = myDataSet mydatagrid.DataBind()

'[Text] = Str(mydatagrid.Items.Count) oraConn.Close()

Catch ex As Exception oraConn.Close()

[Text] = "Oracle Connection failed" & " - " & ex.Message

End Try

David also noted that

Trust=Full is required for the Oracle .Net dataprovider

(otherwise there is a "security error")

Oracle .Net client is required on the server

III.73 In an Issues List, how do I set alerts so that I get an alert only when something is changed in a post assigned to me?

You can't achieve this with an alert.

Instead as

Steven Collier

pointed out, you do it in the Issues List itself.

1. Open the Issues List (not the web part; the List itself)

2. Modify Columns and Settings in the left-hand column

3. In the General Settings section choose Change General Settings

4. Select Yes for Email Notification

WSS will then send you an email when a task is assigned to you or updated.

III.74 How do I apply a theme that was created outside my environment?

The answer here is a combination of the information provided by

Steven Collier

and

John Jansen

. Thanks to both of them!

Themes are provided in .elm files.

These need to be unpacked with the unpacker found here http://support.microsoft.com/default.aspx?scid=kb;en-us;295409

Then the unpacked file(s) need to be added here

102

c:\program files\common files\microsoft shared\themes11\ and then the theme can be applied by using FrontPage 2003.

III.75 We need to specify default.aspx when accessing our WSS sites. What’s the problem?

Instead of being able to access WSS sites via http://servername (etc.) it became necessary

(after "unspecified" changes made by non-WSS admins) to specify http://servername/default.aspx (and other versions) in order to access the site.

(Otherwise there was a File Download warning saying this is an unknown file type and some files can be harmful to your computer.)

Chip Mitchell

provided the solution - which is an amendment to IIS (!).

Execute permissions property under the Home Directory Tab for the Default Site had to be reset from 'Scripts Only' back to 'Scripts and Executables'. Somehow this had been changed in trying to solve another problem.

III.76 When I try to upload a file I get “Form validation error”. What might the problem be?

On trying to upload a file

Scott

got the following message:

Form Validation Error

Please correct the information you provided by following these steps, then submit the information again:

Iyaz

came up with a solution

Open up enterprise manager(Sql), expand the database folder and for each database, right click/properties/options.

At the bottom of the window, under the compatibility level, ensure that the Database compatibility level is 80. Make sure this is so for all the databases especially the tempdb database.

That solved it.

Thanks to both

Scott

and

Iyaz

for an interesting solution!

103

IV. Basic Customization

IV.1 How do I customize the Quick Launch section of the main page?

In STS 1.0 the items listed in the Quick Launch section were generated from the database. They were links to (only) those lists that had been defined in the User Interface when adding or amending a list as "Yes, I want this in the Quick Launch list".

There was one Quick Launch list per main web or per subweb.

If you wanted to add your own links (for instance to sites outside the STS site or to pages within the STS site that were not main List pages), you had to add some (<A> </A>)

HTML code just above or just below the code for the generated Quick Launch links.

In WSS there are several different Quick Launch sections. The initial information they contain is generated as before from the database.

However if you now want to add additional links (external or internal) *within* the

"normal" links this is now possible through the use of Front Page 2003 by selecting first the Quick Launch section; and then either using "Add a Link" or right-clicking and adding a link after selecting 'Link Bar Properties'.

IV.2 How do I customize the main section (centre/right) of the main page?

IV.2.1 General Customization of the main section

In STS 1.0 the only customization of this section of the main page that could be done in the User Interface was the definition of which Document Libraries and Lists would appear in this section. (Sites and Settings / Customize Home Page Layout)

Using FrontPage XP or using even an HTML editor allowed to do other changes such as re-sizing columns; changing colours etc. (see also IV.2.2)

In WSS you can also move into position onto the main page the Document Libraries and

Lists as before, but you can also move in a selection of Web Parts (both actions done by

Modify Page / Add Web Part - the Doc Libs and Lists are also called Web Parts in this version).

In addition most of the changing of the look of the page can as before be done in Front

Page 2003 or by amending the page in an HTML editor. (see also IV.2.2)

104

IV.2.2 Customizing the look of Document Libraries in the main section

In STS 1.0, the default look of a document library when made available in the main section of the front page was that it consisted of three fields Icon; FileName and

Modified By. The default number of documents was 20. Both these settings could be changed by entering the site in FrontPage XP; accessing the default.htm file; selecting the

List; right-clicking and then by 'View Properties' followed by amending (for the above two cases) the Files and Options settings.

(Note that the View Properties box was centered on the screen)

In WSS the default look is the same and the View Properties box is accessed in the same way but is now a new right-hand column (in the same sort of location as the clipboard for instance) rather than a centered box. The items listed are roughly the same with the same use of 'Fields' to change the fields used on the default page and the Use of Style followed by Options (rather than just 'Options') to amend the default number of documents (which unfortunately still has the same default of 20).

IV.3 How do I add Icons?

STS 1.0 came with a small set of icons for the main Office applications. When a document from one of these applications was listed in a document library, the special icon for this document type was shown otherwise all documents used a general icon. It was possible to add icons (from a selection available on a private website) by amendments to the templates (by amending an .xml file and adding the .gif of the icon to a specfic directory).

These icons were then valid for all sites and subwebs created after this template change was made. A further amendment to the templates was needed for the icon to become available to existing sites and subwebs.

The official word in the beta newsgroups was that WSS comes with a slightly increased number of icons with icons for Visio and Project (probably) available in addition to the previously available icons for Word, Excel, and PowerPoint.

However tests have shown that more icons are available than this (stored at

...60/TEMPLATE/IMAGES - as the usual IC???.GIF - there are almost 100 images including everything under the sun *except* for .pdf).

Images are chosen slightly differently than before. Icons for a small group of standard

MS document types (Word, Excel etc.) are chosen on the basis of the document type.

Other icons are chosen on the basis of the file type (.xxx). Priority is given to the MS document type before the file type, thus if you save a MS Word document but give it a

.mht file name, you will see in WSS the icon for MS Word not for .mht files. The file used for the above is DOCICON.XML which you will find in ...60/TEMPLATE/XML.

105

As with STS 1.0 in order for a newly added icon (amendments to both the IMAGES folder and to DOCICON.XML) to work you need to Restart IIS. ((IIS Manager / local computer + right click / All Tasks(Restart IIS).)

Unlike STS 1.0, following these actions the new icon is available for ALL document libraries - not just those in subwebs created after the change.

Note: If you are looking for suitable icons, here is a source of them http://www.greenfel.demon.co.uk/scode/SPSIcons.zip

IV.4 How can I add Images?

In STS 1.0 customization with Images was done either through using HTML code directly or by generating HTML code through the use of FrontPage. Most often images were not added to the centre and right-hand columns, although the default home page included the STS logo at the top of the right-hand column. (From where I always removed it as it took up unnecessary space)

In WSS the same customization possibilities are available as above. However in addition it is possible through the use of Web Parts to add images at suitable positions in the centre and right-hand columns. This process is not as easy as it looks at first glance and therefore this section deals with a recommended procedure.

First create a Picture Library which will contain all the images that you want to use on the web site. Then use standard WSS techniques to upload images to that library. (This initial step is essential as a means of getting a web address for the images so that they can also be accessed at that address from other PCs apart from the server).

Secondly go into the web page and select "Modify My Page" or "Modify Shared Page"

(or "Modify My Page" followed by "Shared View" followed by "Modify Shared Page").

Select "Add Web Parts" / Browse and choose "Image Web Part" now either Drag and

Drop or use the Center/Right + Add button. Close the Add Web Parts window.

Go to the new web part on your page and click on "open the tool pane". Enter here the full address of the image that you earlier entered into your Picture Library for Web site images (you did do a Ctrl-C so you can now do Ctrl-V didn't you). OK (to have defaults for everything else) and you now have an image visible in that part of the column whenever you (if done in Personal View) or anyone (if done in Shared View) accesses the web site from any location.

Note the following peculiarities in the way these Web Parts work. a. If you create an Image Web Part in Shared View it is immediately also present in the

Personal View.

106

b. If you create an Image Web Part in Personal View it is only present in Personal View c. An Image Web Part created in Shared View can be closed in Shared View. In this case it are still present in Personal View *if it has been subsequently amended in Personal

View* otherwise it is removed from Personal View too. d. An Image Web Part created in Shared View can be deleted in Shared View (Delete is only available in "Design This Page" mode). In this case the Image Web Part is no longer present in Personal View. e. Image Web Parts created in Shared View can be amended only in a limited way when in Personal View. For instance the URL of the image can not be amended in this case.

This also applies to Image Web Parts when the Image Web Part has been closed in the

Shared View. f. The default view of an Image Web Part includes a Title Bar and Frame. This can be easily changed to None (no Title Bar or Frame) which is in my opinion a much more sensible option for an Image. (Modify Web Part / Appearance Section / Frame Style) g. Watch also out for "Reset Page Content" when in the Personal View. This will make your Personal View a copy of the Shared View.

IV.5 How can I apply new (whole-site) Themes?

In STS 1.0 it was possible to customize the _layout files.

In WSS it is no longer possible because these _layout files are per server.

In order to make a change of look valid for the whole site you can either use one of the ready-made themes MS include or create your own.

Here are some instructions for how to create your own.

Open your site in Front Page 2003

Format | Theme

At the very bottom of the theme task pane select "Create new Theme"

You'll get the "Customize" theme window

Click on "Text"

Click on "More Text Styles"

From the list, choose the selector you want

Modify (modify the attribute(s) you are interested in for that selector)

107

Repeat for each selector you want to modify

| OK | OK

Save as "MyTheme" |OK

Apply "MyTheme" to your SharePoint site

When you select customize a theme, goto the Text panel and click on "More Styles" - there you can edit all class styles (ie .ms-xxxxx).

This information comes from Gabe Bratton who also pointed out that the theme does not replace the existing (ows.css on an WSS site) style sheet, but instead acts as a modifier for it.

IV.6 How can I create and use New Templates?

In STS 1.0 there were three standard templates - one of which was blank. Amending the template meant finding the correct file(s) in the file structure and changing the code. The choice of three templates was however fixed - you had only changed the look of one of them.

In WSS there are more standard templates on offer and it is possible to add more templates to choose from.

The following sections deal with a) creating a template b) making the template available globally c) viewing the templates you have in the global catalog d) creating a new site on the virtual server with a particular template. e) how to remove a list template f) how to preserve roles when using a template g) the maximum size of a template h) how to remove a template

i) how to hide default templates

Thanks to Gabe Bratton for supplying the basic info for 6.1-6.4

Note that you will probably have to run IISRESET after making these changes (Rohit

Puri)

108

See

IV.6.1 How to Create a Template and

IV.6.2 How to make a template available globally and

IV.6.3 How to view the templates you have in a global catalog and

IV.6.4 How to create a new site on a virtual server with a particular template and

IV.6.5 I have created a template from a site where roles were defined. How can I preserve the roles when I create a site from the template? and

IV.6.6 What is the maximum size for a site template?

And

IV.6.7 What is the maximum size for a list template? and

IV.6.8 How do I remove a list template?

Also don't forget the long Tutorial on templates at -

VI.2 Details on Templates

IV.6.1 How do I create a Template?

Amend your site as you wish (using FP etc.), then go to Site Settings / Site

Administration / Save Site As Template

IV.6.2 How do I make a template available globally?

Go to Site Settings / Site Administration /Manage list template catalog

You will see the list of list template fwp files. You can hover over the link for the fwp, right click and save the file to disk. a) You could save the file directly to \program files\common files\microsoft shared\webserver extensions\60\bin.

To add to the global catalog, you would run the command line: stsadm -o addtemplate -filename template.fwp -title "Custom Template" -description

"Template Description" or

109

b) You could save the file locally (to C:\ say) (Rohit Puri) in this case you would run the command line stsadm -o addtemplate -filename c:\template.fwp -title "Custom Template" -description

"Template Description"

IV.6.3 How do I view the templates I have in a global catalog? run the command line: stsadm -o enumtemplates

This will provide output such as:

Custom Template - Language: 1033 - Site Template: _GLOBAL_#1

IV.6.4 How do I create a new site on a virtual server with a particular template? run: stsadm -o createsite -url http://server/sites/teamsite -ownerlogin domain\username ownername "Mike Walsh" -owneremail [email protected] -sitetemplate _GLOBAL_#1

IV.6.5 I have created a template from a site where roles were defined. How can I preserve the roles when I create a site using this template?

You can't.

Roles are not preserved as part of the template in this (first) release of WSS.

IV.6.6 What is the maximum size for a site template ?

The maximum size for a site template is 10MB.

If you create a site larger than that you will normally get the error message "This site is too large to save as a template".

Another possible effect is that you will get a time-out. This tends to happen when you have both more than 10 MB of data AND a large list with substantial list data.

(Thanks to Gabe Bratton - the text is mine)

Gabe also later confirmed that this 10MB limit is hard-coded and it is not possible to change it.

110

IV.6.7 What is the maximum size for a list template ?

The maximum site for a list template is (like the maximum list for a site template) 10MB.

Again this is hard-coded and can't be changed.

Please see also the item VI.7 "How to save a Document Library as a template that with content is greater than 10 MB in size (and not lose data)" in the Tutorial section for a way of moving lists via the "Save as List Template" function that are greater than 10MB in size.

IV.6.8 How do I remove a list template?

If you created the templates by going through the WSS UI and selecting 'Save List as

Template', you can remove them as follows:-

Site Settings / Site Administration

In 'Site Collection Galleries' click on “Manage List Template Gallery”

Edit (the Template you want to remove) + Delete

(based on a reply by Jerry Orman)

IV.6.9 How do I hide default site templates?

The full question from Leslie was

How would I hide some of the default site templates, so when the user creates a new site, only certain templates can be selected?

The answer from

Iyaz

was

Go to Webtemp.xml in templates\1033\XML

There you can change the HIDDEN property of a particular configuration ("Team Site"

"Blank Page" etc.) for it not to show up when you create a site.

This needs an IISRESET.

Thanks as always,

Iyaz

!

111

IV.7 How do I build into a WSS web page the contents of another Web Site ?

In STS 1.0 this required coding. Specifically because (for instance) an asp-based web site required a different pre-processor to that used by STS, it was necessary to add code containing a so-called IFrame into the STS page where the contents of the other web site should appear.

In WSS this no longer requires coding. A Web Part "Page Viewer Web Part" is available that can be dragged and dropped into the Web page and details of the site to be accessed along with size in this page etc. are specified in the fill-in box that appears at the righthand of the screen.

IV.8 WSS unlike SPS 2003 doesn't have "My Site". Can I simulate this in WSS?

Not easily.

Adam Macaulay came up with this suggestion for the direction to take to achieve this.

He described it as "cloggy" or in other words "a technique used to get the job done in the wierdest way possible, not the norm".

-----------

Create an entry ASPX Page which the user will authenicate to and then will redirected to the site in question. You will not be able to create your own login box but the

SharePoint/Browser Authenication box should be good enough. Bascially what you are doing is catching the authentication error that can occur if the user does not have access.

If they have access to the first they will get redireted accordingly, if not then they will get the second redirect.

The code below is not real so you will need to look to the SDK for WSS to get the correct syntax but I just wanted to give you an idea.

Try

{

Set your site object to open a site SPWeb objWeb =

SPControl.GetContextSite(Site).AllWebs

objWeb.CatchAccessIsDenied = true;

Redirect the user to the site url Page.Redirect(objWeb.URL)

} catch

{

} try

{

112

Set your site object to open a site SPSite objSite =

SPControl.GetContextSite(Site).AllWebs

objWeb.CatchAccessIsDenied = true;

Redirect the user to the site url Page.Redirect(objSite.URL)

} catch

{

}

-----------

This is as stated just the direction in which someone who wanted to achieve this should be looking.

If anyone manages to complete this process and provide a complete solution, I'd be very happy to add it here!

IV.9 How do I add Hyperlinks to an Announcements List?

Here - with thanks to

Gregg Smith

- is a code solution to this need.

Open the SCHEMA file for the announcements list type found in in the

ANNOUNCE dir of the tempalte root. at the top of the file find:

<MetaData>

<Fields>

<Field Type="Note" RichText="TRUE" Name="Body"

DisplayName="Body" Sortable="FALSE" ></Field>

<Field Type="DateTime" Name="Expires" DisplayName="Expires"

Format="DateOnly" FromBaseType="TRUE" ></Field> in the FIELD definition for Body add in AllowHyperlink="TRUE"

It IS case sensitive!

IISreset and you should be all set. You should have a button that lets you add

HyperLinks.

113

IV.10 How do I remove the Sharepoint toolbar (new/edit/delete item) from dispform.aspx of a list?

Add this just before the closing </head> element:

<style>.ms-toolbar {display : none;}</style>

Thanks to

Dustin Miller

(and to

Wayne Small

for asking the question and confiming that it works)

IV.11 How do I set "Overwrite existing file" off by default?

When you upload a file within the WSS User Interface, the default is that the new file replaces an old one with the same name.¨

You can of course remove the "x" on 'overwrite existing file' or you can change the default as below.

Look for the line in the doclib's schema.xml starting with

<INPUT type=hidden name="putopts" id=putopts value="true"> and change it to

<INPUT type=hidden name="putopts" id=putopts value="false">

Also look for the line starting with

<INPUT TYPE=CHECKBOX name="overwrite" id=overwrite value="false"

CHECKED and change it to

<INPUT TYPE=CHECKBOX name="overwrite" id=overwrite value="false"

UNCHECKED

Thanks to

Iyaz

for proving this solution!

114

IV.12 How do I make only database rows with different keys visible in a WSS web part?

John Jansen

suggested the following (edited)

Create a Data View Web Part (using FrontPage) and hand-code the XSLT to select unique values.

This is the relevant section of the XSLT Developer's Guide http://msdn.microsoft.com/library/default.asp?url=/library/enus/xmlsdk/htm/xsl_advanced2_5zec.asp

Thanks, John!

[The top-level of the XSLT Developer's Guide is at http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnanchor/html/anch_xmlprod.asp

as far as I know there is no download available (2 April 2004 status)]

IV.13 How do I use the Search Form from the default page on another page?

This has been asked several times in the newsgroup so I am adding it here, even though the link has been available in the Non-MS Articles section of the site for several months.

This is covered in the following article http://www.sharepointcustomization.com/resources/tipstricks/04wss-searchbox-tip.htm

at the FrontPage Customization site.

To save you time, please note that the technique there only works when transfering to a

web part page

.

IV.14 How do I remove the entries for web parts in the Virtual Server gallery BUT keep the web parts?

Thanks to

Iyaz

for his very complete answer (here slightly edited) on this.

1. I you create or use a web part package without dwps, then the virtual server gallery is not populated on installation of the package. (It is if the package contains dwps)

115

2. If the web part package has already been installed with dwps - i.e. you already have an entry in the virtual server gallery - you can delete the dwps from the wpcatalog folder

(\inetpub\wwwroot\wpcatalog)

3. If you manually install a web part then you will place the assembly where you want to place it and you will add the appropriate SafeControl markup. In this case you just won't add dwps to the wpcatalog folder.

Note: Iyaz adds that you can test this using InstallAssemblies (available on the web) and select an assembly; uncheck the Generate Dwps option; Click Install.)

IV.15 How do I get the logged on user’s display name into a basic page?

Here's an answer from

John Jansen

based on use of FrontPage 2003's Data View. It certainly wasn't the first answer that came to my mind, but it seems to work.

1. Insert a Data View of some WSS list (for instance the Announcements list although the source doesn't matter as long as you have at least one piece of data in it).

2. Create a conditional formatting rule on this to show items when Created By ==

[Current User]

(Having selected Conditional Formatting, you'll have to select the contents of any one of the fields from this custom list in order to be able to "Create" a conditional rule.)

3. Do a Find in the Code View in Front Page 2003 for xsl:value-of select="@Title"/>

4. Replace this with

<p>Hello, <xsl:value-of select="$UserID"/<<p>

He notes a couple of things a) he does 2. above to make sure the parameter is in scope for the XSLT template.

(If it isn't, then on switching back to Design (View) you see a long message saying that 'a reference to variable or parameter "UserID cannot be resolved" etc. I hope to be able to add here what you do then)

116

b) it might be easier to create a custom list that has one item in it rather than to use

Announcements c) you have to make sure that this code is not within a "FOR EACH" because then you will have "Hello Joe" for each record.

(You nicely avoid this by following b) and creating a custom list specially for this with one record only)

-------------

On the other hand you might want to use a ready made web part. There's one at http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a=380

Thanks to Bil Simser for pointing this out and Adam Macauley of CorasWorks for writing it and making it available free of charge.

IV.16 How do I remove ”Upload Multiple Documents”?

While most questions are "why can't I see Upload Multiple Documents?" (answer: you need Office 2003), one person asked how he could remove "Upload Multiple

Documents".

Here - from

John P. Grieb

- is the answer to how you remove it *from sight* ("It just disables the "Multiple Upload" functionality on the Web page because it thinks that it thinks that the appropriate browser isn't running or a required control isn't installed").

Edit the file upload page in FrontPage.

Switch to Code view.

Modify the function EnsureUploadCtl to return 0;.

The only problem with this method is that you have to do it for each document library you want to disable multiple file upload for.

Thanks

John

!

117

V. Interaction with Office Products (details)

This section has been added because of the major changes made between Office XP/STS

1.0 and Office 2003 / WSS.

V.1 How does Outlook interact with WSS?

V.1.1 Outlook Interaction – Contacts

With STS 1.0 it was possible to import contacts from Outlook 2002. It was not possible to export contacts to Outlook 2002.

With WSS it is possible in an WSS Contact List to Import Contacts from Outlook 2003 and also to export Contacts to Outlook 2003.

In the later case, your web "area"'s (web, subweb, Meeting Place, Document Workspace etc.) Contact list will be transfered to Outlook 2003 as a new Contact Library.

Contacts will not be added to an existing Outlook Contact list.

These Contacts then appear in Outlook 2003 as an item in the "Other Contacts" section, but they may be then transfered by drag and drop into (for instance) the "My Contacts" section of the Contacts left-hand column.

In Outlook 2003 Contacts may (as before) be exported to a file. There is no easily accessible way to transfer the contents of a file into WSS. *as far as I can see*.

In STS 1.0 the Contact information available for each person was text information which could also include a URL of the person's web site.

In WSS the Contact information available for each person is similar if not identical (looks the same to me) to that in STS 1.0 but in addition it is now possible to add an attachment

(person's photo perhaps).

V.1.2 Outlook Interaction – Attachments to mail messages

With Outlook 2002 attachments could be added to mail messages. The person opening the mail message opened the version of the attached document that was available when it was attached.

With Outlook 2003 and WSS, the master copy of an attachment is stored on the WSS site. The person opening the mail message will always receive the latest version of the attached document.

118

Note: For much more detailed information on the interaction of Contacts between WSS,

Outlook, Excel and Access, please look at section VI. (Tutorials) where this is item 1.

Synchronizing Contacts.

V.1.3 Outlook Interaction – Meetings

V.1.3.1 Outlook Interaction – Meetings - From Outlook 2003

Meetings created in Outlook 2002 specified a time in your (and your invitees) Outlook calendar.

Meetings created in Outlook 2003 also allow (not compulsary) a 'Meeting Workplace' to be created. This is a regular WSS site for which a set of ready-made templates are available thus allowing a site that is most suitable for the type of meeting.

The default "Basic Meeting" type for instance consists of lists for Objectives and

Attendees; and Agenda, Document Library, Action Items and Decision. People invited to the meeting are informed of the URL of the meeting workplace.

(I presume that as with the standard WSS, additional local meeting templates may also be available for selection.)

In other words these meeting workplaces are short-term WSS sites designed mainly as a way of making a meeting or perhaps rather a series of meetings more effective. The most common use for them will (in my opinion) probably be for projects where a Meeting

Workplace will be created when a Project Group is founded.

Only the people invited to the meeting initially have the rights to access the Meeting

Workplace. It is logical that the list of users of a Meeting Workplace can vary as required

(using standard WSS 'modify users' techniques.

V.1.3.2 Outlook Interaction – Meetings - From WSS

In STS 1.0 typically the administrator would create on request a web site for a Project.

In WSS Meeting Workplaces would probably be created automatically from inside

Outlook 2003 as above.

However, Meeting Workplaces can also be created from within WSS. In particular they can be created at the same time that a new Event is created.

In this case all authorized users of that part of the WSS site will have the rights to access the Meeting Workplace. Otherwise functionality is similar.

119

V.1.4 Saving E-mail messages and attachments in WSS

V.1.4.1 Outlook Interaction - Saving only E-mail messages in WSS

To save an E-mail message in Outlook directly to a document library in WSS

- open the e-mail

- File / Save As

- In the 'File Name' box type the http:// address of the WSS site (e.g. http://<servername>)

A window opens containing the WSS site

- Navigate to the Document Library you want

- Save the e-mail

(You will be allowed to change the document's name. Default mode is probably .htm which seems to work fine)

Note: If you already have a Network Place pointing directly to the Document Library that you want to use, you can (in the Save As window) click My Network Places (in the lefthand column) and select that Network Place (main section) instead of needing to use the http:// method.

Note2: In beta-2 there were errors when accessing the web site within the Save As box but these could be ignored with no ill effects.

Note3: It is probably better not to store files as .txt as long lines are not visible on the screen when opened in WSS (even though they may be correctly displayed in Outlook)

(Thanks to Jerry Orman for the technique)

V.1.4.2 Outlook Interaction - Saving only E-mail attachments in WSS

Follow V.1.4.1 above but instead of File / Save As use File / Save Attachments.

V.1.4.3 Outlook Interaction - Saving both E-mail messages and attachments in WSS

Follow V.1.4.1 above but when you Save As specify the File Type 'Outlook Message

Format' (*.msg).

Note: when trying this with a 3MB attachment I ran out of system resources. Saving the same attachment by itself (V.1.4.2) was OK. Your mileage may vary.

120

V.2 How does Word interact with WSS?

V.2.1 Word Interaction - General interaction (New document; Edit Document etc.)

In STS 1.0 if your default template for a document library was the standard Word template, then 'New Document' would open a Word session (either within your browser or as true Word depending on your settings); you would write your document and when you saved it, you would be saving it to the STS site and would have the opportunity of changing additional (STS) fields such as Category or Source.

This worked fine but only if the user had Office XP.

You also had the possibility of "Edit in Microsoft Word" - i.e. amend an existing document located in an STS document library which worked in roughly the same way

(also only in Office XP).

This worked BUT was something I never demoed because although the change had been done to the document on the STS site, the document sent to the browser was invariably in a demo a back version.

In WSS the same possibilities are available as with STS 1.0, that is with the Document

Library fully open you can still choose "New Document" as above. (Office 2003 and presumably Office XP)

You also still have the possibility of Edit in Microsoft Word. The functionality of this has been slightly improved as it is now possible to access this function via a drop-down list box alongside the document name AND this list box is available both in the smaller view of the document library that you may have on the main page of the web or sub-web and in the normal full document library page.

(Robb Wray comments that in WSS setting his browser to "check for changed pages every time" meant that on using Document Update he never sees back versions. So you can try that for Edit in Microsoft Word too.)

WSS offers in the same document library page the new "Edit in Datasheet" facility but this doesn't seem to offer any additional ways or adding or editing the contents of existing documents and just offers a different (and more compressed) view of the list of documents to that provided by the standard web site.

The final additional feature (ignoring check-in/check-out and versioning which are dealt with elsewhere) offered by the interaction between Word 2003 and WSS is the possiblity when you create a document in Word 2003 of being able to specify that there will be a

Document Workspace for the document.

121

This function is selected in WSS after the document has been created in Word 2003.

("Create Workspace" is the final selection on the drop-down box mentioned above in connection with 2.0's Edit in Microsoft Word) This Document Workspace is a full-scale mini WSS site contained a document library (containing the document); an

Announcements section (with an Announcement of the site; Members; Links and Task sections (in the main part of the screen) and even Lists, Discussions, Surveys and Pictures available from the left-hand columns.

(If 'Document Workspace' is selected, the document is still listed in the original document library as well as in the document workspace site's document library. Updating the version of the document in the Document Workspace does not seem to update the version of the document in the original document library)

Note: It was in Beta-1 possible to add further documents to a Document Workspace and also to create a Document Workspace within a Document Workspace etc. just as if a

Document Workspace were a normal WSS WebSite. This was in Beta-2 only possible for one level down. (RTM?)

V.2.2 Word Interaction - Propogation of Word Properties

Word 2003 documents have a set of Custom Properties

Checked By

Client

Date completed

Department

Destination

Disposition

Division

Document Number

Editor

Forward To

Group

Language

Mailstop

Matter

Office

Owner

Project

Publisher

Purpose

Received from

Recorded by

Recorded date

Reference

Source

122

Status

Telephone number

Typist

Values from a Word Document for any of these fields will be propogated to the WSS

Document Library by the following method. a) Create a document library and add a new field of type Single Column.

Give it the same name as one of the above (example Language) b) Open Word 2003 and create a new document.

After writing it and before saving it, go to Properties / Custom and specify Language as

(say) "Finnish". c) Save the document (with Save As) to the web site (enter the URL or specify an existing Network Place).

Note: see http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=172 for more information on the following restriction to the above.

The Properties

Subject

Author

Manager

Company

Category

Keywords

Comments Hyperlink Base are not propogated as above.

V.3 How does Excel interact with WSS?

In STS 1.0 it was possible to get a copy of your Contacts information into Excel (by clicking "Export" while in a Contacts screen). Similarly Announcements, Events in fact any (custom) List could be transfered into Excel.

In these cases synchronization between Excel and the STS list was only possible in one direction - namely a change in the STS list could be synchronized within Excel (using

Data/Refresh External Data). Any additional line made in the Excel data meant that the

'Refresh External Data' option was greyed out; also any change made to an existing line in Excel was not transferable to STS (Refresh External Data merely removing the change made).

123

It was not possible to transfer the contents of a view (such as 'All Documents' of a

Document Library to Excel in this way.

In WSS It is also possible to transfer the contents of a view of a Document Library to

Excel in addition to the (custom) Lists mentioned above.

In WSS changes can be made to the list in either Excel or WSS and synchronized in both directions. The only restriction of this is a document library where because a document library contains hidden columns, additional rows (records) can not be added to the Excel version - changes to the contents of existing rows is however also possible in Excel even for Document Libraries.

The best method to do this is by using the Task Pane and clicking on "Export and Link to

Excel" with synchronization taking place with "List / Synchronized with SharePoint"

V.4 How does Access interact with WSS?

In WSS list data can either be exported to an existing Access database or to a new Access database.

If you use "Export to Access" to do this, it will not be possible to synchronize data in either direction.

If you use "Create Linked Table in Access" to do this then synchronization is possible in both directions but it works in different ways.

- If you update the data in Access, the changes are immediately transfered to the WSS copy.

- If you update the data in WSS, the changes are only visible in Access if the linked table is first closed (in Access) and re-opened.

V.5 How does InfoPath integrate with WSS?

This is a general set of questions that will be added to over time as I become aware of them. I am not myself planning to use InfoPath so help from others in adding to this list would be appreciated.

Some of the following use "SharePoint", I am assuming they apply to WSS.

V.5.1 InfoPath Interaction - Can I create a drop-down control on an InfoPath form that gets it's values from a SharePoint List if online or saved in a form if off-line?

InfoPath allows you to publish a form template to a SharePoint v2 form library and promote data in the form (XML template) to SharePoint columns.

124

You can populate a dropdown from a SharePoint list but we do not have this as a built-in connection in InfoPath.

(Source: Utilises information from an InfoPath Solutions chat session - permission granted for re-use here)

V.5.2 InfoPath Interaction - Can InfoPath forms be used both to add data to a WSS list

(forms library) and to reference data from an existing list?

Posting InfoPath forms to WSS Form Libraries is built-in.

Referencing data from an existing list is possible but it requires more manual work to hook it up through the web service adapter or through WSS's XML Interface.

("through WSS's XML Interface" is FAQ maintainer's revised text. Comments *please*:

Original text "XML as datasource adapter through WSS's XML interface").

(Source: Utilises information from an InfoPath Solutions chat session - permission granted for re-use here)

V.5.3 InfoPath Interaction - Can InfoPath publish to Sharepoint, but NOT require

InfoPath to edit the form?

InfoPath is required to fill out the form if you want InfoPath's rich structural editing, schema validation, and connectivity capability features.

The data InfoPath inputs/outputs is just XML (your defined schema) so you can work with that raw data any way you like but you will then have to handle all the schema validation and expose the structural editing yourself.

(Source: Utilises information from an InfoPath Solutions chat session - permission granted for re-use here)

125

VI. Tutorials

VI.1 How do I Synchronize Contacts?

This paper deals with Contacts and the interaction between WSS; Outlook; Excel and

Access.

The aim of the following scenario is to ensure that the above four programs all have access to the same version of the Contacts list.

Step 1 - Create identical copies of Contacts in WSS; Outlook; Excel and Access

Step 1.1: (Outlook export to Excel)

In order to export Outlook Contacts to Excel it will be necessary (the first time) to install extra functions over the "typical" Office 2003 installation, so the user will need to have access to the Office 2003 CDROM to perfrom this operation.

In Outlook a. Open Contacts b. File / Import and export / Export to a file c. Create a file of type / Microsoft Excel d. Select Folder to Export from / Contacts

Step 1.2: Import into WSS

In order to import from Excel into WSS it will be necessary (the first time) to install extra functions over the "typical" Office 2003 installation, so the user will need to have access to the Office 2003 CDROM to perfrom this operation.

In WSS a. Click on Contacts (under Lists) b. (from the Menu line) "Import Contacts" c. (from Select Users to Import) Select all the contacts; Add; OK

** After step 2 Outlook; Excel; and WSS are in sync, but updating all of them is difficult.

The next step is to create a copy of the Contacts in Access. This will become the master copy. **

Step 1.3: Creating a copy of Contacts in Access

In WSS a. Create Linked table in Access

126

b. In Export - New Database

** At this stage all four programs (Outlook; Excel; WSS and Access are in Sync. **

*** From this stage on it is important that Additions to the Contacts are made only in the

Access master table.***

Step 2 - Maintain identical copies of Contacts in WSS; Outlook; Excel and Access

Step 2.1 Add new Contacts

In Access:

Add new contacts.

Step 2.2 Transfer the new version of Contacts to WSS

In WSS a. Open Contacts b. In the menu line "Refresh Data"

Step 2.3 Transfer the new version of Contacts to Outlook

In WSS a. Open Contacts (if not still open from 2.2.a) b. In the menu line "Link to Contacts"

At this point Outlook (if opened and thus in the task menu bar) flashes and needs action

In Outlook

A query box appears with "a request has been made to add the following SharePoint

Team Services folder to Outlook ..... Would you like to add it ?"

Pressing OK will create a new section in Outlook (Other Contacts) that contains "Team

Web Site - Contacts" in addition to the standard Contacts section containing "Contacts".

At this point Contacts contains old information and ought in future to be ignored and

WSS contacts used.

127

[Note that the same information box message appears even when "Team Web Site -

Contacts" is already available. Pressing OK will then update (=synchronize) the existing information or - if no changes have been made in Access/WSS - leave it as it was. It will not cause second "Team Web Site (2) - Contacts to be created.

Step 2.4 Transfer the new version of Contacts to Excel.

In WSS a. Export and Link to Excel

In Excel

(Alternative 1 - Excel is open and in it your Contacts xls file (Contacts11.xls) is open.) b. The query box "Import Data" appears. c. In this box select "Existing Worksheet" and as entry point a point in column A directly below the existing Contacts list. d. OK e. Delete the previous version of Contacts11.xls

(Alternative 2 - Excel is closed) b. Book1.xls is created containing the new contact information. c. Save this as Contacts11.xls thus overwriting the older version of this file.

** Following all these steps, you have a version of the Contacts list that is identical in

WSS; Outlook; Excel and Access. **

*** Note that if you don't see the need for an Access copy of this information, you can follow the above scenario but omit the Access sections and do all the updating in WSS

(for which I would suggest the Datasheet View). In this case, thus, WSS would be the master copy. ***

128

VI.2 Details on Templates

(Courtesy of Jorgon Johanson of Norway and only edited in a minor way)

One of the great new features of WSS seems to be how easy it is to use Site and List templates. Templates can be used to generate "pre-cooked" site and list setups that can be applied when generating new sites, lists and document libraries. Site templates includes the the look (theme), the layout of the home page, the lists and document libaries and so on. List templates include the views, pre-generated columns and so on.

Since both Site and List templates can optionally also be generated *with* contents, templates are a convenient way of moving both sites and lists (see below).

Making a Site Template

Browse to a site that is to be used as a source for the template. Then go to:

Site Settings

Go to Site Administration

Management and Statistics: Save site as template

Decide on a file name (the xxxxxx.fwp file). Decide on a template title and a description for this template. Also, decide if the *contents* (of all lists and document libraries) should be included in the template. If you are going to use the template for migration purposes, check "Include content". Also, if you want to create new sites complete with some contents, check "Include content". Otherwise you may leave "Include contents" unchecked. Click OK.

Note that possible sub-sites of the site used as a source for a template will NOT be included in the template (this option is currently missing in WSS).

The new Site template will now show up in "Site Collection Catalogs: Manage site template catalog" in the root site (see "Managing Templates" below). Note however that the new template will be available for use in the top level (root) site and all sub-sites.

Generating a New Site From a Template

There are many places where you are given the possibility to generate a new site. The new site can be based on one of the predefined templates or on one that you have created yourself. First browse to the site that is to be the parent site. If this is a sub-level site, you have the following possibilities:

Create

Web Pages: Sites and Workspaces

- or -

Documents and Lists

129

See Also: Sites

Create

- or -

Site Settings

Manage sites and workspaces

Create

If you are going to create a site just below the top level site you have the additional possibility:

Site Settings

Go to Site Administration

Manage sites and workspaces

Create

Either way, give your new site a Title, a short Description and also it's URL name (which unlike STS 1.0 can be different to the Title name). Hit Create and you will be given the oppertunity to select a template. If you have generated any Site Templates yourself you will see them in the list. Select one and hit OK.

Making a List Template

Browse to the list or document library that is to be used as the source for the template.

Then go to:

Modify settings and columns

General Settings: Save list as template

Decide on a file name (the xxxxxx.fwp file). Decide on a template title and a description for this template. Also, decide if the *contents* (text etc. in lists lists or the actual documents of document libraries). If you are going to use the template for migration purposes, check "Include content". Also, if you want to create new lists/libraries complete with some contents, check "Include content". Otherwise you can leave "Include contents" unchecked. Click OK.

The new List template will now show up in "Site Collection Catalogs: Manage list template catalog" in the root site (see "Managing Templates" below). Note however that the new template will be available for use in the top level (root) site and all sub-sites.

Generating a New List From a Template

The new list template will be available from the Create Page. It shows up under

Document Libraries, Picture Libraries, Lists and so on according to the type of the list used to create the template.

130

Managing Templates

You can admininister your Site and List templates by going to these locations on a

*main* (root, top level) site:

- Site Templates:

Site Settings

Go to Site Administration

Site Collection Catalogs: Manage site template catalog

- List Templates:

Site Settings

Go to Site Administration

Site Collection Catalogs: Manage list template catalog

The two catalogs are actually two special purpose document libaries. The "documents" held in the libraries are template files (xxxxx.fwp files).

Migrating Sites and Lists

Since the Site and List templates are stored in .fwp files moved into the two special purpose documents libraries (the Site Template Catalog and the List Template Catalog), it is easy to get the template out of the current site by just clicking on one of the templates and save it to some location (locally). It is then just as easy to Upload the template to another WSS site by clicking "Upload Template" in the appropriate Template Catalog

(don't confuse Site templates and List templates).

Since a template can be generated with the total contents of a site or list, this feature can be used to move whole sites and lists. Note however that a Site template does not include the sub-sites of the original site. This means that when moving a site tree you will have to move one (sub)site (the root or one of the branches) at a time.

131

VI.3 Customizing the Home Page

(Courtesy of Jorgon Johanson of Norway and only edited in a minor way)

In STS 1.0 you could customize the Home page to some degree. Without resorting to

FrontPage you could for instance select which lists/libraries that showed up in the center and right column. Using FrontPage you could do a lot more.

WSS is quite a different story. Even without FrontPage you can do alot more to the look of the Home page.

My View / Shared View

First of all, it is important to notice that WSS allows each user to have his/her own Home page view. Looking at the top right hand corner of the Home page you will see either see a "Sign In" button, "Modify Shared Page" or "Modify My Page".

If it says "Modify My Page", the Home page shows your personal Home page view.

If it says "Modify Shared Page" it shows the view seen by other users that have not yet customized their view.

If the "Sign In" button is shown WSS don't know yet who you are (you are regarded as an anonymous user) and the Home page shows the shared view.

Note that you need enough privilges to be able to add/remove/view shared views (the

Administrator site group has these privileges by default).

When you have signed in, the Home page defaults to the personal view. You can however change to the shared view by clicking "Modify My Page" and selecting "Shared

View".

At the beginning all personal views equal the shared view. If you have made any personal changes, you can at any time revert back to the shared view by clicking "Modify My

Page" and selecting "Reset Page Contents". Any personal amendments to the (own)

Home page will be lost.

Web Parts

The stuff shown in the center and left column (in WSS now called the left and right zone) of a WSS Home page are Web Parts.

We can say that a Web Part is an object that is used to show/present something on Web

Part pages (note that the Home page is actually a kind of Web Part page).

132

Often a Web Part is used to show the contents of a list or a document library. There are also Web Parts that can show other things (like an image). The Web part controls only the layout and appearance (i.e. the look) of the list/library, while the actual contents come from the list/document library.

Note that when you drag a web part onto a page (like the Home page) you are not dragging the actual Web Part, you are only creating and placing an instance of this web part. You can place multiple instances of the same Web Part on the same page. Each instance can be given its own set of properties controlling its appearance on the page.

In WSS you alter the Home page by placing Web Part instances on the page and by changing the way these instances of Web Parts present their information (by changing the instance properties).

Thare are in effect two main types of Web Parts. The first type is generated automatically each time a list (or document library etc.) is created. There is one such Web Part for each list in the current site. These web parts are associated with (and take their data from) this list. The other types of Web Part are more explicit and there is a special site catalog for them, the Web Part Catalog.

You can see these Web Parts at:

Site Settings

Go to Site Administration

Site Collection Catalogs: Manage Web Part catalog

Here you can upload new Web Parts. Click on any of them and you get a preview of what it does!

Adding New Web Part Instances to the Home Page

Browse to the Home page where you want to add something. If you want to add to your personal view, check that "Modify My Page" is shown in the upper tight hand corner. If you want to add to the shared view, make sure that "Modify Shared Page" is shown

(change to the correct view by clicking "Modify xxxx Page" and select either "Shared

View" or "Personal View").

Click on "Modify xxxx View" and select "Add Web Part" | "Browse". The Browse Web

Part pane is now shown on the right side of the page. Web Parts (or Web Part instances) can be located on four different scopes:

- Web Part instances available for this Web Part Page only

- Web Parts available for this site

- Web Parts available for the whole virtual server

- Web Parts available online

133

"Web Parts available for this site" is selected by default. Just below you see a list of available Web Parts. You probably notice that some icons are yellow and some are grey.

The yellow ones are the Web Parts automatically generated for the lists of the site (used to show the contents of these lists). The grey ones are other web parts as described above.

Lets add a Web Part instance showing the contents of the document library "Shared

Documents". You can do this in two ways:

- Drag the icon for "Shared Documents" to where you want to place the Web Part instance.

- or -

- Select "Shared Documents" from the list, set "Add to:" to either "Left" or "Right", then click the "Add" button.

The first option is somewhat similar to the way STS 1.0 works and is often quicker because you can place the new Web Part instance where you want it in one go (If you use the second alternative the Web Part is placed at the top of the selected zone and you have to move it later if you want it to be somewhere else).

When you are done you can click the "X" next to "Add Web Parts".

Deleting and Closing a Web Part Instance

If you want to remove a Web Part instance from the page you can either "Delete" it or

"Close" it.

What is the difference?

Deleting

Deleting a Web Part instance from the page makes it go away for good (only the instance, not the Web Part itself).

Closing

Closing a Web Part instance on the page removes the instance from the page. However the instance is not gone. It has been moved into the "Web Part Page Library" (Web Part instances available for this Web Part Page only as described above). When adding Web

Parts to a page you can then re-add closed Web Part instances when selecting "Web Part

Page Library". It is important to note that we are manipulating "instances". Each instance

(even when derived from the same Web Part) can have its own set of property values controlling its apperance. So, saving closed Web Part instances for later can save some customization work. See "Modifying Web Part Instances" below.

134

When you want to Delete or Close a Web Part instance you can for instance enter

"Design this Page" mode by clicking "Modify xxxx Page" and selecting "Design this

Page". Then click the little triangle or down-arrow (<what is this really called?>) on the right hand side of the Web Part Title Bar. Then select either "Close" or "Delete". If the

Web Part Instance does not have a Title Bar (which makes it a bit difficult to reach the triangle...), click "Modify xxxx Page", select "Modify xxxx Web Parts" and select the

Web Part instance you want to Close/Delete (the Title Bar will now be visable!).

Note that the "Close" option may also be available for a Web Part instance without going through "Design this Page" (but, it is possible to turn this off in the "Advanced" Web Part instance parameters).

Also, "Close" may be available as an "X" next to the little triangle.

Changing the Attributes (look etc.) of a Web Part Instance

Now that we have added a Web Part instance to the page we may want to change the way it looks. When it was first placed on the page it was given a default look.

One of the more annoying things about STS 1.0 was that you cannot change this default look without having to resort to FrontPage. For instance, the default defines which columns are shown, the order of these colums and also the sort order. In other words, when the list is placed on the page it is given a default *view*. This is also true with

WSS, but now you can actually change this view without having to use FrontPage.

To change the look of the new "Shared Documents" Web Part instance click on the little triangle or down-arrow on the right hand side of the Web Part Title Bar again. Select

"Modify xxxx Web Part". The Web Part instance propery sheet is then shown to the right of the page.

There are 4 main sections of properties:

- List Views

- Appearence

- Layout

- Advanced

List Views

In WSS you can actually assign one of the views allready designed for the list or document library to the Web Part instance.

So, if you don't like the default view (called <Summary View>), just make a suitable view for the list first (do this on the list or document library page just as you may be used to from STS 1.0). Then you can assign this view to the Web Part instance.

135

In the "Selected View" drop-down list you will be able to select the <Summary View> or any of the views available for the list or document library itself.

Note that the association between a list/library view and the Web Part instance is not dynamic. This means that if you change the assigned view in the list/library itself after having done the assignment, the view of the Web Part instance will not change (when you assign a view to a Web Part instance, the view is actually *copied* from the list view into the Web Part instance properties).

In the List Views section you can also change the Toolbar type to be used by the Web

Part instance.

NOTE: You will not be allowed to change the List Views on shared Web Part instances if you are in "Modify My Page" mode! You can however change List Views on your private Web Part instances.

Appearance

Here you can change the Title of the Web Part instance (each instance can have its own

Title, handy if you have multiple instances of the same Web Part on the page etc.). You can also set the height and width of the Web Part instance. The Frame State (minimized or normal) and Frame Style can also be changed.

Layout

Here you can hide the Web Part instance, set the alignment (left-to-right or right-to-left).

You can also move the Web Part instance to another location by changing the Zone and

Part Order.

Advanced

Here you can (among other things) disable the possibility of minimizing, closing and changing the zone for the Web Part.

When you have finished changing the Web Part instance, click "Apply" to see the effect of the changes while staying in "change" mode or click "Done" to apply the changes and get back to normal mode.

Note the minimized/maximized state of a Web Part instance can be changed by just clicking on the little triangle or down-arrow on the right hand side of the Web Part Title

Bar and either selecting "Minimize" or "Restore". The state is saved and is personal/shared specific.

136

VI.4 Using Web Part Connections

Introduction

In STS 1.0 with Web Parts not even available, it was naturally impossible to link Web

Parts. Linking libraries required use of a field of type Lookup (which I never found particularly easy).

In WSS Web Parts are available. One of the hidden features of the use of Web Parts in

WSS for people coming from an STS version 1 background is the ability to link Web parts to each other.

The following example attempts to make the use of Web Part Connections clear.

The Aim of this "Project"

The aim of the "project" is to create a web site that contains information about the various members of a Project. The Project has members from several different locations and companies and thus it is important that members can be identified both by company and name.

Web Part Connections will be used to achieve this goal in a quick and simple way.

Details

A Subweb is created with the name of the Project (W2K).

In the Subweb a couple of custom libraries are created. a) Custom Library 1 - Company

This custom library will contain the names of the companies from which the project members are taken.

- amend the default field name from Title to CompanyName, retain all other defaults

- get rid in All Items of the Attachment

- sort All Items in CompanyName order

- add to the Company custom library the companies

The three (say) records in the Company custom library now contain Firm1; Firm2; Firm3 b) Custom Library 2 - Personnel

137

This custom library will contain the details of the people in the project such as:

CompanyName; DisplayName; NetworkName; PictureLocation; Skills. again amend the Title Field, this time to DisplayName and then add the other fields

- Use Choice for the CompanyName

- NetworkName would typically be short (8?)

- PictureLocation is of type Hyperlink or Picture/Hyperlink (and is optional)

- Skills could be a 'multi-choice from a list' field or a multi-line field (possibly with Fillin = Yes)

Populate the Personnel custom list making sure if you have a picture for the person that the Hyperlink is valid and accessible by all users.

Connection Number 1 - Company to Personnel

Now go to the Home Page of the SubWeb (i.e. of W2K) and Click 'Modify My Page'

- Select Shared View

- In 'Modify Shared Page' select Add Web Parts; Browse.

In the 'Team Web Site Library' you'll notice your two new custom lists Company and

Personnel now listed as Web Parts.

Select Company and add it to the centre column (for Web Parts = Left) and then select

Personnel and add it to the Right column.

Now you need to go in 'Modify Shared Page' to "Design This Page"

Then Click on the arrow at the top-right of Company.

Select Connection/Provide Current Row To/Personnel

Say OK to the use of CompanyName from Company; Select CompanyName from

Personnel and click Finish.

You know have a list of radio buttons in Company none of which are selected. All items are still listed in Personnel.

Select one of the radio buttons in Company. If all is well you will immediately see in

Personnel a reduced list of items (those only for the company selected)

Tidy up by removing the CompanyName from the list of visible items in All Items in

Personnel.

138

(Tip: A better way is to create a new view without CompanyName and use that view rather than All Items on the top page)

Add an Image Web Part and connect to that

Now Modify Shared page again and select 'Image Web Part' - add it to the centre column.

'Design this Page' and this time connect Personnel to Image Web Part specifying

PictureLocation.

The names in Personnel now become radio buttons and when selected the appropriate image will appear in Image Web Part.

[In Beta-2 on clicking one of the Personnel radio buttons, the entire list of Personnel appears and the radio buttons in Company are not longer clicked - i.e. the two sets of radio buttons on the page are regarded as being one set . This is resolved in later fixes.]

139

VI.5 The Data View Web Part in Front Page 2003

John Jansen posted the following message in a beta newsgroup (he has given me permission to include it "as is" in this FAQ)

"My favorite web part is the Data View web part.

This part allows you to connect to almost any data source that can generate XML. For example, I test against SQL server, Oracle, XML web services, server-side scripts, XML files located both internal and external to my web site, as well as standard WSS list data.

Once connected I just drag the data source onto a new page and start making the view look exactly as I want it to look using standard Table and formatting tools.

I haven't seen very many posts about this new feature set, but it is huge and very cutting edge and I have a feeling there are some really interesting issues lurking just below the surface waiting to be found.

Please try the following:

1. Open a WSS site in FrontPage

2. Create a new page in design view / Open an existing page in design view

3. Click on Data..Insert Data View

4. Drag the "Announcements" list from the Data Source Catalog onto the page created/opened in 2.

NOTICE: FrontPage will generate an XSLT table containing some of the Data Values from the Announcements list. You are now authoring XSLT in a WYSIWYG environment. You can add borders, conditional formatting, filters, sorting, grouping, etc.

Because of our leveraging WSS and Web Parts for this, you can also connect this data view to other data views.

Repeat the steps above after adding some announcements so that you have two data views on the same page. Right click the first one and choose Web Part Connections. Go through the wizard to create a connection that will filter the second view based on the ID of the first view and then view this page in Internet Explorer.

NOTICE: As you click to fire the connection, you will see only the data from that specific record in the second view. "

140

VI.6 The Form Web Part

Once again John Jansen has given me approval to use one of his very useful texts from the FrontPage 2003 beta newsgroup.

This one concerns the Form Web part and is very relevant stand-alone as well as in the

FrontPage context.

---

The idea of a Form Web Part is to allow you to easily provide user response on a page as data to another Web Part through Web Part Connections. The Form Web Part is very similar to the Content Editor Web Part in that you can specify the HTML source that the

Web Part renders. However, the Form Web

Part also has the ability to detect the form elements that are in its HTML source and determine which elements are possible data sources in a Web Part Connection.

The Form Web Part implements the Row Provider connection interface. As such, it has the ability to pass a row of data to another Web Part. During connection authoring time, the Web Part parses through its HTML source to find all the form elements that can provide HTML, and enumerates them as cells in the row of data you're about to provide. The names of the cells correspond to the names of the form elements in the HTML.

By default, the Form Web Part comes with a textbox and a submit button. However, any number and variety of the following form elements can be used in the Form Web Part to provide data:

Text Boxes:

When used as a data source, a text box provides the text that the user entered.

e.g. <input type="text" name="T1">

Check Box:

When used as a data source, the check box provides the "value" attribute of the control when it is checked, and the value "off" when it is not checked.

e.g. <input type="checkbox" name="C1" value="checked">

141

Select Control:

When used as a data source, the drop down provides the "value" attribute of the item that is selected. In the case of multiple selections, it provides the value of a comma delimited string of all the selected values. In the case of no selection made, it provides the value

"off". e.g.

<select size="1" name="D1">

<option value="foo">foo</option>

<option value="bar">bar</option>

</select>

Radio Button:

When used as a data source, the radio button provides the

"value" attribute of the selected radio button. e.g.

<fieldset>

<input type="radio" value="foo" name="R1">

<input type="radio" value="bar" name="R2">

</fieldset>

Text Area:

When used as a data source, the text area provides the text that the user entered. e.g.

<textarea rows="2" cols="20" name="S1"></textarea>

Finally, FrontPage offers a great environment for working with the Form Web Part. In

FrontPage, you can insert form elements or edit the HTML content of the Form Web Part in a WYSIWYG environment, much like how you would be editing any other part of your HTML pages. You can also connect up the Form Web Part with other Web Parts from right within FrontPage.

142

VI.7 How to save a Document Library as a template that with content is greater than 10 MB in size

If the size of a Document Library is greater than 10MB, it is impossible to save the

Document Library with content as a template. It is also impossible to change the 10MB limit as this is hard-coded.

This brief tutorial shows one simple way of getting round this problem.

1. Save the Document Library without Content

Try first to save the Document Library as a template with content. When this doesn't work because it is too large, save the Document Library as a template anyway *without content*.

(Save it say as "Sample")

2. Create New Document Libraries

Next create several new Document Libraries based on the "Sample" Template - call them

Sample1; Sample2; Sample3 etc.

3. Transfer Documents to "Sample1"

Open the original Document Library in Explorer Mode.

Open Sample1 in Explorer Mode in other browser instance.

In Explorer Mode the documents are in Alphabetical order of the Name (i.e. File Name).

The file sizes of the documents are also listed.

Go to the original Document Library.

Select the first group of documents (in alphabetical order) until ca 7MB of total size. Ctrl-

C. (Note the number of documents you are copying)

Go to Sample1.

Ctrl-V

At this stage all the documents have been copied across but none of the fields you added to the original Document Library have been populated except for Office Documents (i.e. the fields for e.g. .pdf files haven't been populated)

4. Populate the fields

143

a) Create a View in the Original Document Library that includes all the fields that need to be populated and is in 'Name' order. b) Create an Identical View in Sample1.

Go in both cases to the Dataview version of this View (easiest is to use Create a View of type Dataview at stage a) and b)).

Copy and Paste carefully as a single group all the field contents for these documents from the original Document Library to Sample1.

5. Save "Sample1" as a Template with content

Complete the process by saving Sample1 as a template with content.

6. Loop

Repeat for Sample 2, Sample3 etc. until all Documents have been transfered.

You will now have templates for several document libraries with content.

7. Load the templates into your other server

Next Create Document Libraries in your other server using the templates Sample1;

Sample2 etc. Call the first one by the name you intend to use in this site. ("NewSample")

8. Transfer to "NewSample"

Finally repeat steps III and IV above in reverse - copying from Sample2 to NewSample; from Sample3 to NewSample etc.

9. Housekeeping

Finally don't forget to delete the temporary Document Libraries from both servers !

144

VI.8 The Company Web in SBS 2003

This "Tutorial" is in fact a collection of information about the SBS 2003 Company Web

(which uses WSS). The initial set of information was kindly provided by

Ed Lee

. Many of the answers he used were provided by

Ray Wong

. (The editing is mine)

This long set of questions and answers are only relevant to the SBS 2003 implentation of WSS!

Are there SBS features which may be dependent on WSS?

Almost none except you want to route incoming fax to WSS, then you need WSS.

Where are the files placed in the WSS Companyweb stored?

They are stored in either a WMSDE or SQL database depending on whether you are using the Standard or Premium version of SBS 2003.

The default location for the database files is

Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data

Can these database files be moved? How?

To move the SharePoint database:

OSQL -E -S servername\sharepoint [Enter] sp_detach_db STS_Config [Enter] go [Enter] sp_detach_db STS_servername_1 [Enter] go [Enter]

<Before you go to the next two steps. Go ahead to copy the SharePoint files from the original location (Program Files\Microsoft SQL

Server\MSSQL$SHAREPOINT\Data) to the "new location"> exec sp_attach_db @dbname = 'STS_Config', @filename1= 'E:\new location\STS_config.mdf', @filename2 = 'E:\new location\STS_Config_log.ldf'

[Enter] go [Enter] exec sp_attach_db @dbname = 'STS_servername_1', @filename1= 'E:\new location\STS_servername_1.mdf', @filename2 = 'E:\new location\STS_servername_1_log.ldf'[Enter] go [Enter]

145

Are there any advantages to using SQL rather than WMSDE?

The main differnce is that SQL provides search capabilities.

Is it possible to upgrade the Companyweb database from WMSDE to SQL?

With SBS 2003 Premium Edition there is a premiuminstallsteps.htm on the Premium

Technologies cd that outlines the steps to upgrade the SharePoint named instance and suggest installing the Full-Text search component of SQL.. But basically in order to use

Full-Text search in WSS you need to have the following

(answer supplied mainly by

David Copeland

)

1) The SQL Server that WSS is using must be full SQL Server 2000.. In a default SBS case that would be the SharePoint named instance.

2) During the upgrade of the SharePoint named instance be sure to select to install SQL's

Full-Text Search option

3) You need to install the SQL Server 2000 SP3a on the instance that it is using.. By default again, the SharePoint named instance

4) Then go to Start/Administrative Tools/SharePoint Central Administration and click on Configure full-text search and then check the box for Enable full-text search and index component

Something to keep in mind is that the full-text search functionality uses a technology called Ifilters to index the files.. Depending on the file types you are wanting to search you may want to look to see if there are Ifilters for them..

For example. if you were uploading Visio 2002/2003 files there are the following two downloads available

Visio IFilter 2002 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0D585A2

1-DD90-447F-B145-DED2BC21CB5C

146

Visio IFilter 2003 Add-in: Text Search in Visio Files http://www.microsoft.com/downloads/details.aspx?familyid=dcee9e09-448b-4386-b901efea29cac808&displaylang=en

Where can I learn more about the WSS technology used to create Companyweb?

http://wss.collutions.com

is probably the most comprehensive WSS FAQ site.

Microsoft's site is at http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx

The SBS FAQ at http://www.smallbizserver.net

has a section on SharePoint.

The WSS newsgroup is at microsoft.public.sharepoint.windowsservices

Can I make Companyweb accessible over the Internet?

This differs depending on whether you are using SBS Standard Edition or SBS Premium with ISA Server 2000.

For Standard Edition, run the Configure E-mail and Internet Connection Wizard and check the option to publish Companyweb. You can then access the site at www.yourwebsite.com:444 . If you have a router, make sure it is configured to pass port

444 traffic to your SBS server.

If you are using the Premium Edition with ISA Server 2000 as your firewall, Microsoft has an article and there have been at least two other successfuly used configurations: http://support.microsoft.com/default.aspx?scid=kb;en-us;838304

Tony Su

has made some recomendations at http://www.su-networking.com/faq/SBS2K3_ISA_Recommendation.htm

Les Connor

made some recomendations at http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-

8&selm=e9qlUtB5DHA.2300%40TK2MSFTNGP10.phx.gbl&rnum=1

147

How do I back up and restore http://Companyweb data in SBS 2003?

See KB article 829112 at http://support.microsoft.com/default.aspx?scid=kb;en-us;829112&Product=sbs

How do I remove or install Companyweb?

See KB article 829114 at http://support.microsoft.com/default.aspx?scid=kb;en-us;829114&Product=sbs

or as supplied by Ray Fong -

Remove:

1. Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set

Server Tools to Maintenance. Set Intranet to Remove

2. Control Panel -> Add Remove Program -> Microsoft SQL Server Desktop Engine

(SHAREPOINT) -> Remove. (This step is not required if you believe the SharePoint database is installed correctly.)

3. Delete

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet

4. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL

Server\SHAREPOINT

(!!!!!Do NOT delete this key if you did not remove Microsoft SQL Server Desktop

Engine (SHAREPOINT) in the pervious steps !!!!!)

5. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web

Server Extensions\Ports\Port /LM/W3SVC/4: (Do not delete "Port /LM/W3SVC/1:" because it is FronPage Server Extension 2002 which is installed on the Default WebSite.

If you see additional "Port /LM/W3SVC/X:", backup the keys first and then remove them)

6. Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT to

MSSQL$SHAREPOINT.OLD (!!!!!Do NOT rename this folder if you did not remove

Microsoft SQL Server Desktop Engine (SHAREPOINT) in the pervious steps !!!!!)

148

7. Control Panel -> Add Remove Program -> Add/Remove Windows Components.

Uncheck Application Server -> Internet Information Services (IIS). Click Yes to confirm removal of ASP.NET and RPC Over HTTP Proxy

8.Rename C:\Inetpub to C:\Inetpub.old

Install:

1. Control Panel -> Add Remove Program -> Add/Remove Windows Components

a. Check Application Server -> Internet Information Services (IIS)

b. Check Application Server -> Internet Information Services (IIS) -> FrontPage 2002

Server Extensions, NNTP Service, SMTP Service

c. Check Application Server -> ASP.NET

d. Check Networking Services -> RPC Over HTTP Proxy

2. Control Panel -> Add Remove Program -> Windows Small Business Server 2003

a. Set Server Tools to Reinstall.

b. Set Intranet to Install. (If Intranet failed to install, please refer to Q832880)

c. Expand Client Deployment, set Internet Explorer 6.0 and Microsoft

Office Outlook 2003 to None (Installed).

d. Set Exchange Server to Reinstall.

Configuration:

1. Run CEICW. This will reconfigure the IIS for OWA/Remote Web

Workplace/Companyweb.

2. Verify you can logon to OWA via https://localhost/exchange , RWW via https://localhost/remote , and Companyweb via http://Companyweb

149

VII. Documents and Web Sites

VII.1.1 General Documents

For Microsoft documents please go to http://wss.collutions.com/Lists/MS%20Articles/Grouped%20by%20Category.aspx where I will try to keep them up-to-date.

VII.1.2 Web Part Documents

I. Office Web Part Components

There are .chm files available for most of the Web parts supplied with the Office Web

Parts and Components download (see 'MS Articles' on this site)

These are stored on your hard disk as part of the installation of that package, typically at c:\Program Files\Common Files\Microsoft Shared\Web Components\11\1033

The five files are

OWCRCH11.chm - Charts

OWCRDP11.chm - Data Access

OWCRPL11.chm - Pivot Table

OWCRSS11.chm - Spreadsheet and

OWCVBA11.chm - Object Models details for the above four web parts.

Thanks to Jeff Cate for supplying the impulse to investigate this further.

II. General Information on Web Parts

- A Developer's Introduction to Web Parts (May 2003) http://msdn.microsoft.com/library/en-us/dnspts/html/sharepoint_northwindwebparts.asp

150

The remaining documents follow in alphabetical order.

- Building an On-line Web Part Library (August 2003) http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnspts/html/sharepoint_buildinganonlinewebpartgallery.asp

- Converting Dashboard Web Parts to the Web Part Infrastructure (August 2003) http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnspts/html/sharepoint_movingwebparts.asp

(Thanks to Marco Russo for correcting the address after it changed)

- Modifying the User Interface for Web Parts and Web Parts Pages (May 2003) http://msdn.microsoft.com/library/en-us/dnspts/html/sharepoint_modifyingui.asp

- Packaging and Deploying Web Parts for Microsoft Windows SharePoint Services (May

2003) http://msdn.microsoft.com/library/en-us/dnspts/html/sharepoint_deployingwebparts.asp

- Web Part Templates for Microsoft Visual Studio .NET (March 2003) http://msdn.microsoft.com/library/en-us/dnspts/html/sharepoint_webparttemplates.asp

(These parts are retained here for the PDF edition, otherwise Web site visitors are advised to go to the MS Articles page here at http://wss.collutions.com/Lists/MS%20Articles/Grouped%20by%20Category.aspx which will be kept up-to-date

VII.1.3 Some IIS 6.0 Documents (and tools)

- IIS 6.0 Resource Kit Tools at http://www.microsoft.com/downloads/details.aspx?familyid=56fc92ee-a71a-4c73-b628ade629c89499&displaylang=en

- Windows Server 2003 Deployment Kit: Deploying Internet Information Services (IIS)

6.0 http://microsoft.com/downloads/details.aspx?FamilyId=F31A5FD5-03DB-46D2-9F34-

596EDD039EB9&displaylang=en#filelist

151

VII.2 Web Sites (in alphabetical order)

- Collutions

www.collutions.com

/ wss.collutions.com

Collutions is the company that designed the STS newsgroup FAQ in STS form( www.collutions.com/Lists/FAQ ) and now also the WSS newsgroup FAQ

(wss.collutions.com) on a WSS site. It is also the home site of Jim Duncan's (an STS

MVP) Collutions company that provides custom solutions based on STS/WSS for web sites.

- FrontPage 2003 Customization Kit for SharePoint Products and Technologies

http://www.sharepointcustomization.com/default.aspx

A site that I'm now told is a Microsoft site. Some useful hints of the use of FrontPage

2003 with WSS sites many of which are linked to in the MS Articles section here.

- SharePoint 2003 Resource Portal

http://portal.sharepointsolutions.com/default.aspx

The WSS part of this site has lots of the same links to articles and web casts etc. that you can find here in the WSS FAQ site, but there's also extensive sections for SharePoint

Portal Server 2003 and it IS organised in a different way, so you might find it suits you better.

- SharePointExperts

http://www.sharepointexperts.com/

This is Dustin Miller's (one of the STS MVPs) company's site. It's a consulting and development firm which also has some STS add-ons. These days also a training firm that provides at its "Boot Camps" in-depth training in WSS. They also have a web hosting service (see below VII.3)

- SharePointTips

http://www.sharepointtips.com

152

This is a source of STS/WSS information. It's also linked to perhaps the oldest specialist

STS/WSS web hosting company - UnifiedWebMedia (see below VII.3). These days sharepointtips.com mainly links directly to the wss.collutions.com information.

- SharePointUniversity

http://www.sharepointu.com/

This is an online community, run by SharePointExperts (see above), for STS/WSS users and developers. There are code samples, how-tos, SharePoint-related news and a very active online discussion forum.

Some areas require free registration, others such as the link to "Other SharePoint related sites" (where you'll find this FAQ in PDF form) do not.

- SPS FAQ

http://www.spsfaq.com

This is the site that hosts the SharePoint Portal Server FAQ. Originally, naturally, for version 1 of that product, it now also covers version 2.

Useful for those people who are considering "upgrading" WSS to SPS and also for those people who just love to add code to their WSS site.

- Web Revel

http://tsc.webrevel.com/issues/topics.asp?appid=2

Their own set of questions and answers ...

(

SPS 2003

is at appid=4 in case you need that too)

- WSS Demo Site

http://www.wssfaq.com/

Here's a brief explanation of what this site is about (quoted from the site in extract)

"This site is not a true WSS FAQ, there are plenty of other sites providing that" ....

153

"I enjoy doing cool things with WSS and FrontPage. Some examples of this can be seen on this site." ...

"I will endeavour to write some articles that explain how to achieve these effects using

FrontPage 2003 (and Windows SharePoint Services, XML Web Services, XSLT Data

Views)."

- WSS FAQ

(see above Collutions)

- WSS FAQ European Mirror Site

www.asaris-matrix.com/mvp-walsh

VII.3 Web Hosting for STS/WSS sites (in alphabetical order)

Please note that a listing here does not mean a web hoster for WSS is a recommended web hoster for WSS. I have for instance received a negative report on one of the below. So as always make your own investigation and make your own decision.

The only web hoster I have long time personal experience of is Unified Web Media, where I have never had any reason to be anything but 100% satisfied. (Mike) [I have also used Asaris with no problems - but so far only for a couple of months.]

- 724 Hosting

http://www.724hosting.com/sharepoint/

- Apptix On-Demand

http://www.sharepointsite.com/default.aspx

- Asaris (German) (Host of the WSS FAQ European Mirror)

http://http://www.asaris-matrix.com/

- bCentral (Microsoft)

http://www.bcentral.com/Default.asp

- FrontPages Web Hosting Network (from 2.2004)

http://www.frontpages-web-hosting.net/windows.sharepoint.services.htm

154

- myOfficeSystem (UK)

http://www.myofficesystem.co.uk/services/windowssharepointservices.asp

- Outlook Technologies

http://www.outtech.com/hosting.html

- Reinvent Technologies LLC

http://www.re-invent.com/sharepoint2003.asp

- SharePointExperts

http://www.sharepointexperts.com

- UnifiedWebMedia (Host for the WSS FAQ site)

http://www.unifiedwebmedia.com/

- VIA net.works

http://www.vianetworks.net/VIA_Solutions/Intranet/WSS/

VII.4.1 SPS 2003 and WSS Training – SharePoint Experts Boot Camps

http://www.sharepointexperts.com/training.htm

"Boot Camps" provide in-depth training in WSS given by Dustin Miller.

VII.4.2 SPS 2003 and WSS Training – SharePoint Summits

http://www.sharepointsummit.com/

Bill English's training courses.

VII.4.3 SPS 2003 and WSS Training – SkillSolve (UK)

Planning, Implementing, and Managing a Microsoft SharePoint Products and

Technologies 2003 Infrastructure (3 days) http://www.skillsolve.co.uk/technicalcourse.asp?CourseID=212

VII.5 WSS Products

This section will be a brief listing of any products that say that they extend the facilities contained in the standard WSS product.

155

The list is provided without any guarantees and will not contain companies that provide web parts as these are well covered elsewhere.

The list will be enhanced as and when I read about the existence of such products (or am sent mail)

VII.5.1 WSS Products – SmartLibrary http://www.nintex.com/ProductSmartLib.aspx

Brief extract:

Nintex SmartLibrary is a cost-effective solution that extends Microsoft SharePoint Portal

Server 2003 and Microsoft Windows SharePoint Services to provide advanced document management features.

VII.5.2 WSS Products - Scene7 for SharePoint Portal Server 2003 http://www.scene7.com/news/2004/20040224.asp

Brief extracts:

A cost-effective digital asset management (DAM) solution for small/medium businesses. provides "previews of CMYK images, vector images, and layered Photoshop® files along with related metadata. Reads and writes popular file formats for Web, print and wireless use including BMP, WBMP, GIF, JPG, PNG, PCT, TIFF, PDF, TGA, Adobe

Illustrator® and Photoshop PSD or EPS files with accurate ICC color profiles."

Note: I am

assuming

this product will work with WSS as wel

l

VII.5.3 WSS Products - iOra for Microsoft SharePoint http://www.iora.com/products/sharepoint.asp

Brief extract: iOra for Microsoft SharePoint enables organisations to extend the benefits of SharePoint to their mobile workers. Users enjoy full access to information on their portal even when they are not connected to their corporate network.

156

VII.5.4 WSS Products - Workflow Accelerator for SharePoint Technologies http://www.skelta.com/

Product still (May 2004) in pre-release state.

VII.5.5 WSS Products – My Workplace for Outlook http://corasworks.net/Products/Software/workplace/mwo/index.html

"Now, you can have full access to Microsoft Outlook folders from within your SharePoint sites. With My Workplace for Outlook, each of the core functions of Outlook are now a web part that can appear in your workplace. When you log into your workplace you now have your Outlook information appearing with your SharePoint information."

Pricing on the site; + yearly maintenance charges

VII.6.1 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003

Unleashed

UK: http://www.amazon.co.uk/exec/obidos/ASIN/0672326167/ref=ase_heme/202-1531874-

7158254

US: http://www.amazon.com/exec/obidos/tg/detail/-/0672326167/ref=ase_heme0f/002-

7288644-9928022?v=glance&s=books

VII.6.2 SPS 2003 and WSS Books – Microsoft SharePoint Portal Server 2003 :

Planning, Design and Implmentation

UK: http://www.amazon.co.uk/exec/obidos/ASIN/1555583016/ref=ase_heme/202-1531874-

7158254

US: http://www.amazon.com/exec/obidos/tg/detail/-/1555583016/ref=ase_heme0f/002-

7288644-9928022?v=glance&s=books

157

VII.6.3 SPS 2003 and WSS Books – Microsoft SharePoint Products and

Technologies Resource Kit

UK: http://www.amazon.co.uk/exec/obidos/ASIN/073561881X/ref=ase_heme/202-1531874-

7158254

US: http://www.amazon.com/exec/obidos/tg/detail/-/073561881X/ref=ase_heme0f/002-

7288644-9928022?v=glance&s=books

VII.6.4 SPS 2003 and WSS Books – Microsoft SharePoint: Building Office 2003

Solutions

UK: http://www.amazon.co.uk/exec/obidos/ASIN/1590593383/ref=ase_heme/202-1531874-

7158254

US: http://www.amazon.com/exec/obidos/tg/detail/-/1590593383/ref=ase_heme0f/002-

7288644-9928022?v=glance&s=books

This version – 3rd June 2004, Helsinki, Finland

158

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement