<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Microsoft Office Sharepoint Server 2007</title><subtitle type="html">...</subtitle><id>http://blogs.technet.com/victorbutuza/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.technet.com/victorbutuza/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2008-12-29T09:36:00Z</updated><entry><title>Crawl schedules do not work</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/08/26/crawl-schedules-do-not-work.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/08/26/crawl-schedules-do-not-work.aspx</id><published>2009-08-26T18:48:25Z</published><updated>2009-08-26T18:48:25Z</updated><content type="html">One issue you might have encountered after experiencing some Search problems.Although everything looks ok, the crawl schedules are not respected and the crawler fails to index the content at the specified times. No errors are logged and if you start the crawl manually , everything works great and the items are indexed ( regardless if you run a full or an incremental crawl). What you need to know is the crawler schedules are monitored by a timer job , specifically the Indexing Scheduling Manager Timer...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/08/26/crawl-schedules-do-not-work.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3277130" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author></entry><entry><title>Profiles don’t get imported from AD</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/08/17/profiles-do-not-get-imported-from-ad.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/08/17/profiles-do-not-get-imported-from-ad.aspx</id><published>2009-08-17T13:00:53Z</published><updated>2009-08-17T13:00:53Z</updated><content type="html">I ran into this while attempting to import the profiles and playing with my managed properties in the SSP. Here’s what I did and noticed: Having defined my&amp;#160; BDC as a People Details Repository&amp;#160; the initial purpose of the test was to completely replace all the user details in the search results with the results coming from BDC, because , as in life, the user details like address or office or job role might change and it is more likely that the updates will occur first in the BDC not always...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/08/17/profiles-do-not-get-imported-from-ad.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3274124" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="People" scheme="http://blogs.technet.com/victorbutuza/archive/tags/People/default.aspx" /><category term="Search" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Search/default.aspx" /><category term="Indexing" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Indexing/default.aspx" /><category term="Do Not" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Do+Not/default.aspx" /></entry><entry><title>This Site scope does not return any results</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/08/06/this-site-scope-does-not-return-any-results.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/08/06/this-site-scope-does-not-return-any-results.aspx</id><published>2009-08-06T15:42:41Z</published><updated>2009-08-06T15:42:41Z</updated><content type="html">Noticed something weird the other days: I was fiddling around managed properties in my search settings and thought of deleting some of them to remove them from being indexed and from the search results. Among other managed properties deleted, I also deleted the “Site” managed property. What I noticed after running a full crawl was that the “Search This Site:” Scope was no longer returning any results. I could retrieve the results from my search portal on the same SSP, which meant the documents were...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/08/06/this-site-scope-does-not-return-any-results.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3271155" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Search" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Search/default.aspx" /><category term="Do Not" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Do+Not/default.aspx" /></entry><entry><title>"The language is not supported on the server. "</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/08/06/the-language-is-not-supported-on-the-server.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/08/06/the-language-is-not-supported-on-the-server.aspx</id><published>2009-08-06T11:23:44Z</published><updated>2009-08-06T11:23:44Z</updated><content type="html">If you, like me had the chance of re-installing SharePoint (with all the language packs that you might have used before), it is likely that you have encountered this message. You will most likely see this message when running the configuration wizard , or attempting to create new sites, even in other languages than the installation. To sort this issue check if the following registry key is present: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\ServerLanguage If it’s not there create...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/08/06/the-language-is-not-supported-on-the-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3271080" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Install" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Install/default.aspx" /><category term="Uninstall" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Uninstall/default.aspx" /></entry><entry><title>Search crawl issues after installing .NET 3.5 SP1</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/06/04/search-crawl-issues-after-installing-net-3-5-sp1.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/06/04/search-crawl-issues-after-installing-net-3-5-sp1.aspx</id><published>2009-06-04T12:54:03Z</published><updated>2009-06-04T12:54:03Z</updated><content type="html">A number of issues with crawling content in SharePoint was observed since installing .NET 3.5 SP1.&amp;#160; The behavior, usually is the inability to crawl the content and various permission-related messages in your crawl log. Among these the most frequent message sounds like: Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content… The reason for all these messages is actually a change in the http authentication process implemented in this...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/06/04/search-crawl-issues-after-installing-net-3-5-sp1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3250277" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author></entry><entry><title>Federate to Sharepoint inside the same domain across farms</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/05/22/federate-to-sharepoint-inside-the-same-domain-across-farms.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/05/22/federate-to-sharepoint-inside-the-same-domain-across-farms.aspx</id><published>2009-05-22T19:30:00Z</published><updated>2009-05-22T19:30:00Z</updated><content type="html">Among many features and improvements to the search engine, things brought by the Infrastructure Update, perhaps the most awaited one, search federation, was finally deployed. With search federation the search results are no longer restricted to the site collection, webs, farms in other words, local search results. On the same search result page using the same search query term the user will retrieve the results from both the index as well as external search engines. But this doesn't mean that you...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/05/22/federate-to-sharepoint-inside-the-same-domain-across-farms.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3244626" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author></entry><entry><title>Move one site collection  from one web application to another</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/04/15/move-one-site-collection-from-one-web-application-to-another.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/04/15/move-one-site-collection-from-one-web-application-to-another.aspx</id><published>2009-04-15T20:24:42Z</published><updated>2009-04-15T20:24:42Z</updated><content type="html">I know that reading the above you will say : backup and restore&amp;#160; or export and import . Perfectly true. What if the procedure involves moving one BIIIIIIG Site &amp;gt; 15 Gb? If you have the time to do it, that’s perfect. Just schedule the operations and go ahead. Here is a method that will save you some time in completing this operation: Say you have the webapplication http://myportal Your customers create their sites under http://myportal/customers/subportal CustomerA&amp;#160; upgraded his contract...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/04/15/move-one-site-collection-from-one-web-application-to-another.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3226825" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="How To" scheme="http://blogs.technet.com/victorbutuza/archive/tags/How+To/default.aspx" /><category term="database maintenance" scheme="http://blogs.technet.com/victorbutuza/archive/tags/database+maintenance/default.aspx" /></entry><entry><title>Manual SharePoint uninstall procedure</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/04/14/manual-sharepoint-uninstall-procedure.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/04/14/manual-sharepoint-uninstall-procedure.aspx</id><published>2009-04-14T21:45:54Z</published><updated>2009-04-14T21:45:54Z</updated><content type="html">Here is a procedure that might come in handy when you, for some reason are required to&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; re-install the binaries of the server. Scenarios requiring this might include reverting to a previous state, fixing a corrupted farm, etc. I have ran into those situations where if you simply click on uninstall would not do much good, so here is a manual removal procedure , should you need it: First step (required if you want to recover your farm...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/04/14/manual-sharepoint-uninstall-procedure.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3226409" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author></entry><entry><title>Workflows do not start</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx</id><published>2009-03-14T08:55:32Z</published><updated>2009-03-14T08:55:32Z</updated><content type="html">You are of course aware of the fact that starting with Service Pack 1 the workflows created in SharePoint designer that should launch under the credentials of the system account will no longer start automatically. You know what the resolution is for this problem: simply do not to use the system account. You implemented all the steps written here http://support.microsoft.com/kb/947284 ,but the workflow still does not start. More interesting, if you email-enable a document library and attach a workflow...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3212706" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Workflows" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Workflows/default.aspx" /></entry><entry><title>How to enable workflow tracing (debug)</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/02/26/how-to-enable-workflow-tracing-debug.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/02/26/how-to-enable-workflow-tracing-debug.aspx</id><published>2009-02-26T08:38:00Z</published><updated>2009-02-26T08:38:00Z</updated><content type="html">This might come in handy whenever you (like myself and I am sure thousands of others) see some error in the execution of one workflow and found the completely useless messages like “Error Occurred” Dig deep and find nothing first troubleshooting step would be to enable verbose logging on the workflows category and check the SharePoint logs. If this does not provide you with a clue on what might be going on, you can try the following thing: Add the following code to the web.config of the site where...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/02/26/how-to-enable-workflow-tracing-debug.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3206903" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Workflows" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Workflows/default.aspx" /><category term="How To" scheme="http://blogs.technet.com/victorbutuza/archive/tags/How+To/default.aspx" /></entry><entry><title>Search Based Alerts</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/02/24/search-based-alerts.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/02/24/search-based-alerts.aspx</id><published>2009-02-24T20:27:00Z</published><updated>2009-02-24T20:27:00Z</updated><content type="html">Purpose : To get notified whenever something new gets indexed, based on a search term you specify. Say for instance that you would like to get notified whenever a new “TOP SECRET DOCUMENT” :) gets indexed. Go to the search page, issue a query and when the results page is displayed, click on the “Alert me“ link, configure the Search: TOP SECRET DOCUMENTS alert to inform you when there are New items in search result or, Existing items are changed or, All changes and choose the notification type to...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/02/24/search-based-alerts.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3206260" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Search" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Search/default.aspx" /><category term="Alerts" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Alerts/default.aspx" /></entry><entry><title>How to move an SSP</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/02/10/how-to-move-an-ssp.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/02/10/how-to-move-an-ssp.aspx</id><published>2009-02-10T11:29:00Z</published><updated>2009-02-10T11:29:00Z</updated><content type="html">In the past few months , I have come across quite a big number of issues who’s only supported solution (other than rebuilding everything) was to create a new Shared Service Provider. Easier said than done, an SSP change raises a very valid question: What data can be transferred between SSPs and what data cannot be moved? A short answer would be all the data that lies in the content database of each respective webapplication will move without problem and without manual interaction whereas all the...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/02/10/how-to-move-an-ssp.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3200007" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author></entry><entry><title>Office Server Search Service cannot be started because it does not exist.(Object reference not set to an instance of an object)</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/01/29/office-server-search-service-cannot-be-started-because-it-does-not-exist-object-reference-not-set-to-an-instance-of-an-object.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/01/29/office-server-search-service-cannot-be-started-because-it-does-not-exist-object-reference-not-set-to-an-instance-of-an-object.aspx</id><published>2009-01-29T21:46:00Z</published><updated>2009-01-29T21:46:00Z</updated><content type="html">Office Server Search Service cannot be started because it does not exist. One of the most simple problems I’ve seen lately is : Why can’t I start the Office Server Search Service in my MOSS install.I have the right key , the right CD and the latest fixes.I installed it and it is simply not there. I have checked the NT Services and the service is there but Even if I start it it does nothing What should I do? As you can probably guess, there’s nothing wrong with your PC or Cd or key, you simply did...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/01/29/office-server-search-service-cannot-be-started-because-it-does-not-exist-object-reference-not-set-to-an-instance-of-an-object.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3194479" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Administration" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Administration/default.aspx" /><category term="Install" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Install/default.aspx" /></entry><entry><title>Sharepoint Designer 2007 workflow error occurred on Update List Item when field is Person/Group</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2009/01/20/sharepoint-designer-2007-workflow-error-occurred-on-update-list-item-when-field-is-person-group.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2009/01/20/sharepoint-designer-2007-workflow-error-occurred-on-update-list-item-when-field-is-person-group.aspx</id><published>2009-01-20T21:58:00Z</published><updated>2009-01-20T21:58:00Z</updated><content type="html">This is concerning an error found encountered in Sharepoint Designer based workflows after installing the October Cumulative updates. The behavior you will encounter is the following: Create a simple list with two fields: Title (default) User type Person/Group Lookup Create a Sharepoint Designer Workflow attached to this list , set it to start manually. In step 1 add an Action : Update List Item (or set Field Value to) Update the User Field to a specific User ------------------------------ Create...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2009/01/20/sharepoint-designer-2007-workflow-error-occurred-on-update-list-item-when-field-is-person-group.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3187328" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Workflows" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Workflows/default.aspx" /><category term="Sharepoint Designer" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Sharepoint+Designer/default.aspx" /><category term="People" scheme="http://blogs.technet.com/victorbutuza/archive/tags/People/default.aspx" /><category term="How To" scheme="http://blogs.technet.com/victorbutuza/archive/tags/How+To/default.aspx" /></entry><entry><title>Type 'Microsoft.SharePoint.SPFieldUserValueCollection' in Assembly 'Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' is not marked as serializable. </title><link rel="alternate" type="text/html" href="http://blogs.technet.com/victorbutuza/archive/2008/12/29/type-microsoft-sharepoint-spfielduservaluecollection-in-assembly-microsoft-sharepoint-version-12-0-0-0-culture-neutral-publickeytoken-71e9bce111e9429c-is-not-marked-as-serializable.aspx" /><id>http://blogs.technet.com/victorbutuza/archive/2008/12/29/type-microsoft-sharepoint-spfielduservaluecollection-in-assembly-microsoft-sharepoint-version-12-0-0-0-culture-neutral-publickeytoken-71e9bce111e9429c-is-not-marked-as-serializable.aspx</id><published>2008-12-29T12:36:00Z</published><updated>2008-12-29T12:36:00Z</updated><content type="html">Among other things solved by the August Cumulative Updates, here is an issue which arosed after installing this patch. One of those issues is that if you modify a default list form (Editform.aspx, DisplayForm.aspx) using Sharepoint Designer 2007 and on this modified form you had an inpage user picker control, when you try to access this page in internet Explorer you will get the error from the title of this blogpost. Type 'Microsoft.SharePoint.SPFieldUserValueCollection' in Assembly 'Microsoft.SharePoint,...(&lt;a href="http://blogs.technet.com/victorbutuza/archive/2008/12/29/type-microsoft-sharepoint-spfielduservaluecollection-in-assembly-microsoft-sharepoint-version-12-0-0-0-culture-neutral-publickeytoken-71e9bce111e9429c-is-not-marked-as-serializable.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3174314" width="1" height="1"&gt;</content><author><name>Victor Butuza</name><uri>http://blogs.technet.com/members/Victor+Butuza.aspx</uri></author><category term="Sharepoint Designer" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Sharepoint+Designer/default.aspx" /><category term="Customization" scheme="http://blogs.technet.com/victorbutuza/archive/tags/Customization/default.aspx" /></entry></feed>