A 32-bit vs. 64-bit mismatch. FactorySoft is typically a 32-bit application trying to access a 64-bit COM server registration that lacks a 32-bit proxy.

Before you run the installer, ensure you have the following in place. Attempting to install without these will likely result in "Class not registered" errors or failed COM connections.

Select the desired tags (e.g., Temperature , Pressure , Cycle_Count ) and click the or Move to List arrow. Click OK to close the tag browser.

Before you double-click the setup.exe, 80% of potential failures can be avoided with proper preparation.

Ensure the host machine can ping the target OPC Server IP address or hostname.

Select or create a program folder shortcut name, then click Next .

If your FactorySoft OPC Client is connecting to an OPC server hosted on a different physical machine, you must configure Windows DCOM settings. Skip this step if your OPC server and FactorySoft client are on the same local computer.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

Here is your step-by-step guide to getting the FactorySoft OPC Client up and running without the headaches.

Under the tab, edit both Limits and Defaults for Access Permissions and Launch/Activation Permissions.

Open the FactorySoft OPC Client via your desktop shortcut or Start Menu. The main graphical user interface (GUI) will present a split-pane layout consisting of a server/group browser tree on the left and an item display grid on the right. Step 2: Browse and Select a Local or Remote Server

: While FactorySoft has historically focused on OPC Classic, modern industrial standards are shifting toward OPC UA. Users looking for native, cross-platform UA support might find these toolkits more limited compared to newer frameworks like Open Automation Software