<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>FuelsManager Oil and Gas Knowledge Base Articles</title>
    <link>http://www.varec.com/rss/Varec_KBA_OilGas_RSSfeed.xml</link>
    <description></description>
    <pubDate>Tue, 12 July 2011 16:00:00 +0000</pubDate>
    <language>en</language>

    <item>
      <title>FuelsManager® Data Manager and Operate update — incorrect title displayed in tank groups</title>
      <link>http://www.varec.com/docs/KBA/KBA626GVAE2611.htm</link>
      <pubDate>Tue, 12 July 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA626GVAE2611 - This article addresses a problem in the FuelsManager Data Manager and Operate applications. When the tank group is displayed, one or more values display “*Last Good Value*” instead of “LKG”. Data Manager and Operate applications have been updated to reflect the correct title.

]]></description>
    </item>
	
	    <item>
      <title>FuelsManager® Operate update — cannot silence or acknowledge alarms</title>
      <link>http://www.varec.com/docs/KBA/KBA625GVAE2611.htm</link>
      <pubDate>Tue, 12 July 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA625GVAE2611 - This article addresses an update to the FuelsManager Operate application. When the Global Silence Security right is turned off in OperNT, alarms can no longer be silenced or acknowledged. The FuelsManager Operate application has been updated to reflect the proper Global Silence Security right when the alarms are turned off.

]]></description>
    </item>
	
	    <item>
      <title>FuelsManager® Version 7.5 SP1 Installation Update (IIS7)</title>
      <link>http://www.varec.com/docs/KBA/KBA620GVAE0511.htm</link>
      <pubDate>Tue, 12 July 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA620GVAE0511 - This article addresses the Internet Information Server (IIS) 7 features required for the installation of the FuelsManager® Terminal Automation System. When installing FuelsManager Terminal Automation (Web Applications), the installation requires IIS to be installed prior to installing FuelsManager v7.5 Service Pack 1.]]></description>
    </item>

    <item>
      <title>FuelsManager Oil and Gas v7.5 Service Pack 2 Release Notes</title>
      <link>http://www.varec.com/docs/KBA/KBA617GVAE0411.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA617GVAE0411 - This article describes enhancements made to FuelsManager Oil & Gas v7.5 for the Service Pack 2 release.]]></description>
    </item>
	
	    <item>
      <title>FuelsManager Oil and Gas v7.5 Service Pack 1 Release Notes</title>
      <link>http://www.varec.com/docs/KBA/KBA554GVAE1209.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA554GVAE1209 - This article describes enhancements made to FuelsManager Oil & Gas v7.5 for the Service Pack 1 release.]]></description>
    </item>
	
	    <item>
      <title>FuelsManager Bills of Lading (BOLs) problems with unposted closeout days and "No Load" records</title>
      <link>http://www.varec.com/docs/KBA/KBA615GVAE0311.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA615GVAE0311 - This article addresses two problems in FuelsManager related to Bills of Lading (BOLs). The first problem is that FuelsManager allows a day to be closed out while there are still unposted BOLs in the system. This prevents BOLs that may require correction from being corrected. The second problem is that FuelsManager is failing to send “No Load” records to PIDX. This causes problems whereas load authorizations are not being cancelled out, preventing later loads from being authorized.]]></description>
    </item>
	
	    <item>
      <title>“RPC Server Unavailable” error occurs on an Optomux device definition</title>
      <link>http://www.varec.com/docs/KBA/KBA614GVAE0311.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA614GVAE0311 - This article addresses the “RPC Server Unavailable” error message received when attempting to change the communications port for any Optomux device. When this error message occurs, an error is also logged in the Windows Application Event Log of Event Viewer indicating a fault in the Optomux OPC server’s dynamic link library.]]></description>
    </item>
	
	    <item>
      <title>TimeOut is not set until the driver cards out at the Bills Of Lading (BOLs) printer</title>
      <link>http://www.varec.com/docs/KBA/KBA613GVAE0311.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA613GVAE0311 - This article addresses the problem in which TimeOut on BOLs is not being set in the event of a power outage during a load. TimeOut is also not being set in the event that the BOL printer is not available.]]></description>
    </item>
	
	    <item>
      <title>Mutex errors—event logging changes</title>
      <link>http://www.varec.com/docs/KBA/KBA602GVAE0111.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA602GVAE0111 - The event logging type and the conditions for logging Mutex errors have been changed in order to lower the severity of the event log entries associated with Mutex errors, and to limit their logging to occur only during the normal operation of the DataManager.]]></description>
    </item>
	
	    <item>
      <title>Importing new alarm priorities does not take effect</title>
      <link>http://www.varec.com/docs/KBA/KBA608GVAE0211.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA608GVAE0211 - This article addresses the problem of importing new alarm priorities or coded variables not working for tank level or temperature in the FuelsManager Oil & Gas application.]]></description>
    </item>
	
	    <item>
      <title>Cumulative change for FuelsManager Terminal Automation</title>
      <link>http://www.varec.com/docs/KBA/KBA595GVAE1110.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA595GVAE1110 - A hotfix for FuelsManager Terminal Automation v7.5 SP1 has been developed to address multiple issues reported from the field. This hotfix accumulates changes made since the release of the v7.5.1.10 hotfix.]]></description>
    </item>
	
	    <item>
      <title>Custom application for changing the tank command mode to stop</title>
      <link>http://www.varec.com/docs/KBA/KBA590GVAE0810.htm</link>
      <pubDate>Tue, 14 June 2011 14:00:00 +0000</pubDate>
      <dc:creator>Varec</dc:creator>
       <description><![CDATA[ KBA590GVAE0810 - The custom application changes the Tank Command Mode to Stop if the specified criteria are met.]]></description>
    </item>


  </channel>
</rss>
