Error 1031 occurred at Open VI Reference in. This error occured in the ni5640R Template Config ADC (FPGA).vi

When I tried to open the ni5640R Template (FPGA).vi I got this error
Message Edited by 09441213131 on 05-23-2009 02:42 AM
Attachments:
error.JPG ‏135 KB

Most likely, you did not include the required libraries in your build script. When building an executable in which you use the Report Generation Toolkit, you must include the _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs on the Source Files tab.
Check this article for more info.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
Daniel L. Press
PrimeTest Corp.
www.primetest.com

Similar Messages

Error while loading the Web template "0ANALYSIS_PATTERN" (return value "4")

I activated all 0* objects in BTMP and checked that they are all activated, but I found errors when opening the BEx Web Analyzer
Error messages :
Error while loading the Web template "0ANALYSIS_PATTERN" (return value "4")
ERROR: Command type SWITCH_AXES of object not recognized
ERROR: Parameter GENERAL_TEXT_ELEMENT not recognized; check your metadata
So I ran RS_TEMPLATE_MAINTAIN_70 (0ANALYSIS_PATTERN) version D report to check and choose validate.
Error messages :
Template Include Item HEADER_TEMPLATE unresolved or empty. Close and reopen template.
Template Include Item FOOTER_TEMPLATE unresolved or empty. Close and reopen template.
Width of object item:GROUP_ITEM:GROUP_ITEM_1 is very small (1amp;1)
Query does not exist in the BI System (Object QU )
Cannot instantiate data provider
I also ran RS_TEMPLATE_MAINTAIN_70 (0ANALYSIS_PATTERN) version A and got the following errors:
Command type SWITCH_AXES of object not recognized
Command type SWITCH_AXES of object not recognized
Command type SWITCH_AXES of object not recognized
Parameter GENERAL_TEXT_ELEMENT not recognized; check your metadata
Parameter GENERAL_TEXT_ELEMENT of object item:GROUP_ITEM:GROUP_ITEM_1 not recognized
Command type SWITCH_AXES of object item:GROUP_ITEM:GROUP_ITEM_1 not recognized
Command type SWITCH_AXES of object item:GROUP_ITEM:GROUP_ITEM_1 not recognized
Command type SWITCH_AXES of object item:GROUP_ITEM:GROUP_ITEM_1 not recognized
Command SWITCH_AXES cannot be located in parameter ACTION
Command SWITCH_AXES cannot be located in parameter ACTION
Command SWITCH_AXES cannot be located in parameter ACTION
Parameter GENERIC_TEXT_BINDING of object item:GROUP_ITEM:GROUP_ITEM_1 cannot be higher-level node of GENERAL_TEXT_ELEMENT
Item item:GROUP_ITEM:GROUP_ITEM_1 of type DROPDOWN_ITEM cannot be a parent node of DATA_PROVIDER_REF
Item item:GROUP_ITEM:GROUP_ITEM_1 of type CHART_ITEM cannot be a parent node of VISIBLE
Item item:GROUP_ITEM:GROUP_ITEM_1 of type CHART_ITEM cannot be a parent node of LEGEND_POSITION
Item item:GROUP_ITEM:GROUP_ITEM_1 of type CHART_ITEM cannot be a parent node of LEGEND_VISIBLE
Item item:GROUP_ITEM:GROUP_ITEM_1 of type CHART_ITEM cannot be a parent node of LEGEND_ONLY
Invalid parameter value for parameter ACTION in object item:GROUP_ITEM:GROUP_ITEM_1
Invalid parameter value for parameter ACTION in object item:GROUP_ITEM:GROUP_ITEM_1
Invalid parameter value for parameter ACTION in object item:GROUP_ITEM:GROUP_ITEM_1
bi-Tag bi:item has unknown attribute key. Please check your spelling
bi-Tag bi:item has unknown attribute key. Please check your spelling
bi-Tag bi:item has unknown attribute key. Please check your spelling
bi-Tag bi:item has unknown attribute key. Please check your spelling
What could be the problem?

hi,
Please look into this note let me it helps...url=https://websmp202.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=917950&_NLANG=E]Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web[/url]
check this link as well for [<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ca6de811-0c01-0010-43b2-c64584eef943">Bex Web Configuration</a>
wht is the SP Level?
Nagesh Ganisetti.

Error -54 - can't find any reference to this but it's the error I'm getting!

I am running Mac OSX 10.7.5 and iTunes 11.0.3 (42).
Suddenly my iTunes is giving the following error message: Unable to save iTunes file -error 54
I have searched for this error code and don't see any other users talking about it.
Does anyone know what's going on and what I should do?
Thanks

When do you see this error? What are you trying to do when this error occurs?
The error code -54 is a permissions error (Software lock on file; Not a subscriber [permissions error on file open])
So the first thing I'd try would be to repair the permissions on the drive, where your iTunes Library is located.
If the library is on an external volume, you can use Disk Utility, but to repair your system volume, boot into Recovery and use the Utilities menu (Disk Utility) there. OS X Lion: About Lion Recovery
Regards
Léonie

Java Error while executing the excel template in the BIP 10g report server

Hello Gurus,
While we are executing the excel template we are getting the following java error and the report cannot be rendered to user who triggers the report. Where as the same excel template is generating output when user run it against the same data locally.
"oracle.apps.xdo.servlet.scheduler.ProcessingException: [ID:652] Document file to deliver not found : C:\Oracle\bipublisher\oc4j_bi\j2ee\home\applications\xmlpserver\xmlpserver\xdo\tmp\xmlp3307tmp
at oracle.apps.xdo.servlet.scheduler.XDOJob.deliver(XDOJob.java:1172)
at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:495)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)"
We have tried with designing the .rtf template for this report and we are able to generate the report form the server. Please let us know the cause for this error in the server and way to rectify the exception from the report server.
Thanks,
Kamath.

"oracle.apps.xdo.servlet.scheduler.ProcessingException: [ID:652] Document file to deliver not found : C:\Oracle\bipublisher\oc4j_bi\j2ee\home\applications\xmlpserver\xmlpserver\xdo\tmp\xmlp3307tmp
imho it's about empty result file
Data are there
may be yes but is some data from all for report itself ?
in other words data can be in output ( in xml ) but report can filters data and so report doesn't have appropriate data to representation ( it's assumption for error )
Data are there, when we are using rtf template, it is generating the output.
if you sure about data for report and on this data report works fine by bip desktop, so no ideas, only SR
btw you can first check my assumption and try to catch "no data found" in template
also you can check data itself, is it well-formed xml

We have build a nice Flex BI front end and want to open-source it would this be useful to the group?

Hello, I am the CEO of DataRoket (www.dataroket.com) and we are a data integration and analytics platform. As part of our effort, we have built a really nice data visualization and reporting package.
Since this is not our core business and we want to give back to the community and also see it continue to evolve, we are going to open source the Data Visualization module of data roket.
You can look at the application by going to www.dataroket.com. If we did this, we would like to get some people to work on this and use it freely for your clients etc.
I want to know two things please:
1. is this interesting and would it be useful to the community
2. Are there people that would like to continue to push this capability and shepard the open source effort with us?
Thanks in advance for your feedback
James Fox
[email protected]

I like the idea of open source. Have you considered adding a demo/dummy Flex
app to your website for a fictional business. Just to show your capabilities.

Error while executing the BW template from Enterprise portal.

HI all,
i need a help in resolving the issue. when i am trying to run the template(WAD) from Enterprise portal i am facing an error.
the error message is as follows
cannot load query ''query name'' (data provider "DP_1":)
Notification Number RSBOLAP 013
please help me out in resolving the issue.

Hi Ganesh,
actually it the scenario is some this like this i have created an WAD with email as an button up on click on the button it will execute the BI Broad Casting Functionality
He have published the template on to portal, the template is executing fine in Enterprise portal but upon button click we are perfectly invoking the broadcasting functionality but i am unable to send mail when i am click on Execute button.
The functionality is working fine from BW system .please help me out in resolving the issue.
regards,
santosh

Error when executing the webr template in Bi 7.0

Hi,
When I exceute my webtemplate in BI 7.0 I am getting the following error
A pop up block is activated .This prevents distrubted session management from functioning correctly. the WEb Application will therefore be ended.check teh sap note 919196
Deactivate the pop up blocker and restart the Web application
I have ckhecked the notes but didnot undersatnd it.
Could any one pls help me out.
Regards,
Maya

Hello,
were able to solve the problem entering sapregsv.exe mshtml.tlb in C:\Program Files\SAP\SapSetup\setup.
It seems to be an alternative to reinstall the Internet Explorer.
The original source of the solution is:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/sap-gui-removal-breaks-ie-integration-2452079
SAP GUI removal breaks I.E. integration, 3rd answer (thecdog on 11/13/2008)
Best regards
Thomas
See "main" thread PopUp blocker preventing BI 7.0 Web reports

Firefox not scrolling or scrolling very slowly when i open a new tab, this just started within the last few weeks. Ive tried reloading firefox but have the same problem.

when i am using firefox if i click on a link that opens a new tab the new page wont scroll or scrolls very slowly. this has never happened before and i have had many many tabs open at once without any problem, now if i have just two the second one gives me these problems while the first one continues to work fine.

'''I fixed mine by removing the Ask.com extension.'''
Tools
Add-ons
Settings icon
View Recent Updates
Ask.com '''DISABLE'''
Running FF 8.0 on Windows 7 (64-bit)

Error 1003 occured at Open VI Reference

This error occured when I want to used the LabView Report Generation Toolkit for Microsoft Office Example.
It's impossible for me to execute the example "Generate Report from Template(Excel)"
I suppose I have a problem with the Open VI Reference.vi function but I don't know where is that VI.
Could you let me know where are the VIs listed in the Application Control Pallette.
Do you know why I have this type of problem.
Thanks
Lucie

The VIs located on the application control palette are primitives and are part of LabVIEW itself. Therefore you can not look at their diagrams because they don't have one.
However the 1003 error means that you are trying to dynamically load a VI that is not executable. I would suggest turning highlight execution on and following the code to see what path is sent into the Open VI reference function.
Once you have the VI that is failing to open go manually open it.
Chances are that it is broken, so see why it is broken. If I remember correctly there is a linking issue in that example, so you can open the VI that is broken and hit ctrl-shift-Run Button, and that should relink it all and fix the issue.
If not take a look at this
Why Do I Get Error 1003 From Application Builder When I Try to Build Excel Macro Example.VI?

Quirk, Open VI Reference and LLB

I found a strange quirk opening a VI Reference (on a PXI). The "normal" method of doing this is to Open Application Reference (to find the remote site) then to Open VI Reference with the path to the desired VI. Darren Nattinger pointed out (in 2006) that you can use just the name of the VI, provided the VI is on the same folder or LLB as the current VI.
Caveat -- this behavior is present in LabVIEW 7.0 (I'm maintaining some "legacy code"). I suspect it will be present in later versions, but haven't (yet) tested it.
Quirk 1 -- if the VI in question has been downloaded (or deployed) to the remote site, and hence is in memory, then the "path" information isn't used, only the VI name. Thus if you have a path "C:\ni-rt\startup\MyVI.vi" specified in the Open VI Reference, but have absolutely nothing in the startup folder on your PXI, but have "deployed" your Project, this call will work, even though the "path" part of the argument is not valid. Useful when testing.
Quirk 2 (and the "real" reason for this post) -- if the VI is embedded in an LLB, it depends on whether or not it is a "Top-level" VI or not. Suppose the path is C:\ni-rt\startup\MyLib.llb\MyVI.vi. Consider two VIs in this LLB -- TopLevel.vi and SubVI.vi (where TopLevel is at the top level of the LLB, whereas SubVI is not).
Case A -- the LLB has actually been downloaded to the remote site. Doing an Open VI Reference, with either the full path or just the VI name, works, whether or not you are calling TopLevel or SubVI. Nothing surprising here.
Case B -- you are taking advantage of Quirk 1, and have not actually put the file on the Remote site (i.e. there is nothing at the path specified). You have, however, downloaded the LLB to the Remote. Doing an Open VI Reference with SubVI, whether with full path or just VI name, works fine. However, trying to open TopLevel fails, with Error 7 (File Not Found), whether using full path or VI name.
Summary -- Quirk 2 is that Quirk 1 has a quirk if the VI being referenced is a top level VI in an LLB.
[My apologies if this is common knowledge -- I failed to find this behavior documented, but may have overlooked something].

Bob Schor wrote:
I found a strange quirk opening a VI Reference (on a PXI). The "normal" method of doing this is to Open Application Reference (to find the remote site) then to Open VI Reference with the path to the desired VI. Darren Nattinger pointed out (in 2006) that you can use just the name of the VI, provided the VI is on the same folder or LLB as the current VI.
Caveat -- this behavior is present in LabVIEW 7.0 (I'm maintaining some "legacy code"). I suspect it will be present in later versions, but haven't (yet) tested it.
Quirk 1 -- if the VI in question has been downloaded (or deployed) to the remote site, and hence is in memory, then the "path" information isn't used, only the VI name. Thus if you have a path "C:\ni-rt\startup\MyVI.vi" specified in the Open VI Reference, but have absolutely nothing in the startup folder on your PXI, but have "deployed" your Project, this call will work, even though the "path" part of the argument is not valid. Useful when testing.
Quirk 2 (and the "real" reason for this post) -- if the VI is embedded in an LLB, it depends on whether or not it is a "Top-level" VI or not. Suppose the path is C:\ni-rt\startup\MyLib.llb\MyVI.vi. Consider two VIs in this LLB -- TopLevel.vi and SubVI.vi (where TopLevel is at the top level of the LLB, whereas SubVI is not).
Case A -- the LLB has actually been downloaded to the remote site. Doing an Open VI Reference, with either the full path or just the VI name, works, whether or not you are calling TopLevel or SubVI. Nothing surprising here.
Case B -- you are taking advantage of Quirk 1, and have not actually put the file on the Remote site (i.e. there is nothing at the path specified). You have, however, downloaded the LLB to the Remote. Doing an Open VI Reference with SubVI, whether with full path or just VI name, works fine. However, trying to open TopLevel fails, with Error 7 (File Not Found), whether using full path or VI name.
Summary -- Quirk 2 is that Quirk 1 has a quirk if the VI being referenced is a top level VI in an LLB.
[My apologies if this is common knowledge -- I failed to find this behavior documented, but may have overlooked something].
This will likely not apply at all to >= 8.0. LabVIEWs Open VI Reference will now distinguish cleanly between absolute path and just the VI name itself. If you use just the VI name the VI needs to be in memory or for a built application included in the app. The quirk about VIs in the same LLB as the currently active VI sounds very strange to me but it may still work.
However if you specify an absolute path, Open VI Reference will bark with an error if the VI can not be found at that location or if the VI already loaded in memory with that name has not the same absolute path. This is supposedly to make it very hard to create cross linking even when using VI server.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

VI Server - Open VI Reference is using local path, not remote

First time posting to NI Developer Zone, so bear with me.
I have a PXI-1050 chassis with a PXI-8187 controller that runs LabView RT. I have set up this PXI system to utilize a VI server on port 3363 and opened access to my host PC which runs LabView 8.2 with the RT module.
I am having trouble openning a remote VI using the VI Server and the "Open VI Reference" function. I am fairly certain that the VI server is connecting using the "Open Application Reference" function, but it seems that the vi I wish to run cannot be found.
Here is the error that is thrown back to me
"Error 7
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Non-existent board.
VI Path: D:\LabView_Projects\VI_Server_Test_Project\/ni-rt/startup/temp_1.vi"
You will notice that the "Open VI Reference" is prepending the local path 'D:\LabView_Projects\VI_Server_Test_Project\' to my remote path. If I specify the path using Windows style path, e.g. 'c:\ni-rt\startup\temp_1.vi', again the remote VI cannot be found. I think I am missing something trivial, but I don't know what it is.
Thoughts?

Several things:
1. When u open the vi reference u must use and invoke node to make the Run vi, if you dont make it the vi is loaded but not running.
2. Insert correctly the path on your RT and the IP of your RT target
3. is better to have the variables on your HOST than on your RT becoz of two things:
- Not to use resources of your RT system as memory etc... is better to use the host ones that are more available
- The library needs to be deployed when running the vi on the host. If you put it on the RT it would need to be redeployed, so it is better to leave it on the host becoz of that.
4. Then as the library is on the host it needs to be deployed with the proper invoke node inside a stacked sequence to ensure is the first thing you do.
5. The enable RT fifo on the variables is used only to pass data between different vi's or processes inside the RT, it has no sense to enable it when sharing data RT - Host coz it is not possible, Shared variable work with TCP/IP not as RT FIFO.
See the attached vi for extra info.
I give u these extra links for your info:
http://digital.ni.com/public.nsf/websearch/F4010DD5C8D1B13D862565BC007384E9?OpenDocument
http://digital.ni.com/public.nsf/websearch/04D9A85B6967EE87862571140065EEC6?OpenDocument
http://digital.ni.com/public.nsf/websearch/48D244EC86971D3986256BD4005CCC28?OpenDocument
Regards,
Jaime Cabrera
NI Applications Engineering Spain
Attachments:
Compartida.zip ‏66 KB

Open VI Reference prevents execution of other parallel threads

I am using splash screen to start an application. I use dynamic loading of the Main.vi and an animation during the loading, both in parallel threads (see image below). However, when the Open VI reference VI is called everything else stops executing (the animation stops running) until the Open VI reference is done. I must call the Main.vi dynamically, because it takes some time to load and I want to notify a user that the application is loading (using animation). Is there an option to prevent the Open VI reference to block the execution of other threads? Or should I use some other approach?

andrej wrote:
But the problem is not in the Run.VI method because the Open VI Reference blocks the execution of the top loop and I need the Open VI Reference to call the Get VI Dependencies method. Other approach could be to create a static array of dependencies and then to use this array to load VIs from bottom up.
The only question now is if the Get VI Dependencies method returns dependencies in top to bottom order? If it does then I can just load VIs in reverse order from the array.
Well the problem is the Open VI Reference! This executes in the UI thread, as several people have explained already (and really can't be made to do otherwise without causing a number of possible and nasty race conditions, some of them even related to the underlaying OS and not just LabVIEW itself), just as your two Property Nodes in the upper loop have to use the UI thread too.
Once Open VI starts it only returns if it has loaded the required VI fully into memory (and that includes any dependencies that aren't already in memory) and linked them all properly together or runs into an error during loading. For this duration, NO UI Property Node can execute, which is what stalls your upper loop. If you would use local variables or terminals instead the upper loop would happily run along while Run VI loads the entire VI hierarchy but it would still not show on the UI, because in order to draw the new data from the diagram passed to locals and terminals LabVIEW has to catch the UI thread to do the UI drawing.
So first fix is to kick out any property nodes from the upper loop and the second part of the solution is to load your VI hierarchy in chunks instead of simply loading only the top level VI directly. It would be nice if Open VI had an option to allow UI thread release between loading of chunks of VIs, but the implications are not that nice. It would be quite easy for an uncareful LabVIEW programmer to create a lockout situtation then, where two functions are in fact waiting on each other to release some locks so that the program gets hang up. And a simple warning in the documentation to watchout as this option can allow to create such lockout situations is not very useful as nobody reads them anyhow.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Open VI Reference LAN Help

Hi!
I have a LAN/TCP connection. On the side A, I have a simple VI, and I would like to call it from side B. How can I do that?
+++ In God we believe, in Trance we Trust +++
[Hungary]

Hi Durnek,
The best is to use the Application Control palette, create a VI server on side A, on side B open a reference to the VI server with Open Application Reference Function, then you can access the VI with Open VI Reference and using the Invoke and Property nodes from the same palette you have access to a lot of information and settings.
Let us know if you have more questions!
Have a good day!
Patricia

"error opening url to submit this form"

Hi,
I develop AcroForm PDF file using Acrobat. file Contain so many fields and Submit button.
when I was click on Submit button than I got the Error message
Error opening url to submit this form
I set the return type XFDF on button.
How can I fix this bug?

To which URL are you trying to submit it?

Pci-5640R Config.ADC 0 Microport Address write error

I am trying to run the tutorial in the "Getting Started with the NI PCI-5640R IF Transceiver and the LabVIEW FPGA Module" document. I got everything set up, but when I run it, I get an error which says
"Error -61059 occurred at Read/Write Control:Config.ADC 0 Microport Address in Simple Spectrum Analyzer.lvlib:ni5640R ADC address_port_write.vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC read_write.vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC read_write (multi-byte).vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC write_register.vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC 01 - Chip IO Access.vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC Global.vi->Simple Spectrum Analyzer.lvlib:ni5640R ADC Default.vi->Simple Spectrum Analyzer (HOST).vi"
I can't figure out how to fix it.

It may be that the FPGA Refernce has not been binded. The issue was that the VIs need to be bound to the ni5640R FPGA VI Reference.ctl control. This is an option on the popup menu when clicking on the Open FPGA VI Reference VI. In some cases, it may already be selected in the popup menu. In this case, unselect the Bind to Typedef option. For good measure, I usually selected the FPGA VI to use with the host VI, and then I reset the Bind to Typedef option. In most cases this should fix the ni5640R FPGA VI Reference.ctl control mismatches throughout the VI. In some cases, I have to Save All, close the host VI and all subVIs. Then reopen the host VI. This has always working in all cases for me.
Jerry

Error 1031 occurred at Open VI Reference in. This error occured in the ni5640R Template Config ADC (FPGA).vi

Similar Messages

Maybe you are looking for