Troubleshoot Error C0000005 or C0000006

  • Created:
  • / Author: tombucci
Solution:

C0000005 and C0000006 is a Microsoft Visual FoxPro (VFP) error used to report general issues and occur randomly in the program. The error has been linked to and not limited to the following:

  • Hardware conflicts
  • Printer drivers
  • Background applications/processes
  • Corrupted data/bad indexes
  • Temporary files

Common Causes

Please refer to the list below for the leading causes of this issue (listed by frequency of occurrence):

  • Printer Driver Conflicts
    This can be resolved by reinstalling the driver or by using a base emulation driver such as HP 4.
  • Background Applications
    running in the background such as the Microsoft Office Shortcut Bar and anti-virus software have been found to be some of the leading causes of there errors.
  • Environmental Causes
    There may be many environmental issues such as:

    • A bad network card (NIC).
    • The temporary directory does not exist on the workstation.
    • The temporary directory has been marked as system file. Please refer to solution 21934 for more information.
    • There are issues with the temporary files. You may need to perform a clean reindex and delete temporary files.
  • Corrupted Data or Indexes
    Bad indexes are the main cause; however issues with corrupted data have also been reported.
  • Program Issues
    In Sage Pro 6.5 Builds 2500 and 2501 issues were reported when using an MDI form. These errors appeared if the information grid at the bottom of the form was edited and the X button was used to exit the screen. This could be avoided by pressing the ESC key or using the exit button instead. This was documented in PTR 60832 and fixed in Sage Pro 6.5 Build 2502.
  • Roaming Profile
    These errors may also appear if a Roaming Profile is shared between Microsoft Windows 2000 and XP workstations. This is a VFP 8.0 issue and is documented in Microsoft Knowledge Base article 839024.

Troubleshooting

C0000005 and C0000006 errors are general in nature and identical causes are rarely reported. Please refer to the list below for help in troubleshooting this error:

  • Find a pattern
    This is important in isolating the exact cause of the error. Refer to the list below for some examples:

    • Determine whether the error occurs during printing or previewing. If it occurs during printing, then it is most likely a printer driver issue.
    • Investigate whether these errors occur on all workstations. If so, then it is most likely a network, data or program issue. If this is observed only on one or a few workstations, it will most likely be an environmental issue such as background applications, no temporary directory on the workstation or the temporary directory has been marked as a system file.
    • Verify whether this issue occurs in all companies. If so, then this could be a program or environmental issue. If not, it is most likely caused by corrupted data or a bad index.
  • Eliminate potential causes based on pattern
    Refer to the examples below:

    • If these errors occur on all workstations while printing, ascertain whether the workstations are using a single or multiple network printers. Remove the existing driver on one workstation and install a base emulation driver. Test a local printer to eliminate the network print queue as a potential issue.
    • If these errors occur sporadically on one workstation, then it is most likely an environmental issue. Shut down any programs running in the background to avoid conflicts.
  • No pattern identified
    If no pattern could be identified, follow the steps below to help narrow down the issue:

    • Simplify the workstations as much as possible by shutting down all programs in the background until only Explorer and Systray are running.
    • Clean reindex and delete the temporary files for the Sage Pro.
    • Utilize the System Recovery Tools in System Manager.
  • Record Information
    If the issue cannot be corrected or identified, users should record the following information when the error occurs. This can be useful in helping to identify a pattern:

    • Screen shot of the error.
    • Document the steps that were taken prior to the error. This includes:
      • Company
      • Module
      • Transactions
      • Open windows
      • Specific customers, vendors and items
      • Using mouse or keyboard

© Copyright Sage Software

Leave A Comment?