CPP error line 638

Hi I'm having problems with the CPP ERROR at line 638, my application includes profibus and vision. In the past when I had CPP ERRORS I had found if I sequenced the profibus VI this would eliminate the problem, however the problem has returned. I thought maybe it would be the IMAQ for the vision, so I bypassed the vision altogether, it is still in the code but not currently called or used. This hasn't helped either, I was wondering if the issue could be with too many VI's running at the same time, perhaps a memory allocation problem, but I don't know at this point.
This has been most frustrating I'm running out of I deals
Thanks
Jeffery Orn

Hello Colorado,
Normally when you are starting up LabVIEW after a crash or another error happens, LabVIEW will give you the cpp file name and the line number. You then have the option to investigate the error. This will send a report to NI so that we can work on finding why the error happens and what we can do to fix it. You should probably send that error to NI if you have not done so already.
Since the cpp file and the version of LabVIEW is missing from you post, you may want to include it. It would probably be helpful to others who may have run into this error.
I hope this helps.
Steven T.

Similar Messages

Windows LV6.0 running on Linux Wine: config.cpp error (line 404)

Have anyone tried to run LabView (Windows version) under Linux using the Wine "emulator"?
Trying this on Debian Woody, with a Win98 install of LabView 6.0 returns:
config.cpp error (line 404)
I tried to search for such a file on both Win/Linux partitions: there's none.
So how am i gonna check this line 404?
Any clue would be strongly welcome!

I agree with Labviewguru about getting Labview for Linux. The only
problem is that you have to dish out $2000 or $3500. They don't have a
Base package.
I'm not sure if NI recomends a particular window manager but I do know it
will run on any of them. In an extreme case I used it on a PII 233MHz,
64MB ram, and a 300 MB disk. It was a Slackware distro using the fvwm2
window manager. Ran great. Presently I run it with Gnome.
My point is that if you have to buy a LV for Linux license, at least you
can save money buy putting it on a machine that's been used as a paper
weight for several years.
-kevin
In article <[email protected]>,
"Labviewguru" wrote:
> I don't believe you can run LabVIEW in an e
mulation environment. There
> is too much system control that LabVIEW needs a handle on to be able to
> run on an emulator.
>
> The reason you are not able to find and troubleshoot that file is
> because it is part of the source code for LabVIEW, and doesn't exist
> except in a super secret vault which may or may not be located in Austin
> Texas...
>
> Are you aware that there is a version of LabVIEW for Linux? I believe
> that they recommend running KDE or similar GUI, but check on the support
> website for that at ni.com/linux.
>
> I hope that was enough of a clue...

Image.cpp error line 11035, LabVIEW 6.0

I recieved the error image.cpp, line 11035 and cannot find the patch to fix this error. The program shuts down when I try to print. Where do I find the correct patch for this error in Windows?
Thank you.

Hi, I believe that this problem was solved with patch 6.02 see: release notes for 6.02
Hope that this helps,
Erik van Dijk

Linker.cpp error @ line 2075 w/Labview 6.0.2 and Appl. Builder

So frustrating! The libraries run in the debugging environment just fine. No errors and two minor warnings. I have to constantly tweak and upgrade these libraries because each has about 40 VIs and are rebuilt on average two times a week. The executables are used at a dozen places and I can't place the developer system on each computer, that is what the Builder and the Labview runtime engine is for.
About a month ago after doing very minor changes in one VI I rebuilt the library into an executable using the same build file and BANG, I get this linker error. After acknowledging Labview disappears (stealth crash). Well eventually I figured I had to copy the diagram of the VI I had changed (yes, complete with changes) to another blank VI. After deleting the old VI and renaming the new (it used to be blank) VI, I rebuilt it. Everything was fine.
Well I have tried to rebuild frequently after each change and save often several copies back a month but somehow this has been futile as the error is back in both libraries. In the two libraries I maintain there are as many as 20 VIs identical between the two libraries. I make a change in one VI in one of the libraries then use the library manager to copy it to the other library. This has worked hundreds of times over the last year and half. Well somehow the problem has come back in both libraries and I can't isolate the bad VI.
Obviously one (or maybe more!) of the VIs are put together wrong but Labview doesn't detect it. I don't use any fancy linking to anything other than DAQ and SERP drivers, everything else are simple VIs (just Labview code) with only the Labview supplied VIs talking to DLLs. I have tried my little cut and paste trick with the last few changed VIs but it didn't work. I tried to use Application Builder to build VIs seperately but that was useless. I tried elminating the lastest changed VIs from the library and rebuilding but to no avail. It fails approximately 1/4 to 1/3 into the build process bar indicator but the Builder doesn't say what file it is building so I can't relate it to any specific VI. Tried relating the bar position to a latest changed list and an alphabetical list but that was inconclusive.
This issue is currently being worked on by NI support but I want to try the resources of the developer community because this is such a rare problem with big implications (at least to me).

OK, NI support came through! If the library is mass compiled the typedef in my controls won't mess with the linker. Labview 6.1 solves this problem.
Since my email to NI support got returned I'm not sure they received it. The message is: it worked and thanks.

Labview 6.0.2 patch does not remove my "image.cpp" error

I have an industrial PC with the following characteristics:
* Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours only option)
* ROBO 608, Industrial SBC motherboard with onboard video driver, from Chips and Technologies, 69000; 2MB onboard video memory
The standard VGA driver is the most recent driver, and in fact the only one available for this hardware.
Labview 5.1 runs without problem on this machine, but when I loaded Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error, line 4150" every time I tried adding a graph to the front panel. Changing the screen acceleration properties did not make any difference.
Though I have gone back to version 5.1
for the time being, my application would benefit substantially from the current version.
Are there any fixes for this, or is Labview 6 simply not compatible with VGA screen drivers?
Thanks,
Jo

I have LV6.0.2 running on an Arcom SBC with the Chips and Technology 69000
HiQVideo 2MB display chip. This chip is not capable of rendering 3D graphics.
I have noticed the CPU will go to 100% usage if I open a sub-VI panel with lots
of the new 3D graphics on it, as the display chip passes rendering off to the
main processor.
Perhaps you could try replacing the LV6 3D graphics with the older versions
that are available on the Controls pallet. At 16 colors the new graphics look
terrible anyway.
I am running the chip at 1024 X 768 screen resolution and 65K colors with
no other problems.
Regards,
Alan Brause
"Jo" wrote in message news:[email protected]..
> I have an industrial PC with the following characteristics:
>
> * Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours
> only option)
>
> * ROBO 608, Industrial SBC motherboard with onboard video driver,
> from Chips and Technologies, 69000; 2MB onboard video memory
>
> The standard VGA driver is the most recent driver, and in fact the
> only one available for this hardware.
>
> Labview 5.1 runs without problem on this machine, but when I loaded
> Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error,
> line 4150" every time I tried adding a graph to the front panel.
> Changing the screen acceleration properties did not make any
> difference.
>
> Though I have gone back to version 5.1 for the time being, my
> application would benefit substantially from the current version.
>
> Are there any fixes for this, or is Labview 6 simply not compatible
> with VGA screen drivers?
>
> Thanks,
> Jo

What is memory.cpp at line 1038?

We have been running the same test in LabVIEW for a few years. Now all of a sudden, we are starting to get a memory.cpp error at line 1038. The test normally runs days at a time (~2 weeks), but we are getting this error after about 18-24 hours. Any ideas of what could cause this? Could this be caused by any Windows XP hotfixes? We are using LabVIEW 7.1 on a windows xp machine.

I've already checked out that particular site for info. And we do open and close files in our tests. And we do have quite a few loops. But it has worked with no issues for a few years and much longer time spans (and also more open/close files and loops). So after the error occurred on our only two machines (with exact set up) that run LabVIEW 7.1 (the rest are still on 6), we rolled one back to a date before all of the hotfixes occured and we have had no problems since. The second machine had an issue with rolling back so IT came and reinstalled XP. The problem is that they install an updated version and we cannot install an older one. It has Service Pack 3 in it and I think there are some hotfixes that came along with it that are the source of the problem. But I can't gaurantee it. Hopefully we'll figure it out soon.

Getting CURL.cpp - Error?

Hi,
I updated to Mountain Lion and when using a audio converter, Sound Grinder 3.4.4, I get an error that reads as follows:
CURL.cpp - error "No URL" when getting Full Path, in getFolderFullPathAs CString0, line: 248
Can't find any thing regarding it so if someone can enlighten me of what this is and if there is a way to fix it I would appreciate it.
Thanks!

Funny I posted this and bang I figured it out. Seems Apple is getting as bad as PC's with their convoluted errors that make zero sense. Basically Sound Grinder's path to save a file, which was set in the preferences, was deleted by the new install. So once I told it where to save it was fine.
Thanks for the quick reply by the way!

Good morning, I have the following problem. I can not start Adobe Muse on my computer because I get a box Assertion Failed in file "... \ src \ ape \ DOMFontProvider.cpp" at line 482: numFontadded = = 1 Doregisterfont fail to add font. Check museapp \ he

Good morning, I have the following problem. I can not start Adobe Muse on my computer because I get a box Assertion Failed in file "... \ src \ ape \ DOMFontProvider.cpp" at line 482: numFontadded = = 1
Doregisterfont fail to add font. Check museapp \ hello \ resources for missing files

Are you still facing the same issue ? if yes then please post the screenshot of exact error and few details such as if you are getting this error while opening a specific file or on double click on Muse itself ?
Thanks,
Sanjit

Image.cpp error

When I try to print the labview panel & diagram on my new canpn pixma iP1000 printer I get the following message. I am using LV6.0
"image.cpp error" in line 11035. Please contact ni.com. Anyone can help!

hi labview 1958,
please look here:
Failure: image.cpp, line 11035 in LabVIEW 6.0
Greets!

Load.cpp error

i fail to run my VI and it shows load.cpp line:4081 failure. what happen?

There are number of threads on this error. Here are some:
Failure : "load.cpp", line 4081
Failure : load.cpp in line 4081
failure at load.cpp in line 4081
Is
there a fix yet for error load.cpp line 4081?
They all happen when you try to open in LabVIEW 6.1 a VI, that has some tab controls on its front panel, and that was developed in the student or evaluation edition version 6i.
If you send me the VI that causes the error, I may be able to recover it. You can either post it here, or send it to [email protected]
Zvezdana S.
National Instruments

I am gettign objheap.cpp error

i had a cluster ( pretty large one ), i added few more controls to the cluster. when i tried to open the main vi where this custer is a contol in the FP, further the cluster is used for processing(updating , reading etc)in the code.
When i try to open the main vi with the modified cluster i get objheap.cpp error and the labview closes by itself when i press ok. What could be the reason for this problem.
Is there any precaution i need ahere to when working with large clusters.

Did you get a line number? That would go a long way to finding the reason for the error.
I believe that your VI has become corrupted due to the number of controls on your front panel. Not counting the controls in the clusters, how many objects do you have?
The following link points to another link that discusses the interal errors of LabVIEW. It might help.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000007510000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control

Failure : load.cpp in line 4081

I'm working in a new application demo. Yesterday i saved it normally, but today when i tried to open gives me this failure message:
"Failure : load.cpp in line 4081"
I need to recover the file, because i don´t have any backups.
Thank you in advance, regards.
Fede

On Tue, 12 Nov 2002 12:58:08 -0600 (CST), Fede2002 wrote:
>I'm working in a new application demo. Yesterday i saved it normally,
>but today when i tried to open gives me this failure message:
>"Failure : load.cpp in line 4081"
>
>I need to recover the file, because i don=B4t have any backups.
>
I had the same error changing video resolution (developed both in
1280x1024 and 1024x768).
The error has gone returning to the higher resolution.
Try It & let us know! :-)
Bye!
http:\\www.depquest.net

HP Officejet Pro 8500 909g Windows 7 64 bit Scrip error line 2115

When printing from the laptop I get a message
Script error
Line 2115
Char l
error-- unspecified error
Code 0
Url res:/ieframe.dll/prview.is

Hello GayeLake and Beer,
I believe the answer(s) to this issue can be found HERE.
If I have helped in any way, just click the Kudos star on the left. Also, if your issue has been resolved, don't forget to select Accept as Solution

Dbms_xmlsave Error line 65

We are passing a clob to dbms_xmlsave.insertxml successfully for all XML clobs under .5 megs but once we go over that size the Error line 65 "Invalid arguments encountered processing ROW ELEMENT 0 show up. Is this a size limitation for dbms_xmlsave? Is there an approach that can handle clobs over .5 meg?

Looks like XDB is not installed. You can verify this by doing desc RESOURCE_VIEW. If RESOURCE_VIEW does not exist then you need to install XDB to install the dbms_xmlstore() package
You need to run the script catqm in $ORACLE_HOME/rdbms/admin. This will add the DBMS_XMLSTORE package. catqm takes 3 arguments. The XDB password, typically XDB, the tablespace to be used for the XDB repository and the name of the temporay tablespace to be used by XDB. Once this has been run DBMS_XMLSTORE() should be there.
Once XDB has been installed you should get the following:
SQL> desc dbms_xmlstore
PROCEDURE CLEARKEYCOLUMNLIST
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
PROCEDURE CLEARUPDATECOLUMNLIST
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
PROCEDURE CLOSECONTEXT
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
FUNCTION DELETEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           VARCHAR2                IN
FUNCTION DELETEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           CLOB                    IN
FUNCTION DELETEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           XMLTYPE                 IN
FUNCTION INSERTXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           VARCHAR2                IN
FUNCTION INSERTXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           CLOB                    IN
FUNCTION INSERTXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           XMLTYPE                 IN
FUNCTION NEWCONTEXT RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
TARGETTABLE                    VARCHAR2                IN
PROCEDURE SETKEYCOLUMN
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
COLNAME                        VARCHAR2                IN
PROCEDURE SETROWTAG
Argument Name                  Type                    In/Out Default?
CTX                            NUMBER                  IN
ROWTAGNAME                     VARCHAR2                IN
PROCEDURE SETUPDATECOLUMN
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
COLNAME                        VARCHAR2                IN
FUNCTION UPDATEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           VARCHAR2                IN
FUNCTION UPDATEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           CLOB                    IN
FUNCTION UPDATEXML RETURNS NUMBER
Argument Name                  Type                    In/Out Default?
CTXHDL                         NUMBER                  IN
XDOC                           XMLTYPE                 IN
SQL>
Message was edited by:
mdrake

How to avoid output file and error lines when condition does not match

Hi Experts
A customer want to send purchase order files to several vendors and each vendor has their own requirement to content and file format. I have prepared scenarios for each vendor and a template is (conditionally) called when CardCode matches. It works fine, - PO file is generated when CardCode matches, but error lines are written to SAP B1 Control Center each time CardCode does not match the one defined in a scenario (100 or more times per day). Problem is that these error lines does not get automatic deleted. Conditional processing are made in this way:
Result Message in SAP B1 Control Center when CardCode does not match:
I tried to avoid an error line in SAP B1 Control Center when CardCode does not match in this way:
Then no error lines are written to SAP B1 Control Center, but an output file is generated each time (order file when CardCode matches and an empty file when CardCode does not match).
Any suggestions on how to avoid both errors types (error lines in SAP B1 Control Center and empty output files)?
Or - can lines in SAP B1 Control Center be automatic deleted?
Regards
Steen

Hi Steen,
using <b1im_skip> should be the right approach, if you're working with B1 OUTBOUND.
Following extract form the B1i help describes the usage to skip the outbound processing:
1.1 Skipping Outbound Processing
If you do not want to hand over the message to the receiver system, the scenario step can create a special tag that indicates to generic processing in the integration framework to skip the message processing.
Add the following to the final transformation atom (atom0):
<b1im_skip xmlns= ”” info=”my info” msglog=”true” msgout="yes">
If the integration framework skips the message, it puts the message log information to the Filtered section, if the message log is switched on. The result message contains the Message skipped by vBIU logic information.
info
To display an individual message, define it using the info attribute.
msglog
If you want to avoid an entry in the message log, introduce the msglog attribute and set it to false.
msgout
To display the skip information in the Success section of the message log, use the msgout attribute and set it to yes.
In case you don't want any MsgLogEntry in case of a skipped message, please enter the following in final atom0:
<xsl:template name="transform">
<xsl:attribute name="pltype">xml</xsl:attribute>
<xsl:choose>
<xsl:when test="$msg/BOM/BO/Documents/row/CardCode='C20000'">
<xsl:call-template name="transform2"/>
</xsl:when>
<xsl:otherwise>
<b1im_skip info="skipped" msglog="false"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
Best regards
Bastian

CPP error line 638

Similar Messages

Maybe you are looking for