Windows 7 lookout opc server problems

Hello,
I am not able to successfully read from my OPC server 2011 within Lookout 6.6 on one of my pcs. I had built a process on a different pc that worked. Now on a new pc, after installing NiMax and configuring a NIDAQ PCI-6052E device and building the NI-DAQmx Global virtual channels using AI1-AI8 points then installing and configuring Lookout and building up a process, I can see the AI1 - AI8 points in lookout when I traverse the object browser and find process1>OPCClient1>computername>system>DAQmx>AI1 (for example). Once I do that, lookout alarms with priority-8, object name ...OPCclient1, area-comm description - Internal error (2): Processing read data (50): Can't convert data to Lookout format (00000004).
This has worked on a different pc, when I run lookout as Administrator... Any help would be appreciated.
David Istre

Hello, I replied once, but my response did not show up on the discussion forum.
Both PCs are running Windows 7.
I have placed the opcclient.ini file within the Lookout folder and then ran lookout 2 times. The first time I ran lookout, I was getting data from my opc client. The log file shows that (from 8:11am). I closed lookout and did some other things for about an hour and then ran lookout again. This time I could not get data from my opc client. Again, the log shows that (around 9:50am).
Is there a way to use a NIDAQ card within lookout 6 without having to use OPCClient? Also, is there a way to get better lookout support than through these forums?
David
Attachments:
OPCclient1log.txt ‏64 KB

Similar Messages

Lookout OPC Communication Problems

I am running a Lookout process with an OPC server to connect to a
ControlLogix PLC. My Lookout process will not always reflect the
current state of hardware, i.e. simple Boolean objects do not update
on the display control panel. I can, in some cases cause the display
to change by changing the state of my hardware manually (actuating a
limit switch for example) thus Lookout sees an event and updates the
display. But this does not work in all cases so I have no way of
knowing if the display is accurate.
Similary, changing the position of Lookout switches and pushbuttons
on the control panel will be reflected in the plc ladder logic but not
write back to Lookout to report the change. This is true for both
local and remote position source
s. I should add that switching from
OPC1 to OPC2 or OPC2 to OPC1 can cause some signals to reflect what
hardware is doing but there is no definite consistency that one can
point to that will identify the problem.
Finally, communication between the OPC Server and the PLC is fully
functional and verifiable. So there seems to be a fundamental flaw in
my design any advice on this issue would be greatly appreciated.
Leo

Hello Leo,
Have you tried turning On the Force refresh after write setting?
Also, try polling the device periodically to force the updates.
Regards,
Khalid

SMB connection to Windows 2008R2 File Server Problem

Hello, I recently migrated a file server from Windows 2003 to Windows 2008R2. Since the migration, I can no longer use our Canon multi-function printer to scan documents to a network share on the new file server. The share has Everyone, System
and Authenticated Users set to Full control and the NTFS Security is setup for Everyone to modify. The connection from the Canon uses SMB using a domain account called jdoe.
I wondering if the problem is related the the LAN Manger authentication level settings. On the new file server and domain controllers it's set to Network security: LAN Manager authentication level is set to Send NTLMv2 response only\refuse LM &
NTLM. I have setup a network capture and hope somebody can help me out with determinging the problem.
Here is the detals of the Error

It does seem possible that the NTLMv2 authentication level might be affecting things. So I would give it a try. It's difficult to troubleshoot from the image, but I beleive there is a flag in the negotiate response that might give you a clue.
In either case, I think your question would be better served by our networking group, rather than the group that makes the tool. While we have some general protocol knowledge, we don't have the depth that the experts for each component would have.
If changing that setting doesn't work we can move this thread over to the right place.
Thanks,
Paul

How can I edit the database in Lookout OPC Modbus driver OPC sever with the address that has a write attribute?

When I use Lookout Modbus driver OPC to communicate with my instrumnets, I edited the database number such as 41202 that has a Write attribute in my instrumnet manual, the OPC explorer got bad data, and the OPC server gave the illegal address alarm, when I input the address such as 41203 that has R/W attribute, it worked very well. Is there a way to fix this problem. When I used other OPC server, there was no this kind of problem. Thanks!

Thanks for your suggestion. I checked the Modbus manual of my instrument, the register is 16 bit. I tried to edit the data according to the Modbus data member in lookout modbus drivere server for several different member, but the OPC still gave me the illegal address. I think the problem may be produced by their attribute, for the address 1201 and 1202, they have the write attribute, for other addresses, they have W/R attribute, and they can be read or write through Lookout OPC server perfectly. when I used the demo OPC server from other company, it can work well, but it is not convinient for me to use Labview when I use that software. I prefer NI Lookout OPc server. I am using the Lookout 4.5. I am wondering whether the Lookout has some shortcoming when I
use the Modbus driver. Please give me any suggestion, is there any newest version of Lookout OPC sever? Thanks!

Lookout Logos ressource problem

Hi,
I have encountered a very weird behaviour using Lookout. We have a server (quad xeon 700) using a dual port intel networking card. Since we had some problems with one of the server we tried to use a backup server that is identical. Once we'd setup it (same configuration as the old server) we had a problem with Logos ressources.
- The first time we boot the computer Lookout was working. We have a monitor interface and everything was running, the console were communicating with the server.
- We use a Datasocket link between a LabVIEW server and the Lookout server on the same computer. When we start the communication between them Lookout crash randomly, no error messages.
- After a crash there is "red X" on the monitor screen and the
Lookout server Logos ressources are not accessible. What I have tried to do is to re-link the object that as "red X". It worked but when I restart Lookout the new objects have "Red X" on top of them.
- The following action make Lookout works again : Change the Network configuration (Unregister and register them back to the domain), Re-install Lookout, Re-install LOGOS. But when LabVIEW communicate with Lookout the same problem occur again.
I know that it looks very strange and I don't expect that someone else had this problem before. This system works on the other server (we have put it back and everything works fine except for some bugs). I wonder if someone could have an idea of items I could check.
Any help appreciated!
Thanks a lot!
Thrawn

Thrawn,
We need a little more information on your situation. Please indicate your software versions (Lookout and Logos) and Operating System of both PCs. Was the Datasocket connection in LabVIEW DSread, DSwrite, or front panel? Are you using the OPC protocol or the Lookout (logos) protocol? If you have not already, try connecting to the Lookout OPC server using Server Explorer. What is the result?
Regards,
Michael Shasteen
Applications Engineering
National Instruments
www.ni.com/ask
1-866-ASK-MY-NI

Can i use OPC server 5.1 to communicate over ethernet to an SLC505 PLC

i would like to use the industrial automation opc server to communicate with my Allen Bradley SLC505 over ethernet, but the ethernet or 505 options dont seem to be available, i have used lookout opc server 4.5 successfully to do this, but it requires server explorer to be connected to the server before labview datasocket will work. where version 5.1 connects automatically.

This particular Allen Bradley PLC is not supported by lookout 5.1 (see documentation) and KB on the web 2ZRB25HW.
hOWEVER, In the SLC500 object you could select ethernet and have limited success in Lookout 5.0. But this was removed in Lookout 5.1. If you replace the attached file with the 5.1 allbrad.cbx file with the 5.0 CBX file then you will have the same unsupported functionality in 5.0
Attachments:
allbrad.cbx ‏221 KB

Problems using Modbus TCP accessed by NI OPC Server

Hi there,
i'm using NI OPC-Server to access a measurement module. The buildup is quite easy, my system with NI OPC, a modbus gate and there the module connected with RS485.
There's a thermocouple to provide me some sample data.
But there's the point. I know, my data is in the Holding Registers and I can access them, but every data type I'm trying doesn't bring my my data out, just any other (sometimes Huge with e34, sometimes very small like e-13...) sorts, i can't understand.
The type provided by the module should be single precision.
In Lookout the address used to be is 41000 in Labview it's just 999 and in the "target" OPC-Server I get some values at 401000 but not useful.
I also get the same results accessing 301000 in different types.
Read/Write or Read Only is equal.
I've tried to tell my OPC that the values are Strings, Floats, Words, BCD and all other possible ways OPC offers me, but nothing results in a usable temperature.
I hope I missed something and you could suggest it.
Cateros
Solved!
Go to Solution.

Thanks for your reply.
in LabVIEW I'm using the provided Modbus Libraries. If I unbundle the Holding registers, my value appears at Holding Register [0], I'm type casting it to single and get the sample temperature. (Address 999->unbundle->typecast->value)
In NI OPC, I'm reading ( [depends on zero based addressing] 300999/301000 equal to 400999/401000) an already typecasted Holding Register [1] compared to LabVIEW (and the value changes in the second or third digit behind the comma and they are changing at the same time). Data type in the tag is float.
Another disturbing thing is even if I change in the options "using zero-based addressing in registers" my value does not change.
If I'm reading two addresses close to each other (as you mentioned 401000-401001) I'm getting an unknown data type and no results. How do I read multiple addresses without such errors? And how do I specify a special register to read?
Scaling should not be the problem, I am having three ways to get my value (FTP-Server on the gate (just a *.dat file with correct type), software the the module manufacturer (while measuring and configuring the module) and LabVIEW(as can be seen above)) .
Sadly, I have not found any useable modbus documentation about the module (just it can use modbus, you have the registers, you could read/write and fine)
When I'm adding a second couple to the module, in LabVIEW Values in Holding Register [2] and Holding Register [3] appear and are changing.
Cateros

Lookout OPC Client – Asynchronous I/O and Update Rate serious problems (Sequence of data)

I am using the Lookout OPCClient driver to connect to AB PLCs (EtherNet/IP protocol) and power measurement equipment (Modbus TCP protocol). The OPC server is the NI OPC Servers. The data that are read out from PLCs and PMs are energy meter readings, energy counters, power, voltage, current, frequency, power factor and el. energy quality measurements (THD). That energy meter readings are being stored in SQL database.
I am experiencing a serious problem regarding the accuracy of the meter readings. Several times per day, randomly, meter readings are losing the time sequence. For example, sequence is: 167, after few seconds 165, 166. In other words, present value followed by two previous old values. That generates a serious problem in our application that is expecting a naturally rising sequence of counter values.
Analyzing further, I isolated the problem to the connection between Lookout OPCClient and OPC Server. I made a simple application in Lookout 6.7 (opcproc.lkp, attached) with OPCClient parameters: NIOPCServers, OPC2, Asynchronus I/O, Update rate: 10000, Deadband: 0.0, that is reading just one tag from NI OPC Servers demo application (simdemo.opf).
By using OPC diagnostic tool from NI OPC Servers I record the sequence of OPC requests and responses. I found out that OPCClient sends every 2.5 sec “IOPCAsyncIO2::Refresh2()” call that is request for refreshing of all items in one OPC group. Few milliseconds later OPC Sever responds with callback function “IOPCDataCallback:: OnDataChange()(Device Refresh)” that actually refresh the data.
This periodic sequence is intrinsic to the OPCClient and cannot be disabled or changed (by my knowledge). This sequence is periodically interrupted by “IOPCDataCallback:: OnDataChange()” caused by update rate parameter of OPCClient (client is subscribed to server for periodic update of changed items).
In the case of demo application on every 4 refresh callbacks caused by refresh requests (2.5 sec) there is one update subscription callback determined by Update rate (10 sec).
QUESTION 1:
What is the purpose of update sequence and update rate when we have every 2.5 sec fresh values?
PROBLEM
The problem arises when we have a large number of items in OPC group. In that case the OPC Server starts to queue refresh requests because they cannot be fulfilled in 2.5 sec time because of large number of I/O points that must be scanned. At the same time update subscription callbacks are running at the period determined by Update rate. I observed in my production system that regular update callbacks has higher priority than refresh callbacks from the queue. That causes the loosing of timed sequence of data. After the update callback with fresh data, sometimes follow one or two refresh callbacks from queue with old (invalid) data. By adjusting Update rate parameter (1 hour, 2hours …) I can postpone the collision of data refreshes but I cannot eliminate it. Furthermore, the 2.5 sec automatic refresh are large burden for systems with many I/O points.
QUESTION 2:
Is there a way to disable automatic refresh request every 2.5 sec and just use update requests determined by Update rate?
QUESTION 3:
Is there a way (or parameter) to change the period of automatic refresh (2.5 sec)?
This problem is discovered for Lookout 6.5, 6.6 and 6.7 so I could say it is intrinsic to OPCClient. If I use synchronous I/O requests there is not an automatic refresh, but that is not an option for large systems.
Thanks!
Alan Vrana
System engineer
SCADA Projekt d.o.o.
Picmanova 2
10000 ZAGREB
CROATIA
T +385 1 6622230
F +385 1 6683463
e-mail [email protected]
Alan Vrana
SCADA Projekt d.o.o.
ZAGREB, Croatia
Attachments:
opcproc.zip ‏4 KB

The physical connection from LV to the switch is (I believe) copper crossover to fiber converter into a switch. Then, fiber from the switch to the end device (relay). The relay has all of the typical modbus registries and has been verified by inducing signals in to the system and measured/polled in LabVIEW and observed Variable Monitor. I am working with LV 8.2 and 8.5.
An OPC server would only add an additional translation of addressing within the configuration. The only real draw back would be the network overhead required to do this processing and not being representative of the end design configuration.
I will reiterated my question in another way:
I must answer the question to management that relates to data collection, test results and analysis; how often are you polling the client in relation to the outcomes measured? At this time I can not point at any configuration in the set up and execution that directs the data framing rate. I only measure the traffic and work with results. This needs to be clearly identified based on the relay modbus/tcp design capability of supporting an fixed number of client requests per second.
For testing purposes, I would like to be able to stress the system to failure and have prove capabilities with measured data. The present problem is that I have no basis to establish varying polling rates that effect the measured data transmission.
This raises another question. What handles the Variable Monitor data requests and how is this rate determined?
Thanks for your interest in my efforts.
Steve

Lookout opc problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem?

doug:
You may want to repost in the Lookout board:
http://forums.ni.com/ni/board?board.id=190
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Lookout opc or link problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem? Thanks!

This problem is fixed by lookout 6.0.2 updates. It can be downloaded from http://joule.ni.com/nidu/cds/view/p/id/506/lang/en
You need first to login MyNI, and then download lo602_updates.zip. Unzip it and copy all files to lookout folder.
This update is applied to Lookout 6.0.2 server system. You don't need to copy these files to client system.
Ryan Shi
National Instruments

Problems connecting to a remote OPC server in write mode using CWDataSocket control

Hi.
I have been struggling with an odd feature when trying to connect to a remote OPC server using CWDataSocket control, though I'm not sure if it's a CWDataSocket related problem. But anyway, the following error occurs: "Active: Can't write data." Error number: "-2147467259". Now, when I connect to a local OPC server
and write some data and then again connect to the remote server, no errors occure and reading and writing work fine. The same error occurs when I try the same in LabVIEW. What could be the problem?
No errors occure when I connect to the server with some other OPC client application.
Thanks in advance.
- Asko -

The ConnectTo operation (as are all DataSocket operations) is asynchronous. In order for it to complete, you must process Windows messages after calling it and before calling another operation. Is it possible that you are trying to write data before the connection operation is complete?
One easy way to test this would be to put the ConnectTo and the Write in separate control callbacks, cause ConnectTo to be called, wait a while, then cause the Write to be called. Alternatively, you could do something like the following:
dsWrite.ConnectTo txtUrl.Text, cwdsWrite
While Not ((dsWrite.Status = cwdsConnectionActive) Or (dsWrite.Status = cwdsConnectionIdle))
DoEvents
Wend
If this is the problem, then you'll probably want to go with the
second option. In a production system, you should include a timeout in the While loop so that if the connection actually cannot be made, you are not stuck in an infinite loop.

Omron OPC Server with Lookout 5.0

I am trying to set up a Lookout 5.0 application using the OPC Client, connecting to the Omron OPC server, CX ServerOPC. When I add the OPC Client, I find the server on the drop down list, but when I click 'OK' to create the OPC client object, once it connects to the OPC server, Lookout crashes. I get the message that Lookout.exe has encountered a problem and has to close. Has anybody used this server before and seen this problem? Any hints as to what could be incorrect in the client or server settings?

Hi,
What happens if you connect to the Omron OPC server from the National Instruments Server Explorer? Do you access to the OPC items succesfuly in Server Explorer?
Please also check the Tutorial linked below:
http://zone.ni.com/devzone/conceptd.nsf/webmain/B0CC5FE5CBC5727F86256808006AD802?opendocument
Hope this helps.
Best Regards,
Remzi A.
National Instruments

Opc server 2011 V5.5 in Lookout 6.6

Hello,
I am using Lookout 6.6 with the OPC-Server 2011 V5.5.
The NI-Server is reachable via Lookout and via the integrated OPC-Quick-Client. But if I am using an other Client such as the OPC Data-Spy or PROFILAB,
the server is not reachable, the server name is displayed in the list, but can not be accessed. Other installed OPC-Servers on my PC can be accessed by every client. Do I need to have a special licence for the NI OPC Server that came with the Lookout 6.6 Software Package? I am using Windows 7 Home 32bit.
Thank you for any advice
Greetings
Claude
Solved!
Go to Solution.

Hello,
Thanks for the reply, I found now the information to in the Licence Manager.
It is a pity , but I have to accept.
(Even my Labview 2009 Educational Version can not connect)
Greetings
Claude

Can Labview v7.0 talk to a Micrologix 1100 PLC via Lookout Protocol Drivers OPC Server v4.5?

Micrologix 1100 <-> Lookout Protocol Drivers v4.5 <-> Labview v7.0
Hello all,
I am helping a local company to use their existing seat of Labview v7.0 to talk over Ethernet with a new Micrologix 1100 PLC. We were hoping to use their existing OPC server that came with Labview (circa 2000) so that they do not have to purchase a new OPC server. Their Labview package is the "NI Developer Suite Professional v7.0 Control Edition" which comes with a "DSC Module" which contains an OPC server called "Lookout Protocol Drivers OPC Server v4.5 (build7)". This software came out several years before the Micrologix 1100 was born, but OPC is supposed to be a cross-platform, cross-generation standard isnt it?
So, when I set-up the OPC server, it asks me which type of PLC I have and the only choices are AB_Logix (Micrologix 1500), AB_PLC2, AB_PLC5 (15 different flavors), and AB_SLC500 (5 different flavors). Can I use one of these that might be similar to the ML1100? I definitely want to use ethernet, not serial.
My application is just reading and writing a couple of variables from/to the Binary, Integer and Float data storage locations approx once per second.
Does anyone see a problem doing this without having to upgrade the OPC server to something that "officially supports" the ML1100 (Like Kepware)?
Thank you very much!!
frenchy

Hi Frency,
You can always just try the 1500 and cross your fingers! We could try to speculate on the forum, but a quick test would certainly be a better use of time. However, I do recommend that if you can upgrade the OPC server to one that supports the 1100 driver you should do so. Kepware and NI-OPC Servers both support this device.
Cheers,
Brian A.
National Instruments
Applications Engineer

NtfsServer problem on Windows 2000 Advanced Server

I've installed Oracle 8.1.6 and iFS 1.0 on Windows 2000 Advanced Server. Everything else seems to work fine with iFS, but the NtfsServer always fails to start up.
Is this a compatibility problem between Oracle and Windows 2000? I have no drive letter O: so it should be free for iFS to use.
Here is the last entry from NtfsServer.log:
Sun May 28 19:47:07 GMT+03:00 2000
iFS NT File Server Version 1.0.8.1.0 Production
Sun May 28 19:47:07 GMT+03:00 2000
ServerName(id): NtfsServer(6508)
server: NtfsServer
username: system
AnonymousUsername: guest
DriveLetter: o
NtfsSessionCache: 40
OptimizeStartup: true
LogLevel: 1
LogStackTrace: true
net start OracleIfsd
Return code = 0
ifsmount o
Return code = 1
SR Event: ID:6757 PENDING SPECIAL SUBTYPE:13 6766L
SR Event: ID:6757 COMMIT SPECIAL SUBTYPE:13 6766L
(0) Unable to open IFS device
ifsdismount o
Return code = 2
Cache performance for session cache
CurrentSessionCount=0
HighestSessionCount=0
CurrentSessionCache=0
Performance of readonly connection pool:
MinimumSize=5
TargetSize=20
MaximumSize=100
TargetSizeTimeout=1000 ms
MaximumSizeTimeout=10000 ms
CurrentSize=5
AllocatedSize=0
ImmediateAllocationCount=4
DeferredAllocationCount=0
FailedAllocationCount=0
AverageAllocationTime=0 ms
Performance of writeable connection pool:
MinimumSize=5
TargetSize=20
MaximumSize=100
TargetSizeTimeout=1000 ms
MaximumSizeTimeout=10000 ms
CurrentSize=5
AllocatedSize=0
ImmediateAllocationCount=2
DeferredAllocationCount=0
FailedAllocationCount=0
AverageAllocationTime=0 ms
Cache performance for S_LibraryObject cache
CACHESIZE=65
OBJECTCOUNT=65
PUTCOUNT=130
REMOVECOUNT=0
FINDCOUNT=370
HITCOUNT=237
MISSCOUNT=133
HITRATIO=0.6405405405405405
MISSRATIO=0.35945945945945945
Cache performance for FolderPath cache
CACHESIZE=0
CacheSizeEstimate=0
ACCESSSEQUENCE=1
SequenceAtLastPurge=0
PUTCOUNT=0
REMOVECOUNT=0
PURGECOUNT=0
FINDCOUNT=0
HITCOUNT=0
MISSCOUNT=0
HITRATIO=1.0
MISSRATIO=0.0
Cache performance for committed S_LibraryObjectData cache
CACHESIZE=329
CacheSizeEstimate=329
ACCESSSEQUENCE=3
SequenceAtLastPurge=0
PUTCOUNT=329
REMOVECOUNT=0
PURGECOUNT=0
FINDCOUNT=685
HITCOUNT=356
MISSCOUNT=329
HITRATIO=0.5197080291970803
MISSRATIO=0.4802919708029197
Cache performance for LibraryObject cache
CACHESIZE=65
OBJECTCOUNT=65
PUTCOUNT=65
REMOVECOUNT=0
FINDCOUNT=73
HITCOUNT=8
MISSCOUNT=65
HITRATIO=0.1095890410958904
MISSRATIO=0.8904109589041096
iFS NT File Server terminating
null

I have the exact same symptoms on a Win2000 Pro development machine. fails at ifsmount,same as you...

Windows 7 lookout opc server problems

Similar Messages

Maybe you are looking for