I am copying below the entire Application Deployment section of that version (the formatting is gone, though). You absolutely must make sure that you have all the prerequisites installed.


Application Deployment
This chapter describes how to deploy applications developed with use of QuickOPC.NET.
For some uses, it is acceptable to perform the deployment manually. In other cases, you will find yourself writing an installer for your application, and you will probably want to include the installation of QuickOPC.NET components in it as well.
Deployment Elements
Assemblies
Depending on which assemblies you have referenced in your application, you may need one or more of the following files be installed with your application:
For .NET Framework 2.0, 3.0 and 3.5 For .NET Framework 4
• EasyOpcCommonNet.dll
• EasyOpcDANet.dll
• EasyOpcDANetForms.dll
• ShellLib.dll • EasyOpcCommonNet-v4.0.dll
• EasyOpcDANet-v4.0.dll
• EasyOpcDANetForms-v4.0.dll
• ShellLib-v4.0.dll
Please refer to “Product Parts” chapter for description of purpose of individual assemblies. You will find them under the Assemblies or Assemblies-v4.0 subdirectory in the installation directory of the product. Assemblies for the x64 platform are one level further below, under “x64” subdirectory.
The assemblies need to be placed so that the referencing software (your application) can find them, according to standard Microsoft .NET loader (Fusion) rules. The easiest is to simply place the assembly files alongside (in the same directory as) your application file.
Prerequisites
Besides the actual library assemblies, QuickOPC.NET requires that following software is present on the target system:
1. Microsoft .NET Framework 2.0 with Service Pack 1.
o For x86 platform, you can install it from www.microsoft.com/downloads/details.aspx?FamilyId=79BC3B77-E02C-4AD3-AACF-A7633F706BA5.
o For x64 platform, you can install it from www.microsoft.com/downloads/en/details.aspx?FamilyID=029196e...99-3c61d19a4c5a&displaylang=en.
Needed when: If you target .NET Framework 2.0, 3.0 or 3.5.
o Redistributable package for x86 platform can be downloaded from www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
o Redistributable package for x64 platform can be downloaded from www.microsoft.com/downloads/en/details.aspx?FamilyID=b44a000...fb-40e78d788b00&displaylang=en.
Needed when: If you target .NET Framework 2.0, 3.0 or 3.5.

2. Microsoft .NET Framework 4 (Full or Client). You can install it from
www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d5...e5-b386f32c0992&displaylang=en. Redistributable package can be downloaded from www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391ab...9f-b21f31ab88b7&displaylang=en.
Needed when: If you target .NET Framework 4.

3. Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update. You can download it from www.microsoft.com/downloads/en/details.aspx?familyid=2051a0c...f5-770a549fd78c&displaylang=en. You need to select the package appropriate for the targeted platform (x86 or x64). If you are going to redistribute it within your own installer, you can call it with “/q” on the command line, for silent installation.
Needed when: If you target .NET Framework 2.0, 3.0 or 3.5.

4. Microsoft Visual C++ 2010 Redistributable Package.
o For x86 platform, you can download it from www.microsoft.com/downloads/details.aspx?FamilyID=a7b7a05e-6...23-37bf0912db84&displaylang=en.
o For x64 platform, you can download it from www.microsoft.com/downloads/en/details.aspx?familyid=BD512D9...BF-9350143D5867&displaylang=en.
If you are going to redistribute it within your own installer, you can call it with “/q” on the command line, for silent installation.
Needed when: If you target .NET Framework 4. It is also needed by the License Manager utility.

5. OPC Core Components 3.00 Redistributable (x86), version 3.00.105.0 or later. You can download it from www.opcfoundation.org. You need to select the package appropriate for the targeted platform (x86 or x64).
IMPORTANT: On 64-bit system, only install the 64-bit package, even if you intent to use some 32-bit OPC components. The 64-bit package includes everything that is needed for 32-bit OPC as well.
If you are going to redistribute it within your own installer, you can call it via MSIEXEC.EXE with “/q REBOOT=Suppress” on the command line, for silent installation.
Needed when: Always.
Note that due to a bug in the OPC Core Components installation, it may silently skip installation of certain critical components (such as OPC COM proxy/stub) if .NET Framework 2.0 or later isn’t present on the system at the time of installation. Always make sure that .NET Framework is installed, before installing OPC Core Components.
Licensing
Proper license (for runtime usage) must be installed on the target computer (the computer where the product will be running). The License Manager utility is needed for this. It is contained in LicenseManager.exe file, located under the Bin subdirectory in the installation directory of the product.
Deployment Methods
Manual Deployment
In order to deploy your application with QuickOPC.NET manually, follow the steps below:
1. Check that proper version of Microsoft .NET Framework is installed, and if it is not, install it.
2. Run the QuickOPC.NET installation program, selecting “Production installation” type.
3. Perform any steps needed to install your own application.
4. Copy the QuickOPC.NET assemblies to their target locations for your application.
5. Run the License Manager from the Start menu, and install the runtime license.
Automated Deployment
The installer for your application should contain following steps:
1. Check that proper version of Microsoft .NET Framework is installed, and if it is not, instruct the user to install it.
2. Install Microsoft Visual C++ 2008 SP1 Redistributable Package for the appropriate platform, if needed.
3. Install Microsoft Visual C++ 2010 Redistributable Package for the appropriate platform.
4. Install OPC Core Components 3.00 Redistributable for the appropriate platform.
5. Perform any steps needed to install your own application.
6. Install QuickOPC.NET assemblies to their target locations for your application.
6. Install LicenseManager.exe (from Bin or Bin\x64)
7. Offer the user an option to run the License Manager.
The user who deploys the application will then:
1. Run your installer and follow the steps.
2. Use the License Manager and install the runtime license.
If the above described procedure for installing the license (presenting the user with the License Manager utility user interface) does not fit the needs of your application, please contact your vendor, describe the situation, and ask for alternative license installation options.

The version you have is so old that all information to it is on archived DVDs, and off-site.
We do not support older versions; that is, I am willing to look at it, but it only goes so far.

As I wrote, the first suspicion goes towards the C++ redistributables. The documentation for the version should hopefully state the precise installation package(s) needed - that's what I want to look up when I am back. It is possible that your setup includes the PDF version of the doc, then the info should be there too.

Another way to make sure that right C++ redistributables are on the machine is to run the QuickOPC setup program. Have you done it on your computer, or do you just have the QuickOPC assemblies?

Best regards

Hello,

this is quite an old version. Please wait until Thursday when I am back in the office and can look up some info in the archive.

It could have to do with Visual C++ redistributables (precise version matters a lot).

Also, what kind is your project? (such as Windows Forms app, console app, ASP.NET, Windows service, etc.?)

Best regards