I've been made aware that comments on the blog are not available.

We will get the development team to investigate this and apply SP2 (making sure that all blogs will not explode after 180 days!  ) - Please bear with us

SharePoint SP2 will expire 180 after implementation of the service pack.

Taken from the SharePoint team blog ....

"During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users"

A KB article has been released on this and a fix is being worked on quickly!

We all make mistakes ...

I often go to execute a stsadm command and find it is not in the path on the server I am working on, so I looked for a while of a way of adding it permanently through powershell and then realised it's a straightforward task with .NET code. The following will add the BIN folder within the program files structure to the PATH environment variable at local machine level so that all users will benefit.

   1:  $envpath = [environment]::GetEnvironmentVariable("Path","Machine")

   2:  $binpath = $env:Programfiles + "\Common Files\Microsoft Shared\web server extensions\12\BIN"

   3:  if ($envpath.contains($binpath) -ne $true ) {

   4:  $envpath = $envpath + ";" + $binpath

   5:  [environment]::SetEnvironmentVariable("Path",$envpath,"Machine")

   6:  Write-output "BIN Path added."

   7:  }

   8:  else

   9:  {

  10:  Write-output "BIN Path already added."

  11:  }

I have added a check to not add it if it is already present as the traditional method of using

SET PATH=%PATH%;C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

ends up with multiple copies of the BIN path in the variable and only applies for the current session.

owssvr.dll can be used in InfoPath projects to provide filtered or cascading drop down lists. Use an XML datasource - the syntax is http://yourserver/yourweb/_vti_bin/owssvr.dll?Cmd=Display&List={guid}&XMLDATA=TRUE.

However, beware if your list contains a lookupfield that allows multiple selections. If you have this, then the above syntax will return an invalid XML, or a blank data set.

List contains lookup field(s) with single selection - syntax works.
List contains lookup field(s) with multiple selection - syntax fails.