Erreur Toolkit report Excel avec office 2013

Bonjour à tous,
J'utilise LAbview 2014 sur windows 7.
Alors j'ai plusieurs programmes qui utilisent le toolkit de génération de rapport sous Excel.
Ces programmes fonctionnaient parfaitement avec office 2010 mais suite à une mise à jour et au passage sur office 2013, le fichier Excel n'est plus remplie et mes programmes sont donc inutiles.
Pouvez vous me dire d'ou vient cette erreur ? Que dois-je faire ?
Merci d'avance

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

Similar Messages

Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

Hello community,
on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

Can't open .dz attachments in Outlook to Excel in Office 2013

We have a custom ERP we use at our company that creates .dz attachments which our users can open in Excel. In order for the employees to open these .DZ files in Excel we needed to make a registry edit.
I just upgraded machines to Office 2013 and now we have the same problem. We don't remember what the registry fix is and hope someone can point us in the right direction.
Thanks in advance.
IT

Yes, it can't be opened as an attachment.

Microsoft Office 2013: License 01A - Microsoft license ledger for Microsoft License Statements

I have a client who uses these reports for their license counts etc. Recently they have deployed Office 2013 (Not through SCCM) and the reports do not reflect any Office 2013 installations although running a query for Add/Remove or looking at software
installed on a specific computer via other reports clearly shows Office 2013. Was there a specific rollup or hotfix for this? Thank you in advance for your time.

Thanks. I reviewed that in the past and did not see anything specific regarding Office 2013 nor in the R3 release notes.
@roblizz, sorry, I just noticed you commented on the TN wiki article for CM07 patches (which I help to curate).
It seems related to this question you asked, and the same sort of timeframe.
Did you get this sorted out ?
If not, this other HF for AI might be worth considering (assuming you haven't previously applied it).
Otherwise, it looks like we all missed the boat on getting a HF for this, since CM07 is now out of mainstream support.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Erreur 2147352567 avec Toolkit Report Generation

Bonjour,
Je dois programmer la génération automatique d'un rapport sous Excel. Je possède le Toolkit Report Generation.
Tout fonctionnait correctement jusqu'à ce que je reçoive le message d'erreur "2147352567" en executant le vi permettant de générer mon rapport.
Ce message survient dès l'utilisation du sous-programme NewReport.vi .
Lorsque je cable entrées et sorties d'erreur, cela m'indique le message suivant: Nœud de propriété (arg 1) dans NI_ReportGenerationToolkit.lvlib:Excel_Open.vi->NI_ReportGenerationToolkit.lvlib:Excel Try Opening Excel Again.vi->NI_Excel.lvclass:new report subVI.vi->NI_report.lvclass:New Report.vi
Merci d'avance pour votre aide.

salut j'aime bien utiliser le report generation toolkit.
A la lecture de ton post; je suis étonné par l'erreur; en effet
et
si je lis ton message, l'erreur provient de Excel_open.vi
Donc ouverture d'excel OK; mais erreur "-2147319784
J'ai le sentiement qu'Excel est dans une apparence que l'ActiveX n'arrive pas à modifier.
> Tu peux laisser le vi ouvert, et regarder les valeurs des paramètres d'entrées
> tu a redémarré ton PC?
> Excel est bien fermé? plus de process ouvert? ctrl + alt sup
> Faire un exemple
A+
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

Is ms office 2013 supported for report generation? Error 41106

Hi
I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
When using the report generation toolkit, I get an error 41106.
I have reinstalled the toolkit - no effect.
I sort of assume therefore that office 2013 is not supported?
Any hints, tips, patches or workarounds please.
Bill

Bill_Shepherd wrote:
Hi
I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
When using the report generation toolkit, I get an error 41106.
I have reinstalled the toolkit - no effect.
I sort of assume therefore that office 2013 is not supported?
Any hints, tips, patches or workarounds please.
Bill
I've seen some issues when I upgraded to Office 2010. Note that it is possible that the route cause of your problem is totally different but in my case there was some ActiveX properties or Methods call that have been changed. I solved this issue by navigating to the property/method that caused the error, clicked on it and reselected the same property/method. You could probably find some older post that discuss that. Hope this help.
Ben64

How to report a bug in all excel versions 2007 - 2013

I found error in excel calculation (Wrong answer) compared to manual methods or other specialized programs. how do i report this error for Microsoft

Hi,
Thanks for your feedback.Could you give me more information about the issue? If you could share me some images or the file, it'll be benefit to me.
If you use Office 2013, you could use the smiley and frown icons have been added to provide positeve or negetive feedback regarding the new Office to Microsoft dev team.
http://blogs.office.com/b/visio/archive/2012/08/03/give-us-feedback-on-the-new-visio-by-sending-a-smile-or-frown.aspx
Regards,
George Zhao
TechNet Community Support

Does Essbase Excel Plugin 11 work fine with Microsoft Office 2013

Hi,
My Company is planning to Upgrade to Microsoft Office 2013. Does Essbase Excel Plugin 11 work fine with Microsoft Office 2013?
Thanks,
Shashi

Hi Shashi,
Below content is taken from oracle certification matrix.Microsoft office 2010,2008 supports the lastest version of 11.1.2.3.More info check with the oracle certification matrix.
Version Supported
Vendor
Certification Type
Version
Exceptions and Additional Information
11.1.2.3
Microsoft
Office Productivity Suite
Office 2007 (all SP levels included)
Office 2010 (all SP levels included)
1. MICROSOFT OFFICE IS REQUIRED FOR: Smart View and Offline Planning when used with Reporting and Analysis, Financial Management, and Planning. Microsoft Office is also required for Disclosure Management, FDM, Financial Reporting Client, Performance Management Architect File Generator, and Strategic Finance.
2. Offline Planning and Excel must be installed on the same machine.
3. Microsoft Office 2010 (32-bit Office on 32 or 64-bit operating systems, 64-bit Office on 64-bit operating systems)
4. EXCEPTION: Disclosure Management has installation prerequisites. For Office 2007. See http://support.microsoft.com/kb/970942.
5. EXCEPTION: FDM server only supports the 32 bit version of Office.

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Move a Excel 2010 Dokument Addin Project (Visual Studio 2012) to another devleopment machine with Visual Studio 2012 , but Office 2013

Hi
we do have the following situation
on computer A there is a Excel Document Addin development project , Visual Studio 2012, Office 2010 installed. All works fine.
we would like to bring the project to another machine with Visual Studio 2012, but Office 2013 installed.
Visual Studio can not build the project. It says that the application is not installed on the machine (though Excel 2013 is installed , but not Excel 2010) It seems to have a problem with the
vbproj.
In other forums I found a hint that "Hostpackage = ..} needs to be set accordingly in the vbproj. I created then a "empty Excel-Addin project" under Visual Studio , looked at
the Hostpackage entry, put that into the vbproj of "problem project. It still does not work.
It would be great if anyone could help.
Thomas

Hello Eugene
Problem is that it says that projectboard (the name of the main project) can not be loaded. All other projects in the solution can be loaded. Strange thing is , now that I try to create a empty excel Project it says that according to Excel security settings
it can not be generated !?
I opened then Excel and set all Trust Center settings to "Default" - but no effect. I really have no idea what is wrong ..!?
Tom

REPORT GENERATION TOOLKIT AND EXCEL

i have a problem with report generation toolkit and excel
the problem is:
i must read & write from a excel worksheet when this is open but when i using the report generation the worksheet is open another time
have some solution for this problem?
sorry for my english

You need to close Exel when before your VI is running. Excel can not have two instances running at the same time.
Joe

Report Generation Toolkit, Print Excel Report, LabVIEW Crash

Hello,
when printing a report generated with the report generation toolkit for excel my build application crashes on our customers PC.
When I run this application on my PC it works fine.
The problem is the active X invoke node that trys to print the report but i cant get any error messages to find out where to locate the problem.
Maybe that there is a problem with the active X node or the Excel Version on the customers PC?
I use LabVIEW 2010 and Excel 2007 the customer has Excel 2003 SP 3.
I changed the report to generate it in Word where the Print_Report.vi fine on both PCs. But in Word Report there is called another active X invoke node to print the Report. So it seems for me that there really is a problem with the Print in Excel active X invoke node.
Mybe someon can help me in finding out whats the problem.
Greetings Daniel.
Solved!
Go to Solution.

Hi Daniel,
your behavior has been reported by others. For example:
Application Build Failure on Excel.Print Report call
http://forums.ni.com/t5/LabVIEW/Application-Build-Failure-on-Excel-Print-Report-call/m-p/1563242
Problem posted: 05-17-2011 02:19 PM
Workaround posted: 06-01-2011 and later
So their workaround was to use Excel 2007 or 2010 instead of 2003. Is this working for your customer?
Best Regards,
Jan

Cannot open Office 2013 Excel, Word, PPT Files on Network Share

Cannot open Office 2013 Excel, Word, PPT Files on Network Share
I am having a problem opening any Office 2013 file when it is located on a network drive. I immediately get the error:
"Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space.
. To make more memory available, close workbooks or programs you no longer need.
. To free disk space, delete files you no longer need from the disk you are saving to."
It only occurs when I try to access the file when it is stored on a network share. I cannot open any word, excel or PPT files located on my file shares.
I am on Windows 8 (pro), part of a local domain based on Server 2003, and have administrator rights to the domain and the file share where the Excel file resides (and Word files -same problem). If I copy the file locally, I can either open
it directly, or right-click, go to Properties and 'un-block' the file and then open it. But it is impractical to keep doing this, as I edit different files from the directory tree all day.
I have bing'd and google'd this extensively, and the only answers I come up with do not work, such as going into the DCOM config system and changing the user from interactive to launching user, or vice versa, or even using a specific user - mine
with the password. Since the product is so young there aren't a lot of posts on this, and nothing has improved the situation.
Can you add any insight to this? I really want to use Office 2013, but this is such an obstacle I'm going to have to downgrade if this problem cannot be resolved. Thank you very much for any help you can offer.
Evan

Dear Evan,
If DCOM config solution did not work, I'd suggest narrow down the problem by trying to access another network share on another server, try to open an Office file there, do we still have the error? It could help us determine if the issue is on the client
machine or the server side.
Best regards,
Daisy Cao
Forum Support
Please take a moment to "Mark As Answer" if they help.

2013 Excel docs open up to grey screen (Office 2013 Home and Business)

What I have tried:
-Opening in safe mode (using shift).......still shows grey blank screen.
-File>Options>Advanced> "Ignore all other applications using DDE" check marked......Still shows blank screen.
-Don't have the option to click "unhide" because every tool option is greyed out.
***When the 2013 excel doc opens up to the blank grey screen, ALL the menu tools and options are grayed out as well. I cannot click on anything besides File>New or Open or Account or Options.***
Please help me with my direct problem. I have been everywhere on the internet and no one has my particular problem that i have found. There are similar ones but those solutions i have already tried. (See Above)
Thanks

Hi,
First, try to repair Office 2013 to check the issue.
Second, try to reapply the registry patch:
reg add HKCU\Software\Microsoft\Office\12.0\Excel\Options /v NoReReg /t REG_DWORD /d 1
Jaynet Zhang
TechNet Community Support

Office 2013 Home & Business Edition - None of the application (Word, Powerpoint, Excel or Outlook) is opening, not even in safe mode..

Office 2013 Home & Business Edition - None of the application (Word, Powerpoint, Excel or Outlook) is opening, not even in safe mode.. I tried to run the application in compatibility mode by right clicking the excel.exe and choosing the compatibility
mode, still no success. It is installed on Windows 7 Professional SP1. All the latest updates are already installed. I have also tried Microsoft fixit, but still no Success. Please help!!

I'm so sorry that I forgot the Office programs even not open in safe mode and provide useless information in my last reply.
The problem persists when we perform a Windows clean boot, right?
Were the Office programs suddenly not working? Or it just can’t be open after you install it? Did you get any error message?
If you haven’t try a repair of your Office installation, we can try it to check the result:
http://office.microsoft.com/en-us/project-help/repair-office-programs-HA010357402.aspx
In addition, try to use Event Viewer to see if we can get some useful error log about this problem. See:
http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Erreur Toolkit report Excel avec office 2013

Similar Messages

Maybe you are looking for