<?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>Common native mode client -&amp;amp;gt; MP error messages and what to do about them</title><link>http://blogs.msdn.com/ameltzer/archive/2008/04/14/common-native-mode-client-mp-error-messages-and-what-to-do-about-them.aspx</link><description>Often times, basic communication issues can happen between the client and MP and they can be hard to decipher from logging alone. The error class I'll concentrate on here are the "WINHTTP_STATUS_CALLBACK" errors that may appear in the ccmexec.log on the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Microsoft news and tips &amp;raquo; Common native mode client -&amp;gt; MP error messages and what to do about them</title><link>http://blogs.msdn.com/ameltzer/archive/2008/04/14/common-native-mode-client-mp-error-messages-and-what-to-do-about-them.aspx#8393773</link><pubDate>Mon, 14 Apr 2008 20:59:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8393773</guid><dc:creator>Microsoft news and tips &amp;raquo; Common native mode client -&amp;gt; MP error messages and what to do about them</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoftnews.askpcdoc.com/?p=2322"&gt;http://microsoftnews.askpcdoc.com/?p=2322&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>