<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Sridhar's Blog : Troubleshooting Tips</title><link>http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx</link><description>Tags: Troubleshooting Tips</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>What happened to my My Links Web Part?</title><link>http://blogs.msdn.com/sridhara/archive/2008/06/27/what-happened-to-my-my-links-web-part.aspx</link><pubDate>Fri, 27 Jun 2008 10:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8660610</guid><dc:creator>sridhara</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/sridhara/comments/8660610.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sridhara/commentrss.aspx?PostID=8660610</wfw:commentRss><wfw:comment>http://blogs.msdn.com/sridhara/rsscomments.aspx?PostID=8660610</wfw:comment><description>Well, did you add a link like "file://C:/folder1/folder2"? In one customer's environment this was the exact issue. A user added some file system link like the above and ended up with the following symptoms: 1. The user couldn't add the "My Links" web...(&lt;a href="http://blogs.msdn.com/sridhara/archive/2008/06/27/what-happened-to-my-my-links-web-part.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8660610" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sridhara/archive/tags/MOSS+2007/default.aspx">MOSS 2007</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Code+Samples/default.aspx">Code Samples</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx">Troubleshooting Tips</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/MySite/default.aspx">MySite</category></item><item><title>Indexing MSCMS 2001 using MOSS 2007 indexer?</title><link>http://blogs.msdn.com/sridhara/archive/2008/06/25/indexing-mscms-2001-using-moss-2007-indexer.aspx</link><pubDate>Thu, 26 Jun 2008 00:23:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8653400</guid><dc:creator>sridhara</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sridhara/comments/8653400.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sridhara/commentrss.aspx?PostID=8653400</wfw:commentRss><wfw:comment>http://blogs.msdn.com/sridhara/rsscomments.aspx?PostID=8653400</wfw:comment><description>This might be a cake-walk for most of you, but I got delayed a bit to get MSCMS 2001 contents indexed using MOSS 2007. Basically what I saw after I setup a content source and started a full crawl was the below warning: The specified address was excluded...(&lt;a href="http://blogs.msdn.com/sridhara/archive/2008/06/25/indexing-mscms-2001-using-moss-2007-indexer.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8653400" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sridhara/archive/tags/MOSS+2007/default.aspx">MOSS 2007</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Content+Management+Server/default.aspx">Content Management Server</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx">Troubleshooting Tips</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/SharePoint+Search_2F00_Indexing/default.aspx">SharePoint Search/Indexing</category></item><item><title>"The site is not assigned to an indexer" error in SharePoint custom search</title><link>http://blogs.msdn.com/sridhara/archive/2008/06/21/the-site-is-not-assigned-to-an-indexer-error-in-sharepoint-custom-search.aspx</link><pubDate>Sat, 21 Jun 2008 17:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8632002</guid><dc:creator>sridhara</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sridhara/comments/8632002.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sridhara/commentrss.aspx?PostID=8632002</wfw:commentRss><wfw:comment>http://blogs.msdn.com/sridhara/rsscomments.aspx?PostID=8632002</wfw:comment><description>Strangely enough! We'll not see this issue with an OOTB search. It is seen only when we use search APIs or web service and perform a custom search. Apparently, when we use Microsoft.Office.Server.Search, the content database also gets indexed and this...(&lt;a href="http://blogs.msdn.com/sridhara/archive/2008/06/21/the-site-is-not-assigned-to-an-indexer-error-in-sharepoint-custom-search.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8632002" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sridhara/archive/tags/MOSS+2007/default.aspx">MOSS 2007</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/WSS+3.0/default.aspx">WSS 3.0</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx">Troubleshooting Tips</category></item><item><title>"The security validation for this page is invalid" error when updating objects through SharePoint object model</title><link>http://blogs.msdn.com/sridhara/archive/2008/06/21/the-security-validation-for-this-page-is-invalid-error-when-updating-objects-through-sharepoint-object-model.aspx</link><pubDate>Sat, 21 Jun 2008 16:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8631754</guid><dc:creator>sridhara</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/sridhara/comments/8631754.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sridhara/commentrss.aspx?PostID=8631754</wfw:commentRss><wfw:comment>http://blogs.msdn.com/sridhara/rsscomments.aspx?PostID=8631754</wfw:comment><description>This error is often encountered when SharePoint OM is used to update site/web/list objects from within a web context. Some thing so basic as the code below could fail: using ( SPSite site = new SPSite ( "http://moss" )) { using ( SPWeb web = site.OpenWeb())...(&lt;a href="http://blogs.msdn.com/sridhara/archive/2008/06/21/the-security-validation-for-this-page-is-invalid-error-when-updating-objects-through-sharepoint-object-model.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8631754" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sridhara/archive/tags/SPS+2003/default.aspx">SPS 2003</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/MOSS+2007/default.aspx">MOSS 2007</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Code+Samples/default.aspx">Code Samples</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/WSS+2.0/default.aspx">WSS 2.0</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/WSS+3.0/default.aspx">WSS 3.0</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Coding+tips/default.aspx">Coding tips</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx">Troubleshooting Tips</category></item><item><title>Database Schema compatibility error in FBA</title><link>http://blogs.msdn.com/sridhara/archive/2008/06/21/database-schema-compatibility-error-in-fba.aspx</link><pubDate>Sat, 21 Jun 2008 08:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8629425</guid><dc:creator>sridhara</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sridhara/comments/8629425.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sridhara/commentrss.aspx?PostID=8629425</wfw:commentRss><wfw:comment>http://blogs.msdn.com/sridhara/rsscomments.aspx?PostID=8629425</wfw:comment><description>This is an interesting issue I came across recently and it was nice to know things that I thought would be hardly a matter to be considered. Well, the gist of the issue is very simple. When using default providers (AspNetSqlMembershipProvider &amp;amp; AspNetSqlRoleProvider)...(&lt;a href="http://blogs.msdn.com/sridhara/archive/2008/06/21/database-schema-compatibility-error-in-fba.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8629425" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sridhara/archive/tags/MOSS+2007/default.aspx">MOSS 2007</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/WSS+3.0/default.aspx">WSS 3.0</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/FBA/default.aspx">FBA</category><category domain="http://blogs.msdn.com/sridhara/archive/tags/Troubleshooting+Tips/default.aspx">Troubleshooting Tips</category></item></channel></rss>