WSS

WSS 3.0: Document Library saved as a template is not in the Libraries choices on the Create Page

Robin Edwards — Tue, 14 Oct 2008 18:41:55 GMT

Windows SharePoint Services 3.0: Document Library saved as a template is not in the Libraries choices on the Create Page

The scenario:

A SharePoint user, named Pat, creates a Document Library and saves several forms.
The user then requests an administrator of the site to save this as a template (and include the content) named SchoolDocumentLibrary.
Pat then tries to Create a new Document Library with the newly created template. However, the SchoolDocumentLibrary is not listed in the Libraries templates.

The solution:

List templates are stored in a gallery list at the Site Collection level
Users creating new items must have Read access to the gallery list
Users that have been given access to a Site Collection at a site lower than the root will not see the List Template Gallery items (as they do not have Read access).
- Pat had been given access to a site that was 3 levels deep in the site collection. Therefore she did not have read access to the List Template Gallery at the root level.
Give users that will be creating document libraries (or lists) using custom templates Read access to the List Template Gallery at the root level of the site collection.
NOTE: I have not found a way to give item level permissions to items contained in the List Template Gallery.

WSS 3.0: Permission To Add Users to SharePoint Groups

Robin Edwards — Tue, 14 Oct 2008 18:02:01 GMT

General information

The Group Owner of a SharePoint group has permission to add / remove users from a group.
The Site Collection Administrator has permission to add / remove users from a group.
Only one person (or group) can be assigned as the Group Owner.
SharePoint Groups belong to the Site Collection.

Set an individual as the Group Owner

Navigate to the Change Group Settings page. One way to do this is:
- Browse to any site within the site collection.
- On the Quick Launch Click People and Groups.
- On the Quick Launch Click on the group you wish to modify.
- Click Settings – Group Settings
Change the Group Owner to the desired individual.

Set a group as the Group Owner

Create a SharePoint Group for all individuals that will have the Group Owner permissions (such as MySite Group Owner.
Add individuals to this group.
Follow the steps for setting an individual, but enter the SharePoint group name. HINT: You can use the address lookup to help find (and insure correct spelling) the desired group.

WSS & MOSS 2007 Tools

Robin Edwards — Mon, 13 Oct 2008 18:29:03 GMT

Links showing tools to help make development and/or administration of WSS 3.0 and/or MOSS 2007 easier

Katrien's About .NET Blog

Windows SharePoint Services 3.0: Software Development Kit (SDK)

http://www.microsoft.com/downloads/details.aspx?familyid=05e0dd12-8394-402b-8936-a07fe8afaffd&displaylang=en

WSS 3.0 - Features vs features

Robin Edwards — Thu, 12 Jun 2008 17:48:51 GMT

Now that I have migrated a site from WSS 2.0 to WSS 3.0 I am discovering that the sites migrated do not necessarily have the same functionality as new sites created in WSS 3.0. That's fine -- but I would like get a handle on what is different between the two sites.

Features seems to be an area with differences. I began researching this with google. Why oh why, did Microsoft call a feature a Feature in WSS 3.0. I am returning more results with new features (meaning new functionality) than I am for "Features" in WSS 3.0. When I first heard "Feature" was a formal name, I laughed. Right now it's annoying.

WSS 2.0 to 3.0 Upgrade - Alerts are not working

Robin Edwards — Sat, 12 Apr 2008 01:09:32 GMT

Following a recent upgrade of a WSS 2.0 to WSS 3.0 (using database migration due to moving to new hardware) it was discovered that alerts set in WSS 2.0 were not firing in WSS 3.0. It was strange because if you looked in Site Settings - User Alerts (under Site Administration column) it will look like the alerts migrated successfully.

It turns out, if you are using a different URL for the sites in 3.0 than 2.0, the alerts will not be correct. The alerts are stored in a table in the content database and one of the columns contains the the Site Url - this site Url is the Url from the 2.0 installation.

I think it is best practice to delete the alerts (which you have to do one by one) and then readd them (which you can add multiple users at one time) ... BTW, if you know of a way to delete multiple alerts for a list, please share.

Microsoft provides a suggestion by using code and updating the SiteUrl column in the ImmedSubscriptions table. More here

I reviewed the existing alerts in the table and then talked our DBA into updating the SiteUrl column in the ImmedSubscriptions table from myold.url.path.com to mynew.url.path.com.

Time to test, after making the change in production :)

I added an item to the list - the alerts all worked successfully. I am NOT guaranteeing this will work in every situation, but I took my chances and it worked for me.

RCC4 Presentation: WSS 2.0 to WSS 3.0

Robin Edwards — Wed, 07 Nov 2007 23:22:28 GMT

If you want the slide deck for my presentation "Wss 2.0 to Wss 3.0" I delivered at Richmond Code Camp 4 you can find it on the RCC4 site here.

Upgrading from WSS 2.0 to 3.0: Another Approach

Robin Edwards — Fri, 26 Oct 2007 12:59:29 GMT

Microsoft provides three approaches for upgrading from WSS 2.0 to WSS 3.0. More here.

If you are installing WSS 3.0 on a different server than the existing WSS 2.0, the only approach available is the “Database Migration”. This approach is considered "advanced" and requires additional steps. If you have a WSS 2.0 that has not been customized, this seems likes overkill for such a simple upgrade.

The following approach lets WSS do some of the behind the scenes work for you. This approach has WSS 3.0 creating the files needed for a new Web application and configuring IIS.

SUMMARY:

Using Central Administration, create a new Web application in WSS 3.0
- Create with all of the “production” values desired EXCEPT create a temporary content database.
Using STSADM, attach the V2 content (which WSS 3.0 will upgrade to V3) .
Using Central Administration, remove the temporary database.

DETAILS:

Install WSS 3.0 on the new server (if you have not already done so)
Copy the WSS 2.0 content database to the database you wish to use for 3.0
- (copy MyContent2 to MyContent3).
Using WSS 3.0 Application Management:
- Create a new Web Application
  - Create new IIS Web site with a temporary database
  - Database Name : wss_Portal_Temp (this database will be deleted, you must use a name of a database that does not already exist when creating a new Web application)
Attaching content from WSS v2
- Verify the SetupService account is a dbowner for the MyContent3 database
- Run stsadm
  - stsadm –o addcontentdb –url http://wss/ -databaseserver MyWSSServerName –databasename MyContent3
  - This might run a while if you have a large database
- Review log file: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS\Upgrade.log
- Review the Application event log on the WSS 3.0 server
Using WSS 3.0 Central Administration remove the temporary database
- Application Management tab
- SharePoint Web Application Management section
- Content Databases Link
- In the “Manage Content Databases”
  - Select desired web application in the Web Application dropdown
  - Click the link for the Temporary Database
  - In the “Manage Content Database Settings”
    - scroll to the last section and check “Remove Content Database”
    - Click “OK”

WSS 3.0 - Behind the scenes of creating a new Web Application

Robin Edwards — Mon, 27 Aug 2007 23:09:01 GMT

The new Central Administration site for WSS 3.0 is proving quite easy to use. In fact, it's so easy to use you can click some links, fill in the blanks and have a new Web Application in no time. It's so easy, if you don't know the best value for the "fill in the blanks" as you create the Web Application it still works. But then, if you want to remember what your answers were; it's not just a single click away. I needed to document the steps used in creating a Web Application and after some digging around in SharePoint and IIS found what happens behind the scenes when you complete the "Create New Web Application" page in the Central Administration site.

Create New Web Application - WSS 3.0
Central Administration: Create New Web Application Page Item	Behind the scenes OR How to determine the value entered after the Web Application has been created	Sample Value
Create a new IIS Web site: Description	IIS:	MyTopSiteDescrip
Create a new IIS Web site: Port:	IIS: Web site tab: TCP Port	24225 (I used random number chosen)
Create a new IIS Web site: Path	IIS: Home Directory Tab: Local Path	D:\wss\MyTopSite
Load Balanced URL: URL	IIS:	htp://MyTopSite
Application Pool	IIS: Home Directory Tab: Application Pool	wss_AppPool
Database Name and Authentication: Database Server	WSS Central Administration: Application Management Tab: SharePoint Application Management section: Content Databases - Click link under Database Name Column	ProdDataServer
Database Name and Authentication: Database Name	WSS Central Administration: Application Management Tab: SharePoint Application Management section: Content Databases - Click link under Database Name Column: Database Identification Section	wssMyContentData
Search Server: Windows SharePoint Services search server	WSS Central Administration: Application Management Tab: SharePoint Application Management section: Content Databases - Click link under Database Name Column: Search Server section	wssServer

WSS: Form Validation Error - No wait, I mean Invalid character in file name

Robin Edwards — Wed, 22 Aug 2007 13:06:29 GMT

One of my co-workers received the following error message when uploading a .pdf into a SharePoint Document Library

Form Validation Error

Please correct the information you provided by following these steps, then submit the information again:

The URL 'FolderA/FolderB/FolderC/FolderD/DocumentName #1234.pdf' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

Turns out this means:

You have an invalid character in the document name. In this case, rename the document without the "#".

Turns out :

There are lot of restrictions on document names (and url lengths) when uploading into SharePoint document libraries. I found an excellent summary of this information on Joel Oleson's blog File Name, Length, Size and Invalid Character Restrictions and Recommendations

SharePoint - IE Crashes when opening Office documents

Robin Edwards — Mon, 18 Jun 2007 13:34:55 GMT

Running WSS 2.0, IE 7, Office 2003 AND Groove 2007 - recently IE 7 crashes everytime I try to open an Office document. PDF documents open just fine. The error was:

"Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience."

Googled and tried several suggestions that did not correct the problem, including remove the Office Tools - Windows SharePoint Services Support (under the advanced add/remove for Office2003).

This worked from Microsoft MVP post - Outlook by the Sound (Paul Hollis) Guess it was due to having installed Groove 2007. Even after deleting the owssupp.dll - Groove 2007 continued to work

From: nick <nick discussions microsoft com>
Subject: RE: Office 2007 crashes IE7 with MOSS after updates
Date: Sun, 14 Jan 2007 13:00:01 -0800
Newsgroups: microsoft.public.sharepoint.general

The problem happens when you have, or had, two versions of office installed. You have to go into your program files directory and delete the version of owssupp.dll you're not using (for example if you upgraded to office 2007 and then downgraded back to office 2003 you delete owssupp.dll in the office12 directory). IE 7's manage addons you can see two versions of the owssupp dll registered so IE gets confused and you have to forcefully remove the version you're not using anymore.

Additional note:

Some additional information from Microsoft (KB 833714) can be found here.

WSS