Friday, 25 July 2008

Content Deployment's Next Run Changing Time

Not sure if anyone has come across this, but if you are using Content Deployment and you have a Scheduled Job and you go to the "Manage Content Deployment Paths and Jobs", every time you refresh the screen, the Next Run time changes! Not the hours or minutes, but the seconds.

If anyone knows why, can you please let me know cause I'm curious about it.


Thursday, 17 July 2008

SharePoint Infrastructure Updates Available (Post SP1)

The Infrastructure Updates for WSS 3.0 and MOSS 2007 are now available.

Key updates for Windows SharePoint Services 3.0 include:
  • Platform performance improvements and fixes.
  • Several backup and restore fixes.
  • Several core Workflow fixes.
Key updates for SharePoint Server 2007 include:
  • New Search features such as federated search and a unified search administration dashboard.
  • Several core fixes to Search to improve performance and scale.
  • Platform performance improvements and fixes.
  • Several core fixes to the publishing Content Deployment features to improve reliability.
It is strongly recommended you install these updates which are also cumulative and include previous roll ups.

Ill let you know if I have any issues with installing them....


Monday, 14 July 2008


Are you looking for SharePoint work and live in Australia? There's plenty of openings going here. Email me and let me know and Ill forward your CV to the right people.


Thursday, 10 July 2008

Content Deployment Scheduled time keeps changing

Not sure if anyone has come across this before, but if you go "Manage Content Deployment Paths and Jobs" and have a scheduled job for content deployment. If you refresh the screen, you will notice that the time it's scheduled for keeps changing. Not the hours or the minutes, but only the seconds. Keep refreshing it, and it keeps changing. Does anyone know why?

Wednesday, 9 July 2008

Error “Guid should contain 32 digits with 4 dashes” during content deployment

I started getting an error saying “Guid should contain 32 digits with 4 dashes” during content deployment. After a lot of research I finally found the problem.

If you are referencing fields via GUID and including { and }, that is what causes this error.

eg field id="ab78ad79-6a48-1182-c3e5-93a3ed3e7831"
not field id="{ab78ad79-6a48-1182-c3e5-93a3ed3e7831}"

After going through all the site and removing the { and }, I did a content deployment and it worked.