FAQ (Frequently Asked Questions)

YES. First decide where the Phoenix SQL database will reside. Phoenix will install a free version of Microsoft®’s SQL Server Express 2014 on the same machine as the Phoenix, if desired, or point Phoenix at an existing installation of Microsoft®’s SQL Server (Standard or Enterprise versions 2005/2008/2016) already installed on a machine within the company network.

Next, decide where the Phoenix Service Engine component will be installed. This component must not only have direct access to the SQL Server for database management, but must also have connection-point access to each fuel site that will be managed. This can be done using a serial COM port if direct connections are required, an installed Windows modem for dial-up access or TCP/IP connectivity using the company LAN. (Due to security issues, public Internet access to fuel site controllers and tank gauges is not recommended). 

Finally, because Phoenix is a Web-enabled application, the PC chosen for Phoenix installation must have Internet Information Services (IIS) enabled and must be securely managed behind a corporate firewall. Phoenix will enable IIS if needed during installation.

Note for Current Phoenix for Windows Users: After installing Phoenix SQL, there is a database migration utility that will import existing Phoenix for Windows data. Once complete, depending on how Phoenix is used, some modifications may need to be made to the imported data with respect to Accounts and their associated Cards.

YES. Simply insert the Phoenix SQL Installation DVD and follow the supplied Phoenix SQL Start-Up Guide that shipped with your Phoenix SQL DVD. The Phoenix Installation Wizard will auto-run. Before installing, first exit all other open applications.

There are two:

• SQL Server 2014 Express Edition: Select this option if access to a remote installation of SQL Server Standard or Enterprise Editions is not available (Phoenix SQL will install).
• Select SQL Server: Select this option if an existing installation of SQL Server 2005 Express Edition was installed on the specific machine, or if a remote version is available on the company network.

There are two:

• Typical: This is customarily the default Installation Type, and the recommended option
• Custom: For advanced users, you can modify the Website Name/Virtual Directory Name and determine the Destination Path via the Browser button

YES. Provided the Service Engine has remote access to the SQL Server. 

NO. If SQL Server Express 2014 is installed on Phoenix then Service Engine must reside on the same machine as Phoenix SQL.

After purchase, activating Phoenix SQL is simple. Whenever Phoenix SQL is installed it first opens as a DEMO version providing a 60-day, two-site configurable version.

Once purchased, Phoenix SQL can be activated for use with purchased features. To activate Phoenix SQL, log in as “sysadmin” and click the Account button on the Main Toolbar. When the Account page is displayed, click the Activate button on the Ribbon Bar. This leads to the product activation page. 

Fill in the required information and click Apply to activate Phoenix. Be sure to enter your Company Name as you want it to be displayed. The name entered will be displayed as part of the header on ALL Phoenix Reports.

Please note that once Phoenix is activated for use, the Activate button on the Ribbon bar becomes Upgrade; this option is now available when you purchase additional features in the future.

If you reinstall Phoenix on the same or a different local machine, you must contact OPW Fuel Management Systems' Customer Service at +1-708-485-4200 for reactivation.

Note: Port 5050 must be open for connection to the OPW server.

YES. After purchasing and activating your copy of Phoenix SQL, the existing P4W database can be imported. Begin by running the Phoenix SQL installation. At the Software Setup screen, select Phoenix SQL Migration Utility and click Install.

YES. The virtual directory name must be referenced when attempting to log into Phoenix SQL from another machine using a Web-based browser. For further Remote Access instructions, please select the Help button at the bottom right-hand corner of your Phoenix SQL Home page.

Note: Due to security concerns, OPW-FMS does not recommend polling FSC’s under TCP/IP connections outside of a secure company LAN.

All existing features of Phoenix for Windows are available in Phoenix SQL and includes additional features such as: 

• Fuel Zones: Allows you to define what cards will be managed at which sites; this helps control which cards fuel where and controls against FSC card memory issues
• Group Access Rights: Allow you to determine what access rights a Phoenix SQL user has in terms of managing, editing or viewing by accounts and sites
• Supports Windows^® Authentication for logging in

This has been corrected on the latest version of the Phoenix SQL DEMO disc. Check to see if you have DEMO DVD with volume label 4.4.102.3. If you do not, contact OPW Customer Support to request a new Phoenix SQL DEMO disc.

NO. Phoenix SQL licensing requires you to purchase secondary licenses (at a reduced cost) for multiple installations.

NO. As of today, Phoenix SQL licensing does not allow you to move your SQL database from one licensed connection to another.

If you are running  DVD v4.0 of Phoenix SQL you must first install patch v4.1.99.1.  If you have v4.1.99.1 or higher you only need to install the latest patch available.  For download information, please visit the Phoenix Software Downloads page.

PCI-DSS Requirement 8 calls for a two-factor authentication for remote access. Therefore, connecting to the FSC remotely using the CAP Port does not provide a two-factor process. This allows OPW's Phoenix Software, third-party software (such as DM2's autopoll) and remote users to access the system for the purpose of polling transactions using only a single authentication process. To implement the installation of the FSC3000 in a PCI-compliant manner you must always make remote dial-in connections using the FSC3000's Internal Modem.

Note:  If the site is NOT processing Bankcards (or any others cards governed by the rules of PCI compliance) and is only using the FSC3000's Proprietary Card File for authorization, then use of a modem on the CAP Port is allowed.

Yes, but these sites would not be able to take advantage of any features added thereafter. OPW will not maintain or provide enhancements to earlier versions of software that are not PC-compliant. There is no reason to not use the PCI-compliant version. Your OPW Sales Representative can direct you on ways to use the compliant software.

OPW has released an FSC3000 version of the System2 R/W Chipkey Software with Mileage Reasonability. Purchasing this software with the R/W feature disabled will provide a standard version of System2 PCF software with almost all of the features of the Multi-Trucking Network-based PCF support. Contact your OPW Sales Representative for more information on the differences.

Contact the manufacturer of the third-party software you are using and ask them to implement software changes to support the new password constraints.

Note: DM2 Software has provided OPW with an update to their "AutoPoll" software in support of the new password constraints. This update can be found on the FSC3000 ARTWare Configuration Utility CD (version 3.1) or you can contact our Technical Service Group at 877-679-8324 to receive the update via e-mail.

OPW cannot control or govern the security of a private company network, therefore the FSC3000 must always operate and be installed in a compliant manner as described in the OPW PCI Implementation Guide provided with all PCI-compliant Fuel Site Controllers.