<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Those 8197 Free/Busy Errors</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx</link><description>Do 8197 free/busy errors appear in your application log every 25 minutes? The actual text states: Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8197 User: N/A Computer: servername Description: Error initializing</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Those 8197 Free/Busy Errors</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408400</link><pubDate>Fri, 29 Jul 2005 21:51:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408400</guid><dc:creator>Pyr0</dc:creator><description>Impressive. Now I finally understand why I was getting this. The servers were in a site with DCs from the Root and we had a trust issue.</description></item><item><title>Windows, XP, Exchange, ISA, SMS, IE, Security, LCS, Misc.</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408480</link><pubDate>Mon, 01 Aug 2005 21:03:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408480</guid><dc:creator>Windows Server Clustering </dc:creator><description /></item><item><title>re: Those 8197 Free/Busy Errors</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408515</link><pubDate>Tue, 02 Aug 2005 09:56:55 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408515</guid><dc:creator>jasperk</dc:creator><description>Yes, pyr0 in the general connectivity troubleshooting between the Exchange server and the GC I should have explicitly mentioned trust. This is another common cause.</description></item><item><title>re: Those 8197 Free/Busy Errors</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408520</link><pubDate>Tue, 02 Aug 2005 11:01:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408520</guid><dc:creator>Pat</dc:creator><description>so you both mean, that to move from step one to step 2 you have to do network comminication testing and this includes, that there ist a trust form the exchange to all GC Servers. right? So that was the problem with my organisation. i resoved it by taking the GC role from the root DC&amp;#180;s away. &lt;br&gt;&lt;br&gt;another question is if there is a way to uninstall outlook on the exchange server?&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Those 8197 Free/Busy Errors</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408667</link><pubDate>Thu, 04 Aug 2005 22:56:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408667</guid><dc:creator>jasperk</dc:creator><description>Pat, you should make sure there is trust between the Exchange server and the GC listed in that registry key if you intend the Exchange server to talk to that GC. If you did not intend the Exchange server to talk to that GC (and therefore there is no trust) you may need to re-architect your active directory topology to rule out the possibility of ever having it contacted by the Exchange server. Hope that makes it clearer.</description></item><item><title>Weekend reading</title><link>http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx#408701</link><pubDate>Fri, 05 Aug 2005 13:13:03 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:408701</guid><dc:creator>subject: exchange</dc:creator><description /></item></channel></rss>