<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-3569767159965585285</id><updated>2012-02-16T02:37:02.892-08:00</updated><title type='text'>Leveraging Microsoft SharePoint Server</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>5</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3569767159965585285.post-1827376565477768668</id><published>2008-05-07T07:40:00.000-07:00</published><updated>2008-05-07T19:00:16.229-07:00</updated><title type='text'>Memory Corrupt Error Search Settings Page</title><content type='html'>Recently, a customer indexer server suffered a crash and had to be rebuilt. I went to SSP admin settings page and changed the indexer and all went well. However, when i went to the central admin site i received "Attempted to read or write to protected memory". I did alot of research on the problem but did not find anyone that had the problem on the search settings page. Mostly, alot of memory errors where related to a hotfix for .net but not for browsing to a particular page. Because it was production and time was of the essence, i started the crawl using stsadm utility.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Update: I could browse to the pages underneath search settings, for instance the _layouts/listcontentsources.aspx so i sort of left the problem alone until i could come up with a good solution (it wasn't affecting anything). However, after installing SP1 for sharePoint, I am happy to report the problem went away. I didn't see this as a reported fix in the issues list but it must be an undocumented fix.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3569767159965585285-1827376565477768668?l=dominicbrigham.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/1827376565477768668/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3569767159965585285&amp;postID=1827376565477768668' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/1827376565477768668'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/1827376565477768668'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/2008/05/memory-corrupt-error-search-settings.html' title='Memory Corrupt Error Search Settings Page'/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3569767159965585285.post-3871036990059318271</id><published>2008-04-16T18:43:00.000-07:00</published><updated>2008-04-16T19:57:20.629-07:00</updated><title type='text'>Load Balancing and SharePoint</title><content type='html'>Recently, I across a problem with my sites at a c&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;lient's site&lt;/span&gt;.  A load &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;balancer&lt;/span&gt; was added into the farm on two &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;FE W's&lt;/span&gt;.  The &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_3"&gt;my site&lt;/span&gt; and portal site were separate web applications but shared different host headers on different ports.  The portal (&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;kerberos&lt;/span&gt; enabled) work perfectly.  However, my sites returned page cannot be found error.&lt;br /&gt;&lt;br /&gt;I resolved the error by creating a new &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;ip&lt;/span&gt; for &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;mysites&lt;/span&gt; in &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;dns&lt;/span&gt; and then adding that new &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;ip&lt;/span&gt; to the load &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;balancer&lt;/span&gt; with a new host header.  In addition, the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;iis&lt;/span&gt; website had to be deleted and &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_11"&gt;re extended&lt;/span&gt; using the new host header.&lt;br /&gt;&lt;br /&gt;Although i am still trying to figure out why the hardware load &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;balancer&lt;/span&gt; was dropping the port, it is always best practice to use different host headers for different web applications for various reason including &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;kerberos&lt;/span&gt; &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_14"&gt;authentication&lt;/span&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3569767159965585285-3871036990059318271?l=dominicbrigham.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/3871036990059318271/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3569767159965585285&amp;postID=3871036990059318271' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3871036990059318271'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3871036990059318271'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/2008/04/load-balancing-and-sharepoint.html' title='Load Balancing and SharePoint'/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3569767159965585285.post-3653952293179468227</id><published>2008-04-08T18:16:00.000-07:00</published><updated>2008-04-08T18:39:43.733-07:00</updated><title type='text'>Weird Permission Errors Inside of Navigation Settings</title><content type='html'>I was on a clients S&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;harePoint&lt;/span&gt; farm and few days and a developer sent me an email saying he was getting prompted for credentials on the site navigation settings page on a non root &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;sub site&lt;/span&gt;.  Turns out, when you went to any site navigation settings page of any new or existing site collection, you were prompted for each picture and links inside of the navigation box.  After some playing around with various &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;settings&lt;/span&gt; inside of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;SharePoint&lt;/span&gt;, I decided it had to be something wrong outside of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;SharePoint&lt;/span&gt; Settings.&lt;br /&gt;&lt;br /&gt;The resolution ended up to redo the directory security of the web application inside of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;IIS&lt;/span&gt; manager and apply it down the tree to each one of your front end web servers.  In our case, we had the web application with &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;Integrated&lt;/span&gt; Windows &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_7"&gt;Authentication&lt;/span&gt; with no &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_8"&gt;anonymous&lt;/span&gt; access.  Once I changed this setting, everything worked no problem and users where not prompted for credentials.  Also, in our case, we could always get to the site navigation setting page in the root site collection.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3569767159965585285-3653952293179468227?l=dominicbrigham.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/3653952293179468227/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3569767159965585285&amp;postID=3653952293179468227' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3653952293179468227'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3653952293179468227'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/2008/04/weird-permission-errors-inside-of.html' title='Weird Permission Errors Inside of Navigation Settings'/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3569767159965585285.post-3683377314401713434</id><published>2008-03-31T06:26:00.000-07:00</published><updated>2008-03-31T06:36:20.477-07:00</updated><title type='text'>Kerberos Configuration for RSS feeds</title><content type='html'>When testing the default rss viewer on Moss, remember some key things.  First, if you have anonoymous access turned on, the user will see the rss feed regardless whether coming in NTLM or Kerberos.  For kerberos feeds to work correctly with anonoymous access turned off, the user must come in as kerberos and have permission to the feed.  If the user does not have permission to the feed, they will receive "the user does not support authenicated feeds" which is also the same error a user will receive if they come into the SharePoint site using NTLM. &lt;br /&gt;&lt;br /&gt;One of the big gotchas is that if you a behind a proxy server, you will need to modify the web.config file in order to fill in the proxy server name.  Otherwise, the rss won't work becase the credentials are not being passed for the user.&lt;br /&gt;&lt;br /&gt;Great links for setting up Kerberos:&lt;br /&gt;&lt;a href="http://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx"&gt;http://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://blogs.msdn.com/martinkearn/archive/2007/04/27/configuring-kerberos-for-sharepoint-2007-part-2-excel-services-and-sql-analysis-services.aspx"&gt;http://blogs.msdn.com/martinkearn/archive/2007/04/27/configuring-kerberos-for-sharepoint-2007-part-2-excel-services-and-sql-analysis-services.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/cc263449.aspx"&gt;http://technet.microsoft.com/en-us/library/cc263449.aspx&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3569767159965585285-3683377314401713434?l=dominicbrigham.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/3683377314401713434/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3569767159965585285&amp;postID=3683377314401713434' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3683377314401713434'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/3683377314401713434'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/2008/03/kerberos-configuration-for-rss-feeds.html' title='Kerberos Configuration for RSS feeds'/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3569767159965585285.post-8477943902147613415</id><published>2008-03-13T18:39:00.001-07:00</published><updated>2008-03-13T18:40:18.272-07:00</updated><title type='text'></title><content type='html'>Welcome to my blogging site!  Much information to come on SharePoint Server.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3569767159965585285-8477943902147613415?l=dominicbrigham.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dominicbrigham.blogspot.com/feeds/8477943902147613415/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3569767159965585285&amp;postID=8477943902147613415' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/8477943902147613415'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3569767159965585285/posts/default/8477943902147613415'/><link rel='alternate' type='text/html' href='http://dominicbrigham.blogspot.com/2008/03/welcome-to-my-blogging-site-much.html' title=''/><author><name>Dominic B</name><uri>http://www.blogger.com/profile/08635753042843531790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
