If you receive a message of possible data corruption, simply contact us for information on how to run a simple (free) utility program to repair any corruption that may exist.

Remediation Steps if you receive a message of possible data corruption:

  1. Simply contact us for information on how to run a simple (free) utility program to repair any corruption that may exist.
  2. For an overall more stable environment for all your applications, upgrade all Windows PCs to Windows 8 or Server 2012 or preferably newer versions such as Windows 10.
  3. Understand the issue may occur again if the root cause such as a  faulty hardware component or outdated OS versions are not identified and addressed.

Problem Details You Should Know:

If you receive an error message of possible data corruption in a file while using FleetVIP, this could be caused by various problems including:

  1. A power outage.
  2. A PC or server was turned off or unplugged without doing a normal Windows shutdown.
  3. A PC was accessing FleetVIP via wifi and the wifi connection dropped during a transaction update.
  4. One or more PCs running unsupported versions of Microsoft Windows such as XP or VISTA.
  5. A faulty hard drive is corrupting data.
  6. A faulty network card is corrupting data.
  7. Some other hardware or network malfunction is corrupting data.

In addition, this problem may occur if opportunistic locking (oplocks) which is a form of file caching has not been turned off when using older versions of Windows prior to Windows 8.

Microsoft has admitted this was a problem in the past with various versions of the Windows OS prior to Windows 8. Microsoft has issued at least two hotfixes including:

  1. https://support.microsoft.com/en-us/kb/2028965 – this article includes an optional workaround registry entry for client workstations;
  2. https://support.microsoft.com/en-us/kb/2618096.
  3. Client workstation registry entry workaround for computers running SMB-2 – To work around this issue, disable(recommended) or reduce the time-out threshold for the local cache update by modifying the registry. To do this, follow these steps:
    1. Click Start, click Run, type Regedit, and then press ENTER.
    2. Locate the following registry subkey:
    3. Under this registry subkey, right-click FileInfoCacheLifetime, and then click Modify.
    4. Under Base, click Decimal, and then type a number that is smaller than the number that appears in the Value data box.Notes
      • Type 0 to disable the time-out threshold for the local cache update.
      • The number that you type indicates the length in second of the time-out threshold for local cache update.
      • This workaround typically applies to Windows Vista, Windows 7 and Server 2008.
      • It is a good idea to backup the registry first.
      • Do not attempt editing the registry if you are not familiar with this process.

The hotfix approach may or may not be appropriate for your environment. Adding a registry entry on client workstations may be an easier option but that is for you to determine.

We are providing this information for educational purposes and it is up to you to determine if it is appropriate for your environment.

There may be newer or additional information available from Microsoft since they are always posting new fixes and troubleshooting tips for their products. If you have questions or need assistance regarding Microsoft products including hotfixes or registry entries, please contact Microsoft.