What is Runtime Error 339?
Often the culprit is a missing file
Runtime errors, such as runtime error 339, are errors that occur when a program is running. Depending on the program that is generating the error, the runtime error may indicate a missing file. For example, if you use Microsoft Business Solutions for Analytics-FRx 6.7 Desktop or FRx Financial Reporter 6.5, a runtime error 339 can occur when running a report. In this case, the required file for generating the report, dzocx32.ocx, is missing or corrupt.
Why a program wont run or task fails
Similar runtime 339 errors affect FRx Financial Reporter as well as Crystal Reports, though the exact file name may be different. What is basically happening with runtime error 339 is the software is calling up a component for generating a report, only the component is missing a required file or the required file is no longer properly registered. When this happens, the component cannot run and the task fails.
An OCX or DLL file is usually to blame
Most often, the runtime error 339 involves either an OCX file or a DLL file. OCX files are a type of ActiveX control. Software developers use these files as building blocks when they develop software applications. DLL files are “Dynamic Link Library” files. These files are used in much the same way. Rather than writing fresh code for a common function (such as generating a report or printing a page), software developers use OCX and DLL files as building blocks.
These files are often already present on your computer and may be shared by other applications. Likewise, when you install new applications, a newer version of the OCX or DLL file may be included, overwriting the older one. When this happens, problems can arise with programs that don’t recognize the new version and now can’t find the old file.
Be wary of the dangers
DLL and OCX files can become damaged due to other forces such as unexpected computer shutdowns, power surges, and computer viruses. They can also originate with the software developer due to poor programming.
The solution to solving runtime error depends on the exact file that is missing or the error being generated. Oftentimes, especially if the computer experiencing the runtime error 339 is on a network, you can copy a fresh copy of the file off of another computer and replace the damaged one. However, runtime error 339 is also a known bug with Crystal Reports 8. No matter which program is generating the runtime error 339, it’s always smart to update the software with the latest updated from the developer. For example, if you are running Microsoft FRx, which is part of the Microsoft Dynamics family of enterprise business solutions, and your runtime error 339 is being generated within FRx, Microsoft recommends that you install the latest FRx Service Pack.
First determine which program is causing the 339 runtime error
As with all computer errors, runtime error 339 requires a bit of detective work to solve. Clues to take note of include the program that is generating the error, the component’s file name such as *.ocx or *.dll, and any error messages accompanying the runtime error alert.
Runtime Error Types
How to Fix Runtime Errors