Professional OPC
Development Tools


Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

Windows Server 2003

23 Aug 2017 04:49 - 23 Aug 2017 04:49 #5450 by support
Replied by support on topic Windows Server 2003
Based on the QuickOPC version table ( ), your only option would be to use QuickOPC 5.23 (a fairly old version). We do not, however, support this version generally, it has less features than the current versions, and bug fixes made to later version will never be projected back.

Best regards
Last edit: 23 Aug 2017 04:49 by support.

Please Log in or Create an account to join the conversation.

22 Aug 2017 19:53 #5449 by bftrock
Windows Server 2003 was created by bftrock
Unfortunately, I have to run my OPC client application, which is written in C#.NET and uses the QuickOpc toolkit on this ancient OS version. My research shows that the latest supported .NET framework supported on this OS is 4.0. I can't seem to build my application targeting this earlier framework version, partly because the QuickOpc component is built with a later .NET version:

Severity Code Description Project File Line Suppression State
Warning The primary reference "OpcLabs.EasyOpcClassic, Version=5.41.1186.1, Culture=neutral, PublicKeyToken=6faddca41dacb409, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the assembly "App_Web_OpcLabs.EasyOpcClassicRaw.x86, Version=5.41.1186.1, Culture=neutral, PublicKeyToken=6faddca41dacb409" which was built against the ".NETFramework,Version=v4.5.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.0". OpcSocketService

Does anybody have a suggestion?


Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.191 seconds