Weird behaviour, dll calling

Hi,
We've run into some slightly buggy behaviour when calling dlls., and we would like to understand or at least fix it. (Unfortunately we aren't allowed to upload running files, but I've got some screenshots)
The program runs on two systems, both identifically configured, LV2010, WinXP32.
The situation occurs when loading a dll.
The dll and loading is okay with system A, with system B it doesn't work.
The problem is the following: Whenever we close the VI, it changes the name of the dll from api32.dll to Api32.dll.
This doesn't happen with system A, but it definitely stops the software from finding the dll.
I've tried to change the path into a constant input, but it doesn't seem to help.
Does anyone have an idea what is happening?
Thanks,
Birgit

Hi,
thanks for playing around with this (and the information that it is not case-sensitive, but the changing behaviour is still suspicious), with loading the dll I mean the call inside the block diagram.
We've set it up on two identical systems with iamges (basically same computer, same OS, same LV, just a few hundreds of kilometers apart) a year ago or so. Theoretically, they are identical, but I'm starting to suspect a update or something similar. A clean reinstall is only a last resort, though.
There's no error message, the subvi just gives you the default values, as configured, but that external library doesn't seem to have LV-compatible error handling.. But I'll have someone work on extracting more information on that and can get you back tomorrow (not in the office today..).
I've never had problems with my own dll-dependencies, they just worked ... can you name me some places where the problem could hide?
Thanks a lot for your time,
Birgit

Similar Messages

HTML Link -AS2 fine, AS3 weird behaviour

Hi Guys, I'm working on a project at the moment, and am
seeing weird behaviour with the way my swf handles html links
inside dynamic textboxes. When rendered as a AS2 file, the link
works on a release as expected. When its inside a AS3 file the link
will only work if the user right click and chooses 'open in new
window' was there a change in behaviour how AS3 handles these
links, or is there now an declaration needed to be made to allow
these link to have the old behaviour?
The project calls for xml data and embedded in that is a html
link. Originally I thought it might have been the way I'd formed
the xml so I tried with a hardcoded version instead (dynamic
textbox, add text -> highlight -> add link through properties
tab). But I still see the same behaviour between the as2 and as3
versions.
Any help would be greatly appreciated.
Cheers.

Actually, the ''href'' attribute is supposed to direct the browser to a new URL, etc., not run a script. Instead, use the ''onclick'' event attribute:
''<a onclick = “$('.div-feedback').fadeIn();”></a>''.
Happy coding!

Weird behaviour in RMIClient

hi all,
i am experiencing a weird behaviour with my RMI Client....
my RMIClient has two methods
init()
callRemoteMethod()
ideally in the init() i should locate the RMIServer, and in the callRemoteMethod() i should call one of hte methods of the RMIServer
the problem is that it does not work!!
my RMIClient code works ONLY if i put the initialization of the RMIServer and the call of one of its method in the SAME method
is it normal that it happens like htis????
can anyone give me some hints??
thanx in advance and regards
marco

hi all,
i solved the problem...i was initializing hte RMI server twice.....
sorry for bothering
regards
marco

SQL MP - SPN Status monitor weird behaviour

Hi all,
I have a strange behaviour with the monitor that checks SQL 2008 SPN status. More precisely I have a weird behaviour with the script used by the monitor. The script is GetSQL2008SPNState.vbs. I configured the SQL monitoring profile (which is used by the
script) with a domain account with necessary rights.
Let's say I have a SQL Server called SQL1. SQL1 is in domain AD1. I have a forest called contoso.com with two child domains AD1 and AD2.
On SQL1 I sometimes see events 4001 generated by this script that mentions a problem to connect to WMI namespace (which is healthy, I checked with wbemtest). The event says that it couldn't connect to
\\SQL1.AD1.contoso.com.AD2.contoso.com\root\blabla. I have no idea why it is using that broken FQDN.
I made some research into the script and understood the following:
The script has the SQL server FQDN as parameter (here SQL1.AD1.contoso.com)
It searches the defaultnamingcontext by doing
Set oRootDse = GetObject("GC://RootDSE)
sRootnamingContext = oRootDse.Get("defaultNamingContext")
It converts the defaultnamingcontext variable from "DC=a,DC=b,DC,c" to ".a.b.c"
It checks if the defaultnamingcontext is in the fqdn and if not it appends it at the end of the fqdn. Dunno if I'm clear here so here are examples of good and bad behaviours:
GOOD:
FQDN is SQL1.AD1.contoso.com, defaultnamingcontext gives AD1.contoso.com, AD1.contoso.com is in SQL1.AD1.contoso.com so the script go on using SQL1.AD1.contoso.com and it's ok...
BAD:
FQDN is SQL1.AD1.contoso.com, defaultnamingcontext gives AD2.contoso.com, AD2.contoso.com is not in SQL1.AD1.contoso.com so the script go on using SQL1.AD1.contoso.com.AD2.contoso.com and it's broken...
I didn't mention earlier but the runas account I use is from domain AD1. It's called AD1\svc_scom_mp
My question is how comes sometimes (sometimes means during 6 hours, a whole day, nothing reccurent :( ) The defaultnamingcontext gives me the fqdn of the other domain ??
I'm wondering if this can be due to the fact that I also have an account called svc_scom_mp in AD2 but I'm 100% sure it's not used here as it's not targeted nor distributed to any AD1 computers.
I guess it's more an AD problem than anything else.
Any ideas ?
<a href="http://myitforum.com/cs2/blogs/fdufour/default.aspx">Supervize Me ©</a>

Hi François
I tested GetSQL2008SPNState.vbs on my POC with a similar configuration (one root and two child domains) and i have got the same issue. I think the root cause is the Server less binding (GC://RootDSE) used to search defaultNamingContext.
With Server less binding, GC name relies on
DNS round robin to find a GC, if a GC from another domain is returned the defaultNamingContext will be the other domain.
You can check GC resolution with nslookup:
nslookup gc._msdcs.contoso.com (the root domain)
repeat the command to see the round robin result.
I wrote a vbscript to test it:
This script search all GC and search defaultNamingContext with GC provider server less and server name binding. With LDAP Provider the right domain name is always returned.
=============================
ldapFilter = "(&(objectClass=nTDSDSA)(options:1.2.840.113556.1.4.803:=1))"
Set rootDSE = GetObject("LDAP://rootDSE")
configDN =   rootDSE.Get("configurationNamingContext")
Set ado = CreateObject("ADODB.Connection")
ado.Provider = "ADSDSOObject"
ado.Open "ADSearch"
Set objectList =   ado.Execute("<LDAP://" &configDN& ">;" & ldapFilter & ";distinguishedName;subtree")
' GC Server less binding LDAP
      Set oRootDse = GetObject("LDAP://RootDSE")
      If Not (oRootDse Is Nothing) Then
            sDefaultNamingContext = oRootDse.Get("defaultNamingContext")
            wscript.echo "Server less binding:
LDAP://RootDSE"
            wscript.echo "   DefaultNamingContext found: " & sDefaultNamingContext
             wscript.echo " "
      Else
            wscript.echo "   NOT found: "
      End If
' GC Server less binding GC
      Set oRootDse = GetObject("GC://RootDSE")
      If Not (oRootDse Is Nothing) Then
            sDefaultNamingContext = oRootDse.Get("defaultNamingContext")
            wscript.echo "Server less binding: GC://RootDSE"
            wscript.echo "   DefaultNamingContext found: " & sDefaultNamingContext
             wscript.echo " "
      Else
            wscript.echo "   NOT found: "
      End If
wscript.echo "Server Name binding: GC://<ServerName>/RootDSE"
While Not objectList.EOF
    nTSDSA = objectList.Fields("distinguishedName")
    serverDN = Mid(nTSDSA, 18)
    Set serverObj = GetObject("LDAP://" & serverDN )
    WScript.Echo " GC name:" & serverObj.dNSHostName
    ' GC Server Binding
    Set oRootDse = GetObject("GC://" & serverObj.dNSHostName & "/RootDSE")
      If Not (oRootDse Is Nothing) Then
            sDefaultNamingContext = oRootDse.Get("defaultNamingContext")
            wscript.echo "   DefaultNamingContext found: " & sDefaultNamingContext
      Else
            wscript.echo "   NOT found: "
      End If
    wscript.echo " "
    objectList.MoveNext
Wend
======================================================
Cordialement

Weird behaviour with inlined SubVI's

Every now and then I've ran into some serious weird behaviour where I've eventually traced it down to some inlined subVI. It has seemed as if the values used inside the inlined subVI don't match what the calling VI is feeding into its inputs. I haven't been able to consistently reproduce this issue so I apologize for the vague description, but since I felt I should finally address this and I couldn't really find anything similar by searching, I'll do my best to describe it and we'll see what turns up.
As I mentioned, the issue certainly doesn't occur consistently. I use inlined subVI here and there and most of the time there are no problems whatsoever. I ran into the issues randomly I think four times now, first three of them were on LV2013 and this last time on LV2014. In all cases I have been using AF and I think the first times were actually with an actor class. At the time I thought it might have been related to the AF, and it still might, but now the last time it wasn't the actor class itself but a data member of one. So far all of the problems have occured with class methods, and I think the "corrupt values" have been the object private data, but I can't confirm this.
This time the inlined subVI was a static dispatch method with contents shown below on the left and the calling on the right.
I'm showing the calling just to point out that when I was investigating the problem and I probed the object wires before and after the inlined subVI the values (Calibration.X Step and Calibration.Y Step) were OK, but the result of the VI (Point out) was some insane value as if the actual division inside was performed by corrupt data. I think that the output value wasn't Inf, though, so the divider might not have been a default value such as 0.
Other notes:
I checked that the wires are connected to the inputs and outputs
As I mentioned, the projects have always been relatively large AF setups, the problematic method has been an actor method or a method called by an actor somewhere down the chain. I have no reason to assume AF is the culprit, I'm just pointing this out, just in case
The problem seems to occur quite randomly but once it "starts" it doesn't go away until I find which inlined subVI it was and change it to a normal VI call
The problem might not even be specifically inlined subVI related but for example pre-allocated VI related instead
I don't know whether the problem would occur in a built executable as well, so far I've only ran into them while testing while developing and fixed them there
Looking at the "Known Issues" related to inlined subVI's I don't know if this related to them. The other one deals with execution systems, which I haven't touched to my knowledge, and the other one says "An Inline public methodVI calling a private-scope method VI, inlined into a non-class caller may give a runtime error when trying to call the private method from the inlined code in the non-class caller."
LabVIEW version is 14.0.1 (2014 SP1 32bit) on Windows 8.1
Yep, reading through this post I gotta say I'm not expecting much, what a mess, but it would be great to find out if anyone else has ever ran into similar problems or has a clue what's going here.

Just for the sake of your sanity, I've seen "funky" behaviour with inlined VIs also, but on Real-Time targets.
I've never been able to narrow down the exact problem but it seems to be related to changed made to inlined VIs not being reflected in the compiled code od VIs which call them.
I've reported it but without code which can actually reproduce it, it cannot be fixed.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Error and weird behaviour in executable launch

Hello folks,
This post is regarding a weird behaviour i am experiencing with an executable i built.
LABVIEW version(Includes Runtime engine) LV2012 SP1 f3
DAQmx: 9.6.1
The behaviour is listed below in detail.
In a nutshell, the exectuable runs on the development computer but does not run on the Target computer. Also, Irresepctive of which PC i run the executable on, i cannot access the block diagram even after enabling debugging everywhere.
On the target PC, the app fires up but does not run further, no error codes appear on the screen, it's like the app freezes after firing up. And to add to the misery, i cannot access the block diagram to debug and know what's going on.
Also, I have tried including the dynamic vis to my build script. No bueno.
What I see on running the app is addressed below:
TARGET COMPUTER:
DAQmx 9.7 and LV2012 SP1 f4 RTE have been installed manually.
App does not run: No broken run button, the app launches but does nothing when the vi is run. No error messages.
The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
DEVELOPMENT COMPUTER:
The app launches and runs perfectly.
The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
DAQmx 9.7 and LV2012 SP1 f4 RTE were not installed as the app recognized the already installed Labview environment.
Additional steps that I have tried,
Created and ran only an executable on the target PC, the attempt was unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section.
Created and ran an installer with additional install options(LV2012 f4 RTE and DAQmx 9.7)on the target PC, the attempt was again unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section. No error messages.
Tried both the steps mentioned above on the development computer and the attempts were successful. .
To the best of my knowledge, I believe, the issue here is with the environment I am creating for the executable and the installer to run with/off of. After having carefully followed the installation procedure for the Run-Time Engine and the DAQmx drivers, I still do not know what I am missing.
Please advise.
Thanks guys,
RP.

Hey guys,
So, got the application to work. Almost.
The problem was that the executable was missing the hardware config from the Device.
Now, the new issue is as following:
The goal of the vi is to generate a report of the test conducted. So, the way the vi works is that, the second the vi is run, an empty word file is created with only the company logo,
Field headings, which are populated after the test is conducted.
The logo is a .jpg file, which has a relative path into the executable.
The field heading are String constants wired into a 'concatenate strings.vi' which are in turn wired to into the report generation vis.
What's happening is that when i run the app on the target pc, Only the logo appears on the word template. Even when i conduct the whole test and stop the vi, the results aren't populated in the word file. Which is a little weird.
Does any one know whats doing that?
Please refer to the attached word files.
Right - It is the file format desired.
Wrong - It is the file format achieved.
Please advise.
Thanks,
RP.
Attachments:
Right.docx ‏17 KB
Wrong.docx ‏16 KB

How is it possible to make sure that LV uses the same thread for several threadsafe DLL calls?

Hello,
i have a thread safe DLL and most functions are called from serveral threads from the LV apllication without problems.
In case of an error i have to call an error handler function in this DLL (like WinAPI: GetLastError()) from the same thread which has called the function that failed before.
I can't use the user interface execution because some functions need a long execution time and i don't want to balk the user interface.
All other executions than the user interface execution have more than one thread and in most cases the DLL function calls were executed from different threads - so the error handling doesn't work...
Any idea?
Thanks for your help!

Hmmm....
How about wrapping all of your dll calls in a single VI (or an Action Engine ) and make sure the VI's thread is NOT set for "Same as caller".
"Threadconfig.vi" (sp?) will also let you dictate the number of threads associated with an execution system. Set your target thread for "1".
Not sure on the above.
Please correct me if this is wrong!
Ben
Message Edited by Ben on 07-19-2007 08:26 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Private dll calling in Labview

Hi everyone, (refinement of my question)
I have two dlls. One contains public functions which I call from Labview. The functions in this dll call functions in the other (private) dll. However, how do I tell Labview where to find this private dll?
I have tried installing the dll in the system path directory. I have also put the dll in various different places relevant to Labview (e.g. in the directory of the Labview executable file). However, none seem to work (.
Is there an option in Labview where I can set paths to dlls?
Any help will be gratefully received.
Ciao,
Matthew Banham (colleague of Francois)

> I have two dlls. One contains public functions which I call from
> Labview. The functions in this dll call functions in the other
> (private) dll. However, how do I tell Labview where to find this
> private dll?
>
> Is there an option in Labview where I can set paths to dlls?
>
The problem is that the system loader is what handles the dependent
DLLs. Since LV knows about the primary DLL, we try multiple locations,
the path in the dialog, next to the VI, in the LV search paths, and
finally we ask the system to look in their places. LV doesn't know
about the dependent DLL, and it is up to the system to find it. I'd
recommend trying the system or windows folder again. That should be the
right solution.
An off the wall thought that might h
elp would be to add a dependency
directly into LV by making a DLL node that calls in the the "private"
DLL. You don't actually have to call it, you can place it in a case
structure with a constant set the other way. Anyway, this will cause LV
to look for the DLL, and I think it might help if nothing else works.
Greg McKaskle

[Solved] Firefox 3 betas give me some weird behaviour with images

I understand that there will be problems with beta software, however I seem to have memory issues with the firefox 2 series, so I thought I'd give the beta packages a try. I'm using the firefox-nightly package from AUR (firefox3b4), and I'm getting some weird behaviour. The same behaviour can be seen in all firefox 3 beta builds, however. It's hard to explain the problem, so here's a screenshot:
Notice that the image appears twice, once in the tab, and once in the tab toolbar next to the title of the tab. It looks like an attempted preview gone terribly wrong. Upon closing the tab, the tab toolbar shrinks down to the normal size and all is well. This happens with most images up to a certain size. Any one else experiencing this problem? Any suggestions? This is very annoying and I would like anyone's input on the problem.
Last edited by valnour (2008-02-24 07:41:05)

Wow! This issue was solved in #archlinux by Nuked. Apparently I had some funky bits in my .mozilla directory. Removing it solved the problem. Remember kids, IRC is your friend. Anyone else experiencing weird stuff with their Firefox install should give this solution a try.

Configuring array of byte in dll call

Dear all,
I need to send the data 2010010100H to the dll at the question mark(U8) i mentioned in the attachment. Actually the data has to be transferred at a time not in bits and pieces. How to do this? I just put an array constant. Is it correct? Kindly give suggestions asap.
Thanks,
Mathan
Attachments:
1.PNG ‏10 KB

Hi mathan,
the dll call in your pic only accepts single bytes (U8) - so no way to wire an array!
why do you create so many new threads, when the topic doesn't change?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Error Code 1097 Coming in DLL Calling

Hi,
I am getting error code 1097 in DLL calling function. Please find the DLL calling function details for more information.
Function : GetControllerListTest(controller *ptrControllertest,char *max_controller);
Controllertest parameter details:
define NO_OF_CONTROLLER  100
#ifndef CONTROLLER_STRUCT
typedef struct
  CString name;
  char status;
  CString blocked_by;
  char group;
}controller;
Controllertest parameter data type is structure. In LabVIEW, I have configured parameter as a cluster.
name : String control
status : U8 Integer control
blocked_by : String control
group : U8 Integer control
Could you please confirm it, did I configured the datatype in correct way?
I am getting empty array output and Error Code from the DLL 1097. Can you please tell me where I am missing?
Thanks
Sivaramkumar.V
Solved!
Go to Solution.

Call Library Node problems without the VI in question attached AND the complete C prototype of the function provided, AND preferably some documentation about the C function in question can be not diagnosed. These informations are paramount to get the Call Library Node configured properly since there is no way a calling application can retrieve the necessary information from the DLL itself. The DLL interface was never intended to be a self configuring interface and it was designed with the understanding, that the user of such an interface is a fully knowledgeable C programmer knowing both, how to read a header file definition as well as various details about memory buffer handling.
So show us your VI and the C header file, and we can start to help you. Otherwise all we can do is guessing in the way you have done with changing the calling convention randomly. You can of course try to shoot in the shooting range with a blindfold on, but the chances that you not only do not hit the target, but injure some other person instead is very high.
The only reason that the suggestion from Fragger Fox has any merits is the fact that LabVIEW used to have some heuristics that changed the Call Library Node automatically from C calling convention (the LabVIEW default) to Windows calling convention, if it recognized a certain pattern in the exported function name. This heuristic was removed in LabVIEW 2009 because it did prevent the Call Library Node to be able to call functions that were using C calling convention but happened to match the heuristic pattern. So changing a Windows calling convention to C calling convention when the code has "seemed" to work before is NEVER a solution.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to response polling event during dll call

Hello,
There is a long time dll call in my program. The program doesn't response to mouse click in the front panel during the dll call when I want to display other page in Tab control. It only response after the call.
How to solve the problem?
Thanks!

Wether or not it is possible to fix this situation is dependent on the dll itself.
IF
the dll is written to be re-entrant (thread-safe)
THEN
you can configure the Call Library function to not run in the user interface thread. This can be done by right-clicking on the node and selecting "configure". In the configure screen, ther is a drop down selection box that defaults to "Run in UI thread". Change this to re-entrant.
You can then determine which thread the dll runs in by setting the properties of the calling VI.
Warning!
If the dll is not re-entrant you WILL experience random crashes and possible data coruption! All bets are of if the dll is used in the wrong manner.
What is happening:
LV's execution systems are multi-thread with the exception
of the UI thread. The UI thread is single threaded to ensure updates of control and indicator information is updated correctly, etc. This thread also uses co-operative multi-tasking wherein a proccess is expected to "put itself to sleep" regularly in order to allow other proccesses in that thread to gain access to the CPU. Your dll is dominating this thread and prevent user actions to be serviced!
Final note;
If you do not know if the dll is thread-safe and decide you just want to experiment,
BACKUP YOUR ENTIRE MACHINE!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

RoboHelp for Word Version 8-Run-time error 49-Bad DLL calling convention

I just installed the trial version of RH8. I have RH5 installed. I also have Word97 installed. When I start RH8, the RH Explorer pane opens, but when it tries to open Word, the following error message appears: "Microsoft Visual Basic - Run-time error '49'. Bad DLL calling convention." Any ideas on what I can do to fix this problem?

See Snippets on my site.
See www.grainge.org for RoboHelp and Authoring tips
Follow me @petergrainge

I am using a Application in c dll calling from jni jar by java applet in firefox version 19.0 , the problem is click event message box will not working correct

I am using a Application in c dll calling from jni jar by java applet in firefox version 19.0 , the problem is button click event message box or popup window will not working correctly. Please any one suggest me the steps to overcome this not responding or slowness in the responding problem of Button click event.

Hello,
In Firefox 23, as part of an effort to simplify the Firefox options set and protect users from unintentially damaging their Firefox, the option to disable JavaScript was removed from the Firefox Options window.
However, the option to disable JavaScript was not removed from Firefox entirely. You can still access it from about:config or by installing an add-on.
'''about:config'''
# In the address bar, type "about:config" (with no quotes), and press Enter.
# Click "I'll be careful, I promise"
# In the search bar, search for "javascript.enabled" (with no quotes).
# Right click the result named "javascript.enabled" and click "Toggle". JavaScript is now disabled.
To Re-enable JavaScript, repeat these steps.
'''Add-ons'''
You can alternatively install an add-on that lets you disable JavaScript, such as
*[https://addons.mozilla.org/firefox/addon/noscript/ No-Script] (to disable JavaScript on a per page basis, as required)
*[https://addons.mozilla.org/firefox/addon/quickjava/ QuickJava] (to easily disable and enable JavaScript, automatic loading of images, and other content)
Thank you and I hope this helps!

Failure: "gnrclist.cpp" after a DLL call

Forum:
Since adding dll calls in a VI, LabVIEW is frequently crashing, both during VI execution and after exiting the application.
Generally, what issues need to be considered when making successful dll calls (using the "call library function").
Jordan

Hi Jordan,
It sounds like this issue is due to the fact that you are not allocating memory for the dll in advance. This is the most common mistake when implementing a dll in LabVIEW.
For instance, if your dll is going to output an array of 100 double-precision numbers, then you need to allocate this place in memory by passing the dll a dummy array of 100 double-precision numbers that it can operate on. Also be careful not to expand the size of the array. LabVIEW doesn't support dynamic memory allocation within a dll in most circumstances. If you don't allocate a place in memory in advance, LabVIEW may crash when you exit the program and LabVIEW tries to deallocate memory.
A really good example of allocating various types of data for use in a dll is available from the Example Finder (Help >> Find Examples from LabVIEW). Click the Search tab and search for the term DLL. The Example is called Call DLLs. It contains c code that corresponds to various dll functions that operate on various data types, and it shows you how to call these dll functions properly from LabVIEW. For a more comprehensize overview of the process, refer to the document Using External Code in LabVIEW, available here, or browse through these Developer Zone examples and applications notes.
Jarrod S.
National Instruments

Weird behaviour, dll calling

Similar Messages

Maybe you are looking for