Build applicatio​n error
i am now getting a build application error. i tried a vi that had been build previously, stilll get the error. the program runs ok in labview.
Problem Description :
Hello, i never had a problem 'building application' before.
now i get an error and 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 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi ->
AB_Build.lvclassave.vi -> 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_Build.lvclass:Build_from_Wizard.vi ->
AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi ->
AB_Create_Build_Application.vi -> EBUIP_Global_OnCommand.vi ->
EBUIP_Global_OnCommand.vi.ProxyCaller
Possible reason(s):
LabVIEW: Cannot save a bad VI without its block diagram.
NI Software : LabVIEW version 2011
NI Hardware : Select one if your issue is related to hardware device
Driver Version :
OS : Windows 7
Thank You
Timmar wrote:
I get this a lot,
I mean an awful lot.
Caused when Labview Corrupts a project VI, usualy by one of it's ever so frequent crashes.
It won't tell you it's broken but it is,
Indeed, there is an inconsistency between what's shown on the BD and what actually is there in compiled form. Specially obvious with XControls. The BD's can be completley empty, but still LV searches for the XCtl reference when you open the empty FP and void BD???
Several tricks:
Save the VI with another name, close the old one, overwrite the old VI by renaming the new one.
On the block diagram press: CTRL-A -> CTRL-X (select all and cut it out) Create a new vi and paste in the code. Overwrite the old broken VI with the new one.
Only do class name and move path's when the projects are in memory. Not always feasible if you have a lot of re-use, some projects end broken searching for old paths. So that is a bit painful to update all your projects, specially with some ref's are correct and other's not.
CTRL-SHIFT->Run VI, forces a recompilation of the VI hierarchy
Mass compile to find broken stuff.
Good version control is a must to revert if things go haywire and badly out of control with LV.
Br,
/Roger
Similar Messages
-
Build finished with ERROR - Failed to pack public part
Hi,
I am getting an error when I try to build a Development Component in CBS. This is what the build log says:
Ant build finished with ERRORS
Failed to pack public part: Failed to get InputStream for resource D:\usr\sap\PVD\JC01\j2ee\cluster\server0\temp\CBS\2\7\.B\3570\DCs\vecnet.co.nz\general\rimp\preq\preqform\preqcreate\_comp\src\configuration\Components\nz.co.vecnet.general.rimp.preq.preqform.preqcreate.CreatePurchReqComp\CreatePurchReqCompView_Create_Purch_Req_IF.xdp
Error: Build stopped due to an error: Failed to pack public part: Failed to get InputStream for resource D:\usr\sap\PVD\JC01\j2ee\cluster\server0\temp\CBS\2\7\.B\3570\DCs\vecnet.co.nz\general\rimp\preq\preqform\preqcreate\_comp\src\configuration\Components\nz.co.vecnet.general.rimp.preq.preqform.preqcreate.CreatePurchReqComp\CreatePurchReqCompView_Create_Purch_Req_IF.xdp
Build plugin finished at 2008-10-02 15:31:45 GMT12:00 (NZDT)+
Total build plugin runtime: 31.769 seconds
Build finished with ERROR
Could you please tell me why I am getting this error, and how do I resolve this one?
Thanks,
AjayWas never able to find an answer for this on SDN and haven't had the issue in a long time so I'm closing question.
-
SOA Order Booking build properites - BindWebApp error: javax.management.Ref
Hi All,
I am trying to understand the "SOA Order Booking Application" which is given as part of example in SOA Demo.
I tried to follow all the steps as per the user guide for this example, but when I am trying to build XML for SOA Order Booking, I get the following error
Buildfile: C:\Pratap\SOA_DEMO\SOADEMO\SOAOrderBooking\build.xml
java Java Result: 1
pre-deploy:
validateTask:
echo-----
| Validating workflow
validateTask url is file:/C:/Pratap/JDeveloper/jdevstudio10134/integration/bpm/support/files/WorkflowTaskDefinition.xsd
validateTask Validation of workflow task definitions is completed without errors
deployDecisionServices:
echo
| Deploying decision services for SOAOrderBooking on uspg2-10-032, port 8888
deployDecisionServices 08/10/10 15:29:48 Notification ==>Application Deployer for rules_default_SOAOrderBooking_1_0_DecisionService STARTS.
deployDecisionServices
deployDecisionServices 08/10/10 15:29:48 Notification ==>Undeploy previous deployment
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\rules_default_SOAOrderBooking_1_0_DecisionService.ear begins...
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\rules_default_SOAOrderBooking_1_0_DecisionService.ear ends...
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Starting application : rules_default_SOAOrderBooking_1_0_DecisionService
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initializing ClassLoader(s)
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initializing EJB container
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Loading connector(s)
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Starting up resource adapters
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initializing EJB sessions
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Committing ClassLoader(s)
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initialize DecisionService-web begins...
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Initialize DecisionService-web ends...
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Started application : rules_default_SOAOrderBooking_1_0_DecisionService
deployDecisionServices
deployDecisionServices 08/10/10 15:29:49 Notification ==>Application Deployer for rules_default_SOAOrderBooking_1_0_DecisionService COMPLETES. Operation time: 922 msecs
deployDecisionServices
deployDecisionServices
deployDecisionServices *{color:#ff0000}BindWebApp error: javax.management.ReflectionException*
*{color}*
deployDecisionServices
*{color:#ff0000}BUILD FAILED*
**C:\Pratap\SOA_DEMO\SOADEMO\SOAOrderBooking\build.xml:126: Error while deploying decision services on server "uspg2-10-032"*{color}*
Total time: 6 seconds
deployDecisionServices BindWebApp error: javax.management.ReflectionException
I have the build properties file
domain=default
rev=1.0
admin.user=oc4jadmin
admin.password=oc4jadmin
hostname=uspg2-10-032
http.port=8888
rmi.port=12401
oc4jinstancename=home
asinstancename=
opmn.requestport=6003
platform=ias_10g
#platform=oc4j_10g
same every where.
C:\Pratap\SOA_DEMO\SOADEMO\SOAOrderBooking\build.xml:126: Error while deploying decision services on server "uspg2-10-032"
Kindly let me know what should be done to resolve errors.
Regards,
Pratap
Edited by: user10244582 on Oct 10, 2008 4:00 PM
Edited by: user10244582 on Oct 10, 2008 4:02 PMThanks!! absolutely spot on solution.
I developed in 10.1.3.4, got this error, then deployed using 10.1.3.1. Fantastic.
Just that build.xml generated by 10.1.3.4 contains isSSL attribute, which seems is not supported by 10.1.3.1. So I created a dummy project in 10.1.3.1, and replaced the build.xml of my rules project with the one generated by 10.1.3.1 jdev -
Build applicatio​n freezes, USB-6501
I am running LabView 7.1.1 on Mac OS X 10.3.9. I am controlling a couple of instruments via GPIB and the USB-6501 with DAQmx Base. My VI works fine. I'm trying to build a stand alone application with the application builder and it freezes during the build. I have unchecked the box to "Disconnect type definitions and remove unused polymorphic VI instances" in the Application Settings of the Application Builder and it still freezes during the build. I've tried to recompile the VI by holding down the option and shift keys while clicking the run button and it locks up then too. I have successfully built applications without the USB-6501. Can anyone offer some help? Thank you.
Hi All-
Unfortunately MAX is not available on Mac for troubleshooting, Mike. Vob, can you please verify whether you installed NI-DAQmx Base prior to or after installing the LabVIEW 7.1.1 patch? The driver must be reinstalled after installing the LabVIEW patch and after mass compiling your directories. You should not mass compile after the NI-DAQmx Base installation.
Also, this line from from the NI-DAQmx Base ReadMe might be pertinent:
If, when building an executable or shared object project using NI-DAQmx Base VIs, the Application Builder catches an error, you must restart LabVIEW before running any NI-DAQmx Base VI.
Please give these suggestions a try and repost if you are still experiencing problems.
Thanks-
Tom W
National Instruments -
Interface Builder encountered an error communicating with the iPhone Simulator
Hi,
I downloaded the latest iOS SDK and tried simple helloworld program. Once I try to build it in the xcode, it shows the following 2 errors. I tried to re-install the SDK several times, and it doesn't work.
CompileXIB MainWindow.xib
cd /Users/qingzhao/Desktop/ch1/HelloWorld
setenv IBCMINIMUM_COMPATIBILITYVERSION 3.2
setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr /bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Developer/usr/bin/ibtool --errors --warnings --notices --output-format human-readable-text --compile /Users/qingzhao/Desktop/ch1/HelloWorld/build/Debug-iphonesimulator/HelloWorld.a pp/MainWindow.nib /Users/qingzhao/Desktop/ch1/HelloWorld/MainWindow.xib --sdk /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.2 .sdk
2010-09-22 13:07:18.333 ibtool[1155:607] Assertion Failure: [toolTask isRunning]
2010-09-22 13:07:18.337 ibtool[1155:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-09-22 13:07:18.337 ibtool[1155:607] Line: 140
2010-09-22 13:07:18.519 ibtool[1155:607] Backtrace:
0 IBCocoaTouchPlugin 0x00000001039b7dcc IBAttachToCocoaTouchTool + 1669
1 IBCocoaTouchPlugin 0x00000001039b5e9f IBAskClassInTargetRuntimeForValueForKeyPathUsingRe sultMarshallerWithContext + 147
2 IBCocoaTouchPlugin 0x0000000103a2d963 IBReleaseIsWildcat + 1791
3 IBCocoaTouchPlugin 0x0000000103a2d538 IBReleaseIsWildcat + 724
4 IBCocoaTouchPlugin 0x0000000103a2d57b IBReleaseIsWildcat + 791
5 IBCocoaTouchPlugin 0x00000001039b29f9 IBReplaceClassNamePrefixWith + 1588
6 IBCocoaTouchPlugin 0x00000001039b682e IBBuildMarshalledDescriptionOfDocument + 2093
7 IBCocoaTouchPlugin 0x00000001039b0515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
8 IBCocoaTouchPlugin 0x00000001039abcad IBUISegmentConfiguration + 2784
9 ibtool 0x000000010000829f
10 ibtool 0x0000000100006e0c
11 ibtool 0x0000000100003161
12 ibtool 0x0000000100001dbc
2010-09-22 13:07:18.519 ibtool[1155:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1158) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
2010-09-22 13:07:18.520 ibtool[1155:607] Assertion Failure: NO
2010-09-22 13:07:18.520 ibtool[1155:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-09-22 13:07:18.520 ibtool[1155:607] Line: 351
2010-09-22 13:07:18.521 ibtool[1155:607] Backtrace:
0 IBCocoaTouchPlugin 0x00000001039b5f62 IBAskClassInTargetRuntimeForValueForKeyPathUsingRe sultMarshallerWithContext + 342
1 IBCocoaTouchPlugin 0x0000000103a2d963 IBReleaseIsWildcat + 1791
2 IBCocoaTouchPlugin 0x0000000103a2d538 IBReleaseIsWildcat + 724
3 IBCocoaTouchPlugin 0x0000000103a2d57b IBReleaseIsWildcat + 791
4 IBCocoaTouchPlugin 0x00000001039b29f9 IBReplaceClassNamePrefixWith + 1588
5 IBCocoaTouchPlugin 0x00000001039b682e IBBuildMarshalledDescriptionOfDocument + 2093
6 IBCocoaTouchPlugin 0x00000001039b0515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
7 IBCocoaTouchPlugin 0x00000001039abcad IBUISegmentConfiguration + 2784
8 ibtool 0x000000010000829f
9 ibtool 0x0000000100006e0c
10 ibtool 0x0000000100003161
11 ibtool 0x0000000100001dbc
2010-09-22 13:07:18.521 ibtool[1155:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Failed to determine the value for systemColors of UIColor.
Exception name: IBAssertionFailure
Exception reason: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1158) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
What can I do ? Thank you very much!!!I found this on stack overflow.com and thought it would apply to this article discussion for some users even though I don't understand how to revert the version (through git?)
I think this is a compatibility issue. I think the .xib has moved to Xcode 4 (as shown by the line setenv IBC_MINIMUM_COMPATIBILITY_VERSION 4.2) which Xcode 3.2's version of ibtooldoes not understand.
I think you need to revert to a version of the .xib prior to the update to Xcode 4."" -
Interface Builder encountered an error communicating with the iPhone Simula
Hi,
I downloaded the latest iOS SDK and tried simple helloworld program. Once I try to build it in the xcode, it shows the following 2 errors. I tried to re-install the SDK several times, and it doesn't work.
CompileXIB MainWindow.xib
cd /Users/qingzhao/Desktop/ch1/HelloWorld
setenv IBCMINIMUM_COMPATIBILITYVERSION 3.2
setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr /bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Developer/usr/bin/ibtool --errors --warnings --notices --output-format human-readable-text --compile /Users/qingzhao/Desktop/ch1/HelloWorld/build/Debug-iphonesimulator/HelloWorld.a pp/MainWindow.nib /Users/qingzhao/Desktop/ch1/HelloWorld/MainWindow.xib --sdk /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.2 .sdk
2010-09-22 13:07:18.333 ibtool[1155:607] Assertion Failure: [toolTask isRunning]
2010-09-22 13:07:18.337 ibtool[1155:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-09-22 13:07:18.337 ibtool[1155:607] Line: 140
2010-09-22 13:07:18.519 ibtool[1155:607] Backtrace:
0 IBCocoaTouchPlugin 0x00000001039b7dcc IBAttachToCocoaTouchTool + 1669
1 IBCocoaTouchPlugin 0x00000001039b5e9f IBAskClassInTargetRuntimeForValueForKeyPathUsingRe sultMarshallerWithContext + 147
2 IBCocoaTouchPlugin 0x0000000103a2d963 IBReleaseIsWildcat + 1791
3 IBCocoaTouchPlugin 0x0000000103a2d538 IBReleaseIsWildcat + 724
4 IBCocoaTouchPlugin 0x0000000103a2d57b IBReleaseIsWildcat + 791
5 IBCocoaTouchPlugin 0x00000001039b29f9 IBReplaceClassNamePrefixWith + 1588
6 IBCocoaTouchPlugin 0x00000001039b682e IBBuildMarshalledDescriptionOfDocument + 2093
7 IBCocoaTouchPlugin 0x00000001039b0515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
8 IBCocoaTouchPlugin 0x00000001039abcad IBUISegmentConfiguration + 2784
9 ibtool 0x000000010000829f
10 ibtool 0x0000000100006e0c
11 ibtool 0x0000000100003161
12 ibtool 0x0000000100001dbc
2010-09-22 13:07:18.519 ibtool[1155:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1158) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
2010-09-22 13:07:18.520 ibtool[1155:607] Assertion Failure: NO
2010-09-22 13:07:18.520 ibtool[1155:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-09-22 13:07:18.520 ibtool[1155:607] Line: 351
2010-09-22 13:07:18.521 ibtool[1155:607] Backtrace:
0 IBCocoaTouchPlugin 0x00000001039b5f62 IBAskClassInTargetRuntimeForValueForKeyPathUsingRe sultMarshallerWithContext + 342
1 IBCocoaTouchPlugin 0x0000000103a2d963 IBReleaseIsWildcat + 1791
2 IBCocoaTouchPlugin 0x0000000103a2d538 IBReleaseIsWildcat + 724
3 IBCocoaTouchPlugin 0x0000000103a2d57b IBReleaseIsWildcat + 791
4 IBCocoaTouchPlugin 0x00000001039b29f9 IBReplaceClassNamePrefixWith + 1588
5 IBCocoaTouchPlugin 0x00000001039b682e IBBuildMarshalledDescriptionOfDocument + 2093
6 IBCocoaTouchPlugin 0x00000001039b0515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
7 IBCocoaTouchPlugin 0x00000001039abcad IBUISegmentConfiguration + 2784
8 ibtool 0x000000010000829f
9 ibtool 0x0000000100006e0c
10 ibtool 0x0000000100003161
11 ibtool 0x0000000100001dbc
2010-09-22 13:07:18.521 ibtool[1155:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Failed to determine the value for systemColors of UIColor.
Exception name: IBAssertionFailure
Exception reason: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1158) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
Exception backtrace:
(null)
Exception infonull)
/* com.apple.ibtool.errors */
/Users/qingzhao/Desktop/ch1/HelloWorld/MainWindow.xib: error: ibtool failed with exception: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Failed to determine the value for systemColors of UIColor.
Exception name: IBAssertionFailure
Exception reason: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1158) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
Exception backtrace:
(null)
Exception infonull)I'm using 10.6.4 and having the same issue. Reinstalled the newest SDK a few times (Xcode 3.2.4 with 4.1 of the iOS SDK). I can't build anything to run on the iPhone Simulator, but building regular Mac apps works fine. Here's what it tells me when I try to build and run:
CompileXIB MainWindow.xib
cd /Users/myusername/Development/iTennis
setenv IBCMINIMUM_COMPATIBILITYVERSION 3.2
setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr /bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Developer/usr/bin/ibtool --errors --warnings --notices --output-format human-readable-text --compile /Users/myusername/Development/iTennis/build/Debug-iphonesimulator/iTennis.app/M ainWindow.nib /Users/myusername/Development/iTennis/MainWindow.xib --sdk /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.2 .sdk
2010-10-26 17:07:21.838 ibtool[1428:607] Assertion Failure: [toolTask isRunning]
2010-10-26 17:07:21.934 ibtool[1428:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-10-26 17:07:21.934 ibtool[1428:607] Line: 140
2010-10-26 17:07:22.016 ibtool[1428:607] Backtrace:
0 IBCocoaTouchPlugin 0x000000010383ddcc IBAttachToCocoaTouchTool + 1669
1 IBCocoaTouchPlugin 0x000000010383be9f IBAskClassInTargetRuntimeForValueForKeyPathUsingResultMarshallerWithContext + 147
2 IBCocoaTouchPlugin 0x00000001038b3963 IBReleaseIsWildcat + 1791
3 IBCocoaTouchPlugin 0x00000001038b3538 IBReleaseIsWildcat + 724
4 IBCocoaTouchPlugin 0x00000001038b357b IBReleaseIsWildcat + 791
5 IBCocoaTouchPlugin 0x00000001038389f9 IBReplaceClassNamePrefixWith + 1588
6 IBCocoaTouchPlugin 0x000000010383c82e IBBuildMarshalledDescriptionOfDocument + 2093
7 IBCocoaTouchPlugin 0x0000000103836515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
8 IBCocoaTouchPlugin 0x0000000103831cad IBUISegmentConfiguration + 2784
9 ibtool 0x000000010000829f
10 ibtool 0x0000000100006e0c
11 ibtool 0x0000000100003161
12 ibtool 0x0000000100001dbc
2010-10-26 17:07:22.017 ibtool[1428:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1431) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
2010-10-26 17:07:22.018 ibtool[1428:607] Assertion Failure: NO
2010-10-26 17:07:22.018 ibtool[1428:607] File: /SourceCache/IBCocoaTouchPlugin/IBCocoaTouchPlugin-123/IBPlugin/Utilities/IBObj ectMarshalling.m
2010-10-26 17:07:22.018 ibtool[1428:607] Line: 351
2010-10-26 17:07:22.019 ibtool[1428:607] Backtrace:
0 IBCocoaTouchPlugin 0x000000010383bf62 IBAskClassInTargetRuntimeForValueForKeyPathUsingResultMarshallerWithContext + 342
1 IBCocoaTouchPlugin 0x00000001038b3963 IBReleaseIsWildcat + 1791
2 IBCocoaTouchPlugin 0x00000001038b3538 IBReleaseIsWildcat + 724
3 IBCocoaTouchPlugin 0x00000001038b357b IBReleaseIsWildcat + 791
4 IBCocoaTouchPlugin 0x00000001038389f9 IBReplaceClassNamePrefixWith + 1588
5 IBCocoaTouchPlugin 0x000000010383c82e IBBuildMarshalledDescriptionOfDocument + 2093
6 IBCocoaTouchPlugin 0x0000000103836515 IBBestTargetRuntimeForConversionFromTargetRuntime + 18393
7 IBCocoaTouchPlugin 0x0000000103831cad IBUISegmentConfiguration + 2784
8 ibtool 0x000000010000829f
9 ibtool 0x0000000100006e0c
10 ibtool 0x0000000100003161
11 ibtool 0x0000000100001dbc
2010-10-26 17:07:22.020 ibtool[1428:607] Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Failed to determine the value for systemColors of UIColor.
Exception name: IBAssertionFailure
Exception reason: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1431) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
Exception backtrace:
(null)
Exception info:(null)
/* com.apple.ibtool.errors */
/Users/myusername/Development/iTennis/MainWindow.xib: error: ibtool failed with exception: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Failed to determine the value for systemColors of UIColor.
Exception name: IBAssertionFailure
Exception reason: Interface Builder encountered an error communicating with the iPhone Simulator. "Interface Builder Cocoa Touch Tool" (1431) failed to launch and exited with status 11. Please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" for further information.
Exception backtrace:
(null)
Exception info:(null) -
I've been getting often enough strange compilation errors from the labview application status window, the weirdest being
[10:30:36 AM] Status: Error
linking...
Program Size: Code=94136 RO-data=2936 RW-data=2664 ZI-data=14536
".\Obj\LabVIEW.axf" - 0 Error(s), 0 Warning(s).
Status: Build failed.
The build failure without errors seems to be a red herring; it actually builds and links fine, but for some reason Labview takes offense to it and reports a build failure. If you rerun the build again it resumes where it had "failed" and the target is loaded and started... very strange behaviour, and it is not limited to the LM3S project, I get it with the MCB2378. Anybody knows why this would happen?
Anyway just putting this out there for others who would encounter this problem.Hey Simon,
When you reload the code and it compiles correctly does it operatre as expected? Here are some things that I believe we have gone over but should be useful for other members of the forums:
Debugging in Keil uVision
After c generating an embedded application, you should have the project loaded in the Keil uVision IDE. The following steps will help you debug the application.
Click "Reset CPU"
Click "Run"
Click "Halt."
You should be stopped in a loop in a function named OCDI_RDMWaitOnStart in OCDICheckPoint.c. The function waits for LabVIEW to be ready by checking the variable named OCDI_RDMStart. Since we are not using LabVIEW to run the application, we need to change this variable manually using the watch window.
Add the variable OCDI_RDMStart to the watch window.
Set any other breakpoints that you want in the project.
Select View->Period Window Updates
Click "Run"
From the watch window, change the variable OCDI_RDMStart to 0x01. The application will exit the loop and run your VI.
To run the application again:
Click "Reset CPU"
Click "Run"
From the watch window, change the variable OCDI_RDMStart to 0x01.
You can also add "one button dialog" nodes to your VI, and this will do a printf that you can see in the Keil IDE. Choose View->Serial Window->Real-Time Agent Terminal to see the window that receives the output.
My guess is that the first time you run it the project is looking for a pointer or something and then the second time it know knows where it is and finishes without error.
Sam S
Applications Engineer
National Instruments -
Hi Everyone,
I need your help again: I got below error when building DC:
crm/isa/web/b2b: Build failed for sap.com/crm/isa/web/b2b(sap.com_SAP-SHRWEB_1) in variant "default": The Build terminated with errors
Error: Build stopped due to an error:
IO error scanning directory C:\Documents and Settings\10062219\.dtc\3\t\2D3B976A9B8E2D6D0E97D7D6C151292D\dependand\WEB-INF\xcm\sap\system
Can anyone please help me to resolve this issue?
Thanks, JinHi Jin,
If you talk about default .metadata folder of your NWDS work space then do as below.
1. Open NWDS
2. Click on Window-->Preference
3. Expand "Workbench" and select "Work Space" on right side you will see path for default work space for user.
4. Go to that path i explorer you will see .metadeta folder.
I hope you are looking for this.
eCommerce Developer -
Error message in applicatio​n builder in Build Applicatio​n.vi
Hello,
I'm trying to make an executable file but I recive the following error message:
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
Possible reason(s):
LabVIEW: The VI is not executable.
Does anyboy know the reason for this message?
Thanks.
Javier de PablosHello Jaime,
I've tried to compile a very simple VI (there is only a while loop that executes nothing and counter is wired to an indicator.
I've attached you.) and I've got the same error. So the code or any dynamic VIs are not the problem.
I've repaired the Application Builder within Control Panel > Add and Remove programs but I haven't resolved the problem.
Javier de Pablos
Attachments:
Untitled.vi 13 KB
gg.bld 1 KB -
I'm running LabVIEW 6.1 on Win XP Pro, and my application
builds fine, but I can't create an installer.Dependency Walker will show all of the DLLs NIMSIDistKit.dll is dependent on. There is a tree view in the top but the flat list at the bottom will probably be more helpful. It should show the following dlls (at least on a Windows 2000 system):
ADVAPI32.DLL
GDI32.DLL
KERNEL32.DLL
MSI.DLL
NIMSIDISTKIT.DLL
NTDLL.DLL
OLE32.DLL
RPCRT4.DLL
USER32.DLL
If one of these DLLs is missing it will have an error message displayed beside it. I think all of them are regular Windows DLLs so if you are missing one of them your computer might be having other problems. You could try to reinstall LabVIEW to see if it will install a copy of the dll, but you might have to reinstall Internet Explorer or some portion of the OS to get all
of them.
Probably the most important dll is the MSI.dll. If it is missing or too old it might be the problem. I have version 2.0 but I think version 1.1 of this DLL will also work. If you don't have the dll or the right version run \applibs\distkit\redist\InstMsiW.exe (if on Win NT/2000/XP) or InstMsi.exe (95/98/ME). This will install/update MSI (Microsoft Installer) on your machine.
You can also press F9 to toggle showing just the filename and the whole path to the dlls. Besides NIMSIDistKit.dll all of them should be loading from your system folder. If not you may have multiple copies of that DLL and the correct one is not being found. -
Building applicatio​n exe USB-9215 DAQmxBase LabView7.1 errors
Hello
I’ve been building DAQ applications using the NI 4-channel USB 9215 module. It has a sampling rate of 20ks/sec and with four channels the maximum I can sample per channel is 5000s/sec.
It works with no problems at this rate and lower rates, however when I compile an application and run it, I get the following message:
Onboard device memory overflow. Because of system and/or bus bandwith limitations, the driver could not read data from the device fast enough to keep up with the device throughput. Error code: -200361
This message appears irrespective of the sampling rate, even down to 1s/sec !!. I’m using Labview 7.1 with the ‘DAQmx Base Read.vi’ in a while loop. The PC spec is very high and no other applications are running. The PC has 4 USB ports; only two are in use, one for a mouse, the other for the 9215.
Any ideas would be welcome
Thanks in advanceHi there,
What operating system are you running on and what service pack version?
It seems that there have been occurences of errors similar to this (with other USB devices 9201/9221) reported on machines with Windows XP service pack 1. In particular the version of the Windows file usbehci.sys, as reported in the following knowledge base article.
http://digital.ni.com/public.nsf/websearch/ADC80B3995042EB98625704C006B5753?OpenDocument
If this applies to your situation, I would suggest upgrading the service pack as recommended in the knowledge base article and see if this helps.
Regards
Hannah
NIUK & Ireland -
Why do I get Error 1 when building applicatio​ns
I'm creating an executable using the Labview 6.1 application builder but I get this error: Error 1 ocurred at Gsim Sintax Check.vi. I didn´t install the Simulation and Control toolkit I copied the vis I needed to use them.
What can I do?
Thanksyen,
Do you get this error at build of the application or from the executable itself? Does the VI run in the development environment?
I would build the executable from the development machine that has the toolkit on it.
Brett B. -
I have seen numerous posts about this problem when building an application without a block diagram in LV 7.x, however, I am recieving this error on LV 8.2. Whats most disturbing about it, is that it always hangs when processing Clear Errors.vi. I have tried my source on two different machines, to no avail. Also I tried to do a mass recompile of the entire vi.lib again no help. It is very important that this program compiles, however I cannot get past this error. Any suggestions?
My specific error message is here:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1073 occurred at ABAPI Dist disconnect td-poly.vi -> ABAPI Dist Chg and Save VIs.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
Possible reason(s):
LabVIEW: This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.
-PaulHello Paul,
I am sorry for not elaborating previously. This issue has been documented previously for further investigation to our R&D group (# 3ZK9LGP2). In the report I found that this error, though vague in the description, is fixed by enabling MathScript Support.
To enable MathScript support, check the checkbox in the application properties for the 'Enable MathScript support' option.
-Bob
-Bob -
My VI calls SubVIs (all with the same connections) in a loop with one 'call by reference'. It works great in the VI but when I build an Application I receive Error 1003. After that I read in the KnowledgeBase when I build the Application I must add dynamically all the SubVIs I call by reference. Works fine at the moment but the amount of the SubVIs is rising steadily (approximately 10 per week) and there are many users all over the world of this application. So it is practically impossible and very uncomfortable to build a new application everytime the amount of SubVIs rises. There must be another solution maybe some kind of initialization, adding
the paths of the dynamic called SubVIs programmatically???You do not have to include all the dynamically called subVIs in your build. If you look at the shipping example called Plug In Example, the dynamically called VsubIs are in a subfolder called plugins. In this example, the paths to the subVIs are created based on what files are present and which have the correct type specifier. The high level VI can be built into an executable. The plugins folder could also be included with one or two subVIs but once installed, new subVIs can be distributed separately and just put into the folder. The only trick is to make sure that the path to the plugins folder is correctly obtained whether the VI is run in development mode or as an exe.
-
Error in Build Applicatio​n (EXE)
Hi,
There is an error is prompt as attached when I was trying to build the exe.
Both my Labview 2012 & Database toolkit are evaluation version.
I have no idea how to choose the different option as the error message mentioned.
Is there any alternative way to build the exe?
By the way, my PC still has the full activated version of Labview 8.5.1, can I get any assist from there?
Thanks.
Attachments:
Capture.JPG 51 KBHi tantan,
If you have activated 8.5 then why you are not using this for building exe ?
Any specific reason ?
Kudos are always welcome if you got solution to some extent.
I need my difficulties because they are necessary to enjoy my success.
--Ranjeet
Maybe you are looking for
-
Cannot send a PDF with the Send Mail function
Send PDF as document fails on Adobe Reader on Ubuntu Linux 12.04 LTS. Send Link works.
-
Navigation showing completed form field values in URI
Hi, Using ADF, I have a form for entering values that I want the user to complete and then click a Search button that navigates to another page passing the values the user entered as traditional GET type parameters in the URI. I do not seem to be hav
-
Interaction History in Account assignment block
HI, We are creating the Activity for the accounts and it is visible in the planned activity of my accounts screen. when the document is closed it disappears. i am not able to find any documents in the interaction history assignment block in accoun
-
What is the best Business tax software to use on MACs
What is the best Business tax software to use on MACs?
-
I am taking an online course and need to download the videos to my Imac. How do I do this....new to the mac world