<?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>Action plans and problem solving</title><link>http://blogs.msdn.com/john_daskalakis/default.aspx</link><description>Hello, my name is John Daskalakis and in this blog I will be gathering all the action plans and troubleshooting steps I am using in my daily work. Plus the occasional errors I encounter and how to deal with them. Cheers, John</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Parameter gets converted in execution plan, when you explicitly define a different datatype for the parameter</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/11/13/9921920.aspx</link><pubDate>Fri, 13 Nov 2009 12:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9921920</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9921920.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9921920</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9921920</wfw:comment><description>Consider this scenario: You are trying to identify why a query like this is performing poorly: UPDATE table SET column1 = 0 WHERE table .column2 = @Parameter Where the @Parameter is explicitly specified as datatype VARCHAR(10) and the column2 is defined...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/11/13/9921920.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9921920" width="1" height="1"&gt;</description></item><item><title>Msg 7399 – OLE DB provider “MSDASQL” - The provider reported an unexpected catastrophic failure</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/11/13/9921916.aspx</link><pubDate>Fri, 13 Nov 2009 12:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9921916</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9921916.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9921916</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9921916</wfw:comment><description>Consider this scenario: - You have setup a linked server by using the MSDASQL provider - You are sometimes getting this error: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "MSDASQL" for linked server "XXXXXX" reported an error. The provider...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/11/13/9921916.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9921916" width="1" height="1"&gt;</description></item><item><title>No collector registered for scope: "SetupStateScope” - Message pump returning: 1602</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/10/30/9915165.aspx</link><pubDate>Fri, 30 Oct 2009 08:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9915165</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9915165.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9915165</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9915165</wfw:comment><description>Consider this scenario: - You have already installed a SQL Server 2000 instance on a Windows 2003 machine. - You also try to install a SQL Server 2005 instance on the same Windows 2003 machine. - Searching in the hotfix.log and summary.txt log files you...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/10/30/9915165.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9915165" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/sql+server+2005+setup+failure+error/default.aspx">sql server 2005 setup failure error</category></item><item><title>Request from IIS 5.0 arrives as anonymous login (‘null’) on SQL Server 2000</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/10/30/9915158.aspx</link><pubDate>Fri, 30 Oct 2009 07:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9915158</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9915158.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9915158</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9915158</wfw:comment><description>Recently we did troubleshoot an issue where requests from an IIS 5.0 site arrived as anonymous logins (‘null’) in SQL Server 2000. The ASP.NET application was using IIS 5.0 anonymous authentication for its users to send requests to SQL server 2000. The...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/10/30/9915158.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9915158" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/sql+kerberos+null+login/default.aspx">sql kerberos null login</category></item><item><title>The SQL server specified in SSIS service configuration is not present or is not available</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/10/15/9907652.aspx</link><pubDate>Thu, 15 Oct 2009 13:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9907652</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9907652.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9907652</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9907652</wfw:comment><description>Consider this scenario: - You have setup a SQL Server 2005 failover instance. - You then install SSIS 2005. - When you try to access the MSDB database from inside the Integration Services you get this message: The SQL server specified in SSIS service...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/10/15/9907652.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9907652" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/SSIS+_2600_lt_3B00_ServerName_2600_gt_3B00_/default.aspx">SSIS &amp;lt;ServerName&amp;gt;</category></item><item><title>Test connection failed because of an error in initializing provider (ORA-12154)</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/10/12/9906069.aspx</link><pubDate>Mon, 12 Oct 2009 10:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9906069</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9906069.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9906069</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9906069</wfw:comment><description>Consider this scenario: - You have migrated a DTS packages from SQL Server 2000 to SQL Server 2005. - The new SQL Server is installed on a Windows 64-bit machine. - This DTS package is connecting to an Oracle 10G database. - You get this error or something...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/10/12/9906069.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9906069" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/ORA-12154+DTS+SSIS/default.aspx">ORA-12154 DTS SSIS</category></item><item><title>Installing SSIS services after installing SQL Server database engine</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/10/12/9906046.aspx</link><pubDate>Mon, 12 Oct 2009 09:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9906046</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9906046.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9906046</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9906046</wfw:comment><description>Consider this scenario: - You have installed SQL Server 2005 and patched it with a Service Pack (in our case it was SP3). - Then you install SSIS on the same box, but do not patch it with any Service Pack. - Specifically you get this error when you try...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/10/12/9906046.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9906046" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/SSIS+7000+7009/default.aspx">SSIS 7000 7009</category></item><item><title>Error with event id of 17052 reports Access Violation</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/30/9853261.aspx</link><pubDate>Thu, 30 Jul 2009 15:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9853261</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9853261.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9853261</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9853261</wfw:comment><description>Now this is one was a thrilling issue! Consider the following scenario: You have a SQL 2000 SP4 server running on Windows 2000 SP4 server. After you install some updates, you get an error like this error reported in the event viewer: Event Id 17052 –...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/30/9853261.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9853261" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/17052+Access+Violation+ole32.dll/default.aspx">17052 Access Violation ole32.dll</category></item><item><title>Error 5042 (000013b2) when trying to failover an Exchange cluster group</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/28/9851026.aspx</link><pubDate>Tue, 28 Jul 2009 16:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9851026</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9851026.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9851026</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9851026</wfw:comment><description>Recently we came across an interesting issue. When trying to failover an exchange cluster group, the operation failed with error : "The cluster node was not found", Error ID:5042 (000013b2) This problem has two common causes: 1. One common cause is that...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/28/9851026.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9851026" width="1" height="1"&gt;</description></item><item><title>How to add an additional node to a SQL Server failover cluster</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/27/9849914.aspx</link><pubDate>Mon, 27 Jul 2009 14:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9849914</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9849914.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9849914</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9849914</wfw:comment><description>Sometimes a two-node cluster configuration is not enough for your SQL Server, as you may want to create new SQL instances, which will reside in a different node than the existing SQL instances. So in this case you may want to add a 3 rd or a 4 th node...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/27/9849914.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9849914" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/sql+additional+node+cluster+instance/default.aspx">sql additional node cluster instance</category></item><item><title>URL Rewrite Module may not work as expected when redirecting to file://</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/08/9823614.aspx</link><pubDate>Wed, 08 Jul 2009 11:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9823614</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9823614.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9823614</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9823614</wfw:comment><description>The URL Rewrite Module is part of the Microsoft Application Request Routing for IIS 7: Microsoft Application Request Routing Version 1 for IIS 7 (x86) http://www.iis.net/downloads/default.aspx?tabid=34&amp;amp;i=1709&amp;amp;g=6 Maybe you have been trying to...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/08/9823614.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9823614" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/iis+rewrite+module+file/default.aspx">iis rewrite module file</category></item><item><title>Recovery of database 'XXXXXXXXX' (X) is X% complete</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819535.aspx</link><pubDate>Mon, 06 Jul 2009 14:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9819535</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9819535.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9819535</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9819535</wfw:comment><description>Recently I received a question regarding SQL Server database Analysis and Recovery. It seems that a pretty huge database got into recovering mode, due to a huge transaction that was taking place, when suddenly the disk ran out of space and the transaction...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819535.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9819535" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/recovery+complete+phase+sql+database/default.aspx">recovery complete phase sql database</category></item><item><title>How to identify the version of Sharepoint you are using</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819458.aspx</link><pubDate>Mon, 06 Jul 2009 13:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9819458</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9819458.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9819458</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9819458</wfw:comment><description>At first glance, this seems to be a very simple question, but after a long research in the internet I could not find a clear answer!!! Thankfully, one of my colleagues had the answer and shared it with me :) Strange as it may seem, there are actually...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819458.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9819458" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/MOSS+SPS+Version+identify/default.aspx">MOSS SPS Version identify</category></item><item><title>How to allow a user to view a file over a network share, but at the same time stop him from copying this file?</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819237.aspx</link><pubDate>Mon, 06 Jul 2009 12:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9819237</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9819237.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9819237</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9819237</wfw:comment><description>Recently we had a strange support request that had never occurred to me before: “Is there any combination of NTFS and share permissions that would allow a user to view a video file over a network share, but at the same time stop this user from copying...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819237.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9819237" width="1" height="1"&gt;</description></item><item><title>How to export events from SQL Server 2005 and send them to the Windows Event Viewer Log</title><link>http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819151.aspx</link><pubDate>Mon, 06 Jul 2009 11:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9819151</guid><dc:creator>John Daskalakis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/john_daskalakis/comments/9819151.aspx</comments><wfw:commentRss>http://blogs.msdn.com/john_daskalakis/commentrss.aspx?PostID=9819151</wfw:commentRss><wfw:comment>http://blogs.msdn.com/john_daskalakis/rsscomments.aspx?PostID=9819151</wfw:comment><description>Recently I was asked how to export events from a SQL Server 2005 and send them to the Event Viewer Log, so that the SCOM administrator could see these events. As I found out, there existed no “out of the box” solution for SQL Server 2005. The workaround...(&lt;a href="http://blogs.msdn.com/john_daskalakis/archive/2009/07/06/9819151.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9819151" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/john_daskalakis/archive/tags/event+viewer+profiler+SCOM+SQL+2005+2007/default.aspx">event viewer profiler SCOM SQL 2005 2007</category></item></channel></rss>