Error on AIX6.1 when building 'C' application pointing to oracle 10.2.0.3

Hi
We are trying to build our 'C' application on AIX6.1 pointing to oracle 10.2.0.3 but we are not able to build it successfully because we are getting below error. However, the build is successful if we use oracle 11. Would appreciate for any kind of help or pointer. Thanks in advance.
System default option values taken from: /usr1/arbor/3p/../3poracle/AIX/precomp/admin/pcscfg.cfg
Syntax error at line 148, column 2, file /usr/include/standards.h:
Error at line 148, column 2 in file /usr/include/standards.h
#warning The -qdfp option is required to process DFP code in headers.
.1
PCC-S-02014, Encountered the symbol "warning" when expecting one of the followin
g:
a numeric constant, newline, define, elif, else, endif,
error, if, ifdef, ifndef, include, line, pragma, undef,
an immediate preprocessor command, a C token,
The symbol "newline," was substituted for "warning" to continue.
Syntax error at line 77, column 50, file /usr1/arbor/3p/terrapin/AIX/include/sw_Types.h:
Error at line 77, column 50 in file /usr1/arbor/3p/terrapin/AIX/include/sw_Types
.h
FILE* stream);
.................................................1
PCC-S-02201, Encountered the symbol "FILE" when expecting one of the following:
... auto, char, const, double, enum, float, int, long,
ulong_varchar, OCIBFileLocator OCIBlobLocator,
OCIClobLocator, OCIDateTime, OCIExtProcContext, OCIInterval,
OCIRowid, OCIDate, OCINumber, OCIRaw, OCIString, register,
short, signed, sql_context, sql_cursor, static, struct,
union, unsigned, utext, uvarchar, varchar, void, volatile,
a typedef name, exec oracle, exec oracle begin, exec,
exec sql, exec sql begin, exec sql type, exec sql var,
The symbol "enum," was substituted for "FILE" to continue.
Syntax error at line 99, column 5, file /usr1/arbor/3p/terrapin/AIX/include/sw_Types.h:
Error at line 99, column 5 in file /usr1/arbor/3p/terrapin/AIX/include/sw_Types.
h
sw_dumpMethod dump;
....1
PCC-S-02201, Encountered the symbol "sw_dumpMethod" when expecting one of the fo
llowing:
} char, const, double, enum, float, int, long, ulong_varchar,
OCIBFileLocator OCIBlobLocator, OCIClobLocator, OCIDateTime,
OCIExtProcContext, OCIInterval, OCIRowid, OCIDate, OCINumber,
OCIRaw, OCIString, short, signed, sql_context, sql_cursor,
struct, union, unsigned, utext, uvarchar, varchar, void,
volatile, a typedef name,
Syntax error at line 0, column 0, file ck_OracleBlobDB.pc:
Error at line 0, column 0 in file ck_OracleBlobDB.pc
PCC-S-02201, Encountered the symbol "<eof>" when expecting one of the following:
; : an identifier, end-exec, random_terminal
Error at line 0, column 0 in file ck_OracleBlobDB.pc
PCC-F-02102, Fatal error while doing C preprocessing
*** Error code 1
Regards,
Vishal

Similar Messages

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

When building an application unit tests are added to a support directory

Why are unit tests (.lvtest files) added to a support directory when building an application? I cannot find a way to exclude them from the support directory.

I'd imagine this is happening to you because they are in the "Dependencies" section of your project file (*.lvproj). Is this correct?
If so, you should add them to your project file somewhere. Then you will be able to prevent them from being installed. In my experience LabVIEW grabs files it thinks are nesecary from the Dependencies list and installs them in a support directory.

Error 1 when building my application in Labview 2010 Version 10.0f2

I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.

Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S.

Error message when building an application for Labview PDA

When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error of heads when build the .dll by visual studio 2003

I am trying to call the dll function in labVIEW which build by visual studio 2003.
while I compile the basic program in visual studio 2003,the dll will be built successfully,but if I include heads like or in my program, etc.Compiling has the error of ,so the dll can not be built.
I have trued to look for the solution in NI Discussion Forums,but havent seen the related article about the error of including .
If someone can answer this for me,that will be a great help,and I'll be so appreciate if anyone get me out
of the trouble.
Sean

I'm a little unclear about your question. What is the exact error that you are receiving and at what point are you receiving it? Is the error occurring when calling the DLL in LabVIEW or is it occurring when building the DLL in Visual Studio? Further clarification about exactly what the problem is and where it is occurring would be a big help!
Regards,
E. Sulzer
Applications Engineer
National Instruments

"application error" in LV8 when building an .exe .

Hi All
I am trying to build an .exe using LabView 8. I can generate a preview, fine, I can see all my files and where they will be, however
I click the build button to star building the application and the application starts build fine. I get messages like:
First "Initializing build"
Then "Preparing File", "Loading items to build", "updating libraries" and "Processing .............vi"
Suddenly just crash with the following error message pop up window:
"dwwin.exe - Application Error
The application failed to initialize properly(0X=0000142). Click on "OK" to terminate the application"
Does anyone knows what 's wrong??
Thank You Very Much in advanse

Togos,
Well at least you got it to build once. So even with the exact same settings you were unable to rebuild the EXE? That is certainly odd. Since you are able to build the example, we know that it is probably the VI that is being built that is causing the problem. I have a couple of suggestions for you at this point. The first is to try to create a new Build Specification and just use the default options to try to get the EXE to compile. Since you probably have already tried this, there is a more involved suggestion. This sounds like a very large VI, so I might suggest trying to whittle down the problem by deleting code and attempting to rebuild the EXE. Once you have deleted enough code, you will probably get down to a point where the VI will compile (hopefully before you reach an empty block diagram). At this point we can test to see if the recently deleted past of the VI will compile by itself to see if it is a specific code snippet that is causing this problem. As mentioned this is a lengthy and involved process, so before I tried this I might treat this as a VI corruption error, and try to copy and paste the Block Diagram from the problematic VI to a blank one to see if that makes any difference.
Let me know if any of that helps or if you have any other questions!
Andy F.
National Instruments

Placing ini file in specific location when building the application

Hello,
I have a small problem. I have an ini file that I use to store certain parameters. Lets call this file app.ini. When I build the Application.exe, it puts that file into the data directory. I was hoping that it would be one level higher and be located in the same directory as Application.exe is (otherwise it won't read the file correctly.) I looked at the Source File Settings in the Category list in the properties window for the build and set the Destination to be "Same as caller", but that didn't put it where I wanted it. I'd really like this file to be one directory higher when I make my build in order for my app to read it correctly. Any suggestions?
I use this executable later on when I make my installer and the problem simply propagates there too, not good.
Solved!
Go to Solution.

One way to solve the problem:
1) In build properties window select Destinations and create a new destination. Select as "Destination Path" the same dir where the exe will be stored
2) Assign this destination to the .ini file.
Let me know if it works
Marco

When Building an Application, which .icd file gets used on the deployment machine?

Hello all,
I am building an application that needs to support multiple configurations for multiple cameras. I currently have a development machine with everything you would expect to be installed, and a deployment machine that does not have LabVIEW installed, but does have LabVIEW run-time, appropriate drivers and MAX.
My question is: When I build an application, I would like to be able to give a particular end user their own .icd file which the built application will recognize on their own machine. Then the .icd parameters can be tailored to their application. Is this possible?
I had hoped that this would just be the case, however when I compiled an application and tried to run it on the deployment machine it was obvious that the built application retained the .icd settings on the development machine and ignored the .icd settings on the deployment machine. Perhaps it has something to do with how I am compiling? Any additional info would be awesome.
Thanks everyone for your time!

Cole,
The easiest thing to do would be to manually replace the default .icd files with your configured .icd files at the directories specified in the following knowledge base.
Where Do I Place My Camera File Once I Download It?
LabVIEW won't copy the .icd configuration automatically because it is a configuration file for the IMAQ driver which is platform independent. Another option would be to create VI that runs at installation or application run time that programmatically configures the .icd file. You can add the .icd file to your project and copy the attributes to the camera file that exists on the deployed machine or replace it entirely.
Regards,
Isaac S.
Applications Engineer
National Instruments

Error code -13 when building installer

Hello,
I need some help! I am trying to create an installer for my application; which was created with no problems; but I keep getting a message about an error code -13. I'm adding an image of the message since it is a long one. I really don't understand what the error means or how to repair it. Any help I could get is appreciated!

Hello rd.mcdt,
The following link has information about a similar problem, could you try to follow the process described on the link? Please look for error code 13 instead error code 30 and let us know if this helps.
Error 30 Occurred at CDK_CreateNewWizard_Invoke.vi.ProxyCaller When Trying To Build a LabVIEW Installer:
http://digital.ni.com/public.nsf/allkb/8E5E6C58C625B88A8625786A005B21E0
Best Regards
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

When building my application the system W98 crashing

I have an application with subvi dinamically linked, My O.S. is W98 and the Labview 6.1 with the Application builder 6.1.The latest version of MAX(3).The target is P3 666Mhz 32MB ram. When i compile the application in this target machine i have a crash of system (only reeboot for resolve it).I have try in my portable with W2000 P4 2,4Ghz 512MB ram, and the application is builded correctly no error and the run is OK.
Thanks Nicola
Bytelabs.it

Hi Randy,
The previous version is not too small of new version.I buy another bank memory and trying but now i have also a message error in the step of loading VI in application builder.
The message is :
LABVIEW ha provocato un errore di pagina non valida nel
modulo KERNEL32.DLL in 017f:bff7d76b.
Registri:
EAX=fed9f000 CS=017f EIP=bff7d76b EFLGS=00010207
EBX=81672784 SS=0187 ESP=00dcee20 EBP=00dcee44
ECX=fecc3c50 DS=0187 ESI=0000dbaf FS=4507
EDX=bffc9490 ES=0187 EDI=fed31280 GS=45a6
Byte all'indirizzo CS:EIP:
83 38 00 74 28 83 c0 08 46 3b f1 72 f3 be ff ff
Immagine dello stack:
00dcee44 00000000 00000000 ce114ff0 bff92e7f 81672784 bff7db0e 81672784 00000000 001f0003 bff8521c 81672784 ce114ff0 001f0003 00dcee84 00000000
Whe
n the process of loading is in act i have very full of memory an i'm with you for the memory small.
If you have advise for the message error thank's for answer.
Kind Regards
Nicola
Bytelabs.it

Error 8 occurred when building an executable due to file permission error?

I received this error on executable builds from two different .vis. Other .vis in the project build without incident and the message below doesn't seem to indicate the file that is causing the problem, unless it is the SPT-errors.txt file listed at the end of the error message.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files\National Instruments\LabVIEW 8.5\project\errors\Japanese\SPT-errors.txt

Hi DanielAllis,
Like mentioned earlier, there is most likely an application on the internet that you can find and use where you can see what processes are calling specific files or folders to see if that specific file is being used by anything else. It doesn't sound like this is the root of your problem, but it couldn't hurt to check. Also, I have seen a similar problem to this with someone who was using the software Subversion and Tortoise with their application. I am not familiar with this software in particular, but I have attached a link below that goes through the steps that this other person took to try and fix the same error when having this software on their computer. Let me know if any of this helps!
http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537
Regards
Noah R
Applications Engineering
National Instruments

Getting the message "Error generating preview" when building the installer.

I'm getting this error when attempting to expand the application in the installer. However, I am able to preview the built application without errors. Please see the attached screen shots. I have built this application several times before without incident. I made some modifications to the application and now I'm getting this error. What does it mean? I'm using Win XP and LV8.5.
Dave
Attachments:
App Builder Error.pdf ‏55 KB

If I understand this correctly, you are able to build the executable--it's just that you are not able to see the preview in the Application Builder. Is that right?
I searched some of our internal documentation. I found a record of a customer who also experienced the "unable to generate preview" error when upgrading to a new version. He was able to solve it by making sure that all of the VIs ini the build were saved in the current version of LabVIEW. This may be helpful for you.
Also, I would like to recommend that you create a new forum thread rather than posting on a very old thread like this one. You will generate more discussion from the other ni.com users. It also helps our R&D department to automatically keep track of how often these issues are reported.
Jeremy P.
Applications Engineer
National Instruments

Getting "Error 10 occurred" when building exe

I am getting the following error when trying to build an executable: "Error 10 occurred at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\Daq\lvdaq.dll"
Listed under possible reasons were:
LabVIEW: Duplicate path.
NI-488: New I/O attempted with old I/O in progress.
I made some changes and added a .vi to my program, but get no errors if I run the program from the top level .vi.
Any ideas?

Hi Rob,
For some reason there's an issue with the link to the lvdaq.dll in your
application. The lvdaq.dll is used by the DAQ VIs from the palette -
are you by any reason calling the DLL directly from a Call Library
Function Node?
Can you please explain what changes you made to the VI that caused the
issue. It would also be a help if you submit the VIs that you are
trying to build into an executable, thanks.
- Philip Courtois, Thinkbot Solutions

Error on AIX6.1 when building 'C' application pointing to oracle 10.2.0.3

Similar Messages

Maybe you are looking for