Message "fpsane.cpp" line 269

I get this message when I try to save or find problems with program. After I hit the ok button 10 times it comes to failure screen and then shuts down.

Robby,
This error is related to what LabVIEW refers to as an 'insane object.' These errors, along with some possible solutions, are discussed in the following Knowledge Base article:
Knowledge Base 1F398NU0: What Does an "Insane Object" Error Mean and What Should I Do?
I recommend looking through this article and trying the various solutions listed there. Also, it appears that there was a bug in LabVIEW 6.0.x that caused these types of issues. If you are using this version of LabVIEW, you may want to consider upgrading. LabVIEW versions 6.1 and later have fixed this issue.
JohnM

Similar Messages

LV crashes when I try to save a VI - "fpsane.cpp line 269 error"

Dear LV users:
“Fpsane.cpp, line 269 error”
I have this error when I modify the VI and try to save it. Often I run it once and save it without problem. When I modify it again and try to save it, the error appears and LV crashes.
First I made a 6.0.2 upgrade and later I followed the “solving troubles” procedure at NI home page, like empty the TEMP directory and so on.
Later I sent my VI to NI support and I received the confirmation that they were able to reproduce the error, but not able to isolate it. Also they wrote that “Maybe can be a problem with the charts” and “it could be a bug in LV 6.0.2 which is fixed in LV 6.1”.
They saved my VI as a 6
.1 version and there were no problems (any error).
The problem is:
“ LV 6.1 is the next release (newest version) of LV and it will be released this year (the date is not fixed). That's not an update like LV 6.0.2 but a new version of LV. It must be purchased”
So I have a trouble here. I have some VIs that contains some parts in common. Now they are crashing too. I’m not confident anymore to make tests and modifications, since LV will crash again. What I’m doing after run my VI is exiting LV and open the VI again. Only after I can realize (and save) the modifications. This way is really a pain in a neck....
Please, can someone tell me a good way to isolate this problem or to solve it? I really don’t want to wait LV 6.1 nether to buy it to solve this “bug”....
Thank you in advance
Rodolfo
OS: Nt4 sp 6
LV 6.0.2

Dear LV users
Sorry for not have included the VI.
"test time save format.vi" is a learning program that contains some ideas to be used in another one. The error (fpsane.cpp) that appears here also was detected in LV 6. On the first time after grouping/edit some controls.
This error occurs when you modify the VI and try to save it. Often you run it once and save it without problem. When you modify it again and try to save it, the error appears. This is the same problem that happened with 2 other VI, even with one LV original example (after grouping).
The same error happened in another computer (also running NT4). All libraries were rebuilt during the installation of LV 6.02 and the TEMP directory is empty.
I hope that this vi will help us.
Thanks ag
ain
Rodolfo
Attachments:
Test_time_save_format.zip ‏92 KB

The last time you ran LabVIEW, an internal error or crash occurred at fpsane.cpp, line 444. WHY?

I keep getting this error every time I open LabVIEW 10. Everything seems to be working fine whenever I'm using it but for some reason, LabVIEW would not close properly and linger in the background. I still see the icon in the task bar and I would sometimes close it with task manager in order to re-use LabVIEW. Does anybody out there know how to fix this problem?
Attachment:
Solved!
Go to Solution.
Attachments:
lvlog2010-11-30-09-23-36.txt ‏3 KB

Thanks Hinz,
I believe I was able to solve this particular problem myself by using "LVdebugKeys". I was able to isolate the offending VI using the debug and it came out that an old "Write Test Data to File vi." does not work well with LV2010. I replaced this vi and it no longer gives me the error.
Thank you for your help.
Attachments:
Write Test Data To File.JPG ‏3 KB

Fpsane.cpp

After changing the History chart length in waveform chart and trying to save the vi, an error message popped up and it reads as follows,
Fatal Internal Error: "fpsane.cpp", line 397
LabView 8.0
Can anyone tell me what the problem is?

I also get this error, which is totally annoying.
I am currently working with some classes into a shared variable. After I add the variable to to routine, the LabView becomes really slow and crashes finally with the mentioned error.
This bug seriously hampers my development progress!
Bart
Logfile:
#Date: 2008 Feb 19 10:27:30 AM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 11:08 GMT
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x0080305A - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C48ADE - LabVIEW <unknown> + 0
0x00C497C6 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004DAF97 - LabVIEW <unknown> + 0
0x004E10B1 - LabVIEW <unknown> + 0
0x00C14A89 - LabVIEW <unknown> + 0
0x00C14C90 - LabVIEW <unknown> + 0
0x00C172E6 - LabVIEW <unknown> + 0
0x008032EF - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C070A - LabVIEW <unknown> + 0
0x00B7BA47 - LabVIEW <unknown> + 0
0x00CA8CCF - LabVIEW <unknown> + 0
0x006C055A - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C48ADE - LabVIEW <unknown> + 0
0x00C497C6 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004DAF97 - LabVIEW <unknown> + 0
0x004E10B1 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C14B7B - LabVIEW <unknown> + 0
0x00C14C90 - LabVIEW <unknown> + 0
0x00C172E6 - LabVIEW <unknown> + 0
0x008032EF - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00B7BA5D - LabVIEW <unknown> + 0
0x00803579 - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00B7BA5D - LabVIEW <unknown> + 0
0x00CAA12C - LabVIEW <unknown> + 0
0x00CA8FA3 - LabVIEW <unknown> + 0
0x00CA9515 - LabVIEW <unknown> + 0
0x00CA9F42 - LabVIEW <unknown> + 0
0x00D13F2F - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
.\typedesc\TDOMIdRefnum.cpp(1373) : DWarn: Insane dataspace: contexts do not match for udclass type at data=0x08f820f0
$Id: //labview/branches/Europa/dev/source/typedesc/TDOMIdRefnum.cpp#23 $
0x00501B06 - LabVIEW <unknown> + 0
0x0050339B - LabVIEW <unknown> + 0
0x0112DFDA - LabVIEW <unknown> + 0
0x010C452B - LabVIEW <unknown> + 0
0x010C452B - LabVIEW <unknown> + 0
0x00C501E2 - LabVIEW <unknown> + 0
0x0076BB5A - LabVIEW <unknown> + 0
0x0076FCD9 - LabVIEW <unknown> + 0
0x00C05721 - LabVIEW <unknown> + 0
0x0076CFE5 - LabVIEW <unknown> + 0
0x00C05721 - LabVIEW <unknown> + 0
0x0076CD42 - LabVIEW <unknown> + 0
0x007707DC - LabVIEW <unknown> + 0
0x00CA9A5E - LabVIEW <unknown> + 0
0x00CAA33B - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
sanity checking heap Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
sanity checking Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
Insane object at FPHP+10C in "Main window 800x600.vi": {dso } (0x200): Panel (FPSC)
.\panel\fpsane.cpp(392) : DAbort: Fatal insanities(0x200) exist in ReportInsanities, 'Main window 800x600.vi'
$Id: //labview/branches/Europa/dev/source/panel/fpsane.cpp#35 $
0x0076CEF3 - LabVIEW <unknown> + 0
0x007707DC - LabVIEW <unknown> + 0
0x00CA9A5E - LabVIEW <unknown> + 0
0x00CAA33B - LabVIEW <unknown> + 0
0x00CA8FA3 - LabVIEW <unknown> + 0
0x00CA9515 - LabVIEW <unknown> + 0
0x00CA9F42 - LabVIEW <unknown> + 0
0x00D13F2F - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
sanity checking heap Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
sanity checking Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
Message Edited by Bart_NLD on 02-19-2008 03:37 AM

Lv crashes every 10 days, "plotsupp.cpp, line 1330"

This vi continually writes to a buffer and displays on a waveform chart. Upon a trigger signal, a predefined amount of data (in the buffer) is written to a file and the vi ends. Labview is crashing every 10 days with failure message "plotsupp.cpp, line 1330". Mac G-4, OS 9, LabVIEW 6.1, 6031 I/O Card, 38 channels of data.

Hello �
What happens every 10 days? Does the program get to the same specific point after 10 days of running? What does that specific part of the program do? Does the user have interaction with the VI or is it running by itself?
The only report of this error crash we have is when the user tried to modify the labels in a control. Somehow the control got corrupted and the problem was fixed by replacing the controls in the front panel with new ones.
If this does not help, you can narrow the problem down and post a simple VI so that we can reproduce the issue.
S Vences
Applications Engineer
National Instruments

Linker.cpp line 2071 error

Gentlemen,
does anyone know what the message "linker.cpp line 2071 error" stands for (under labview 7.1.1 & XP)?
we are building an medium-size application, and experiencing that annoyance without any real hint about what causes crash.
Message Edited by olivierproditec on 02-06-2007 09:05 AM

Hi,
Do any of the VI's or subVI's have names similar to existing VI's in the palettes?
After how many tests does the crash happen? (Is there any way to predict when the crash will happen?)
Does it always crash at the same point in your application?

"fpsane.cpp" in line 269 appears when trying to save ma VI after the 1st run!

Hi LV-users,
this is a problem some of you may had before. But I still don't know how to solve this problem.
LV crashes when I try to save my VI after the 1st run telling me about the fpsane.cpp-error. It also tells about "INSANE object at FPHP+3EE4 in my VI" and it says
"{sub } (0x10)wave chart" and so on.
I wonder if their is a mistake in a sub VI, maybe because I'm working with references for my wave charts and their histograms which have to be saved if the acquired datapoints are not within tolerance.
I already upgrades my LV-Version to 6.02 and so on...I read about this solution in the Discussion Forum.
I added my VI and Sub VIs using references.
Can anybo
dy give me some advice?
Thanks, Kathrine
Attachments:
2405_D_Kurven_in_Cluster.vi ‏199 KB
Kurven_Sichtbar.vi ‏38 KB
3_Historie_speichern_B.vi ‏51 KB

Insane error are not due to your programming. There are several good pages on our site that discuss solving these errors. Goto www.ni.com >> support >> advanced search (it is at the bottom--click on the words). This lauches the best way to search our site because under option 2, you can limit your search to resources of interests. Enter insane in the all the words field and search everything. One of the first hits is a knowlegbase that discusses solving this issue.
Jeremy Braden
National Instruments

Error Message File: \ \src\rmsdk_api_readr.cpp Line: 1405 Expression: loc!=NULL

Error Message File: \ \src\rmsdk_api_readr.cpp Line: 1405 Expression: loc!=NULL

Please try on latest ADE version: 4.0.3

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Internal software error: .\PGCStreamInfo.cpp, line 1413

Im designing a DVD teaching project within Encore DVD 2.0.0.48678 from the Creative Suite 2 Production Premium software system. The project is very large and complex. As of now there are only 2 separate timelines. 1st time line has 50 chapters. 2nd time line is not finished but currently has 15 chapters. Because its a teaching DVD, there are also chapter play list created for each individual chapter. I also have a countless number of menus and links to sub menus and additional video links from the chapter play list. All of my links are set and operational with all functions in the individual menus working properly. This is an ongoing project for 3 months now, with perfect results prior to today. I have used the "preview from here" function with no problems to test the links and verify the menu structures with flawless results for the past 3 months. Today I was giving a demo of my progress, when I selected the "preview from here" I received this new error message, "internal software error: .\PGCStreamInfo.cpp. line 1413". I have checked and rechecked links, buttons, playlists, chapters, end actions, timelines, basically everything I could imagine and have even tried a computer restore point from 5 days back, at this time still have not resolved this issue.
AMD Athlon 64 3000+
2.01 GHz 1.00 GB of RAM
Microsoft Windows XP Home Edition Version 2002 SP2
Gigabyte GeForce 7300 GT videocard
Thanks for any suggestion, if more info is needed to solve this, i can provide it.

There are a couple of other threads about a similar error which seem to point to a possible chapter playlist problem:
Internal Software error ..... When 'preview from here' or Build
Chapter Playlist play order bug?

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

Failure : "resource.cpp", line 2477

When building an application on LABVIEW 6.1 on Window 98, I get the error message:"Failure : "resource.cpp", line 2477". Attached is my Labview failure log file
Attachments:
LabVIEW_Failure_Log.txt ‏1 KB

Hi Kluu,
This error appears when checking the "Do not compress target file" option when building an application. The workaround is to not check that option in Application Builder.
While in the application builder, in the "Target" tab, in "Build Options", do NOT check the "Do not Compress Target File" option.
We are currently looking into this and will soon be fixing it up.
Hope this helps.
Regards,
Pravin Borade
Applications Engineer, National Instruments

Failure: "might.cpp" line 815 on LabVIEW executable

Hi,
I have a program written in LabVIEW 6.1 on a Windows XP platform. The program includes an ActiveX container that shows an Internet Explorer content window (just like the "Using the Microsoft Web Browser ActiveX Control" example found on http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9BF111EE034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p_answer=&p_source=External
, but without the activex queue in that example).
After I built the executable, I was able to run the exectuable on the development machine without problem. However when my client runs it on his PC with LabVIEW runtime engine 6.1 installed, he gets the message:
Failure: "might.cpp" line 815
For assistance in reso
lving this problem, please record the procedeing information and navigate to www.ni.com/failure or contact national insturments.
I cannot find any information on might.cpp on the NI support site. Any idea of what can be done to fix this problem?
Thanks!
Dan

Hi dan,
you must contact NI support sending them the problem. "might.cpp" is a source module of LV and they can investigate the error.
Another thing you have to take into account is that LV stores the class ID and not the application. Has the client PC the same MS IE version installed? If not, the error could also result from different versions of the Active-X control.
As with the reporting Toolkit for MS Office you have to build a different version of your app for each different version of the control.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

DAbort 0x1A7102DF in fpsane.cpp when opening a 2011 vi in a machine with 2012 vs

DAbort 0x1A7102DF in fpsane.cpp
Error message appears when i try to open a vi with LV2012 created in other computer with 2011 version.
Does anyone know how to fix it?.

Does the VI open correctly on the 2011 machine?
Do new VIs work correctly on LV 2012? What about opening shipped examples?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Internal Software Error:.\Vobulator\Titleplaner\CVOBUPlanner.cpp,Line 331

I am very frustrated...
I am using Encore CS3 on a relatively fast system with 2g of ram. I have successfully burned disc using Encore CS3 but it is a crap-shoot. Sometimes it works and half of the time I get this:
Internal Software Error:.\Vobulator\Titleplaner\CVOBUPlanner.cpp,Line 331
I am trying to burn a simple disc - nothing crazy. A static menu with three chapters linked to 3 points on a 1hour and 45minute avi file in the timeline. I organize it check the project and everything is fine. I start the build and it begins to transcode - everthing is still good. After the transcode it begins to organize the disc or something - and that is when I get the error message.
I click OK on the dialog box and notice that the video in the timeline is now only 5 frames long and the audio is still there. (I thought the video had totally dissapeared but when I zoomed in for a closer look I realized it had ben reduced from almost 2 hours to 5 frames.) I look to the project window and it shows that the AVI has been transoded and it shows that time of the transoded file is normal length.... I am lost.
Anyone have any ideas?
Mat Cain

Long File Names Cause Crashing http://forums.adobe.com/thread/588273
And #4 Here http://forums.adobe.com/thread/666558?tstart=0
And This Message Thread http://forums.adobe.com/thread/665641?tstart=0
Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/
Also, for Encore CS4 Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS

Message "fpsane.cpp" line 269

Similar Messages

Maybe you are looking for