Error 1003 when compiling...

Using LabVIEW 7.1 with the Application Builder...
When building a particular VI, I get Error 1003 ("The VI is not executable"). The VI will execute when opened normally. The option that seems to cause the error is having the box checked that says, "Disconnect type definitions and remove unused polymorphic VI instance". When the box is not checked, the VI will compile.
The VI in question uses both ActiveX methods for Microsoft Excel, and GOOP (I would imagine one of those is to blame).
The problem is that I have isolated this small VI, but it is really part of a huge application which--I haven't tested this to find out but... I would imagine will be even more bloated if extra uneccessary code is added. If I can't compile this one little VI with that option checked, then everything else won't compile either, so it will have to remain unchecked when compiling the very large application (hence the issue).
I can upload the VI in question if anyone wants to look at it.

Joe Guo wrote:
what are the excel versions on your development and target machines? Sometimes you can build an application with a lower Excel version and it still work with the newer version of Excel.
-Joe
I am developing on a PC with Excel '97 and targeting a PC with Excel '03. When I first ported my code to the Office '03 machine, the ActiveX methods/properties broke that were different so I modified them to make them work on the '03 machine. Since it was just the code in one .llb file, I maintained independent versions of that .llb--one on my machine, one on the Office '03 machine.
The complications are that:
- The Office '03 machine is not local to me
- The Office '03 machine has all the hardware on it and obviously a much newer version of Office
- The Office '03 machine is not typically used for development
- My development PC can't have Excel '97 and '03 installed at the same time
- A third '97 PC is also involved in building the application since our Software Configuration Management department has to independently verify the build.
Ideally, I'd like to be able to drop in the Excel '03 .llb file I use and force it to build the application installation package regardless of whether or not the ActiveX component for Excel '03 is registered on my system--it will be registered on the target system, which is what's important. I talked with NI about this to submit a notice to R&D.
The other thing I am currently looking at is figuring out if I can temporarily unregister the '97 ActiveX components and register the '03 components on a PC so that LabVIEW won't break when it loads the '03 version of the .llb file. I don't have much experience in that department, which would apparently involve the RegSvr32 app.

Similar Messages

Error 1003 when loading a VI dynamically on LabView Run-time ini file configuration

hi all,
I have a problem with my runtime excutable.
On 4 systems, all running XP it runs fine.
On 2 systems ( one a new install of just LVRT 2011 SP1 ) I have:
Error 1003 when loading a VI dynamically on LabView Real-time
Or more spoecifically the error code is 1003 and the error source is Open VI Reference.
When the RT app runs correctly I get these paths:
Path Sent to Open Vi Reference: Yeast_Grower.exe\Tecan_talk_Control.vi,
Path Returned from Open Vi Refence: C:\Program Files\Yeast_Grower\Yeast_Grower.exe\Tecan_talk_Control.vi,
On a system that does gets the 1003 Open Vi Refence error I have the same Path Sent but of course no path returned as it does not open.
To be sure that the vi Dyanmically called vi is compiled and valid at runtime I also include a copy of in the main.vi.
To be extra sure I have also installed the runtime versions of VISA and DAQmx.
I have compiled it with and without the "Use LV 8 calling hiaracy"
My conclusion as this stage is that either the installation of LVRT 2011SP1 misses something the earlier LVRT installtions make.
or is there a MyApp.ini or LVRT .ini that controls how the RT dyanim calls are handled.
Help very welcome how to solve this puzzle.
thanks
michael

I understand that all the PCs (6 of them) have LV 2011 SP1, runtime or the development system installed. Right?
How many of these PCs have the source code available on them?
-> Only one of them has the source code.
I am not sure I understood 'I also include a copy of in the main.vi'. Does it mean you placed the subvi in the main.vi?
-> I meant I have included in main.vi the actual vi that is called dynamically - but only where it is not called.
Did you try including the sub vi which is called dynamically, as 'Always included' in the EXE build?
-> No, I did not know of this option - but the above I did this by default.
Edit: Did you verify the software versions of LV RT, VISA etc on all the PCs? Are they same?
-> I did verify even added DAQmx just in case
There is lots of material available on this forum for error 1003 and dynamic vi calling. Did you find anything useful to try among the forums threads?
-> I did view many of them.
I did finally find the answer.
I have a subvi (callNet.vi ) in the dynamically called vi (dynamic ) that calls .Net libraries.
Now the thing is that this subvi callNet.vi is coded out by enclosing it in a Disable structure.
In fact this subvi ( callNet.vi) does not even compile - ie it has a broken arrow
however if enclosed in a Disabled structure and disabled, the enclosing vi compiles OK.
However I have discovered that even with the .Net calling subvi (callNet.vi) in the Disabled state of the Disabled structure
the enclosing vi (dynamic.vi ) does NOT run - although it compiles just fine.
Once I installed the .Net libraries (I actually did include them with my app installer ) with the vender's supplied installer
then my app now successfully calls the dynamic vi.
So the Summary and warning is: Even if the dynamic called vi is included in Main.vi and Main.exe runs ( but does not call the dynamic vi - except when called dynamically at later some point ) and even if, in this case, the .Net calling subvi is disabled out ie no .Net calls are made the dynamically called vi will not run when called dynamically.
I hope that is not too confusing. In summary it seems the Disable structure does not entirely disable.
Michael

Error 1003 when running .exe

I am having a problem with error 1003 when I run a built application. I have searched the forums and found many others with this problem, but they encounter the problem while building the application, not while running the built .exe.
I have a top level VI (AutoRun.vi) that calls 3 VIs in sequence. All three are called in the same manner. The first two work fine, but I get this error with the third sub vi. This is how I call the subvi:
Use App.kind, check for "Run Time System" (strip app path twice), or "Development System" (strip app path once)
Build path to combine stripped path and file name of subvi to open
open vi reference
Invokee Node - Open FP
         Activated - T
         State - Standard
Invoke Node - Run VI
         Wait until done - T
          Dispose ReF - F
Invoke Node - Close FP
Close VI Reference
The error I get is:
Error 1003 occurred at Invoke Node in AutoRun.vi
Possible reasons:
LabView: the VI is not executable
I do not get this error while running in the development environment. Only when I run it as a .exe. Also I have had no problems with this code in the past. I just made a small change and now I have this problem. I have gone back to the old code and have the problem with it too.
I build the app by starting the app builder, selecting the top level VI, adding dynamic VIs and select all 3 subvis. The front panel of the second VI is not visible while running.  I have to go in and manualy change the "Remove Panel" in the build settings for this VI from the default yes to no. If I do not do this I get an error while trying to run the built application. I have no idea why this happens either, but making this change fixes the problem. After this I select build.
BTW, I have LabView 7.0

Hello,
Not sure what happened on your end, but if the problem comes back repost and we'll explore it!
Best Regards,
JLS
Best,
JLS
Sixclear

Error message when compiling book "file is corrupt" referring to a photo. Or "cannot find original photo". Can you use photos that have been "edited" out of "Book Mode"?

Error message when compiling book "file is corrupt" referring to a photo. Or "cannot find original photo". Can you use photos that have been "edited" out of "Book Mode"?

I did copy it to my desktop, but it still won't let me open it. I think the file on the disc might be corrupt or something like that though the cd itself checks out fine as far as viruses go. I was able to verify the disc, but that's about it. My husband tried it on his iMac and we have the same issue. It's unzipping the folder, but won't let us open the folder on both the Mac Book Pro or the iMac by double clicking, going to file/open or right clicking. It just keeps saying the same message as I posted above. I think I'm just going to have the client put the pictures on either a memory card or a USB memory stick so she won't have to compress the files for zipping purposes. It's been too frustrating trying to open this folder on this cd she gave me. She said she created/zipped the cd on her Mac Book Pro but it sure won't open on mine.

Errors occured when compile the bpel process

Errors occurred when compile the bpel process using bpel designer for Eclipse:
(com.oracle.bpel.designer_0.9.13)
using PM: bpel_jboss_101200
More error infomation following:
Buildfile: E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml
main:
[bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: Invalid expression statement.
[bpelc] retun true;
[bpelc] ^
[bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: ';' expected.
[bpelc] retun true;
[bpelc] ^
[bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:208: Method setPartneLinkBinding(com.collaxa.cube.rm.suitcase.PartnerLinkBindingDescriptor) not found in class com.collaxa.cube.engine.types.bpel.CXPartnerLink.
[bpelc] __pl.setPartneLinkBinding(getProcessDescriptor().getPartnerLinkBindings().getPartnerLinkBinding(__pl.getName()));
[bpelc] ^
[bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:584: Undefined variable: __ctx
[bpelc] __setOutgoingLinks(__sc, __ctx);
[bpelc] ^
[bpelc] 4 errors
BUILD FAILED
E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml:28: ORABPEL-01005
Error in java files auto-generated when compiling ,why?
Thanks!

when compiled again without any change, the same errors like above are not occurs
more info.
Buildfile: E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml
main:
BUILD SUCCESSFUL
Total time: 9 seconds
BUT, some errors occurs in BPEL PM server and in Console the process is not available
more Info: Because I using Chinese version,some chinese Info occurs in the error infomation ,so i have translated some character into English.
process "AboutTest" (version "1.0") compiled sucessfully
15:49:15,718 INFO [STDOUT] <2007-05-11 15:49:15,718> <INFO> <default.collaxa.cu
be.engine.deployment> process "AboutTest" (version "1.0") loaded sucessfully.
16:25:25,265 INFO [STDOUT] <2007-05-11 16:25:25,250> <INFO> <default.collaxa.cu
be.compiler> validating "E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0.jar\
AboutTest.bpel" ...
16:25:35,015 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
.jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: Invalid expression statement.
16:25:35,015 INFO [STDOUT] retun true;
16:25:35,015 INFO [STDOUT] ^
16:25:35,031 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
.jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: ';' expected.
16:25:35,031 INFO [STDOUT] retun true;
16:25:35,031 INFO [STDOUT] ^
16:25:35,859 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
.jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:208: Method setPartneLinkBinding(com.col
laxa.cube.rm.suitcase.PartnerLinkBindingDescriptor) not found in class com.colla
xa.cube.engine.types.bpel.CXPartnerLink.
16:25:35,859 INFO [STDOUT] __pl.setPartneLinkBinding(getProcessDescript
or().getPartnerLinkBindings().getPartnerLinkBinding(__pl.getName()));
16:25:35,859 INFO [STDOUT] ^
16:25:35,859 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
.jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:584: Undefined variable: __ctx
16:25:35,859 INFO [STDOUT] __setOutgoingLinks(__sc, __ctx);
16:25:35,859 INFO [STDOUT] ^
16:25:35,859 INFO [STDOUT] 4 errors
16:25:36,343 INFO [STDOUT] <2007-05-11 16:25:36,312> <ERROR> <default.collaxa.c
ube.engine.deployment> <CubeProcessFactory::generateProcessClass>
process "AboutTest" (version "1.0") compiled failed.
16:25:36,359 INFO [STDOUT] <2007-05-11 16:25:36,359> <ERROR> <default.collaxa.c
ube.engine.deployment> <CubeProcessLoader::create> can not compile the class .
can not compile the bpel class generated from "AboutTest".
16:25:36,375 INFO [STDOUT] <2007-05-11 16:25:36,375> <ERROR> <default.collaxa.c
ube.engine.deployment> process "AboutTest" (version "1.0") loaded failed!!
16:25:37,281 INFO [STDOUT] <2007-05-11 16:25:37,265> <ERROR> <default.collaxa.c
ube> <BaseCubeSessionBean::logError>
if you have installed patched in server, please check whether the proriety "bpelcClasspath" contained the patch class.
16:25:37,343 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
sHolder.bind(CubeProcessHolder.java:1257)
16:25:37,343 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
sHolder.loadAndBind(CubeProcessHolder.java:870)
16:25:37,421 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
sHolder.loadArchive(CubeProcessHolder.java:812)
16:25:37,421 INFO [STDOUT] at com.collaxa.cube.engine.CubeEngine.loadProces
sArchive(CubeEngine.java:985)
16:25:37,421 INFO [STDOUT] at com.collaxa.cube.ejb.impl.BPELDomainManagerBe
an.loadProcessArchive(BPELDomainManagerBean.java:390)
16:25:37,421 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(
Native Method)
16:25:37,421 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(N
ativeMethodAccessorImpl.java:39)
16:25:37,421 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invo
ke(DelegatingMethodAccessorImpl.java:25)
16:25:37,421 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:3
24)
16:25:37,421 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer$Conta
inerInterceptor.invoke(StatelessSessionContainer.java:683)
16:25:37,421 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedCo
nnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.StatelessSessionInstanc
eInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.i
nvokeNext(AbstractTxInterceptor.java:84)
16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWit
hTransactions(TxInterceptorCMT.java:282)
16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:148)
16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.SecurityInterceptor.inv
oke(SecurityInterceptor.java:111)
16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invoke(L
ogInterceptor.java:191)
16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInter
ceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
16:25:37,437 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer.inter
nalInvoke(StatelessSessionContainer.java:331)
16:25:37,437 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java
:709)
16:25:37,437 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor81.invoke(
Unknown Source)
16:25:37,437 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invo
ke(DelegatingMethodAccessorImpl.java:25)
16:25:37,437 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:3
24)
16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.ReflectedDispatcher.dispa
tch(ReflectedDispatcher.java:60)
16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invoc
ation.java:62)
16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invoc
ation.java:54)
16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocat
ion.java:82)
16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invo
ke(AbstractMBeanInvoker.java:197)
16:25:37,453 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MB
eanServerImpl.java:473)
16:25:37,453 INFO [STDOUT] at org.jboss.invocation.local.LocalInvoker.invok
e(LocalInvoker.java:97)
16:25:37,453 INFO [STDOUT] at org.jboss.invocation.InvokerInterceptor.invok
e(InvokerInterceptor.java:90)
16:25:37,453 INFO [STDOUT] at org.jboss.proxy.TransactionInterceptor.invoke
(TransactionInterceptor.java:46)
16:25:37,453 INFO [STDOUT] at org.jboss.proxy.SecurityInterceptor.invoke(Se
curityInterceptor.java:55)
16:25:37,453 INFO [STDOUT] at org.jboss.proxy.ejb.StatelessSessionIntercept
or.invoke(StatelessSessionInterceptor.java:100)
16:25:37,453 INFO [STDOUT] at org.jboss.proxy.ClientContainer.invoke(Client
Container.java:85)
16:25:37,453 INFO [STDOUT] at $Proxy146.loadProcessArchive(Unknown Source)
16:25:37,453 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
sMonitorWork.run(CubeProcessMonitorWork.java:129)
16:25:37,453 INFO [STDOUT] at oracle.tip.adapter.fw.jca.work.WorkerJob.go(W
orkerJob.java:51)
16:25:37,453 INFO [STDOUT] at oracle.tip.adapter.fw.common.ThreadPool.run(T
hreadPool.java:267)
16:25:37,453 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534)
16:25:37,453 INFO [STDOUT] <2007-05-11 16:25:37,453> <ERROR> <default.collaxa.c
ube.engine.deployment> <CubeProcessMonitorWork::run> Error while loading process
archive E:\OraBPELPM\domains\default\deploy\bpel_AboutTest_1.0.jar
why?
thanks

Excel extractor produces error "Error 8 when compiling the upload program"

I am trying to test a new Excel extractor I've created but when I do so I get the following error:
RSAR233
Error 8 when compiling the upload program: row 446, message: A newer version of data type /BIC/B0000788000 was
I've tried reactivating transfer structures and transfer rules but with no success. When I activate the transfer structures I can see in the status bar briefly a message refering "Activating Structure /BIC/B0000788000". I am assuming it's the technical name of the structure which supports the extraction.
Any ideas?
Thanks for the help.

OK, I can see your point. The Communication structure fields have data types, CHAR, CURR and DATS (those are the data types for the info-objects I am trying to load).
But if I try to assign the same data types to the objects of the transfer structure which match the flat file I get errors like "Invalid data type (DATS) for source systems of type Ext. System.". What I understand this means is that I cannot use data types other than CHAR in the flat file structure so how can I assign data from a CHAR flat file to a DATS destination object? Do I need some kind of conversion? How? Do I really need a routine in the transfer rules?

Error 8 when compiling the upload program: row 436

Hi all,
pls let me know how to solve this error
Error 8 when compiling the upload program: row 436, message: A newer version of data type /BIC/B0000582000 was
Thanks
Prashant

Hello SAP gurus.
I know it's a very long time the question was asked, but who cares if it can someday help somebody?
So i just faced the same issue, the solution was sample, i relaunch RSA1 and the problem was solved.
Hope i would be helpful
Salah

Error 8 when compiling the upload program: row

Error 8 when compiling the upload program: row
248, message: Data type /BIC/CCAWSAI_CID_TEXT was
found in a new
kindly help me out pls

Hi Raghu,
Error 8 Implies
The last words should be read as "was found in a newer version".
The system says that the active version of your Infosource is older then another version.
I'd recommend to delete Infosource - Source system assignment (with PSA tables etc.).
Then save (activate) the Infosource (communication structure). Then assign source system, create infopackage and load data again.
else..
Goto se38 and Run the program RS_TRANSTRU_ACTIVATE_ALL and relogin..
Plz look the link.
[Error when compiling the upload program (Message no. RSAR233) ]
Hope this helps...
Regards,
NR
Assign points if helpful...

Error 8 when compiling the upload program

When loading data to the Infocube it gives the following error
"Error 8 when compiling the upload
227, message: Data type /BIC/CCFBZ
found in a ne "
It doesnot go any further from thr infopackage also..

Error when compiling the upload program (Message no. RSAR233)

LC 2 Error 1003 when executing external command brconnect on (xpgid=0,con

Dear all,
I am getting error in sm21.Please suggest .
Details Page 2 Line 23 System Log: Local Analysis of clusa                    1
Time     Type Nr Clt User TCode Grp N Text
10:00:32 DIA 000 600 DDIC       LC 2 Error 1003 when executing external command brconnect on (xpgid=0,convid=.)
Error 1003 when executing external command brconnect on (xpgid=0,convid=.)
Details
Recording at local and central time........................ 10.05.2010 10:00:32
Task...... Process                     User...... Terminal Session TCode Program Cl Problem cl      Package
06952      Dialog work process No. 000 DDIC                      1       SAPMSSY1 S Operation Trace SBTC
No documentation for syslog message LC 2 exists
Parameter
1 .... xpgid=0,convid=.
Technical details
File Offset RecFm System log Grp N variable message data
224 260640                  LC 2 brconnect & &Error 1003 & & &
Regards,
Kumar

Dear Juan,
Please find the logs.Please suggest.
dev_cp log
Trace file of control program (trace level 3)
< Function: BtcTrcInit> Function: main SAPXPG 720
2010-05-10--09-33-29 : Before BtcXpgDetach
> Function: BtcXpgDetach < Function: BtcXpgDetach Accept RFC connection from R/3 system
2010-05-10--09-33-29 : Before RfcAccept
2010-05-10--09-33-29 : RfcAccept returned OK
Begin of check_if_security_list
security check switched OFF
End of check_if_security_list
Begin of check_trace_option
End of check_trace_option
Install RFC call SAPXPG_START_XPG
Install RFC call SAPXPG_START_XPG_LONG
Install RFC call SAPXPG_END_XPG
Wait for RFC call SAPXPG_START_XPG or SAPXPG_START_XPG_LONG
2010-05-10--09-33-29 : Before first call of RFCDispatch
Security: rfcexec_logon_check
rfcexec_logon_check: logon_user =
sapxpg_logon_check: rfc_attr.user = BASIS
rfcexec_logon_check: client =
> Function: BtcXpgStartXpgLong
2010-05-10--09-33-29 : Beginning of BtcXpgStartXpgLong
    > Function: BtcXpgStartXpgImportLong      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgTable      < Function: BtcXpgTable    < Function: BtcXpgStartXpgImportLong
BtcXpgStartXpgLong: special_trace_flag = <6>
    > Function: BtcXpgStartXpgInt      > Function: BtcXpgItTransfer        Content of source log table:
          Line Text
          <No StdOut/StdErr output reported>
        Target log table is not identical to source
        ItGetLine terminated with NULL
      < Function: BtcXpgItTransfer      > Function: BtcTrcReset      < Function: BtcTrcReset      Call mode: VIA RFC
      Input arguments of BtcXpgStartXpg:
        External program: brtools
      tracecntl = : 6
      Display of Parameter string switched off !!
        Contents of control flags:
          StdIn control flag: redirect StdIn
          StdOut control flag: store StdOut output in memory
          StdErr control flag: store StdErr output in memory
          Trace control flag: unknown contents
          Termination control flag: control program will wait for termination
      > Function: BtcXpgCheck        > Function: BtcXpgArgv
          parameter number 1:
          parameter number 2:
          parameter number 3:
          parameter number 4:
          parameter number 5:
          parameter number 6:
          parameter number 7:
          Total number of arguments scanned: 7
          Argument argv[0]: brtools
        < Function: BtcXpgArgv      < Function: BtcXpgCheck      > Function: BtcXpgSigInst      < Function: BtcXpgSigInst      > Function: BtcXpgStart        Rearrange stderr to be collected in memory
        Rearrange stdout to be collected in memory
        Redirect stdin, read from NUL:
        > Function: BtcTrcInit< Function: BtcXpgStartStart status of external program: external program successfully started
Id of external process: 0000005296
StdOut/StdErr collected in memory
Line Text
<No StdOut/StdErr output reported>
< Function: BtcXpgStartXpgInt> Function: BtcXpgStartXpgExport > Function: BtcXpgParam < Function: BtcXpgParam > Function: BtcXpgParam < Function: BtcXpgParam > Function: BtcXpgParam < Function: BtcXpgParam< Function: BtcXpgStartXpgExport
2010-05-10--09-33-29 : End of BtcXpgStartXpgLong
< Function: BtcXpgStartXpgLong
2010-05-10--09-33-29 : After first call of RFCDispatch
Wait for RFC call SAPXPG_END_XPG
2010-05-10--09-33-29 : Before second call of RFCDispatch
Security: rfcexec_logon_check
rfcexec_logon_check: logon_user =
sapxpg_logon_check: rfc_attr.user = BASIS
rfcexec_logon_check: client =
> Function: BtcXpgEndXpg
2010-05-10--09-33-29 : Beginning of BtcXpgEndXpg
> Function: BtcXpgStartXpgExport    > Function: BtcXpgTable    < Function: BtcXpgTable < Function: BtcXpgEndXpgImport > Function: BtcXpgEndXpgInt    > Function: BtcXpgItTransfer      Content of source log table:
        Line Text
        <No StdOut/StdErr output reported>
      Target log table is not identical to source
      ItGetLine terminated with NULL
    < Function: BtcXpgItTransfer    > Function: BtcXpgReadChild      Output of external command not written to log !!
      Process executing external program has terminated
    < Function: BtcXpgReadChild    > Function: BtcXpgEnd    < Function: BtcXpgEnd    Termination status of external program: no errors reported
    StdOut/StdErr collected in memory
< Function: BtcXpgEndXpgInt > Function: BtcXpgEndXpgExport    > Function: BtcXpgParam    < Function: BtcXpgParam    > Function: BtcXpgParam    < Function: BtcXpgParam < Function: BtcXpgEndXpgExport
2010-05-10--09-33-30 : End of BtcXpgEndXpg
< Function: BtcXpgEndXpg
2010-05-10--09-33-30 : After second call of RFCDispatch
2010-05-10--09-33-30 : After call of RfcClose (wait)
< Function: main
2010-05-10--09-33-30 : End of SAPXPG: main
dev_xpg
Trace file of External Program (trace level 3)
< Function: BtcTrcInit> Function: BtcXpgStart External program: brtools -sid prd -F printout alert_log 20100401000000 0128
Regards,
Kumar

Error 1003 when building exe

Hi all,
I saw a couple of thread of other people here having the same "1003 error" when trying to build an exe with LV 7.1.1
The exact text error is :
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.viPossible reason(s):LabVIEW: The VI is not executable.
This is all the more surprising because this error will only happen on my computer !!!
I borrowed a collegue's computer and the build went OK...
After further investigations I noticed only one difference between my collegue's computer and mine : mine has VIPM installed.
Could VIPM possibly be the source of this issue ??
PS : recompling the code (ctrl+shift+run) on my CPU didn't make any change.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Hi TiTou,
You've probably solved this by now, but if not...
A few months ago I was trying to distribute two EXEs - both of which made dynamic calls - and this error (among others) was giving me "fits". I think it can happen if the caller has loaded a VI (.ctl or .vi) that also appears in the callee hierarchy - and the version loaded by the caller is incompatable with the callee's diagram(s.) When the callee runs, it has to use same-named VIs already in memory. If you see different behaviour on two different machines, are there two different versions of the caller?
No matter what the problem really is (was,) the attached VI will try to open all the broken VIs in a hierarchy - which can be a huge help in narrowing the problem. Oh yeah, with the (broken) FP open, click on the broken-arrow to see an error-list that can (but-usually-doesn't) display helpful diagnostic info! Compile this into your EXE (caller) so it runs if there's a problem running the callee.
Cheers.
Message Edited by tbd on 01-15-2007 10:58 PM
Message Edited by tbd on 01-15-2007 11:00 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
Util.VI.OpenBroken.vi ‏62 KB

Mysterious Error 1003 in COMPILED rtexe

My code WORKS PERFECTLY under LabVIEW 8.6 (and LVRT 8.6).
It fails under LabVIEW 2010 (with LVRT 2010).
Here's what I'm trying to do:
My program uses "plug-ins" - stand-alone VIs to do some calculation during data acquisition.
For example, there is a measured SPEED channel and a measured TORQUE channel.
A plug-in VI called POWER calculates speed * torque / 5252.1 and produces POWER.
This is then treated just like it was another measured channel, they can record it, plot it, set alarms on it, anything they can do with a real measured channel, they can do with this artificial channel.
I'm sampling at 10 Hz, each sample causes a run of the plug-in and produces a new POWER sample.
The plugins use a TYPEDEF (called "Units") that has various units defined ("Hp", "kW", "Lb/hr", "ppm", etc).
They might use a subVI or two. I've made sure those are in the compiled executable.
The Real-Time program (called RTEC) does all the sampling, from various PXI boards and UDP sources. The HOST program calls for a channel called POWER, and provides a "signature" (hash value) for the VI that is on the host machine. RTEC compares the signature sent with it's own signature on file and decides if the version is the same. If not, it asks the host to send the whole VI (which is does, as a text block), and stores the VI file locally, along with the signature.
RTEC does the sampling and sends the data to the host. The host records it into a disk file. Along with the data itself, a header (containing setup information) is part of the data file, and also a copy of the plug-in VIs themselves. I do this to guarantee that the calculation used to produce the data is preserved as it is.
When reviewing the file, the user can edit some things (scale factors for instance) and re-process the data, that means re-running the plugins on the host.
The critical point here is that these are plug-ins - I do not want the user to have to open the main project and insert some vI into the project and build a source distribution.
The way it works now is that the user can create his subVI from a template. The template has the workings except for the calculation itself. ALl he has to do is specify that he wants "Engine Speed" in RPM and "Engine Torque" in Ft-lb, and it produces results in "Hp". He then does the multiplication, saves the VI, drops it into a specific folder on the host, and all else is automatic.
ALL THIS WORKS PERFECTLY in LV 8.6.
However, in LV2010, I get an error -1003 in a compiled RTEXE. If I run the RTEC program from the host environment (just clicking on the RUN arrow on the host), all is well. But we need to run compiled, as every host will not have a DevSys.
I have boiled it down to a simple test case - see attached pic.
If I OPEN the VI REF without a TYPE specifier, it works in either case (compiled or RTEXE), but I cannot later run the reference since it's not STRICT.
I tried both a GENERIC and a TEMPLATE reference, since I was first thinking that one was working and not the other, but they seem identical now.
The program works fine in the DevSys, but compile it to an RTEXE and I get error 1003 for the latter two cases.
I have read <a href="http://digital.ni.com/public.nsf/allkb/10F1D411ACBAD3D9862572FF0064C801">this</a>, <href="http://digital.ni.com/public.nsf/allkb/410F2EC66F60F9B0862569EE006F4FA0">this</a> , and <a href="http://digital.ni.com/public.nsf/allkb/0537EAF7F167718386256A96005D1DBC">this</a>.
What I get out of those is that maybe this is a "security" enhancement: it's no longer legal for a plug-in to call code or use typedefs from a compiled master app, whereas it was before.
QUESTION 1: Is that a fair interpretation?
I am guessing that the DevSys is handling this for me, but the RTEXE is unable to (since there is no compiler).
So, if I define ahead of time which TYPEDEFs and subVIs are permitted to be called from my plug-ins, and store a separate copy of those, I have to duplicate that relative path on the RTEXE. If I don't, the signature process will fail (if the path is changed, the signature of the VI will change).
QUESTION 2: Is that a reasonable statement?
And I have to duplicate the same folder of dependent stuff at REVIEWING time, since the exact same VI, extracted from the data file, must be executed by the reviewer on the host.
QUESTION 3: Is that a true statement?
QUESTION 4: Is there a better way? Right now (8.6) the fact that the VI wants to load a TYPEDEF from C:\Users\Steve|Projects\HDT\Libraries\HDT Units.llb\HDT Units.ctl and instead finds it in C:HDT\RTEC.rtexe\HDT Units.ctl (on the PXI box) , or in C:\Whatever\HDT Reviewer.exe (at REVIEWING time) is all automatic, invisible, and not a problem.
Apparently that's not so easy anymore.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

OK, NI Tech Support has been completely useless on this one, and nobody in the forum had ideas, so I had to work all week on it, but I have figured out the root problem. Here it is for anyone who's interested.
It definitely IS still legal to call INTO an executable, my conjecture that it was no longer legal was wrong.
I stumbled across the solution when I discovered that the setting DISCONNECT TYPEDEFS in the BUILD SPEC made a difference. If I tuned OFF the DISCONNECT switch, everything started working. The RTEXE size went from 2.2 Meg to 3.4 Meg, but at least it worked.
Not willing to live with that bloat, I kept chasing the real problem, now knowing that it was NOT a un-findable subVI, but a TYPEDEF that was the problem.
I turned the DISCONNECT TYPEDEF switch back ON, and stripped ALL the code from my plugin. Problem remains.
That suggests that it was with a TYPEDEF, not a subVI.
Two of the terminals of my plugins are TYPEDEFs.
I disconnected one (UNITS.ctl ) on a plugin, and got no change.
I disconnected the other (Channel Preqrequisite.ctl), and got no change.
But the Channel Prerequisite is a cluster, which contains a UNITS.ctl.
When I disconnected THAT, then it started working.
That confirms that it's a TYPEDEF problem (as suggested by the DISCONNECT TYPEDEFS fixing it).
What I had thought (and maybe it was true in LV 8.6) was that having an INSTANCE of a typedef'ed control in the MAIN was sufficient to make the plugins happy.
That is NOT the case. I suspect that this is a change in LV2009/2010 behavior, as I didn't have this problem in 8.6.
I knew that there were instances of the TYPEDEF'ed controls elsewhere in the MAIN, but, since we're DISCONNECTING TYPEDEFS, then the actual definition is not there.
To fix the problem, while still keeping DISCONNECT TYPEDEFS set to ON, I placed a STATIC VI REFERENCE in the main program, pointing to each DEFINITION (one to UNITS.ctl, one to CHANNEL PREREQUISITE.ctl), and it all works.
It works whether 8.X Layout is ON or OFF.
It works whether I run from an RTEXE or from the DevSys.
It works with the DISCONNECT TYPEDEFS setting ON (or off).
Whew!
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Error 1003 when using excel reprt, but not Word

I am trying to use the MS Office Report vi to send my data to an Excel. I am using Labview 7.1.
When I place the VI on the block diagram I get the following message: (Also attached)
Error 1003 occurred at Open VI Reference in ex_RGT_Get
Bookmarks and named cells.vi->Configure MS Office
Report.vi->Confugure MS Office Report.vi.ProxyCaller
Possible Reason(s):
The VI is not executable. (OK Dialog box)
If I click OK, the " Configure MS Office Report pop up window is mostly grayed out . If I select "Basic report for Word" I have no error message.
I am using Excell 2003. The problem is with a laptop computer I am using. I do not see this problem with a desktop computer.
Thanks,
Bill
Attachments:
MS Report 8-24.doc ‏80 KB

Hello Bill,
You are not trying to build an executable, just use the Express VI in a regular development VI, right? If so, this link describes the troubleshooting steps to get rid of this error.
Regards,
Clint M
National Instruments

Error 1003 when building executable

Hi, I'm using Labview 2010 on Windows 7 and I'm getting an error when I try to build an executable:
Error 1003 occurred at Open VI Reference in AB_Engine_EXE_Call_Write_Icons.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: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
VI Path: C:\Program Files\National Instruments\LabVIEW 2010\vi.lib\Platform\icon.llb\Read Icons from ICO File.vi
This happens even when I try to build a simple vi, like a random number generator.

Same problem here. Error 1003 and error 8 I encoutered often.
For error 8 during build process, I needed to save the executable on a higher level in the file hierarchy.
For error 1003, I did not find a solution. Restarting LabView does not help. Sometimes (but not always) restarting the computer helps. Sometimes I need to reinstall the labview system.
More details: I have a first vi, starting the actual vi with a hidden front panel (second vi). This vi can also be started directly. Sometimes, the build process runs smoothly then when I include the second vi as main vi to start the program.
The program runs fine when the build process succeeds, and it runs fine in LabView.

Strange error message when compiling an IPA ("multiple L$start$ labels found at same address in...")

I get this message when compiling an IPA with AIR 3.6:
ld: warning: multiple L$start$ labels found at same address in __ZN9NetStream12DispatchProcEP10NativeInfo at offset 0x06C0
Googling a bit, it seems it's an error message from this C++ class:
http://opensource.apple.com/source/ld64/ld64-133.3/src/ld/LinkEdit.hpp
So I suppose it's a bug in the AIR for iOS compiler. Any clues about why am I getting that warning message?

I've been getting this message for quite a while, but I think a fix will soon be needed. I got the following message from Apple:
==============
Dear developer,
We have discovered one or more issues with your recent delivery for "Quazar". Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Non-PIE Binary - The executable 'Quazar.app' is not a Position Independent Executable. Please ensure that your build settings are configured to create PIE executables.
===============================================

Error 1003 when compiling...

Similar Messages

Maybe you are looking for