Problem connecting to Field Point OPC Server

[j.wright]

I am having a problem using the Field Point OPC Server (version 6.0.2) in Windows XP.  I am running two separate OPC clients – a simple test client and an MFCS/win 2.1 client – on the same computer on which the Field Point server is running.  I can browse the Field Point controller using both clients, but only the test client can read values from the server.  The MFCS client is apparently not able to establish a permanent connection.

I have used the Windows XP security log to observe the connection attempts from both clients.  The Event Viewer displays no Failures and the following Successes:

1) A new process has been created.

Image File Name:  C:\WINDOWS\system32\Opcenum.exe

2) A process was assigned a primary token.

Image File Name:  C:\WINDOWS\system32\Opcenum.exe

3) A process has exited.

Image File Name:  C:\WINDOWS\system32\Opcenum.exe

4) A new process has been created.

Image File Name:  C:\Program Files\National Instruments\Field Point\FieldPointOPC2.exe

5) A process was assigned a primary token.

Image File Name:  C:\Program Files\National Instruments\Field Point\FieldPointOPC2.exe.

For the test client:

6) The Windows Firewall has detected an application listening for incoming traffic.

Path:  C:\Program Files\National Instruments\Field Point\FieldPointOPC2.exe

For the MFCS/win 2.1 client:

6) A process has exited.

Image File Name:  C:\Program Files\National Instruments\Field Point\FieldPointOPC2.exe.

Do you have any idea why the Field Point OPC Server exits immediately in one case but persists in the other?

Can I configure the Field Point server to generate a log file during these connection attempts to assist with diagnostics of the problem?

Are there any other diagnostic techniques that I could use to solve this problem?

[j.wright]

I have now also used Matrikon's OPC Delegator to monitor the connection attempt between the Field Point OPC server and the MFCS\win 2.1 client.  The following error is logged:

[10/13 15:47:07.78] (0) - ISysMatLog::Open() - *** Log file [C:\Temp\OPCDelegator.log] started
[10/13 15:47:13.25] (4) - COPCServerDelegator::FinalConstruct() - Could not create instance of target server
[10/13 15:47:13.25] (4) - COPCServerDelegator::FinalConstruct() - 0x80004005 [Unspecified error]
[10/13 15:47:13.25] (6) - COPCServerDelegator::FinalConstruct() - Function returning [hr]=[0x80004005] at line [118] in [C:\$\ProcessX OPC\Logging Delegator\OPCServerDelegator.cpp].
[10/13 15:47:13.25] (6) -  - 0x80004005 [Unspecified error]
[10/13 15:47:13.25] (7) - COPCServerDelegator::FinalRelease() - Entering function at line [126] in [C:\$\ProcessX OPC\Logging Delegator\OPCServerDelegator.cpp].
[10/13 15:47:13.25] (7) - COPCServerDelegator::FinalRelease() - Function returning at line [128] in [C:\$\ProcessX OPC\Logging Delegator\OPCServerDelegator.cpp]

[ninlmartijn]

Hello J Wright,

Thank you for your post on our webforum. I have a few suggestions to try.

Is it always the MFCS\win 2.1 which cannot connect to FP OPC server? Also when this is the only client?

Is it possible to explore the OPC server with the server explorer ?

What port is MFCS client using, and is the port open in the firer wall? (try with firer wall switched off)

Best regards,