Kit Kai's Tech Blog

Blog about SharePoint

This Blog

Syndication

Search

Tags

News



  • Want to be notified when new posts are available? Click the icon below for more information on how to subscribe.

    Blog Flux MapStats: Stats and Counter for Kit Kai's Tech Blog Subscribe to Kit Kai's Tech Blog

    Locations of visitors to this page Add to Technorati Favorites

Community

Email Notifications

Archives

Sharepoint / CMS Blogs

MVPs', Leads' & RDs' Blogs

Singapore Usergroups

Overseas Usergroups

About Me

May 2007 - Posts

One of my client have a very funny problem. They have deployed MOSS in a POC environment, and had their search settings set properly. Searching for information using the default content scope, "all sites", yeilds expected results, hence crawling and searching is working fine.

I guess some of you might have noticed that when you are at a site, you will see a new search scope, "This Site". When you are at a list, you will see additional scope, "This List". These two scope appears by itself, and there seems to have no place to to set this, or to debug this... How to get this fix?

Then my colleage who set this up told me that because of the IT policy, they have to extend the site to have a new URL. Along the way, the old URL has been render dead, and that causes the site search to fail. Changing the new URL to be in the default zone solved the problem.

 

Posted by kitkai | 3 comment(s)
Filed under:

[Quote Source="SharePoint Designer Team Blog"]

Hi folks, Gabe Hall here again.

If you are using 'Pause For Duration' or 'Pause Until Date' in your workflows, you may want to update your server with the latest Workflow Foundation hotfix. It deals with issues around the 'Delay' activity that those two SPD actions are based on.

The fix can be downloaded from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670&displaylang=en

This download addresses all three issues listed in KB 932816.

Enjoy!
-Gabe 

[/Quote]

Just to make sure everyone understands correctly, after reading the issues listed in the KB, it is not so much a SharePoint Designer problem, but a Workflow Foundation problem which two SPD actions uses. So if you are deploying workflows that deals with delays and timers, and are facing problems, maybe you should deploy the hotfix...

Posted by kitkai | with no comments
Filed under: