User Tools

Site Tools


Troubleshooting Pervasive 3012 / 3014 errors using FSCAN

NOTE: This document is intended for computing professionals to assist with troubleshooting Pervasive server breakdowns.

UPDATE : SEPT 7 / 2016

Be aware that there are several Antivirus programs that that now Identify Fscan as a virus threat, and in some instances will partially disable the Pervasive Service on a network. Some of these antivirus programs include Sophos Antivirus and WatchGuard Antivirus. So as a rule, we should delete the application after using it. It does not have to be running to be recognized as a threat, It just has to exist in a folder, and when the folder is accessed, it will cause the antivirus to report that a threat has been detected. Once this happens the antivirus will take appropriate action to protect the network. We have seen on one occasion, that even if the Fscan.exe file is on a workstation, the antivirus caused the server to block access to one of the pervasive services, effectively preventing everyone from being able to open System Five.

3012 and 3014 errors can be the result of a firewall blocking access to the Pervasive Ports on the server via a client. To ensure that the Pervasive ports are accessible on the server, run a port scanning utility such as FSCAN.EXE from the client to the server using the server name. The Pervasive default configuration will use the server name.

FSCAN utility can found on the link below:

Place this file on the client machine in c:\windows

open up command console

type» fscan -p 1500-3500

Ports 1583/tcp and 3351/tcp should be displayed for proper Pervasive operation. The /tcp represents the connection was made using TCP/IP.

Figure 1 shows the fscan result that should be obtained for proper operation.

Figure 1 - Results from the fscan test

Editor: arose
Edited: 15-Jul-2010

faq/troubleshooting_pervasive_3012_3014_errors_using_fscan.txt · Last modified: 2016/09/07 09:49 by swind