Report Generation Toolkit files in incorrect location after installing deployment

TestStand 2010 SP1 + LabVIEW 2011 + Report Generation Tookit
After installing a deployment, the location of NI_Excel.lvclass is expected to be at ...\VIs for <project name>\SupportVIs\Excel\NI_Excel.lvclass (see attachment)
but the path of the file is located at ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
In the deployment image, under the target folder, the file is in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
and the lvproj finds the file.
The lvproj in the installation finds the file in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
Renaming the folder from data to Excel fixes this problem.
Has anyone else run into this problem?
Attachments:
Report Generation Toolkit Error.png ‏15 KB

I am facing the same issue when I create the TS deployment through utility using TS2012.I thought of adding the file to the Teststand workspace and give the destination in to supportVIs directory.But even tthat didn't worked as it was copying all excel vis in to two locations.
Even adding the Directory path in to TS search directory options to "\data folder" is not resolving the issue and LAbVIEW Vis are not able to locate it.

Similar Messages

Report generation toolkit (1.0) can't be installed under LabView 6.1.

When installing the toolkit, it showed that it was unable to locate the LabVIEW run-time engine of version 6.0 or compatible. However, my computer has already installed a run-time engine 6.1 (I saw it on my control panel->Add/remove programs). Do I need to install another run-time engine 6.0?

Hello William,
You may want to see this article on NI.com. It sounds like it addresses your particular issue.
Regards,
Chris J
Installation Errors with the Report Generation Toolkit 1.0 for Microsoft Office and LabVIEW 6.1
http://digital.ni.com/public.nsf/websearch/BEE4820C6BB7305186256B42005C9514?OpenDocument

File Dialog and Report Generation Toolkit

Hi,
I designed a VI for an electrometer calibration and it works quite well The only problem I have is the following:
I used the Report Generation Toolkit to put the measurement data in an Excel file. When I run the VI I'd like a window to pop up to define the location and name of the Excel report file. If these two things are done LabVIEW should create the specified Excel file and run the rest of the code.
So i tried this with the "File Dialog" Vi and all the needed low-level File I/O VIs and it worked.
But when i connect the "File Dialog" VI with the "New Report" VI of the Report Generation Toolkit I get an error message.
Is there any solution to get this file dialog pop up window with the Report Generation VIs?
thx for any help...!
Message Edited by Flea on 12-15-2005 03:58 AM

Wow, thanks for your fast and very helpful reply devchander!
I already tried this and it works fine
thx!

Problems in using Application Builder to Build a exe file with Report generation Toolkit

Hello,
It's my first time to build exe. But I have Problem when the VI have Report Generation toolkit VI.
It's no problem in VI Format , But It can't work when I build as EXE format
Can Anyone help me, and state step clearly in how to solve the problems?
Thank you!!

If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
There is an error occuring that your code isn't reporting.
There is a file path that under the executable isn't valid.
First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

File name collision during build that includes Report Generation toolkit. How to correct?

When I switched to LV 8.6 (it's also in 8.6.1) I started getting a file name collision warning when building an installer that included the Report Generation toolkit. The executable works, but I don't like to leave warnings uninvestigated. I don't understand 1) why it's happening now and 2) what it's recommending for the fix. Here's part of the actual warning it gives.
LabVIEW prevented a file name collision during the
build. Duplicate file names cannot be copied to the same destination. You can
rename files as part of the build process to avoid name conflicts.
The following files were moved to a unique
location:
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append Control Image to Report.vi
C:\Program
Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append File to Report.vi
C:\Program
Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
File to Report.vi
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append Horizontal Line to Report.vi...........

Hi GS,
The architecture of the Report Generation Toolkit was changed in LabVIEW 8.6 to utilize LabVIEW Classes. As such, there are some warnings during an EXE build because the class VIs have identical names. Classes were not used in the toolkit in LabVIEW 8.5 and previous...that's why you didn't see any warnings during the build until now.
Your EXE should still function properly, and you shouldn't have to change anything about your build. The purpose of the warnings is to let you know that the duplicate-named VIs needed to be handled differently during the build.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

.tmp file is created by NI Report generation toolkit for logging data to MS Excel

Hi,
I am getting ".tmp" file while logging data to MS Excel by NI Report generation toolkit. Instead of assigned file name, toolkit is generating a junk value with .tmp extension, but I can able to open this .tmp file with MS Excel.
Can anyone help to solve this issue?
Thanks,
Thirumala

Hi Thirumala,
You may experience issues when you try to save a Microsoft Excel file if one or more of the following conditions are true:
1. You save an Excel file to a network drive where you have restricted permissions.
2. You save an Excel file to a location that does not have sufficient drive space.
3. The connection to the Excel file has been lost.
4. There is a conflict with an antivirus software program.
5. You save an Excel file that is shared.
6. The 218-character path limitation has been exceeded when you save an Excel file.
7. The Transition Formula Evaluation feature is turned on in Excel.
8. The file was created from a template that contains embedded objects.
Hope this will help to solve your problem.
Thanks,
Sanad MM

Open an existing Excel file created by Report Generation Toolkit

How would I open an existing Excel file that has been created by the LabVIEW Report Generation Toolkit?
Let me explain my application. I have made a test program to collect data on a device. Each time I run the program I want it to append a new row onto an existing data file. Since the tests I do are sometimes over a period of days, I cannot keep the program open and running continuously. So I have to open an existing file and append the new data to it. In technical terms, what I need is to get the 'report out' reference to the existing Excel data file without losing the data that is already there.

For info on accessing Excel do a search in the examples for the word "Excel" you will get an example that shows how to open a spreadsheet and manipulate the data. This should get you started.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Problem writing to excel file using report generation toolkit

hello everyone, i have this report generation toolkit... and i want to output DAQmx Analog I/P data on to an excel sheet. the DAQmx is programmed to collect
data at 3samples/sec. however, when i see the excel file that Report Generation Toolkit generates, the time stamp is updated every second instead of every 0.33sec.
can anyone please help me? i am using the MS Office Report Express VI.
Now on LabVIEW 10.0 on Win7

@All, I got rid of the express VI, decided to work on the custom low level VIs instead. however, i have a new problem now...
I have a case statement wherein, the user selects if he wants to start generating a report. once the program enters tat loop, the program speed reduces!
can anyone please tell me why is it happening? i ahve attached the vi... also another question.. in this VI, i am capturing the unwanted data into the graph as I am indexin the graph input. how can i make a logic
that the graph captures the data only when I am switching the CREATE REPORT button (which is in the while loop). is there a way that I can append the data to the graph without creating a new graph every iteration? please let me know
thanks
Now on LabVIEW 10.0 on Win7
Attachments:
Untitled 7.vi ‏75 KB
Untitled 7.JPG ‏99 KB

The report generation toolkit didn't work after the vi was build to an application.exe

I write a VI using LabVIEW Report Generation Toolkit , it really works in the LabVIEW7.1 and 6.0 enviroment. but after the VI was build in to an application.exe, the LabVIEW Report Generation Toolkit didn't work even the application runs.
thanks for your help.

You might want to follow the procedure here:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
(If the URL doesn't work, you can search for NI document ID: 2B87TVI8)
Dan

How to get data from an existing Excel file using report generation toolkit

I'm trying to use the Excel Get Data vi from the report generation toolkit, but i can't figure out how to turn a browsable path into the right type for the VI. I've tried using the New Report.vi, but that doesn't work unless you use a template. It won't open an existing excel file and make it an open report to pull data from.
Essentially, i have a bunch of excel files that have data in them and i want to use a VI to analyze the data. So, i'm trying to pull in all the data directly from the excel file so i don't have to reproscess them all into text so i can use the more standard spreadsheet VIs. But to even convert the excel file programtically in labview won't i still need to be able to open the excel file and get the data?
Solved!
Go to Solution.

I C.
Got it,
the reason why I can view it using my Excel file because its in .CSV.
I open Microsoft Excel to open .CSV file.
But you can also open .csv file with notepad.
So, you cannot open .xls with Read Spreadsheet File
I learn something everyday
Best regards,
Krispiekream

Report Generation Toolkit - Write cells to already open Excel file.

Greetings,
Does anyone know a way to write numeric cell values to a worksheet in an Excel
spreadsheet that is already in memory using the Report Generation Toolkit?
I've found that if the spreadsheet is already in memory and the user has made
changes to it without saving the changes, when LabVIEW opens the reference to
the report, the user’s changes are overwritten if they have not been saved
since LabVIEW opens the last saved version of the spreadsheet. I'm aware
that there is a setting to "display alerts" to the user but I'd
rather not do this. I would like simply to obtain a reference to the open
spreadsheet without re-opening the spreadsheet file.
Thanks in advance!

Space_Flight wrote:
> Greetings,
> Does anyone know a way to write numeric cell values to a worksheet in an Excel
> spreadsheet that is already in memory using the Report Generation Toolkit?
>
> I've found that if the spreadsheet is already in memory and the user has made
> changes to it without saving the changes, when LabVIEW opens the reference to
> the report, the user?s changes are overwritten if they have not been saved
> since LabVIEW opens the last saved version of the spreadsheet.  I'm aware
> that there is a setting to "display alerts" to the user but I'd
> rather not do this.  I would like simply to obtain a reference to the open
> spreadsheet without re-opening the spreadsheet file.
>
> Thanks in advance!
Space_Flight:
I do not believe this is possible to do with the report generation VIs
(although I have VERY little experience with these. If you really had
to do it this way, you could use activeX controls to manually right
values to cells in an open excel spreadsheet, but this can get rather
cumbersome. Are users changing the values in the spreadsheet while
your program is running? Is there maybe a way around this?
-Ray

Report Generation Toolkit Excel Vi's do not run after creating an executable. What am I missing?

I have labview 8.5 and Report Generation Toolkit version 1.1.2. My vi works fine during development. When I make an executable or an installer the excel vi's do not work. I have seen this question posted before but it has always been for earlier revisions and the answers do not seem to apply with 8.5 and 1.1.2.

Hello ajh,
You will have to include Dynamic VIs in the executable you build. The following link has more information:
http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
Prashant.

Report Generation Toolkit doesn't work after patches A thru I.

For LV7 Express, RGT demo doesn't run any of its operations, Word, Excel,... See attach for cause. Can anyone tell me how to fix this?
Attachments:
RGDemo1.doc ‏36 KB

Hi,
When you get this error, it's normally because the version of the Report Generation Toolkit VIs in your VI that you are trying to open is different from the one on your PC. Normally you can just right click on the bad VIs on the block diagram and choose "Relink To SubVI".
There's a KnowledgeBase that describes another issue when using different versions of Microsoft Office.
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

Getting "Save File" permission message related to Report Generation Toolkit

I started having this problem about a month ago. It does not affect the operation of my project but is a minor nuisance, but a nuisance none the less. I opened a couple of Excel Specific VIs. I did not nor did I attempt to make any changes, I was just curious as to their content (truth is I wanted to see how the active X controls were being used). Ever since then I get the attached messages when saving my project and have not been able to get rid of it. When OK is pressed, a Save As dialog box appears (see attached) pointing to the NI directory which contains the Excel VIs for the Report Generation Toolkit. I press cancel and am able to save my project VIs just fine, but I would like to get to the bottom of this problem.
I would not think that simply opening a VI would cause this behavior. I should also mention, it not only attempts to save the VIs I opened, but every RGT VI that is a part of my project, which is even stranger. I have not attempted a reinstall. I was hoping for something a little less drastic, and that won't prevent this from happening again, unless I can kill my curiousity that is. Is there a setting somewhere which I am missing? Thanks in advance for your assistance.
Reese
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
Attachments:
Save Message.JPG ‏249 KB
Save As Dialog box.JPG ‏305 KB

It did not work. In fact, it called out four bad VIs (see attached). But I think this is probably normal behavior. All the VIs in question are broken due to an unwired input on the bundle. The bundle is the only thing in these VIs. Could you please verify that this is the case. It said the mass compile was complete and I am assuming that it did compile the rest of the VIs, correct? Unfortunately I am still getting the same message. Do you have any other ideas? Anyone? Thanks again for your assistance.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
Attachments:
Mass Compile Dialog.JPG ‏338 KB

Ridiculous number of directories when build includes Report Generation Toolkit

I was getting error 7 with the report generation toolkit, so I followed the steps here and it works. Only problem is, it makes a different support directory for each individual file in the NIReport.llb directory.
The calendar and data directories are my own. The rest are the RGT.
Help? haha.
CLA, LabVIEW Versions 2010-2013
Attachments:
buildsetup.PNG ‏49 KB

I set NIReport.llb to always included like it said, but it wasn't showing up after I did a build. So...I left it included always, I created my own destination with the same name (NIReport.llb) on the Destinations page of the app builder, went to the Source File Settings page of the app builder, selected NIReport.llb and set the location to be my NIReport.llb folder I created. I did a build and this solved the problem and all the NIReport.llb files were placed in a NIReport.llb directory. Someone pleaseeee tell me if there is a better way, but this will work for now.
CLA, LabVIEW Versions 2010-2013

Report Generation Toolkit files in incorrect location after installing deployment

Similar Messages

Maybe you are looking for