Error -2147220224, DataSocket

I have written a program in C++ which uses the functions in Dataskt.dll (the Datasocket functions). I have Labview 8.6 and the program works fine on my computer, but when I pass the program to someone who is running 8.5, I get error #-2147220224 with no explanation other than system error. I think that this error has to do with the cviauto files, but when I transfered them from my computer onto the other one it still generated the same error. The versions of the DataSocket that each computer is trying to access are the same (4.5 (0)).
Does anyone know what files I need to bundle with my program in order for this to work?
Thanks,
-Jeff VT
Solved!
Go to Solution.

Sorry for the confusion, let me try to explain it again.
I have these files for DataSocket: Dataskt.dll,Dataskt.lib,Dataskt.h
I have written a program in C++ which uses the functions in Dataskt.dll. I have then exported this C++ program as another type of dll (.xop) which IGOR can use. I then used the functions in IGOR to get live data being published to a DataSocket Server in the form of strings and arrays.
When I developed the C++ program and the xop file on my computer it worked fine (I have Labview 8.6). But when I tried to implement the xop on another computer (that does not have Labview 8.6, usually 8.5 or 6.1) the IGOR program crashes and gives an error saying that the xop errored and -2147220224 is the error code. The error is not in Labview because it is not running at the time. If I download the demo version of Labview 8.6 on the computer then the program works perfectly, even after the demo expires.
The user never interfaces with Labview or C++. The whole interface is in IGOR. What I need to know is: Is there a particular file that has changed in Labview 8.6 which will allow me to distribute the xop without having to install the full demo of 8.6 if I include it in my install package for the xop?
Thanks,
-Jeff VT

Similar Messages

Error 42 : Datasocket Read Function

Hello,
I have a problem about DataSocket Read Function . I want to read some data from OPC server. I read data and its value 100 as seen in picture dOPCexplorer . But when I give a start Labview .exe as seen Santral Veri Kayıt.vi, I get error 42 about DataSocket Read. Can anyone help me when solving this problem?
Attachments:
LABWIEW.PNG ‏89 KB
OPC SERVER.PNG ‏109 KB
OPC EXPLORER.PNG ‏132 KB

What is the OTHER error on that front panel about? Could the two errors be related?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error using datasocket

Hi,
I am using datasocket with an Applicom card to communicate with a Siemens PLC. When I run the VI I get an error: -10734796672 I can find no mention of this error. Can you help?
Thanks
Tom

take a look at the diagram , and see where the error is thrown. To do this, go to the block diagram >> turn on highlight execution >> run the VI >> watch to see where the error occurs.
If the error comes out of a sub VI, then open stop the main VI, open the sub VI, place a breakpoint on the diagram of the sub VI, return to the main VI and run the main VI again (without highlight execution on). This time the code will pause at the break point, when you can turn on highlight execution, and unpuse the code. Watch to see where the error is thrown.
Once you know where the error is thrown, you will know how to proceed. If the error comes out of a LabVIEW primative (a block diagram object with a yellow background that doesn't open when you double click on
it - like DataSocket Read in LV 7), then have an application engineer take a alook. If it comes out of a call to the Applicom card (typically through a Call Reference Node) then you know that the card is having an issue, and you can look at stuff like board configuration (in devise manager), and what parameters you need to pass to the board via the provided driver.

Error with DataSocket in a dll

I want to use DataSocket in a dll built with LabVIEW7.
For testing, I call the dll in LabVIEW.
What is wrong with my attached example?
A DataSocketOpen allways brings time out (Server on the same machine).
Any idea?
Thank you for helping!
Attachments:
DataSocketDLL.zip ‏33 KB

Now it works !
I found several little mistakes not worth to mention.

FTP Datasocket Error

I am trying to figure out FTP through datasockets. I have written a very simple vi (attached) that looks like it would work based on what I have read. I am trying to FTP from the ni recommended location of ftp://ftp.ni.com/incoming/readme.txt[text]. I continue to get an Error 1184 : Datasocket path not found, FTP login incorrect, or no FTP write permission. I then downloaded an example datasocket ftp vi and recieved the same error. Any hints? Could a firewall or something be causing this?
Thanks,
Strass
Attachments:
simpleftp.vi ‏25 KB

The problem is that you are trying to read out of a directory that the outside world only has write permissions on.
(which is sorta' why it's called "incoming" )
Mike..
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Datasocket shared variable api

I ran into the following the other day whilst debugging some code:
We had a type mismatch when sending data however, when testing the DataSocket API did not return this error information, nut the Shared Variable API did.
DS just returned default data with a change in the timestamp)
This got me thinking:
Is using Shared Variable API the way to go? Is it a better (more refined) API?
Are there different reasons for using one over the other? (I do like that DS's refnum is not datatyped, which means that I have to provide the datatype on the read as opposed to the SV-API).
With respect to the type mismatch, I found that I could actually initialise the Variable with either datatype and it worked (only) for that datatype.
It would only error when the other datatype was used.
Does that mean the Variable does not know what its datatype actually is when a cluster is used?
Cheers
-JG
Certified LabVIEW Architect * LabVIEW Champion

charris wrote:
I'm not sure I quite follow your question regarding datatypes. It looks like the error is being returned because a variable cannot contain a cluster. You can do arrays, but not clusters, so that's probably why the SV API is complaining about the type input.
Hi Caleb
My question was relating to the fact that if the variable is not initialized on one PC, and I try reading from it on another PC, specifying the datatype to read back, then I get an error using the SV API but no error from DataSocket.
My use case was for a Cluster.
I didn't check whether it was Cluster-specific or occurs for every datatype.
I assumed Cluster-only as Clusters differ when setting up the Shared Variable.
I.e. All standard datatypes are available in a drop-down, but you need to select Custom Control for a Cluster.
So the last question was asking could I theoretically use any Cluster with a SV-Cluster as long it is the same when I do a Read and Write.
I.e. When using the DS/SV-API the Shared Variable does not know (/have information on) what its datatype actually is when a Cluster is used - it relies on what datatype is used to initialize it?
Hope that makes sense.
Cheers
Jon
Certified LabVIEW Architect * LabVIEW Champion

Datasocket error when network cable unplugged

Hi,
I'm having problems with my datasockets. I have applications running on multiple computers, which publish data to a datasocket on the localhost. Whenever we unplug a network cable, or the network goes down, the datasocket write function reports the following error code: -2147014843 in Datasocket Write.
I can't find any information about this datasocket error code. Can anyone give me advice on how to find more information about this error code?
The result is that whenever there is a network issue, we need to go and resolve it, then we need to log onto each computer (25+) to get the datasockets working again.
Also interesting to note is this problem has only presented itself since upgrading the computers from NT to Win2k & WinXP.
Thanks for any help that can be given.
Slade Squire

Hi again,
Just in case anybody else looks here, and have a similar problem...
The error code we saw was related to the networking functions of Windows. In particular, the reason we did not see this problem in Windows NT, but it started appearing in 2000/XP, is the media sense functionality of Windows 2000/XP. In 2000/XP, if there is no connection detected, the OS dumps the IP stack, and with it, the IP address. As a result, when we try to write to a datasocket on the computers IP address, Windows returns an error, since there is no IP address anymore.
To resolve this issue, we turned off Media Sense on the affected computers. We followed the instructions on this page:
http://www.windowsnetworking.com/articles_tutorials/Disable-Media-Sense-TCPIP-Windows-XP.html
Now, when the network drops out, we keep the same IP address, and so the datasocket can continue to write to the local computer, without any problems.
Regards,
Slade Squire

Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi, help? please!

Hey guys, I am new to LabView and I have thought myself everything that I know. I am an undergraduate student at NC A&T.
Okay so I took a peice of code that I acquired from Bristol, and it's for a Bristol Wavemeter V1.22. I first edited it to get a graph in there to show the data, and get a slope and Y intercept. Now I am trying to connect it to a computer that controls a COntinuum ND6000. We have existing code for the ND6000 that lets the two computers connect. I took the code out of there that was the part that connects them and now when I wired everything up, I get the "Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi" error message. it states; Possible reason(s):
LabVIEW: Serial port receive buffer overflow.
=========================
LabVIEW: The network connection was refused by the server. For TCP/IP, make sure the server is running and listening on the port you are trying to use. Firewalls can also cause a server to refuse a connection. For VI Server, make sure you have enabled VI Server from Tools>>Options>>VI Server:Configuration."
I tried making sure everything in the configuration was correct and it all is. Can you guys please help me?
Thank you.
I have attached the folder that it is located in because you do have to have the library function. The file is located in the Bristol Wavelength Meter V1.22\Programming Interface\LabVIEW example I.
Thank you again!
Solved!
Go to Solution.
Attachments:
6.jpg ‏153 KB
7.jpg ‏112 KB

So I went through and realized that I had the wrong port typed in by 1 number, I changed that and put in the correct port for the TCP address. Now when I run it I get this error message 66....
"LabVIEW: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server:Machine Access on the server side."
Any help?? I checked the Server Machine access and all of them are set to allow.

Datasocket create item error

I am trying to conect two labview program via datasocket. One run on Linux and the other on windows 98. The datasocket server runs on the window PC and has been opened to everyhost for item creation and reading via the datasocket server manager.
My problem is that the linuw labview can read item but not create one . When i run my program in linux the datasocket signal in my indicator turns green during on second and then red (Error : Not permited to create new item). meanwhile the datasocket server records a new process connected and increases the number of packet received. Someone has an adea of what happens ?

I tested this in 6.0.2 using the DataSocket Writer example on Linux and the DataSocket Reader on Win 2000. The Writer returned Error 63: Connection Refused. I tested again in 6.1 and the Writer VI worked perfectly.
Any possibility of updating LabVIEW to 6.1 or previously defining your datatypes in the DS Server Manager?
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

OPC client using DataSocket - Error 0x80040154

hi everyone,
i am setting up OPC comm between LabVIEW 2010 and SMA OPC Server. they are in the same machine. i have followed all DCOM settings there, and i can view and write data of SMA OPC through MatrikonOPC.
then i start using DataSocket Select in LabVIEW. while i run the vi I can see a pop up window showing all running OPC servers in that PC. but while i double-click my SMA OPC server or other OPC servers, i always get this error -
error code - 0x80040154,
Class not registered
The server is not properly registered on the machine.
Try running <server>.exe /RegServer for an executable server, or RegSvr32.exe <server>.dll for an inproc server.
i tried following the instruction of last line, but never succeed.
Looking for any kind of help. Thank you very much.

Hi Daniel,
Thanks for submitting your question. This error occurs because your OPC server is not registered. For example, here is an article that explains how you can register our FieldPoint servers:
How Do I Register an OPC Server Without LabVIEW?
http://digital.ni.com/public.nsf/allkb/662939B4C756729286256C24005530B9?OpenDocument
Yours might require a different method so it is worth contacting the manufacturer of your OPC server and ask them how you can register your server. Uninstalling and reinstalling the OPC software will sometimes take care of any registration issues.
I also thought you would find these links useful:
http://zone.ni.com/devzone/cda/tut/p/id/3978
http://digital.ni.com/public.nsf/allkb/E9887094890516EB862570A700486F0E?OpenDocument
http://zone.ni.com/devzone/cda/tut/p/id/7450
Hope this helps.
Thanks
Mahdieh G
Applications Engineer
National Instruments UK&Ireland

OPC DataSocket error 42 in writing negative values

I was playing around with OPC and using the DataSocket pallete. Although I've used it reliably for a while and am content, I was baffled by one error. I was hoping someone could explain why this error occurs or how to solve it.
In the NI Distributed System Manager I've created an Shared Variable of the type single, with Read/Write access.
Problem
When writing a value less or equal to 0 to an OPC URL, I get an error 42. When using the equivalent PSP URL, I don't get it.
Using this VI snippet code.
I get these paths and errors:
This error 42 comes for all values below zero and for zero. For all positive values I don't get this error. What's the reason for this behaviour? In my humble opinion this is not wanted behaviour, as OPC tags should accept the whole value range of the single.

White spaces are allowed in OPC URLs, so that cannot be the issue.
I've tested with another LV2013 computer and NI Distributed System Manager 2013 and got the same errors. However, when I tested it on a LV2012 and NI DSM 2012 it was all working. Quite strange.
Now I'm wondering if it's something local or that the bug was introduced in the 2013 distribution and if it has been solved in the 2014 version ...
Could someone test it on LV2013 and/or LV2014, just to check if the problem occurs for other installations in LV2013 and if the problem has been solved in LV2014? Please indicate LV version and DSM version.

I am using datasocket in seperate vi, with error catching, but network slowdown causes labview to crash without any error message ...

I have a master computer setup as a datasocket server with several vi's that publish. I have about 5 other computers each with a vi that reads the data socket publisher. The interval at which the 5 vi's read is every 15 minutes, concurrently. It seems that when ever there is a network slow down, LabVIEW crashes catastrophically, even though I have timeouts in the datasocket readers. Is this error related to the datasockets not being able to handle the slow down or something else? Should I use another technique - if so - which is more reliable (FTP, TCP/IP?). This bug has been hounding me for several MONTHS.

One thing I forgot to mention - the 5 datasocket readers are also web servers, serving out the front panels to the web after getting updated. Well, after weeks of trial and error, would you believe that if I turn off the web server logging, everything works fine. I have had it off for a week now and no crashes. I first discovered this by realizing that if I turned off the web server everything ran fine (which would be totally useless for my application), so then I searched this site and found an off the cuff remark about the web server logging function causing crashes for an unrelated problem. I figured what the heck, I'll disable it and see what happens. So far so good, I am still keeping my fingers crossed ...

DataSocket Data Error

I have a large LabView application (Win 2000) with which I need to communicate from another machine (Win XP Pro) using the DataSocket Server (dstp).
I do not have LabView on the Win XP machine, so I compiled a small LabView application to run on it. I have installed the Labview Runtime Engine 7.1 on the Win XP box corresponding to my version of LabView on the Win 2000 box. The data being transferred is cluster data (booleans, doubles, and ints) that has been flattened into a string.
The problem is that some of the data is being corrupted some of the time. For example, one of the numeric fields has the value of 1000, but it is being displayed on the Win XP box as 831. If I change the data to say, 1100, it is displayed correctly. The corruption is predictible, and depends on the data values. I am not getting any errors on the connection.
If I run this same application on the Win 2000 box, it runs fine. Is there some compatibility issue between Win2000 and Win XP for compiled applications? What else might I be doing wrong?

Brian,
The attached send and receive VI's show the problem. Again, when I run both on the same machine, everything is fine. When I run them on different machines, then I get data corruption. The most common error is setting Number of Samples on the TestSend.vi to 1000 results in 831 being displayed on the other end. As stated earlier, I am compiling these into executables, and 1 machine is XP while the other is Win2000. LabView is 7.1 with the same runtime engine. I have noticed that both machines have other versions of the runtime engine installed as well. I assume the executable knows which version of the runtime engine to launch?
Message Edited by schlew on 01-20-2007 10:12 AM
Attachments:
TestSend.vi ‏49 KB
TestRcv.vi ‏49 KB

"NI Network Browser Error!" When Using 'DataSocket Select URL'

We have two LV 7.1.1-built executables running on two different computers that are networked together. Each executable starts the DataSocket Server on their own computer and then attempts to read from the other computer's DataSocket Server. Everthing works well if both computers are running XP SP2 or SP3.
The problem occurs when one of the OS's is Windows 2000 SP3. The executable on the XP computer can see the DataSocket items in the 'DataSocket Select URL' window on the Windows 2000 computer. However, on the Windows 2000 computer, if you open the 'DataSocket Select URL' window, and try to browse the DataSocket items on the XP computer, one of the following dialogs appears:
NI Network Browser Error!
Cannot enumerate items in this hierarchy
Cannot open a network enumeration
0x000004b8
An extended error has ocurred.
OR
NI Network Browser Error!
Cannot enumerate items in this heirarchy
Cannot open a network enumeration
0x00000035
The volume path was not found
This is usually followed by a DataSocket Read error of 214701483 (this looks like a COM object error, but for once, Google didn't have anything to say about it).
There was a similar post to this one in which Manuel Wielander suggests setting the 'Authentication Level' to 'Connect' and the 'Impersonation Level' to 'Identify'. He also suggested adding 'ole.AuthnLevel=1' to the executable's ini file. None of these suggestions work. I have also added every exception imaginable to the Windows XP firewall with no luck.
Anyone dare to step into the networking abyss with me on this one? Much thanks in advance for any help or suggestions.
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Hello Archimedes,
This problem is a bit difficult to track down. I have Win 2k SP4 and WinXP Pro computers and am unable to reproduce the issue at the moment. However, I have found information that this issue has occurred in the past. In some instances it appears that changing the DataSocket Select URL.vi's Preferred Execution System to something other than "user interface" (eg. "Same as caller" or "standard") from VI Properties>>Execution resolves the problem. However, this is not a guaranteed workaround. R&D is aware of the problem and is working to fix it. I apologize for any inconvenience.
Best Regards,
Chris J
National Instruments

Datasocket write error when launching an application

I have invested a lot of time in an applications that uses a number(>100) datasocket connections to exchange data between an application and plug in modules(called vis). I have two errors relating to the datasocket server for this application: 1.) When the server is started for the 1st time by calling the datasocket server control vi inside my code, I run a write function inside a loop for 10 iterations at 10ms intervals. No matter how I modify the number of iterations and frequency, the write function occasionally errors on first start up., and 2.) When I run the application using the Labview runtime engine(version 6.0.3) I see the same problem in addition to datasocket reads and writes not updating correctly. They do
not error but they do not exchange the correct data like they do when the full version of labview is installed on the machine.
Has anyone seen these problems before? Your help will be greatly appreciated.
Thank You,
Mike W

The export/import option for 3.0.7 are somewhat little brittle .
What I can suggest you is to upgrade your existing 3.0.7 to 3.0.9 atleast (if not 9.0.2) .
This version has got lot of new features which you are looking into.

Error -2147220224, DataSocket

Similar Messages

Maybe you are looking for