SP 2003 – Managed paths

SharePoint 2003: How to exclude paths to run ASP.NET applications
Running an ASP.NET application on a server with a SharePoint instance requires excluding the virtual paths the application needs, as the SharePoint ISAPI filter will intercept all requests. This post assumes you have SharePoint installed as a Default Web Site.

1. From the Administration Tools, click on SharePoint Central Administration.

2. Click on SharePoint Portal Server in the left menu.

3. Click on Configure virtual server settings from the Virtual Server List page.

4. Click on Default Web Site.

5. Click on Define managed paths.

6. Enter a path, check Exclude Path, and click OK.

DataFormWebPart simple example – without GUIDs

<WebPartPages:DataFormWebPart
  runat="server"
  DataSourceID="test1"
  IsIncluded="True"
  AsyncRefresh="True"
  FrameType="None"
  NoDefaultStyle="TRUE"
  ViewFlag="8"
  Title="Contacts"
  PageType="PAGE_NORMALVIEW"
  __markuptype="vsattributemarkup"
  partorder="2"
  __WebPartId="{F282332F-8BEF-4B6B-8A46-7C1E00177C4E}"
  id="g_f282332f_8bef_4b6b_8a46_7c1e00177c4e">
 
 <DataSources>
 
  <SharePoint:SPDataSource
   DataSourceMode="List"
   ID="test1"
   UseInternalName="true"
   SelectCommand="<View />"
   runat="server" >
 
<SelectParameters>
<WebPartPages:dataformparameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues" DefaultValue="Contacts" />
<WebPartPages:dataformparameter Name="WebURL" ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="{sitecollectionroot}" />
</SelectParameters>
 
  </SharePoint:SPDataSource>
 </DataSources>
 
<datafields>@ID,ID;@ContentType,Content Type;@Title,Last Name; SNIPPED HERE
</datafields>
 
 
  <xsl>
      <xsl:stylesheet
        xmlns:x="http://www.w3.org/2001/XMLSchema"
        xmlns:d="http://schemas.microsoft.com/sharepoint/dsp"
        version="1.0"
        exclude-result-prefixes="xsl msxsl ddwrt"
        xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime"
        xmlns:asp="http://schemas.microsoft.com/ASPNET/20"
        xmlns:__designer="http://schemas.microsoft.com/WebParts/v2/DataView/designer"
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        xmlns:msxsl="urn:schemas-microsoft-com:xslt"
        xmlns:SharePoint="Microsoft.SharePoint.WebControls"
        xmlns:ddwrt2="urn:frontpage:internal"
        xmlns:o="urn:schemas-microsoft-com:office:office"> 
 
          <xsl:include href="/_layouts/xsl/main.xsl"/> 
          <xsl:include href="/_layouts/xsl/internal.xsl"/>
          <xsl:output method="xml" />
 
          <xsl:template match="/"
            xmlns:x="http://www.w3.org/2001/XMLSchema"
            xmlns:d="http://schemas.microsoft.com/sharepoint/dsp"
            xmlns:asp="http://schemas.microsoft.com/ASPNET/20"
            xmlns:__designer="http://schemas.microsoft.com/WebParts/v2/DataView/designer"
            xmlns:SharePoint="Microsoft.SharePoint.WebControls"
            xmlns:o="urn:schemas-microsoft-com:office:office">
              <ul class="list-arrow">
                <xsl:apply-templates select="/dsQueryResponse/Rows/Row"></xsl:apply-templates>
              </ul>
          </xsl:template>
 
          <xsl:template match="/dsQueryResponse/Rows/Row">
            <li>
              <a href="{@Title}">
                <xsl:value-of select="@Title"/>
              </a>
            </li>    
          </xsl:template>
 
      </xsl:stylesheet>
    </xsl>
 
</WebPartPages:DataFormWebPart>

>SharePoint Content pushdown

>This is a bit of a challenge.
Create and deploy a content type to Moss, lets say a “person” content type. Which consists of a couple of columns, Name and Address.

Then later you decide you need “phone number” …..

Simple, add an additional site column and re deploy the feature.

This is fine for any new “Person” you create, however all your existing “Person” will not allow you to add the “Phone number”

Enter the need for Content type push down.

Simple, go into site settings and manage site content types, click “propagate down” and all is well.

Unless you do scripted deployments that is.

So along comes Sรธren Nielsen and Gary Lapointe with a nice stsadm command to fix this issue for us.

For me though their solution has a couple of issues.
It seems to mix up display and internal name, causes me to lose (Hide) content, this is bad
It dosent “Seem” to fix up “list column title” which it may have messed up in the “List content type”

So if you have lost content by using “propagate content type changes” you are not alone, and if like me yours is just hidded by Gary’s issues, you can get it back.

I wont post the code here as its quite large and work in progress.

Drop me a mail if you are suffering from this and I’ll let you have the code. (At your own risk of course ๐Ÿ™‚ )

>SharePoint December Cumulative updates

>Had an issue installing this, well a couple of issues actually;

State of Farm prior to December updates: Standalone install also server running Sql 2005

  • Moss 2007
  • SP1
  • Infrastruture update
  • 2 x Security patches (Pre August updates)
  • August updates (However version number did not increment – known ‘to whom’ issue I understand)

The first update (Wss) installs fine but on running the SharePoint configuration wizard, that fails with a nondescript error (States the upgrade failed but gives no reason)
This is annoying as the reason (in this case) actually is in the upgrade log file created by the wizard.

[SearchQFE23318DatabaseAction] [12.1.5.0] [DEBUG] [12/21/2008 10:47:28 AM]: SearchQFE23318DatabaseAction.Upgrade: Upgrading MSSCrawlHistory table index on database WSS_Search_MossDev.

[SPSearchDatabaseSequence] [ERROR] [12/21/2008 10:47:28 AM]: Action 12.1.5.0 of Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence failed.

Or something simmilar in your case.

Fortunately for me we have an MVP on staff and he suggested a resolution to me, which seems to do the trick nicely. Thanks Ben.

Here goes, may or may not work for you.

In Central admin -> operations -> Services on server, disable the search services – both of them

  • Office SharePoint Server Search
  • Windows SharePoint Services Help Search

Confirm / Ensure these services are stopped in windows services

  • Windows SharePoint services Timer
  • office SharePoint server search
  • Windows SharePoint Services Search

Re run the configuration wizard – should now succeed
Re configure the search services back in central admin
You will need to re associate a index server with your SSP
You may need to issue an IISRESET before this finally works

Subsequant install and Config wizard for Moss worked without a hitch.

Second issue:
Although the SharePoint team blog states:

“The version of content databases should be 12.0.0.6335 after successfully applying these updates.”

I found it to be 12.0.0.6334. Apparently, another known ‘to whom’ issue ๐Ÿ™‚

HTH.
Brian

>Stsadm missunderstanding

>THIS IS THE WRONG WAY TO MOVE A SITE FROM ONE SERVER TO ANOTHER AT A DIFFERENT URL

On server A
———–
C:\..\BIN>stsadm -o backup -url http://serverA/ -filename c:\child.bak
Operation completed successfully.

On server B
———–
C:\..\BIN>stsadm -o createweb -url http://serverB/parent
Operation completed successfully.

C:\..\BIN>stsadm -o createweb -url http://serverb/parent/child
Operation completed successfully.

C:\..\BIN>stsadm -o restore -url http://serverb/parent/child -filename c:\child.bak -overwrite
Operation completed successfully.

stsadm -o backup / restore
————————–
Is for site collections only, the seris of commands above overwrites the root site collection on serverB. Which is absoloutly not what you intended to do.

It does not restore the backed up site to http://serverb/parent/child as you intended and as you specified -overwrite you get no warning that your root site collection is about to be overwritten.

THE RIGHT WAY TO GO ABOUT MOVING THE SITE

On server A
———–

stsadm -o export -url http://serverA/ -filename c:\child.bak -includeusersecurity -versions 4
Operation completed successfully.

On server B
———–
C:\..\BIN>stsadm -o createweb -url http://serverB/parent
Operation completed successfully.

C:\..\BIN>stsadm -o createweb -url http://serverB/parent/child
Operation completed successfully.

C:\..\BIN>stsadm -o import -url http://serverB/parent/child -filename c:\child.bak -overwrite -includeusersecurity
Operation completed successfully.

stsadm -o export / import
————————-
This does the right thing and imports the exported site to http://serverB/parent/child as you would expect

Happy days ๐Ÿ™‚

>RSS feeds in wss 3

>So rss feeds in wss 3 are good, however I want to be able to target a particular view on the list in question, how is it done?

I will find out and get back here as soon as I have …

Well, well, low and behold dougv sorted it already, dont you just love google.

which says, more or less, use the following url format

http://server/sites/site/_layouts/listfeed.aspx?List=LIST_GUID&View=VIEW_GUID

but note the GUIDs are sprinkled with Html encoded bits.