Can't connect to the Lookout OPC Server

[Davidd]

OK guys, give me a good answer to this question.

First some background:

Running Lookout 5.1, all latest patches, on Windows 2003 Server.  Also have test serversrunning on Windows XP, and Windows 2000.

Trying to install Cogent OPCDataHub to communicate to rest of services.

I can get the OPCDataHub to work perfectly.  I can start various OPC server software (simulated data for OPC testing), and access that data both on the local computer through the DataViewer, as well as any of the remote systems I wish to try it on.

I can bring up ServerExplorer and it finds any and all of the OPC data sources, and will display data from any of them.

I can manually connect to a running Lookout server and display data items through OPC.

Now for what I can't do.  Through the OPCDataHub I can't locate the Lookout OPC Service.  I have tried 'National Instruments.LookoutOPCServer', as listed in the KB information I've managed to find, and 'LookoutOPCServer' like the ServerExplorer finds, but NOTHING with the exception of ServerExplorer seems to be able to locate the Lookout services.

When I try to setup a connection to the Lookout OPC Service, I get the following message in the Event Log of the OPCDataHub over and over:

"[2006-05-02 16:35:54.578]: OPC client to: \\DHXZ5M21\National Instruments.LookoutOPCServer: Could not connect to OPC enumerator on: \\DHXZ5M21: Error in the DLL"..

Doesn't matter what the name is (of course, in the message the name ends up the same as what I enter for the name in the server connection block).

So here we go, got any ideas what might be wrong?  I'm going bald pulling out my hair on this one.

David Dudley

[Ryan.S]

In server explorer, see the "properties" of LookoutOPCServer. Under registry tab, is the CatIDs set or not?
If it's not registered, run these two commands in "Run",
1. regsvr32 "c:\program files\national instruments\shared\logos\lkopc.dll"
2. "c:\program files\national instruments\shared\logos\lkopc.exe" /regserver"

the directory for Logos may be different.

Have a try.

[Davidd]

Well, it was a good try.  Yes, under Server Explorer properties, the CATIDs were not set.  I ran the two commands you gave, and rebooted the computer, and yes, they are set now.  However, I still get the "Error in the DLL" message constantly, and I can't see any data.

Have to try again.

David Dudley

[Lorenz03Tx]

David,

The error message seems to indicate that Cogent OPCDataHub is unable to enumerate the list of available OPC Servers on the given machine. My guess is that they use OPCEnum.exe to do this, and the error message is because OPCEnum.exe is not installed/properly installed on the machine (in your case it is \\DHXZ5M21).


You kind find an installer for OPCEnum at www.opcfoundation.org

In addition it is likely the Cogent has the redistributable .msi available with their installer.

I hope this helps
-Lorenz

P.S. Some OPC clients use OPCEnum to get from the ProgID to the CLSID (from the 'LookoutOPCServer' to the unique GUID) so even if you don't need to browse the list of available servers it is still possible you need OPCEnum.

[Davidd]

Well, moving right along, Cogent sent me the OPCEnum package, which I have installed.

Now, I can at least see the Lookout OPC service, which has a DIFFERENT NAME than that listed in any of the documentation I've been able to find.

The service is named 'OPC Server Interface to Lookout'.  Be nice if the author of the Lookout software had managed to get it right to start with.

OPCEnum can now find the server, but when I go to get the list of names from the OPC Server itself, the process runs and runs and runs (ran for almost 2 hours, eating up 25% of the CPU time during that period).  Finally had to kill both it and the Lookout task.

The process is not consistant, I have managed to get it started correctly once, and it loaded for around 10 minutes, and then gave me a partial list of the data points on all the systems in the network, EXCEPT for the one I had connected to.  What a crock....................

Be nice if something worked right sometimes.

David Dudley

[Ryan.S]

I have downloaded the OPCDataHub and met the similar problem too. It cost 5 minutes for launching and another long time when I clicked a button. As I tried other 3rd opc client and it works well, I guess the OPCDataHub itself has some kind of problems.

[Davidd]

So far, the Cogent people have been the most helpful group in the bunch.  I've talked to the staff there, and they've sent me two other versions of the software to try.  I still haven't gotten the connection to work, but I can see bits and pieces of it starting to work.  I still don't see how it can be so inconsistent, though.  Figured I'd try a couple of other OPC pieces to see if it is a Lookout or a Cogent problem.

David Dudley

[Davidd]

Well, after being able to let this dog lie for over a year, it has again raised it's head.

I never stated 'why' I needed to do this, and the reason has always been because Lookout won't run on anything except Windows, and all our analysis and logging software runs on UNIX.  Datahub gives us the capability of reading the OPC channels through UNIX from the Windows system.

Back to the problem (wake up! wake up!).

First, I should say that now, I'm having to upgrade and replace the server systems with new hardware.  The lease is up on the existing hardware, so it's got to go back.

I'm trying to get Server Explorer to recognize the new server first.  When I start server explorer on this new hardware, I get a list that doesn't contain the new server in it, and I can't seem to get the new server on the list.  The computers listed under 'Entire Network" all exist, but none of them have Lookout running on them.

How do I get my new server on the list?

[Lorenz03Tx]

David,

    Please elobrate on the "new server", in your previous post from a year ago you were trying to get the datahub client to connect to Lookout. Is the new server a new install of lookout on a diffrent machine? Please also give version numbers and as much information as you can.

If I recall we took your discussion off the fourms and solved them with the normal support channels last time?  Did that work out for you?

[Davidd]

OK, here goes:

1. The existing server equipment is leased.  The lease if over, and I need to replace the servers with new hardware. I have the new hardware in my office, preparing it for installation.

2. The original Datahub installation was never operationally complete on the previous system, I ended up writing a Lookout process that wrote all the variables I was interested in collecting data on into our SQL database system directly.  Although this was an acceptable 'stop-gap' measure, it meant that the failure of one client machine on the Lookout system could stop all historical data collection, and also that every time I added anything into the SCADA system, I then had to go modify this process to add in the new data I was collecting.  Needless to say, I want to rectify that problem while I have a chance, before the production system pressures prevent it.

3. I started by installing Lookout 5.1 on my replacement SERVER system.  This system is a Dual Quad-Core DELL 1950 box w/ 16 GB, with Windows Server 2003 installed.  Now, I know that Lookout isn't directly supported on that software, but the administration above me insisted that 'a server needs server software', and if it wasn't supported 'that's a problem with the vendor', and is beyond my control.  They insisted on a server, if for no other reason, for the redundant power supplies and other additional support hardware.  Again, that really was beyond my control.  The old server has Server 2003 on it also, and Lookout has run acceptably on it for the past 3 years.

4. I've got Lookout 5.1 running on the server, and the next step, I think, is probably to get OPC connections between the server and a client computer operational.  I've got a little sample process running on the server, and I've gotten to the point where I can run a client process in another Lookout instance on that machine, and do OPC connections between them.  That part seems to be working great.   I can also bring up Server Explorer and see the OPC process, attach to it, and read all sorts of information - so far, pretty impressive.

5. OK, here's where I'm stuck right now.  On my client machine, if I bring up Server Explorer (version 2.4.1), I don't even see the other machine. (named \\PRIMARY, bye the way, and the client is named \\CLIENT, just for fun).  I see the LookoutOPCServer on 'My Computer', but nowhere else.  Whats more, if I expand 'My Network Places', I get a list of items like '#STD_CNT/0', '#STD_CNT/1', and '#STD_CNT/2'.  Expanding them leads to even more confusion, as expanding 'Entire Network' repeats the rest of the list, and expanding '#STD_CNT/0' points to one of my UNIX systems, expanding '#STD_CNT/1' is empty, and expanding '#STD_CNT/2' gives me a list of host names, some of which don't even exist anymore, and none of which have anything 'Lookout' related on them (Most are my UNIX servers, and others include the other machines in my office,  only one of which has Lookout).  I can see the server machine if I open 'My Network  Places' under Windows, but not under Server Explorer.  Not sure whats going on here, or how to proceed.  Is a reasonable set of instructions around for setting up OPC between two machines (something newer than Windows 95 or 98 please?)?

David