<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Comments for andrewallen.co.uk</title><link>http://andrewallen.disqus.com/</link><description /><language>en</language><lastBuildDate>Thu, 01 May 2008 21:00:51 -0000</lastBuildDate><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/andrewallen/comments" type="application/rss+xml" /><item><title>Re: Citrix Web Interface and the Fatal Execution Engine Error [updated]</title><link>http://feeds.feedburner.com/~r/andrewallen/comments/~3/281676881/</link><description>I came across a very similar error as you.  My setup was win 2003 R2 standard SP2 64bit running in a VMWare Server version 1.05.  The .net framework was just not stable and any applications using it often crashed.  I had SQL Server 2005 running with Reporting Services and the reporting services service would often fail and many of the sql client tools would also crash.&lt;br&gt;&lt;br&gt;After spending over a week on the issue I upgraded to VMWare Server 2.0 (beta) and all of my problems went away.  The docs for the new version state that they made changes to the way memory was being handled specifically towards 64bit OSes.&lt;br&gt;&lt;br&gt;Maybe a newer version of citrix (if one even exists) would help you?&lt;img src="http://feeds.feedburner.com/~r/andrewallen/comments/~4/281676881" height="1" width="1"/&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gary</dc:creator><pubDate>Thu, 01 May 2008 21:00:51 -0000</pubDate><feedburner:origLink>http://www.andrewallen.co.uk/archives/2008/03/13/citrix-web-interface-and-the-fatal-execution-engine-error/#comment-404243</feedburner:origLink></item></channel></rss>
