LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error Code -2147023116

Solved!
Go to solution
Does anyone have any ideas as to what might cause this error? <<A null reference pointer was passed to the stub.
 in Set Report Orientation.vi->Easy Text Report.vi->Generate Report Test.vi>> All I am using is the Easy Text Report.VI. I set the font to -1,-1,Times New Roman,12. The text is "Test". It is a standard report with portrait orientation. But the error code mentioned above gets generated when I run it. Any help would be greatly appreciated.
Message Edited by Mark70 on 09-17-2009 04:24 PM
0 Kudos
Message 1 of 4
(3,781 Views)
Solution
Accepted by topic author Mark70

Hi Mark,

 

Check this out.


Stephen Meserve
National Instruments
0 Kudos
Message 2 of 4
(3,759 Views)

Hi Stephen,

 

Thank you! Problem solved!

 

Let's go Islanders  :O)

0 Kudos
Message 3 of 4
(3,754 Views)

I know this thread is older than most dogs alive today, but for those of us asked to revive old machines running old software, here is the solution that was lost to the broken link. It was translated from Korean (I think) because that page still seems to be alive:

 

Issues: It works fine with LabVIEW6i, but using "Set Report Orientation VI" in the Report Generation sub palette in LabVIEW6.1 results in Error-2147023116.

Solution: This Error is caused by the property node not being properly linked to the NI-Reports.dll. You will need to re-register this DLL and mass compile the report VIs. Follow the steps below to do this.

1) In Start » Run, type regsvr32 "C:\Program Files\National Instruments\shared\NI-Reports\NiReports.dll". ( NI-Reports.dll If the file is in the same location as above, change it accordingly if it is not. Click OK.
2) Open "Examples" in LabVIEW.
3) Open the Text Report Example.vi by finding Printing and Publishing Data » Generating Reports ».
4) Hold down Shift and Ctrl to run it. This will force a recompilation of the report VIs.

There will be no errors in using it afterwards.

 

I still had to recompile my own VI for the update to take effect, but ultimately it worked. 

Message 4 of 4
(36 Views)