<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PeachFuzz &#187; Errors &amp; Alerts</title>
	<atom:link href="http://tristardatasystems.com/Peachtree/blog/index.php/category/errors-alerts/feed/" rel="self" type="application/rss+xml" />
	<link>http://tristardatasystems.com/Peachtree/blog</link>
	<description>Fruitful commentary on Peachtree Accounting from TriStar Data Systems</description>
	<lastBuildDate>Mon, 23 Jan 2012 21:46:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Peachtree Email Writer dilemma solved</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2011/09/peachtree-email-writer-dilemma-solved/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2011/09/peachtree-email-writer-dilemma-solved/#comments</comments>
		<pubDate>Fri, 30 Sep 2011 19:09:09 +0000</pubDate>
		<dc:creator>Jack Schaller</dc:creator>
				<category><![CDATA[Errors & Alerts]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=141</guid>
		<description><![CDATA[We may have stumbled upon a solution to a really obscure Peachtree problem that has plagued more than one of our clients. Thanks – and kudos – to Anthony Licate of Spidernet Technical Consulting for working through this one and coming up with a definitive solution. Terminal Services has become a very popular vehicle for [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Calibri; font-size: small;">We may have stumbled upon a solution to a really obscure Peachtree problem that has plagued more than one of our clients. Thanks – and kudos – to Anthony Licate of </span><a href="http://www.spidernetconsulting.com/"><span style="font-family: Calibri; font-size: small;">Spidernet Technical Consulting</span></a><span style="font-family: Calibri; font-size: small;"> for working through this one and coming up with a definitive solution.</span></p>
<p><span style="font-family: Calibri; font-size: small;">Terminal Services has become a very popular vehicle for configuring remote computing environments, and most of the software applications we support at TriStar explicitly support Terminal Services. Peachtree is no exception to this. However, there are some very subtle but significant configuration settings which can seriously impact Peachtree’s performance in the terminal services environment. Emailing documents (via the Peachtree PDF Writer) is one of those areas.</span></p>
<p><span style="font-family: Calibri; font-size: small;">Our client was consistently unable to email invoices through Peachtree when operating on the Terminal Server. The client was also experiencing periodic difficulties printing to her local printer when attempting to print to it through Terminal Services. Needless to say, this can get to be <strong>very</strong> annoying very quickly, and erode one’s confidence in the technology which allegedly facilitates this kind of remote access.</span></p>
<p><span style="font-family: Calibri; font-size: small;">After <strong>much</strong> troubleshooting, we discovered that a somewhat obscure “group policy” setting in Windows Small Business Server 2008 was automatically “redirecting” any document sent to the My Documents folder on the Terminal Server over to the file server, which <strong>then</strong> ran afoul of the registry settings, or permissions, for Peachtree when attempting to email (or in some cases print) a Peachtree document.</span></p>
<p><span style="font-family: Calibri; font-size: small;">Having diagnosed it, the fix was simple: turn off the group policy setting for this within Small Business Server. Voila! All Peachtree documents can now be emailed, and the sporadic printing issues have all disappeared.</span></p>
<p><span style="font-family: Calibri; font-size: small;">If you are running on Small Business Server 2008 (or any other version of Server 2008 for that matter) check your “Group Policy” settings to make sure that you are not also an unwitting victim of “My Documents Redirection.” </span></p>
<p><span style="font-family: Calibri; font-size: small;">Emailing invoices out of Peachtree is really very easy and convenient – but only if all of the technology is harnessed to work together.</span></p>
<p><em><span style="font-family: Calibri; font-size: small;">Please let us know if you have also experienced emailing and printing issues in Terminal Server. We may be able to help you fix it.</span></em></p>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2011/09/peachtree-email-writer-dilemma-solved/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bad Info &#8211; Timeslips DOES link OK now</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-does-link/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-does-link/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 19:58:38 +0000</pubDate>
		<dc:creator>tristar</dc:creator>
				<category><![CDATA[Add-Ons]]></category>
		<category><![CDATA[Errors & Alerts]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=54</guid>
		<description><![CDATA[In one of the shortest lived posts we have ever made, we need to now retract our earlier statement about the Peachtree 2010 link with Timeslips being &#8220;non-functional.&#8221; Don&#8217;t know why it would not work yesterday, and don&#8217;t know why Sage Tech Support confirmed for us it would not work, but this afternoon we were [...]]]></description>
			<content:encoded><![CDATA[<p>In one of the shortest lived posts we have ever made, we need to now retract our earlier statement about the Peachtree 2010 link with Timeslips being &#8220;non-functional.&#8221; Don&#8217;t know why it would not work yesterday, and don&#8217;t know why Sage Tech Support confirmed for us it would not work, but this afternoon we were able to configure the integration, run a transfer register, and verify that the Timeslips transactions match up in Peachtree exactly as they are supposed to.</p>
<p>Sorry about raising anyone&#8217;s anxiety levels. In the words of Rosanna DanaDana, &#8220;never mind&#8230;..&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-does-link/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Timeslips and Peachtree 2010 &#8211; Not yet ready!</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-not-linked-yet/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-not-linked-yet/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 15:10:57 +0000</pubDate>
		<dc:creator>tristar</dc:creator>
				<category><![CDATA[Add-Ons]]></category>
		<category><![CDATA[Errors & Alerts]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=50</guid>
		<description><![CDATA[This is a quick &#8220;heads up&#8221; to alert anyone who may be using Peachtree with Timeslips: as of this time Peachtree 2010 does not have a functional link to Timeslips. If you install Peachtree 2010 and then attempt to connect your Timeslips database to Peachtree via the TALPro link between Timeslips and Peachtree, you will [...]]]></description>
			<content:encoded><![CDATA[<p>This is a quick &#8220;heads up&#8221; to alert anyone who may be using Peachtree with Timeslips: as of this time Peachtree 2010 <strong>does not</strong> have a functional link to Timeslips. If you install Peachtree 2010 and then attempt to connect your Timeslips database to Peachtree via the TALPro link between Timeslips and Peachtree, you will be unable to see any of your Peachtree companies from within the Timeslips TALPro setup screen.</p>
<p>We encountered this issue internally yesterday, and were able to confirm with Peachtree Tech Support this morning that &#8220;at this time&#8221; the Timeslips TALPro link is not functional with Peachtree 2010. Sage expects to release a &#8220;link utility&#8221; for Peachtree 2010 at about the same time that they release Timeslips 2010 (early to mid-July), at which time, according to Support, &#8220;some&#8221; (?) earlier versions of Timeslips will be able to link to Peachtree 2010.</p>
<p>For now, our advice to anyone running Timeslips and Peachtree with the TALPro Peachtree link active is to not install Peachtree 2010 yet. By all means purchase the Peachtree upgrade (to capture the upgrade discounts available) but let it &#8220;age&#8221; on the shelf for a while until we have a functional link between the two products available from the manufacturer.</p>
<p>We&#8217;ll post an update here as soon as we have successfully installed a link between Peachtree 2010 and Timeslips. Stay tuned.</p>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/timeslips-not-linked-yet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

