<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:copyright="http://blogs.law.harvard.edu/tech/rss" xmlns:image="http://purl.org/rss/1.0/modules/image/">
    <channel>
        <title>Good, Bad and the Ugly</title>
        <link>http://www.darrinbishop.com/blog/category/5.aspx</link>
        <description>Posts pointing out the good the bad and the ugly of SharePoint</description>
        <language>en-US</language>
        <copyright>Darrin Bishop</copyright>
        <managingEditor>dbishop@darrinbishop.com</managingEditor>
        <generator>Subtext Version 1.9.4.78</generator>
        <item>
            <title>Infrastructure Update Issues</title>
            <link>http://darrinbishop.com/blog/archive/2008/07/24/InfrastuctureUpdateIssues.aspx</link>
            <description>&lt;p&gt;&lt;font face="Tahoma" size="3"&gt;Microsoft's Infrastructure Updates have been out for about a week now. There does seem to be some potential big issues with the updates breaking third party products. Microsoft also has posted a KB article on Alternate Access Mappings issues associated with the Infrastructure updates.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Tahoma" size="3"&gt;Here are a few key posts you should be looking at if you have installed or are considering installing  the Infrastructure Updates:&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://blogs.msdn.com/dwinter/archive/2008/07/23/aam-issue-with-infrastructure-update.aspx"&gt;&lt;font face="Tahoma" size="3"&gt;AAM issue with Infrastructure Update&lt;/font&gt;&lt;/a&gt;&lt;font face="Tahoma" size="3"&gt; &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Tahoma" size="3"&gt;&lt;a target="_blank" href="http://support.microsoft.com/kb/951695"&gt;Description of the Infrastructure Update for Windows SharePoint Services 3.0: July 15, 2008&lt;/a&gt;&lt;/font&gt;&lt;/p&gt;
&lt;font face="Arial"&gt;&lt;a target="_blank" href="http://daniellarson.spaces.live.com/blog/cns!D3543C5837291E93!2966.entry"&gt;&lt;font face="Tahoma" size="3"&gt;KB: When is the SPContext.Current available ? (SharePoint dev)&lt;/font&gt;&lt;/a&gt; &lt;/font&gt;
&lt;p&gt; &lt;/p&gt;&lt;img src="http://darrinbishop.com/blog/aggbug/108.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Darrin Bishop</dc:creator>
            <guid>http://darrinbishop.com/blog/archive/2008/07/24/InfrastuctureUpdateIssues.aspx</guid>
            <pubDate>Thu, 24 Jul 2008 14:59:13 GMT</pubDate>
            <comments>http://darrinbishop.com/blog/archive/2008/07/24/InfrastuctureUpdateIssues.aspx#feedback</comments>
            <wfw:commentRss>http://darrinbishop.com/blog/comments/commentRss/108.aspx</wfw:commentRss>
            <trackback:ping>http://darrinbishop.com/blog/services/trackbacks/108.aspx</trackback:ping>
        </item>
        <item>
            <title>SPSiteDataQuery - Greater Than 10 Lists Issue</title>
            <link>http://darrinbishop.com/blog/archive/2007/07/24/68.aspx</link>
            <description>&lt;p&gt;&lt;font face="Arial"&gt;&lt;font face="Arial"&gt;The Good, Bad and the Ugly  - well Ugly at least...&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Arial"&gt;SPSiteDataQuery is used to query across multiple lists/libraries within  a site collection.  Apparently there is a confirmed issue when you query over 10 or more lists/libraries where columns and column order are not the same.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Arial"&gt;Read Steve's post on this issue at: &lt;/font&gt;&lt;font face="Arial"&gt;&lt;a target="_blank" href="http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery-limited-to-10-document-libraries-or-lists.aspx"&gt;SPSiteDataQuery limited to 10 document libraries or lists &lt;/a&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;&lt;img src="http://darrinbishop.com/blog/aggbug/68.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Darrin Bishop</dc:creator>
            <guid>http://darrinbishop.com/blog/archive/2007/07/24/68.aspx</guid>
            <pubDate>Tue, 24 Jul 2007 19:19:29 GMT</pubDate>
            <comments>http://darrinbishop.com/blog/archive/2007/07/24/68.aspx#feedback</comments>
            <wfw:commentRss>http://darrinbishop.com/blog/comments/commentRss/68.aspx</wfw:commentRss>
            <trackback:ping>http://darrinbishop.com/blog/services/trackbacks/68.aspx</trackback:ping>
        </item>
        <item>
            <title>Office 2007 Trial - ¿Usted habla español?</title>
            <link>http://darrinbishop.com/blog/archive/2007/05/04/64.aspx</link>
            <description>&lt;p&gt;&lt;font face="Arial"&gt;&lt;strong&gt;Editor's Note: The Spanish-only download issue noted in this post appears to been addressed and is no longer an issue.&lt;/strong&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Arial"&gt;Want to try Microsoft Office 2007 products? Microsoft has provided 60 day trial downloads for many if not all of their Office products. Just head to &lt;a target="_blank" href="http://office.microsoft.com/en-us/products/HA101741481033.aspx"&gt;Microsoft Office Online&lt;/a&gt; site and select the trial product, enter some information and download.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Arial"&gt;Oh, just a little note - it appears that there is an issue where only the Spanish version of the product will download ( I have only tried Office 2007 Professional).  After hitting the newsgroups it appears I am not the only one with a language barrier issue.  I am quite sure that my desktop Vista machine has never been native Spanish and the address for the download page displays with a culture of "en-US". So far I have not been able to download a copy in a language that I can read.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font face="Arial"&gt;If anyone has any great suggestions to find the Office 2007 Trials in English please let me know.&lt;br /&gt;
&lt;/font&gt;&lt;/p&gt;&lt;img src="http://darrinbishop.com/blog/aggbug/64.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Darrin Bishop</dc:creator>
            <guid>http://darrinbishop.com/blog/archive/2007/05/04/64.aspx</guid>
            <pubDate>Fri, 04 May 2007 17:21:56 GMT</pubDate>
            <comments>http://darrinbishop.com/blog/archive/2007/05/04/64.aspx#feedback</comments>
            <slash:comments>1</slash:comments>
            <wfw:commentRss>http://darrinbishop.com/blog/comments/commentRss/64.aspx</wfw:commentRss>
            <trackback:ping>http://darrinbishop.com/blog/services/trackbacks/64.aspx</trackback:ping>
        </item>
        <item>
            <title>Daylight Savings Time Strikes Back!</title>
            <link>http://darrinbishop.com/blog/archive/2007/04/08/52.aspx</link>
            <description>So this weekI am researching SharePoint upgrades.  More specifically I am interested in upgrading customized sites in WSS 2.0 and SPS 2003 to WSS 3.0 and MOSS sites using the Gradual Upgrade approach.  To do this I chose an iterative route. Start with a simple, small , un-customized team site in WSS 2.0 and upgrade to WSS v3 team site template.  Well it was simple until DST strikes!&lt;br /&gt;&lt;br /&gt;The VPC was patched and updated for DST.  For some reason, the same simple, small, un-customized team site upgrade which took approximately  ten minutes to finish would not finish.  Updating a site collection using the gradual upgrade approach creates timer jobs that are set for a one-time  run.  Checking the various status pages for the upgrade as well as the timer jobs show that the upgrade is in process but no upgrade job actually running.  Apparently the upgrade has hung up. In a fit of frustration I let it sit to see if indeed it was running behind the scenes and sure enough - it completed an hour later. So what was a 10 min upgrade now is an hour and 10 minute upgrade. My plan of an iterative approach to building an upgrade solution for a customized site is not looking good. At this rate I will be lucky to get in more than 5 upgrade attempts in an 8 hour day.&lt;br /&gt;&lt;br /&gt;So I restarted with a clean VPC, this time changed the diagnostic settings  for upgrade to capture as much as possible and restarted a new simple upgrade. Again it takes over an hour to complete but this time the logs showed the story.  The upgrade was not taking its sweet time to complete. The associated timer jobs did not even start until an hour later. Once the jobs started it was a 10 minute upgrade. &lt;br /&gt;&lt;br /&gt;So now I am thinking DST issue - processes that should be running "immediately"  are running an hour later.  To prove that it was not my imagination I started again with a clean VPC,  rolled back the server clock ( disabling the automatic time update service)  to March 1 and started another upgrade.  This time the jobs started processing within a minute and the complete upgrade was accomplished in approximately 10 minutes.&lt;br /&gt;&lt;br /&gt;So now I double check that I indeed had all the required DST updates on the VPC, which it does. During a web search the final piece of the puzzle falls into place, a KB Article titled "&lt;a href="http://support.microsoft.com/kb/932563" target="_blank"&gt;One-time timer jobs will not run until one hour after the jobs were created in SharePoint Server 2007&lt;/a&gt; ".&lt;br /&gt;&lt;br /&gt;Basically there appears to be an issue with "One-time" jobs and Daylight Savings Time The current "work around" is to either  schedule your jobs an hour earlier to compensate for the issue or change to a Time Zone not affected by the DST if you happen to be lucky enough to live in an area that has a similar Time Zone where DST does not apply . What makes this issue so aggravating is that the job time for the upgrade is set by the system. There appears to be no simple way to change the start time of an upgrade job to an hour earlier.  Most of us also do not live in a location that has a similar time zone that does not utilize DST. So effectively there is no workaround for this particular upgrade issue. Hopefully the issue will resolve itself in three weeks which is when we would normally change to DST. Of course for those that wrote automated processes and compensated by scheduling the start time one hour early will have hopefully paramterized the start time!&lt;br /&gt;&lt;br /&gt;So today  I will say I ran into:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The &lt;b&gt;Bad &lt;/b&gt;with what appears to be a Daylight Savings Time bug &lt;/li&gt;&lt;li&gt;The &lt;b&gt;Ugly &lt;/b&gt;for the current proposed fix - which appears to be none in my particular case. &lt;/li&gt;&lt;li&gt;The &lt;b&gt;Good &lt;/b&gt;for the Diagnostics settings that helped me localize the issue.  &lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;I guess this can all change if we see a hot fix or a service pack update.&lt;img src="http://darrinbishop.com/blog/aggbug/52.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Darrin Bishop</dc:creator>
            <guid>http://darrinbishop.com/blog/archive/2007/04/08/52.aspx</guid>
            <pubDate>Sun, 08 Apr 2007 18:30:12 GMT</pubDate>
            <comments>http://darrinbishop.com/blog/archive/2007/04/08/52.aspx#feedback</comments>
            <wfw:commentRss>http://darrinbishop.com/blog/comments/commentRss/52.aspx</wfw:commentRss>
            <trackback:ping>http://darrinbishop.com/blog/services/trackbacks/52.aspx</trackback:ping>
        </item>
        <item>
            <title>SharePoint - The Good, Bad and the Ugly</title>
            <link>http://darrinbishop.com/blog/archive/2007/04/08/51.aspx</link>
            <description>So where did I go? Well I have been busy with the newest version of &lt;a href="http://www.knowledgelake.com/imaging/default.asp" target="_blank"&gt;KnowledgeLake Imaging&lt;/a&gt;,  getting ready for the &lt;a href="http://www.devconnections.com/shows/SP2007SP/default.asp?s=91" target="_blank"&gt;spring conference season&lt;/a&gt; and generally working with MOSS 2007 and WSS 3.0.&lt;br /&gt;&lt;br /&gt;So what's SharePoint - The Good, Bad and the Ugly? Well I am sitting at the workbench testing and researching WSS 2.0 -&amp;gt; WSS 3.0 upgrades. Pretty simple actually - a brand new WSS 2.0 implementation with a single Team Site. The goal is to upgrade to WSS 3.0 using the gradual upgrade process.  For some strange reason it now takes me over an hour to do a "small" upgrade.  I distinctly remember this previous test lasting only about 15 minutes before. As I am sitting here trying to debug this I realize I am looking at the Bad or maybe the Ugly.&lt;br /&gt;&lt;br /&gt;So the Good, Bad and the Ugly is the new category for the blog where I will point out The Good, Bad and the Ugly.&lt;img src="http://darrinbishop.com/blog/aggbug/51.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Darrin Bishop</dc:creator>
            <guid>http://darrinbishop.com/blog/archive/2007/04/08/51.aspx</guid>
            <pubDate>Sun, 08 Apr 2007 18:29:20 GMT</pubDate>
            <comments>http://darrinbishop.com/blog/archive/2007/04/08/51.aspx#feedback</comments>
            <wfw:commentRss>http://darrinbishop.com/blog/comments/commentRss/51.aspx</wfw:commentRss>
            <trackback:ping>http://darrinbishop.com/blog/services/trackbacks/51.aspx</trackback:ping>
        </item>
    </channel>
</rss>