Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

Similar Messages

VB6 applications crashes when calling C# dll's in production environment

Hi All,
I'm basically .NET developer, not much aware of VB language or VB visual Basic 6.0.
We are trying to work out with VB application running/ using C# dll's. The scenario is like VB exe applications using C# dll's and C# dll's are referenced to VB application using .tlb file.
In development environment(debug mode) the application looks fine and working as expected. But when the same code is put into production environment VB applications are crashing when pointing to C# method calls. We trying to know the reason but application
is getting killed. The issue seems to be sporadic and not able to catch in MsgView(debug tool).
In one more scenario, the VB application is loading C# form and getting data back to VB but when we repeat the same workflow again application is crashing either in 2nd attempt or 3rd attempt.
Has anybody seen such issue? Any input is welcomed.
Thanks,
Shesh

Hi Shesh.ugare
Welcome to MSDN.
I am afraid that these forums donot support VB6, you could refer to this thread:
Where to post your VB 6 questions
If this issue regarding VB6 then you could consider posting this issue in these forums below:
These forums do not support Visual Basic 6, however there are many third-party support sites that do. If you have a VB6-related question please visit these popular forums:
VB Forums
VB City
If not, then you could share more detailed code with us.
Thanks for your understanding.
Regards.
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Is it possible to call DLL develloped with LabView 7.0 in LabView 6.0.2 VIs?

Hello,
I would like to devellop DLLs in LabView 7.0 and use them in LabView 6.0.2.
Is it possible???
I tried this operation. I generated an installer (with the LabView 7.0 runtime in) and tried to load the DLL in a LabView 6.0.2 VI.
When I run the VI, LabView 6.0.2 is crashing...
Here my export function prototype:
typedef struct
LVBoolean status;
long code;
LStrHandle source;
} TD1;
typedef struct
long dimSize;
unsigned char Numeric[1];
} TD2;
typedef TD2 **TD2Hdl;
void __cdecl driver(LVBoolean *SendCommand, unsigned char DataToSend[], long LenDataToSend, char RHICommandString[], TD1 *errorInNoError, LVBoolean *GetAnswer, LStrHandle *FrameReceivedID, long *Da
taLength, TD2Hdl *DataReceived, TD1 *errorOut);
Any example ???
Thanks for your help,
Regards, Pascal.

Hi Pascal,
I made a simple dll in LabVIEW 7 and called it from LabVIEW 6.0 and it worked fine.
I have attached the dll I built. It adds two numbers.
double Testdll(double B, double A);
Try using this and see if it works for you.
Feroz
Attachments:
SharedLib.dll ‏17 KB
SharedLib.h ‏1 KB
SharedLib.lib ‏3 KB

Crash when calling dlll built by LV using timed loop.

I have built a dll with Labview 7.1. Then I use VC++ 6.0 to call this dll. Everything is fine except that it will crash after the whole program finishes. Without timed loop the program can exit normally. When built to exe file, it can also run normally. This happens in both Windows2000 and Windows XP.
Anyone knows the reason for this?
Thanks!

Now the timed loop stops correctly everytime both in Labview environment and standalone exe. But when I call the dll version from C. The c program has no response after the program finishes.
I built another small vi without timed loop to dll and called it. The c program exit normally. What is the problem?
The period of timed loop is 50ms. Is it too short? I found from other post that maybe I should use while loop instead of timed loop. But i need very accurate controling of time.
Any suggestions?
Thanks!

Sun One Web Server 6.1 SP4 crashes when filters are built with CC ver. 5.6

Hi All
We are using NSAPI interfaces to develop the filter for Sun ONE 6.1 SP4 Web Server. Filter was working perfectly fine when it was built using Sun WorkShop 6.0, CC Compiler ver 5.2.
After we upgarded to Sun WorkShop 9.0, CC Compiler ver. 5.6, it no longer works. The web server crashes with Core. Please see the snippet below. There was however no change of code required for the upgrade.
Please let me know if some specific compiler/linker flags has to be used for building filters with CC Compiler ver. 5.6.
bash-2.03$ ./start
Sun ONE Web Server 6.1SP4 B01/20/2005 17:43
warning: CORE3283: stderr: 6950: CSemCounter created a semaphore with ID 25 using key 990470909.
warning: CORE3283: stderr: [10/Nov/2005:18:50:35] [Information] Agent
warning: CORE3283: stderr: Agent is enabled.
warning: CORE3283: stderr: 6950: Cache - created semaphore 26 using key 487154429
warning: CORE3283: stderr: 6950: ResourceCache - created semaphore 27 using key 772367101
warning: CORE3283: stderr: 6950: Cache - created semaphore 28 using key 503931645
warning: CORE3283: stderr: 6950: Cache - created semaphore 29 using key 520708861
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun Microsystems Inc.]
catastrophe: CORE3260: Server crash detected (signal SIGBUS)
info: CORE3262: Crash occurred in function realloc from module /usr/lib/libc.so.1
Back Trace of Core
#0 0xfe042974 in t_splay () from /usr/lib/libc.so.1
(gdb) bt
#0 0xfe042974 in t_splay () from /usr/lib/libc.so.1
#1 0xfe0427e0 in t_delete () from /usr/lib/libc.so.1
#2 0xfe0423e4 in realfree () from /usr/lib/libc.so.1
#3 0xfe041f48 in mallocunlocked () from /usr/lib/libc.so.1
#4 0xfe041ce0 in malloc () from /usr/lib/libc.so.1
#5 0xfe04f568 in strdup () from /usr/lib/libc.so.1
#6 0xff1c3038 in INTsystem_strdup_perm ()
from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#7 0xff1c84c8 in INTvs_get_doc_root ()
from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#8 0xfdb57f4c in __1cKJ2EERunnerIcreateVS6FpkcpknNConfiguration_pnRJ2EEVirtualServer__i_ ()
from /home/porting/project/sunone/bin/https/lib/libj2eeplugin.so
#9 0xfdb528bc in j2ee_vs_create ()
from /home/porting/project/sunone/bin/https/lib/libj2eeplugin.so
#10 0xff1c9444 in __1cPNSAPIVSListenerGinitVS6MpnNVirtualServer_pk1_nIPRStatus__ () from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#11 0xff2273e4 in __1cXVSConfigurationListenerQsetConfiguration6MpnNConfiguration_pk1_nIPRStatus__ ()
from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#12 0xff225dc8 in __1cUConfigurationManagerQsetConfiguration6FpnNConfiguration__2_ () from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#13 0xff245b30 in __1cJWebServerDRun6F_nIPRStatus__ ()
---Type <return> to continue, or q <return> to quit---
from /home/porting/project/sunone/bin/https/lib/libns-httpd40.so
#14 0x10ab8 in main ()
Thanks

I could trace down the problem to the fact that if I don't use the map file (which is passed to the linker using -M mapfile), the plugin works perfectly fine. Further to this if I comment out the local part of the mapfile, it starts working.
mapfile :
NSAPIPlugin.so {
global:
symbol1;
symbol2;
symbol3;
# local:
Is there is any specific linker flag that I have to pass along with -M mapfile with the sun studio 9. What are possibe consequencies if I go ahead with this workaround of commenting out the local directive.

Application crashes when calling run_report_object , FRM-93652: The runtime process has terminated abnormally

I got this error when calling report from my form：
FRM-93652: The runtime process has terminated abnormally
Forms Session ID is WLS FORMS.formsapp.101
Here is the trace dump info :
Last Trigger FORM/BLOCK/FIELD: FRM_ACTIVITY_QUEUE.BLK_ACTIVITY_QUEUE.BTN_PRINT
Last Trigger: WHEN-BUTTON-PRESSED - (In Progress)
Last Builtin: RUN_REPORT_OBJECT - (In Progress)
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
siehDumpStackTrace( call     kgdsdst()            000000000 ? 000000000 ?
)+104                                              7FFFBF18D110 ? 7FFFBF18D1D8 ?
                                                   7FFFBF1AD130 ? 000000000 ?
siehjmpterm()+650    call     siehDumpStackTrace( 000000000 ? 2B1668E4EB00 ?
                              )                    7FFFBF18D110 ? 7FFFBF18D1D8 ?
                                                   7FFFBF1AD130 ? 000000000 ?
__restore_rt()       call     siehjmpterm()        00000000B ? 2B1668E4EB00 ?
                                                   7FFFBF18D110 ? 7FFFBF18D1D8 ?
                                                   7FFFBF1AD130 ? 000000000 ?
00002B1660459EB0     signal   __restore_rt()       2B16603F2929 ? 7FFFBF1ADBD8 ?
                                                   000000000 ? 000000002 ?
                                                   000000001 ? 0EBC57ED8 ?
Anybody knows what might be the cause ?
Thanks

Refer to : Oracle Support : Forms Runtime Crash (FRM-93652) When calling RUN_REPORT_OBJECT in 11g (Doc ID 1306368.1)

Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC

I have a dll built using LabVIEW 6i. I am calling the dll from a VC++ application. When the application loads I get an error pop-up 'cannot find LabVIEW runtime'. If I change the VC++ code to dynamically load MFC (using the loadlibrary function) or dynamically load the LabVIEW dll I created then the problem goes away. Only when both are loaded statically do I get the error message.
The target machine is running Win2K pro and has the LabVIEW runtime installed.
I do not want do dynamic loads as I need to call the dll from a legacy application. Are there any options to change the way LV links to MFC or to force the dll to find the LV runtime?
Alan Widmer

Ben,
I have attached a ZIP of the files required to test a DLL from an MFC application. Or you can build the same application by following the instructions below. I used the numtest dll that you previously sent to me so there is no 'magic' in the LabVIEW or dll.
In VC++ select NEW. Pick the MFC AppWizard (MFC) to build an MFC application. In the wizard select
Project Name: MFCNumtest
Single Document
No database support
No Compound document support
Support for ActiveX
Default settings on the Features page
MFC Standard
MFC as a shared DLL
From the ResourceView of the project explorer, add an item Test to the IDR_MAINFRAME menu then add an item Go as a submenu item (with an ID of ID_TEST_GO)
Right click the new menu item and run the Class
Wizard. Click Add Function.. button to make a function OnTestGo()
Open MainFrm.cpp and scroll to the end of the file to see the skeleton for the OnTestGo function. In this function add a call to the LabVIEW dll. You will also need to add a reference to the .lib file and the usual extcode.h.
When you run the app you will see a window with the Test menu item. Select it and click Go to run the call to LabVIEW.
This all works great. If you now go to Project | Settings and on the general tab change the Microsoft Foundation Classes: item from 'Use MFC in a shared DLL' to 'Use MFC in a static library' rebuild ALL files in the project and run the app you get the error message:
System error 998 while loading the LabVIEW Run-Time Engine (C:\Program Files\National Instruments\shared\LabVIEW Run-Time\6.0\\lvrt.dll).
numtest requires a version 6.0 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of numtest to correct this problem.
I apologies for my slow response, g
ot distracted by some other issues.
Thanks for your help,
Alan Widmer.
Attachments:
mfcnumtest.zip ‏44 KB

Is it possible to view VIs remotely on windows 7 if VI was built with LabView 8.2?

So I know i'm probably dealing with software compatibility issues here, BUT, I wanted to make sure every option was exhausted before considering the idea of upgrades.
Im using LabView full development system 8.2 on windows XP 32bit os. Currently, I run into no issues when controling or building VIs on my computer. Problems do occur when trying to control VIs on a remote computer with windows 7. That computer has run-time 8.2.1 installed on it. For the most part it works best to just view the VIs, and not interact or control too much. More specifically, the VI will freeze once interacting with a control that is intended to pop up a two button dialogue box. I'm sure there are a lot more issues with using run-time 8.2.1 on a windows 7 computer; that one in particular is just the only one i've experienced.
In all efforts to avoid what could eventually be an unavoidable situation where an upgrade is necessary, is there a way to remotely control (on windows 7) a VI front panel that was built with labview 8.2?

Thank you for the response. Just to preface, I am fairly new to LabView so pardon my potentially "stupid" questions. Here's my process in a nut shell: VI programs are created on our server computer and then published for web with the "web publishing tool...". The html page created is then put on a main page with all other created VIs and are then viewed on other computers that are part of the network via ip address.
I was under the impression the LabView run-time engine enabled remote computers to view and control these VIs. Could be wrong? After downloading and installing run-time 8.2.1 (since vi's were created with labview 8.2), those computers are able to enter the ip address and navigate to the main page to control the web published vi's. The issue is with the computer that has windows 7. I know run-time 8.2.1 isn't necessarily compatible with windows 7, but it does seem to run the vi on a pretty minimal level. I run into problems on that computer when hitting particular controls that are wired to be more complex than just a simple boolean.
Just to provide a visual, I attached an image of one of the scenarios where it will freeze up on the windows 7 computer. This is how the VI should normally function; however, before the dialogue box even pops up after clicking a valve control, it freezes.
I didn't even consider VNC or Remote Desktop up to this point. Thank you for that idea. I'll definitely look into that as an alternative.

Applications crash when attempting to use network printer

I just upgraded to Tiger. Now, all applications crash when I attempt to select my network printer (HP laserjet 4600) from the 'File' ->'Print' menu. If the network printer is selected as my default printer, the program closes before the print menu even comes up. However, I can print to this printer if it is my default printer and I use the print icon instead of 'File'->'Print'. I also have a USB printer (Lexmark) which I can print to no problem. I can print to all printers with no problems from Classic applications, and I had no problems printing from either Classic or OS X before upgrading to Tiger. Anyone have any ideas?
Faris

Did you run Disk Utility> Repair Permissions after installing the HP driver software? While Repair Permissions may no longer be a useful as it was as a generic troubleshooting step under OS X 10.2.x, it's still essential if you have any third-party software that requires an administrative password to install, especially HP or Adobe software, which are known to trample around placing files with mis-set permissions all over the place.

OS 10.3.7 Applications Crash when I do a "save "

Applications crash when I save documents, so I always save as, and make the file name alittle different. I have fixed and verified permissions, I have trashed preferences, anything else I can do?? this is really getting annoying!
thanks,
Tori

I agree with Roam -- use the new one for a while. Run all your apps to make sure things are cool and work as you desire. In a few months, once you've grown accustomed to the new account, it will be safe to wipe out the old.
It sounds like there was some corruption in the old account (caches? perms? who knows?) Often these problems can be solved at a more granular level, but if the big and easy answer works, hey, go with that.
Thanks for the star, BTW.
Best,
~FifthWheel

Does a stand-alone EXE built with Labview 8.2 return a return code?

My application is an executable that was built from a VI in Labview 8.2. I'm expecting a return code of this stand-alone executable after the execution, however couldn't find a way to control the return code of the application.
Does a stand-alone executable built with Labview 8.2 return a return code? If yes, how is this code controllable?

Hi Tdot!
Thank you for contacting National Instruments. It looks like your question is something that many others have run into. This topic is discussed here, and looks to be answered along with a couple of suggestions. I hope this helps! Let me know if there is anything else I can clarify. Have a great day!
Jason W.
National Instruments
Applications Engineer

Since upgrading to mavericks my applications crash when i try to use the print dialogue

since upgrading to mavericks my applications crash when i try to use the print dialogue

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, look under User Diagnostic Reports (not "Diagnostic and Usage Messages") for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post other kinds of diagnostic report — they're very long and not helpful.

Please a solution against crashes when opening a file with Acrobat XI pro?

Hello,
Am a member of Adobe Creative Cloud.
Am also constantly having crashes when opening a file with Acrobat XI pro.
Am running on Windows 7 Home Premium, Service Pack 1, 64 bit - RAM 20 GB -
The crash happens systematically after the installation of the update. Within one day I uninstalled and reinstalled the program 4x! It takes of a lot of my time.... Thank you for providing a definitive solution!
Best regards

I've been having the same issue! I try to open it and it crashes - says re-open, it crashes... I re-installed it yesterday and it opened and worked fine. Closed it out at the end of the day thinking everything was finally fine but this morning the same crashes it had yesterday... HELP!!!

I have been using Lightroom 4.4 successfully for over 2 years. Just tried to import some new photos after a vacation and the application crashes when I click "import" every time. Tried restarting computer. Version says it is up to date.

I have been using Lightroom 4.4 successfully for over 2 years. Just tried to import some new photos after a vacation and the application crashes when I click "import" every time. Tried restarting computer. Version says it is up to date.
How do I get formal support for this from Adobe?

Thanks for the response. The application was crashing. A Windows message was displayed showing "Lightroom.exe has stopped working", "Windows can check online for a solution the problem.". Etc.
I just launched Lightroom to check the exact message for this reply - and the Import worked. It had failed dozens of times before.

Every application crashes when i try to print from it!

Hello everyone, i have an HP 1012 laserjet and it was working perfectly fine until i installed all the updates for the ILife and everything else that came out earlier this week. Anyone know what is going on??

I had the same problem as well. All applications crashed when I tried to print.
I found the solution at http://forums.macrumors.com/showthread.php?t=199701&highlight=printing+crash.
What I ended up doing was to delete the system's printer drivers (located in Macintosh HD > Library > Printers), then re-installing them from install disk one (optional install). This was suggested by "mad jew" on macrumors, and worked for "EricNau" (using 10.4.6 on iMac G5 17") as well as myself (using 10.4.6 on MBP 17"). Hope it works for you as well.

Application crashes when calling DLL built with LabVIEW 2011

Similar Messages

Maybe you are looking for