Connect.Collaborate.SharePoint
May
28

Something new that I did today...

Scenario

  • A Document library with metadata column for DocumentType.
  • There are about 20 document types in the lookup and a site collection field that references this list.
  • A Base Content Type that includes this lookup field
  • 5 Content Types that inherit from the base
  • Not all of the document types have an Office template which is why there are fewer content types.

When a user creates a new document from one of the content types that does have a 1:1 relationship with a document type (e.g. Fax) then I want the Document type value to be automatically selected in the Document Information Panel.

When you create the custom DIP form in InfoPath, under the Tools menu you will see a Default Values option which brings up this dialog box.

The default value is set to the item ID for the lookup value in the Document Types list.

When a new document is created using this content type, the correct metadata value is selected from the choice list

Categories:

 
May
9

Just wanted to highlight an update to the instructions on http://technet.microsoft.com/en-us/library/cc261890.aspx that is not mentioned in many of the blog postings that also suggest how to build your MOSS slipstream install.

Important:

Delete Wsssetup.dll because it may conflict with Svrsetup.dll.
Having both Wsssetup.dll and Svrsetup.dll in the updates folder for a slipstreamed installation source is not supported.

 

I have to add a new WFE to an existing farm that is still running SP1 + the Infrastructure Update (nothing post that).
Should I:

  1. Add the new WEF using the original SP1 + IU update install and then upgrade the entire farm to SP2
    or
  2. Upgrade the current farm to SP2 and then add the new WFE using the SP2 slipstream install

I would (and did) go for option 2. The main reason is that I want the most stable platform possible before introducing any architectural or application changes.

Categories:

 
May
6

There have been several problems caused by security changes in .Net 3.5 SP1 that affect .Net 2.0 & 3.0 functionality that MOSS relies.
These issues can now be prevented by installing the hot fix mentioned in http://support.microsoft.com/kb/959209/ before you install MOSS.

Note: the "local loopback" detection will still be an issue for host header address (or other DNS entries) that resolve to the local host.
See http://support.microsoft.com/kb/896861 (go with option 1 for productions systems).

Categories:SharePoint

 
May
5
I have upgraded wssdemo.com to SP2 but not after trying the upgrade on several VPC's to ensure that all would go well. Of course there was one small problem. The Central Admin server installed WSS SP2 fine but the MOSS SP2 file failed with a generic MSI error 1603. A reboot of the server fixed this. The reboot however installed a number of other Windows Updates that were pending which caused search to stop working (I use a dedicated server for search so the loopback detection was blocking access). Next time I would reboot all servers in the farm before applying SP2 and then check the event & error logs for any issues before upgrading.
 
One of the fixes in SP2 means that the WSRP demo now works much better (once you authenticate) http://www.wssdemo.com/Pages/wsrp.asp
Categories:

 
May
1

Use the variationsfixuptool operation   This article describes how to use the Stsadm variationsfixuptool operation, which lets farm administrators control and perform operations against variations.

Pre-upgrade scanning and reporting for future releases (Office SharePoint Server)   This article describes how to use the Stsadm preupgradecheck operation to scan farm servers before starting an upgrade to ensure that some upgrade prerequisites are met and to detect known issues that can prevent the upgrade from completing successfully. The results of the scan enable you to address any issues that are identified.

Preupgradecheck: Stsadm operation (Office SharePoint Server)   This operation runs rules that are intended to assist administrators in preparing for upgrade.

Enumallwebs: Stsadm operation (Office SharePoint Server)  This operation displays the IDs and site map status for all site collections and subsites in the content database.

Variationsfixuptool: Stsadm operation (Office SharePoint Server)   This operation lets an administrator control the different versions—or variations—of a publishing site or page.

Listqueryprocessoroptions: Stsadm operation (Office SharePoint Server)   This operation displays the current values of the SharePoint Search query processor settings.

Setqueryprocessoroptions: Stsadm operation (Office SharePoint Server)  This operation sets the current values of the SharePoint Search query processor settings.

Categories: