I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

Similar Messages

Can somebody fix my corrupted subvi, error "Fatal Internal Error" "objheap.cpp"

Hello,
I have been strugling to open this file after a reboot due to not responding computer. The file is a part a larger library however, this is the part that is not responding and giving "Fatal Internal Error" "objheap.cpp" .
Does anyone know how to fix this issue or how to repair this file.
I am using a LabView 2012.
Thank you for your time.
Attachments:
Corrupted.llb ‏149 KB

Hi obarriel,
that could be a tricky job as LV2013 claims "block diagram can't be opened"!
Meanwhile you should learn two things:
- using LLBs isn't recommend practice nowadays (atleast not for storing daily work VIs)
- make a backup of your works on a regular basis (using SVN/GIT is recommended too…)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Fatal Internal Error : "objheap.cpp", line 579 - Labview 7.1 running on vista

Hello,
I was developing a project in Labview 7.1 and had saved it on vista when the vista OS decided to enter suspend, Labview 7.1 stopped responding as a result and I had to reboot. I will never trust vista again but when I try to open the VI I get the following error:
Fatal Internal Error : “objheap.cpp”, line 579.
And the following text file report is created. What I am wondering is there any way to restoring or uncorrupting this VI which is attached. Sub VI’s are not included but if you can get the VI to open even without them then the problem is sorted.
#Date: 25 Feb 2009 12:13:28
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS
D:\lvmerc\src\source\objheap\objheap.cpp(579) : DAbort: Heap has insane block size
$Id: //labview/branches/Mercury/dev/source/objheap/objheap.cpp#3 $
0x009DFC85 - LabVIEW <unknown> + 0
0x007080AC - LabVIEW <unknown> + 0
0x007079E1 - LabVIEW <unknown> + 0
0x00A66716 - LabVIEW <unknown> + 0
0x00706B02 - LabVIEW <unknown> + 0
0x006073AE - LabVIEW <unknown> + 0
0x0070532B - LabVIEW <unknown> + 0
0x00A653E5 - LabVIEW <unknown> + 0
0x00A66911 - LabVIEW <unknown> + 0
0x009ED231 - LabVIEW <unknown> + 0
0x005ADED7 - LabVIEW <unknown> + 0
0x004B7F79 - LabVIEW <unknown> + 0
0x004B7EA7 - LabVIEW <unknown> + 0
0x004B7CF9 - LabVIEW <unknown> + 0
0x004B8492 - LabVIEW <unknown> + 0
It also managed to corruptly my library file for the project which I cannot open also and is attached,
Thank you
Message Edited by Support on 03-02-2009 08:50 AM
Attachments:
looptest.vi ‏1743 KB
AbbottHMITree.llb ‏4063 KB

Hello Paul,
I have been looking into your error code as well as the attached files of your VI and LLB. Pasting in your error code is proving very helpful in trying to help you. I initially tried to open your files in my system, where I would possibly be able to resave them for you, however it looks like I will have to try a different approach.
As I understand it, you have been using LabVIEW 7.1 Full Development System with Windows Vista. LabVIEW 7.1 was released during the years when only Windows 2000 and XP were available. With the release of Windows Vista in later years, National Instruments produced LabVIEW 8.2.1 with support for Windows Vista Business or greater.
Please reply with the following information:
Are you using Vista 32-bit or 64-bit?
Are you still able to open the LabVIEW Development Environment to produce new VIs?
Have you tried to open other VIs (after backing them up) with LabVIEW 7.1?
Regards,
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

Fatal Internal Error LV2010-DS1

Hallo All,
I was installing LabVIEW from the 2010-DS1 Distribution kit (LV2009-SP1),
after the whole installation process, I started LabVIEW and I've seen the Error : Fatal Internal Error "objmgr.cpp", line 2133...like in the attached image.
I'm working with a NEW Dell Precision M6500 with 8GB RAM and Windows 7 (64bit).
How can I solve the problem?
I've a super Notebook and the latest LV revision...but nothing work!
Thanks
Fabio
Attachments:
Startuperror.png ‏281 KB

Ciao Fabio,
your issue might be related to user account policies.
You need to have administrator privileges to use LabVIEW. If you're not the administrator you would need at least access to these 2 specific folders:
C:\Documents and Settings\All Users\Application Data\National Instruments C:\Documents and Settings\All Users\Documents\National Instruments
Hope this might help.
Andrea
Andrea N.
Systems Engineer ATE & RF - Mediterranean Region
National Instruments Italy

Solaris Studio 12.3 demangle fatal internal error: information lost in character quoting

Hello,
I have run into a problem with the Solaris Studio 12.3 compiler when building one source file that makes use of the open source Eigen library. The compilation fails with the error:
demangle fatal internal error: information lost in character quoting
CC: fbe failed for CSeasonalComponent.cc
The full command that fails is:
CC -c -o .objs/CSeasonalComponent.o -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -library=no%Cstd -KPIC -mt -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 CSeasonalComponent.cc
The problem goes away if the -g3 flag is removed. Replacing -g3 with -g0 does not help - the same fatal error occurs. (Removing the -g0/-g3 options has the effect of not passing a -dbgfile option to the fbe program, and this appears to be what avoids the problem.)
The information in this question is from a Solaris x86 machine, although the same "demangle fatal internal error: information lost in character quoting" also occurs on SPARC with the same source file and similar (although obviously not identical) compiler options.
The result of running the CC command that fails with the -dryrun option added is this:
### CC: Note: NLSPATH = /opt/solarisstudio12.3/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/solarisstudio12.3/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
###     command line files and options (expanded):
### -dryrun -c -o.objs/CSeasonalComponent.o -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags=yes +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -xcode=pic32 -mt=yes -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 CSeasonalComponent.cc
/opt/solarisstudio12.3/prod/bin/ccfe -xarch=amd64 -D__SunOS_5_10 -D__SUNPRO_CC=0x5120 -D__unix -D__SVR4 -D__sun -D__SunOS -D__x86_64 -D__x86_64__ -D__amd64 -D__amd64__ -D_LP64 -D__LP64__ -D__BUILTIN_VA_STRUCT -Dunix -Dsun -D_REENTRANT -D__SUN_PREFETCH -D__SUNPRO_CC_COMPAT=5 -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 -I-xbuiltin -I/opt/solarisstudio12.3/prod/include/CC -I/opt/solarisstudio12.3/prod/include/cc -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -ptf /tmp/ccfe.04.%1.%2 -features=extensions -ptx /opt/solarisstudio12.3/prod/bin/CC -ptk "-dryrun -c -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags=yes +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -library=no%Cstd -xcode=pic32 -mt=yes -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY='22' -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 " -compat=5 -g -xdebuginfo=macro -xdbggen=no%stabs+dwarf2+usedonly -xF=%none -xbuiltin=%all -pic -xldscope=global -xivdep=loop -xalias_level=layout -xdepend -O4 -errtags -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg +w CSeasonalComponent.cc -ptb .objs/CSeasonalComponent.o -o /tmp/ccfe.01.ir -s /tmp/ccfe.02.sd 2> /tmp/ccfe.03.err
/opt/solarisstudio12.3/prod/bin/iropt -Qy -O4 -xarch=sse3 -m64 -xchip=nehalem -xcache=generic -fsimple=1 -g -depend -mt -k -xalias_level=layout -xbuiltin=%all -xlibmopt -xprefetch=auto,explicit -xprefetch_level=1 -xprefetch_auto_type=no%indirect_array_access -xvector=no%lib,simd -F -o /tmp/iropt.05.ir -is /tmp/ccfe.02.sd /tmp/ccfe.01.ir 2> /tmp/iropt.06.err
rm /tmp/ccfe.01.ir
/opt/solarisstudio12.3/prod/bin/c++filt -filt=no%stdlib < /tmp/iropt.06.err >> /tmp/ccfe.03.err
rm /tmp/iropt.06.err
/opt/solarisstudio12.3/prod/bin/stdlibfilt -stderr < /tmp/ccfe.03.err
rm /tmp/ccfe.03.err
/opt/solarisstudio12.3/prod/bin/ir2hf -Qy -g -O4 -xbuiltin=%all -m64 /tmp/iropt.05.ir /tmp/ccfe.02.sd /tmp/ir2hf.07.hf
rm /tmp/ccfe.02.sd
rm /tmp/iropt.05.ir
/opt/solarisstudio12.3/prod/bin/ube -Qy -verbose -iropt -O4 -comdat -m64 -xarch=sse3 -xchip=nehalem -xcache=generic -xannotate=yes -il /opt/solarisstudio12.3/prod/lib/amd64/libm.il -fsimple=1 -ZW -g -xalias_level=layout -PIC -xbuiltin=%all -N -xprefetch=auto,explicit -xprefetch_level=1 -xthreadvar=dynamic -mt -fbe /opt/solarisstudio12.3/prod/bin/fbe -ipo .objs/CSeasonalComponent.o -dbgfile /tmp/ube.09.dbg -S /tmp/ube.08.s /tmp/ir2hf.07.hf
rm /tmp/ir2hf.07.hf
/opt/solarisstudio12.3/prod/bin/fbe -Qy -xarch=amd64 -xchip=nehalem -warn=%none -o .objs/CSeasonalComponent.o /tmp/ube.08.s -dbgfile /tmp/ube.09.dbg
rm /tmp/ube.08.s
rm /tmp/ube.09.dbg
Running the CC command with the -keeptmp option added leaves these files in /tmp:
-rw-rw-r--   1 dave     dev            0 Dec 11 16:20 /tmp/ccfe.1386778859.8273.03.err
-rw-rw-r--   1 dave     dev      45679331 Dec 11 16:21 /tmp/ccfe.1386778859.8273.01.ir
-rw-rw-r--   1 dave     dev            0 Dec 11 16:21 /tmp/iropt.1386778859.8273.06.err
-rw-rw-r--   1 dave     dev       393220 Dec 11 16:21 /tmp/ccfe.1386778859.8273.02.sd
-rw-rw-r--   1 dave     dev      47820727 Dec 11 16:21 /tmp/iropt.1386778859.8273.05.ir
-rw-rw-r--   1 dave     dev      60490992 Dec 11 16:21 /tmp/ir2hf.1386778859.8273.07.hf
-rw-rw-r--   1 dave     dev      22377791 Dec 11 16:21 /tmp/ube.1386778859.8273.09.dbg
-rw-rw-r--   1 dave     dev      8915850 Dec 11 16:21 /tmp/ube.1386778859.8273.08.s
Finally, creating an fbe command similar to the one from the dry run output using the last two files in /tmp with the -V option added as follows:
/opt/solarisstudio12.3/prod/bin/fbe -V -Qy -xarch=amd64 -xchip=nehalem -warn=%none -o .objs/CSeasonalComponent.o /tmp/ube.1386778859.8273.08.s -dbgfile /tmp/ube.1386778859.8273.09.dbg
results in this:
as: Sun Compiler Common 12.3 SunOS_i386 2011/11/16
demangle fatal internal error: information lost in character quoting
I would be happy to provide the /tmp/ube.1386778859.8273.08.s and /tmp/ube.1386778859.8273.09.dbg files to assist with reproduction of this problem if anyone is interested.

The problem with creating a simple test case that doesn't rely on Boost or Eigen is that the error message is so vague that there's no hint about where to start. The pre-processed source of the file that causes the problem is 4.7MB so trying to chop that down without any clue as to what's relevant is going to be very hard.
You could do everyone a favour if future internal error messages contained at least some information about what caused the problem. I know they're not supposed to happen at all, but clearly they occasionally do. For example, instead of:
demangle fatal internal error: information lost in character quoting
something like:
demangle fatal internal error: information lost in character quoting: corrupt symbol is __1cFEigenPPlainObjectBase4n0AGMatrix4CdIBiBiAIBiB___KresizeLike4n0AOGeneralProduct4n0AFBlock4Ckn0AGMatrix4CdIBIB_"""_oops
Then that would give somebody trying to report the problem or change their code to avoid it a starting point for where to look.
Anyway, I've worked around the problem by changing -g3 in the CXXFLAGS in the Makefile to `test $< = CSeasonalComponent.cc || echo -g3` which avoids the error. And hopefully like you say it's a known problem that's already fixed in the next version of Solaris Studio.

Fatal internal error: I/EX

I am developing an application, it will read out data in an olite db(5.0.2.7) using jdbc call, then it will write these data into an oracle 9i db using bc4j.
my system runs in win xp, I am using JDeveloper 9.0.3.1035.
when I run my class as a plain java application, everything is ok.
but when I call my class from a servlet as a web applicaiton, the web application terminate unexpected with an popup error message:
I/EX 311, and I can find this error in log:
Fatal internal error: I/EX
When I debug my program, I found that the error occured in rs.getString() statement :
ResultSet rs = ... ;
String s;
s = rs.getString("...");
Any one can help?
thanks.

Hello ! I am working with Oracle lite :
Connected to: Oracle9i Lite ORDBMS
Database Name: POLITE (Read Write)
Database Version: 4.0.2.0.0
Auto Commit: off
Driver Name: oracle.lite.poljdbc.POLJDBCDriver (OLite 4.0)
and Jdeveloper 9i
JDK 1.3 of the Jdeveloper and W2K Professional
I was searching for an answer cause I have the same problem but I realized that the problem is not directly related with BC4J or OC4J.
I suspect that is involve with the driver olite40.jar I hope you can validate this. I can reproduce the problem and it happen when you run a program in an application Server , I tried with OC4J and Tomcat the code like Weijun Tian explain I show two examples :
1st case : Supouse that I run a query to database like that : select name, price from tableTest ;
Statement stm = con.createStatement();
ResultSet rs = stm.executeQuery(�select name, price from tableTest�);
If the column �name� doesn�t exist or is incorrect writed I expect a SQLException well , that is right if I run a simple program with main method. But if I run the same query into a servlet , I have the problem of Fatal Internal Error I/EX without any explanation. This is running in OC4J now, if I run in Tomcat the same code I obtain :
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6d442b44
Function name=JVM_DisableCompiler
Library=C:\jdk1.3.1_09\jre\bin\hotspot\jvm.dll
Current Java thread:
at oracle.lite.poljdbc.LiteEmbStatement.jniExecDirect(Native Method)
at oracle.lite.poljdbc.LiteEmbStatement.executeDirect(Unknown Source)
at oracle.lite.poljdbc.POLJDBCStatement.executeQuery(Unknown Source)
at com.next.jsptest.Product.getDetail(Producto.java:59)
at com.next.servlets.ControlServlet.doPost(ControlServlet.java:163)
�.
�.
In both of them (OC4J and Tomcat) the server is shut down after the problem.
2nd Case : Now, suppose another situation , imagine a field in the database that is null , well, after the rs.getString(�THE_FIELD�), I expected that the answer will be null ok, if I run this in a simple class with main method there is no problem but if I run the same in a servlet , well, the same problem! I/EX and server shutdown again with OC4J or Tomcat, the same problem.
I think that something like that happen with you Weijun Tian.
Well , what I think is that there is a problem with Oracle Lite to work with application servers, I don�t understand why works fine in simple programs with main method but when I run in a server the same query have these kind of errors , I really hope you can help me because I don�t want to tell that Oracle Lite doesn�t work with an application server or is not a good Database for web applications.
Thanks a lot!!!
PD . I also put here my posts to the metalink and forums.
21 / 10 / 2003
Hi there, I have the same problem but I found that there is not directed relation with the getString(),the problem is in general. Apparently the driver does not work with SQLException , for example I try to make update and I put a column that not exist I expected a SQLException but get the error Fatal internal error: I/EX and the server shut down (?).
I think that it dependes of the driver, I am using OLITE4.jar in windows 2000 and works fine but when I have a simple error (talking about JDBC) get the error I/EX and shut down the server. Could you help me with some advice around this??
21 / 10 / 2003
Also I found that when I use the driver in a simple program the SQLException is captured for the try-catch block but when the same query for example is running in the JDeveloper from a servlet using the server for test of JDeveloper the same exception produce the problem of Fatal internal error:I/EX , I tried the same code in a Tomcat server and this is what I get :
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6d442b44
Function name=JVM_DisableCompiler
Library=C:\jdk1.3.1_09\jre\bin\hotspot\jvm.dll
Current Java thread:
at oracle.lite.poljdbc.LiteEmbStatement.jniExecDirect(Native Method)
at oracle.lite.poljdbc.LiteEmbStatement.executeDirect(Unknown Source)
at oracle.lite.poljdbc.POLJDBCStatement.executeQuery(Unknown Source)
at com.next.jsptest.Producto.getDetail(Producto.java:59)
at com.next.servlets.ControlServlet.doPost(ControlServlet.java:163)
at com.next.servlets.ControlServlet.doGet(ControlServlet.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
and my server shut down as far as I know the driver olite40.jar is a JDBC-ODBC driver I think that this is the reason for the problem maybe if I use a driver type 4 I can work better but, is there other driver for Oracle Lite in windows 32??? type 4 could be a solution.

Fatal Internal error: "oleautomgr.cpp", line 2832

Hi,
I have a program developped with LV 8.2.1.
Now I have import this application with LV 8.5; if I run the VIs in Labview it works; when I run my program (executable version) I got this error
"Fatal Internal error: "oleautomgr.cpp", line 2832"
I got the error after I open a Diadem connection.
Another information: first time I have import the program in LV 8.5 and I have save the prj, LV ask me to overwrite all the VIs of the "Diadem addons". (Diadem connectivity); so I have uncheck "read only" in Diadem.llb and I have save the Vi.
Someone can help me?
Thanx a lot

For the community's future reference, this issue was resolved by the customer calling in for support, at which time it was determined that a Mass Compile of the VIs was necessary to eliminate the error. The process to mass compile is described here.
-Sam F, DAQ Marketing Manager
Learn about measuring temperature
Learn how to take voltage measurements
Learn how to measure current

Fatal Internal error: "oleautomgr.cpp", line 2832 when sending data by means of ActiveX methode

I have experienced error "Fatal Internal error: "oleautomgr.cpp", line 2832" during sending data to CAN card IXXAT iPCI-I XC16/PCI. LabVIEW communicates with that card by means of ActiveX methodes via "VCI Wrapper" which is COM object interface. Mass compiling of the project does not help. Card is initialized and configured propely. The driver card is working propely.
LabVIEW version is 8.5
The efect of that error is that labview completly shot down.
I appraciate any suggetions
thanks a lot

Hello,
Please try to reinstall the drivers for the CAN card, then make sure you close all references to the ActiveX control (at all levels) using the Automation Close primitive in LabVIEW.
Regards,
Emil

Receive "Fatal Internal Error: Linker.cpp, line 1926 when run executable.

Hi, I use invoke node to call multiple subvi.vit, it work fine under .vi but when run under an executable I receive this error:
Fatal Internal Error: 'linker.cpp", line 1926
LabVIEW Version 7.0 You will lose any unsaved work. For more assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
Any suggestion will be very appreciated

Hi David,
What you are seeing is a known issue when calling LabVIEW 7.0 VITs from
an executable or DLL if the VITs include any Express VIs. It can happen if you
try to load
multiple instances of that template VI using VI Server.
There are a couple of workarounds for this issue:
Take
all the express VIs that are inside the template VI and turn them into
static subVIs. You can do this by right-clicking on the express VI and
selecting "Open Front Panel"; then save the express VI as a normal
subVI.
Build the entire application into a single executable, which will force all of the express VIs to get compiled as static subVIs.
Don't use the runtime engine at all and always run your application in development mode.
Let me know if the workarounds fix your issue, thanks.
Good luck!
- Philip Courtois, Thinkbot Solutions

Fatal Internal Error : "OMUDClassMgr.cpp". Line 1128

I received the following message:
Fatal Internal Error : "OMUDClassMgr.cpp", 1128
LabVIEW version 8.2.1
I was trying to build an application using the application builder.
Has anyone else had this issue? What needs to be done to fix this.

Hello,
This was reported to R&D (#4ALB7O89) for further investigation. Are you able to reproduce this problem with the same VI? Are you able to build an application with a simple VI?
Regards,
Elizabeth S.
Applications Engineer
National Instruments

Fatal Internal Error : "ThEvent.cpp", line 209

Hi,
Any help with the following AddRef()/Release() issue would be most appreciated:
I'm a software developer working on a COM (ActiveX) object for use by e.g. C# (test ok) and LabVIEW clients. The object supports events; however, when events are accessed with the "Register Event Callback" block, LabVIEW does not free the object when the VI is finished, and upon subsequently closing LabVIEW, I receive the following dialog:
Fatal Internal Error : "ThEvent.cpp", line 209
LabVIEW version 8.6
You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
and log:
#Date: Fri, Nov 14, 2008 12:44:58 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.6
#AppKind: FDS
#AppModDate: 06/26/2008 05:25 GMT
source\mgcore\ThEvent.cpp(209) : DAbort:
$Id: //labview/branches/Saturn/dev/source/mgcore/ThEvent.cpp#6 $
0x00B129F6 - LabVIEW <unknown> + 0
0x0040F5C0 - LabVIEW <unknown> + 0
0x7719C351 - OLEAUT32 <unknown> + 0
0x7712DB25 - OLEAUT32 <unknown> + 0
0x77EF658C - RPCRT4 <unknown> + 0
0x77EF4BF3 - RPCRT4 <unknown> + 0
0x7717E724 - OLEAUT32 <unknown> + 0
0x77600C31 - ole32 <unknown> + 0
0x77600BDB - ole32 <unknown> + 0
0x7750F237 - ole32 <unknown> + 0
0x7750F15C - ole32 <unknown> + 0
0x7750FC79 - ole32 <unknown> + 0
0x77600E3B - ole32 <unknown> + 0
0x776009BC - ole32 <unknown> + 0
0x77600DF2 - ole32 <unknown> + 0
0x7750FCB3 - ole32 <unknown> + 0
0x7750FAE9 - ole32 <unknown> + 0
0x7E418734 - USER32 <unknown> + 0
0x7E418816 - USER32 <unknown> + 0
0x7E4189CD - USER32 <unknown> + 0
0x7E4196C7 - USER32 <unknown> + 0
0x0041E852 - LabVIEW <unknown> + 0
0x0042AB32 - LabVIEW <unknown> + 0
0x00A27592 - LabVIEW <unknown> + 0
0x00A2DC60 - LabVIEW <unknown> + 0
0x00E3A5B9 - LabVIEW <unknown> + 0
0x008F0FF6 - LabVIEW <unknown> + 0
0x008F0CDA - LabVIEW <unknown> + 0
0x008F0EFB - LabVIEW <unknown> + 0
0x008F0F40 - LabVIEW <unknown> + 0
0x015AB20D - LabVIEW <unknown> + 0
0x7C816FD7 - kernel32 <unknown> + 0
0x00000000 - LabVIEW <unknown> + 0

I've attached a minimal COM server (that starts a thread when events are requested) that shows the issue. Steps to reproduce with LabVIEW 8.6 on Windows XP for x86 follow(stuff in parenthesis are comments):
(1) unzip HelloClass.zip to C:\ (4 files: hello.vi, callback.vi, HelloClass.dll, Hello.tlb)
(2) C:\>regsvr32 helloclass.dll (should get "DLLRegisterServer in helloclass.dll suceeded." dialog)
(3) C:\>hello.vi (start LabVIEW)
(4) Ctrl+R (run the VI. You should see "Command: test" in the String Indicator. At this point the last call into the server is AddRef() but should be Release())
(5) Alt+F4 (close the VI)
(6) Alt+F4 (close LabVIEW)
You may need to perform steps 3-6 up to ~10 times, because at this point one of 3 behaviors randomly occurs:
(A) Fatal Internal Error : "ThEvent.cpp", line 209
(B) Release() is finally called the same # of times as AddRef(), causing the destructor ~HelloClass to run (which kills the thread). This should instead happen after step 4 (which it does if you remove the "Reg Event Callback" block)
(C) Release() is called several times, but not enough to decrement the reference count to 0
Behavior A doesn't occur if the server doesn't start the thread. In source.zip, I've also attached the server's source code for your R&D team along with dbgMon, which is useful for looking at the _RPTF debug output. Thanks much for your patience and for looking at this.
Attachments:
HelloClass.zip ‏84 KB
source.zip ‏173 KB

Fatal Internal Eorror image.cpp 错误

我的一个程序打包成EXE后，在调用Exit退出labview时会弹出个错误框：Fatal Internal Error : image.cpp line 12727。如果直接在VI运行则时一切正常，labview能安全退出，请问是什么原因？
Labview 8.0

Hi
I also have a similar kind of problem, but in my case the exe was working fine for quite some time. say almost a year or so.
There are few screens which i am taking the front panel print otion in my software, when i click print on a particular screen, it pop-up this error
Fatal Internal error "image.cpp" , line 13192, labview version 8.2.1. you will loose any unsaved work, to resolve this issue relaunch labview or contact national instruments.
Once i click ok, it shuts down the software & i have to start the application again
For all the other sceens in the same application .. the same function is working fine.
Now unlike zhdo77 problem, my problem gets resolved once i reinstall the software, or sometimes by reinstalling the device drivers in the PC. But when i restarts my PC the problem appears again.
Now, my Q is ... how come the same exe was working fine for last one year, i faced this problem 2-3 days back only.
& what are the probable causes.
Message Edited by Rajan_77 on 07-02-2009 05:36 AM
Thanks & Regards,
Rajan

I have installed the new up to date itunes which i can open on my PC, however when i connect my ipad or iphone i get an error saying i cannot use the device as the require software isn't installed?? I'm very confused please help......

I have installed the new up to date itunes which i can open on my PC, however when i connect my ipad or iphone i get an error saying i cannot use the device as the require software isn't installed?? I'm very confused please help......

Let's try a standalone Apple Mobile Device Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of why it's not installing under normal conditions.
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/
Right-click the iTunesSetup.exe (or iTunes64setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleMobileDeviceSupport.msi (or AppleMobileDeviceSupport64.msi) to do a standalone AMDS install.
(If it offers you the choice to remove or repair, choose "Remove", and if the uninstall goes through successfully, see if you can reinstall by doubleclicking the AppleMobileDeviceSupport.msi again.)
Does it install (or uninstall and then reinstall) properly for you? If so, can you get a normal iTunes install to go through properly now?
If instead you get an error message during the install (or uninstall), let us know what it says. (Precise text, please.)

U have encountered the unexpected error

Hi,
    I have installed the JDeveloper properly and i have specified the Data base connections and run time connections also properly
     Now i have created the simple page and i am getting the error like below
   U have encountered the unexpected error ,please contact the system administrator.
please any one will help please
Regards,
Sangu

Hi,
You need to get your .DBC file from the server. Did you do the same?
Also paste the entire error stack to get a better idea.
BM

Hello, I have downloaded the new update to my iPhone 4 but I can not instal it , gives me a error signs would you please help me thank you. Nasser

Hello, I have downloaded the new update to my iPhone 4 but I can not instal it , gives me a error signs would you please help me thank you. Nasser

Please identify the error.

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

Similar Messages

Maybe you are looking for