Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

opc client windows service

Created by: jljuan at: 9/9/2008 4:14 PM (5 Replies)

Rating (0)

Thanks 0

6 Entries

9/9/2008 4:14 PM	Rate (0)
jljuan Posts: 7 Rating: (0)	Hello everybody: I'm making an opc client application using c#. I've started with the sample called opcasync.net installed with simatic net. I've made a windows form sample project that is reading every two seconds a plc variable via opc and it works. Now I want to convert this project to a windows service. I create a windows service project and copy the same as I have in the windows form project. When I try to read the plc variable I get the next error: System.Runtime.InteropServices.COMException (0x80040200): Exception from HRESULT: 0x80040200 at OpcRcw.Da.IOPCAsyncIO2.Read(Int32 dwCount, Int32[] phServer, Int32 dwTransactionID, Int32& pdwCancelID, IntPtr& ppErrors) at WindowsService.OPC_Client.Read() Both projects are attached. Attachment projects.zip (298 Downloads)
jljuan Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/13/2008 6:01 PM	Rate (0)
legacy support Silver Member Joined: 7/15/2008 Last visit: 10/6/2024 Posts: 382 Rating: (44)	Hello jljuan, Please check if you have your MDAC "MICROSOFT DATA ACESS COMPONENT" propperly installed and configured.

Suggestion To thank Quote Answer

9/15/2008 11:20 AM	Rate (0)
jljuan Posts: 7 Rating: (0)	Yes, in my com references in visual studio 2005 appears the component name "Microsoft data access components installed version". The typelib version is 2.50 and is installed in C:\windows\system32\odbcconf.dll. What I don't know to do is to configure the MDAC component. I can tell you too that I've found in the Simatic net read me this restriction: User programs that communicate using SIMATIC NET must not be used as Windows services (background processes) and must not be triggered in the Autostart group to avoid undefined initialization statuses during startup. Instead, use the Autostart function for applications and services in the "Configuration Console“. Does it mean that there is no way to programm an opc client as a windows service?
jljuan Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/15/2008 4:25 PM	Rate (0)
JMJ Posts: 487 Rating: (45)	Simatic NET OPC server itself does not allow it to be configured as a Windows service. May be that contributes to the problem. You have not mentioned what is on the otherside ofSimaticNET. Is it an S7 PLC on ethernet? But anyway kepware S7 OPC server allows it to be configured asWindows NT service. So it may be worth a try with it. Trial version is downloadable. Check this links for more info. http://www.kepware.com/Products/Siemens_Suite.html http://www.kepware.com/Products/feature-ntservice.htm
JMJ Posts: 487 Rating: (45)
Suggestion To thank Quote Answer

9/18/2008 11:49 AM	Rate (0)
jljuan Posts: 7 Rating: (0)	I solved the problem. I was starting the service with a local account. I changed to an administrator account and I've got a right read. The dll does not throw an exception now. So it is possible to create an opc client like a windows service.
jljuan Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/25/2008 6:13 AM	Rate (0)
kanan Posts: 133 Rating: (2)	well done!
kanan Posts: 133 Rating: (2)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on