Labview reports 'Excel Sort Data.vi' in Report Generation Toolkit is broken.

[STTAndy]

Good Morning

I have been working on a large project for some time now that includes Microsoft Excel report generation using the toolkit. Labview and the Report Generation Toolkits are both version 2017 

When I attempt to build the project I get the following error.

A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build. Report this error to National Instruments technical support.

C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\addons\_office\excel.llb\Excel Sort Data.vi

I am not calling this vi in my project but I realise it could be called by other parts of the report generation toolkit. When I open the vi it shows an error 'Invoke Node:Contains unwired or bad terminal'.

Currently the only way to build the project is to enable debugging which I dont want enabled.

I have traced the problem area to two report building vis that place data into excel tables but don't call that vi directly, the data is not sorted. They each use 'Append table to worksheet' and only these two report vis use tables so I guess it is connected somehow. If I try to build either of the two report vis I get the same error but  these vis were completed some weeks ago and have not had any issues until this week making me feel something else has changed somewhere, perhaps an update?

I have tried reinstalling the report generation toolkit and even LabView has been reinstalled but the issue persists.

LabView 2017 32bit

Windows 10

The vis both contain sensitive client data so I am unable to upload the vis at this stage. If I need to I can do a version without the data but only if neccessary.

[McQuillan]

Morning,

I've looked at the Excel Sort Data.vi in LV18 (64-bit) and that's also broken. However, after a quick Google I can't find any other mentions of this.

The only things I can think to mention are:

1. Call NI Tech Support so they can file a corrective action request (CAR) with R&D
2. Use the find functions in LabVIEW to search for all instances of this VI in your project and replace them.

From your message I get the impression that you are able to run your code in the development environment, but not as a build executable? Is this correct? If that is the case then you can't be calling this function explicitly, I suspect you would be able to change your build spec so this VI isn't included.

[STTAndy]

Yes Tom it runs without complaints in development and it will build if I activate debugging as is suggested in the error popup. If you are finding yours is also broken then I am happy it is not something I did to break it. It also says on the error Report this error to National Instruments technical support so I guess that is what I will need to do.

Thank you for replying.

[McQuillan]

One quick thought - In Build Specification > Additional Exclusions, have you ticked all of the boxes?

I have found that 'Disconnect Type Definitions' seems to solve issues like this - I'm not sure why or what it's doing behind the scenes but it's worth a try.

[STTAndy]

Ok I just tried that and it did not help unfortunately. I have reported it to NI so hopefully it will be sorted soon, my build has increased substantially by enabling debugging!

[Dhubbell]

Same thing is happening to me!  I have LV2015.  I compiled this project only a day ago and no problems.  Windows update happened last night, probably broke it.  I'm running W7 with O365 2016 suite.

[Dhubbell]

Report this error to National Instruments technical support.

---

I called NI and reported the problem.  If anyone else is experiencing the same issue, please call NI.  I too have an important project I'm in the middle of a release and now I can't support my customer's service requests. 

[FilipN]

Hey, We've stumbled across the same issue yesterday when trying to build our project. I've been in touch with NI and will post when resolved.

[STTAndy]

I managed to find a way of bug reporting on the website so I took that route.

It is clear from the responses that it is a bug, initially I though I had messed something up.

[Dhubbell]

Here's "Excel Sort Data.vi" showing the error.  I never modified this VI.  But the Bug is reporting "One or more required inputs to this function are not wired or are wired incorrectly".

I guess we could get creative and start modifying this VI to fix it.  I don't call this "Excel Sort Data.vi" directly, but, perhaps other VIs do call it.  In a pinch I may need to disable this VI and compile...to see what happens.