Excel black screen when running LabVIEW 12.0 on Windows7 (32-Bit)

[MRKLL]

Eric, this is the template Excel file that is opened and recieves the Oracle download (WIP tab).  This is the file that would not open using the Excel Macro Example.vi.  The error code is -2146827284.  When I tried to save this file as a .xlsx from .xlsm, Excel would not recognize it.  There are macros embedded into the file, so maybe that is why it won't let me change the extension.  Mark

Eric, when I try to add the file as an attachment, I get this error from LabVIEW:

Please correct the highlighted errors and try again.

• The file does not have a valid extension for an attachment. jpg,gif,txt,xls,vi,zip,doc,llb,pdf,png,seq,c,h,cpp,cs,vb,ini,gz,ctl,scr,ico,tar,z,uir,vit,wsp,tsw,rtf,lvproj,xctl,lvlib,cfg,ppt,pps,lks,spy,bld,lep,xlt,xltx,dot,dotx,docx,xlsx,cap,tui,csv,seproj,vip,ogp,vipc,ms10,ms11,ewprj,log,vix,lvprojx are the valid extensions.

I will try to attach an older version of the file.

[MRKLL]

Eric, I stopped the LabVIEW update program.  I went to the Excel template file and tried to open it.  Had the same issue where it would not open correctly.  I closed it.  Then I did a double click on it and it opened correctly.  I did the same thing for the Excel output file.  Next I restarted the LabVIEW update program and it ran correctly.  While it was waiting to run the next update.  I went back to the two Excel files and executed the same process, open\close\open, until both would open correctly.  Then, when the LabVIEW update program ran again, the data was updated correctly.  I did the same thing and did the open\close\open process and the LabVIEW update program updated the files correctly.  The update times were 12:51, 13:07 and 13:20. I did not do the open\close\open this time and will see what happens.  Is there anychance that LabVIEW 12.0 does not like .xlsm files?

I found this Excel forum that may be applicable:  http://syncor.blogspot.com/2012/04/excel-interop-error-code-2146827284.html 

[MRKLL]

Eric, I just checked and the program has been updating correctly since 12:51.  Last update was 14:28.  Not sure why?  Mark

[MRKLL]

Eric, I tried your suggestion when opening the Excel template.  When it didn't open correctly, I was able to save a copy.  When I went to open the copy, it opened correctly.  After the LabVIEW program does it's update, I still cannot open the Excel template correctly on the first try, but the program is updating correctly.

I started running the LabVIEW program using the "running" button, verses the "run continuously" button.  Not sure why that would make a difference, since I have always run it using the "run continuously" button with the LabVIEW 8.0/XP/Excel 2000 combination.  Mark

[MRKLL]

Eric, I tried your suggestion to recompile the LabVIEW program.  I held down the cntrl-shift, then clicked the run button, but I never saw the option "select all"?  When I initially opened the "Update FAB WIP every 20 min.vi", I saw it compile and LabVIEW 12.0 found all of the files to support the program.

Here is a new one.  When I click on the "WIP Fab Process.xlsm" file and get the black screen, I went to the file-check for issues-check assessability.  See the last tab in the attachment for the screen shot.  Not sure what this means "Check the workbook content for people with disabilities", but Excel says it is an "Error"?  It wants me to do something with the embedded macros. Mark

[ShishKeBobby]

Hi MRKLL,

We seem to be splitting at the seams with new issues, we need to take these one by one and keep this as modular as possible.  Lets talk about some of the errors you mentioned.  

Error 97 corresponds to this article, http://digital.ni.com/public.nsf/allkb/41993270817A04E286256C8C00486468?OpenDocument .

In regards to the error "There was a problem sending the command to the program", try to run LabVIEW with admin and see if it returns.

Error code 2146827284 references the an error with a macro.  Are you macros referencing several different excel files?

I would recommend you check that your references are correct, and that the data you're sending to Excel is good (use highlight execution for this) and that your security settings in excel are set to run macros.  Barring this we need to take a step back and work with some low level sample code, get that working, then scale it up to your application.

Also, who is Eric?  Did he post and delete his comments?  

[MRKLL]

Bobby, I was given Eric's (NI Application Engineer) number at the NI phone support by Miriah Whitaker.  I talked to him yesterday and gave him this thread to follow as he looked into the problem.  I think I am past any issue with LabVIEW.  I can get the program to run correctly the first time, but it hangs up when it starts its 20 minute updates.  I still have the problem with the Excel file that will not open correctly.  That is where I am focusing my efforts.

I found this solution on the internet:

http://answers.microsoft.com/en-us/office/forum/office_2010-excel/unable-to-open-xlsx-documents-by-d...

I am pursuing the issue that there is a corrupted network/local profile.  I changed uses on this computer and have run into an issue with VB6.  The main VB file has a .bas extension.  When you look at the properties, it says that it open with visual basic, but that it is a .bas file, not a Visual Basic Module.  When I run the LabVIEW program, it can't find the .bas file to run. 

I have been contacted by Frank Lezu, NI Field Engineer, and he is visiting tomorrow at 11.  I might have it working by then if I can get by this VB issue.

[MRKLL · Accepted solution]

This is a little out in left field, but so far it has fixed my problem.  Our IT tech suggested using the open source (Java?) version of Office 2010, ie. http://www.openoffice.org/download/.  I downloaded and installed it.  Then associated each of my Excel 2010 files with this program.  So far,so good!  Files open with one double click and the LabVIEW program that does the auotmatic download from Oracle and creates the output file is running update without an error.  It appears I may need to do this with every Excel 2010 file that I try to open on this computer, but that is a minor issue.

Thanks to all the LabVIEW team that assisted me with this issue!

[ShishKeBobby]

Thanks for the follow up MRKLL.

Regards,