Access Violation 0xC0000005 in LabVIEW Executable

[Eric1977]

All,

I am trying to figure out where to place the suggested solution within the NI Knowledge Base article located here. I am using the Report Generation Toolkit which most likely uses ActiveX calls. The fix says to manually change the path of the user32.dll but does not state where. Is this in Labview? Excel?

I do not want to assume so a little guidance is appreciated.

[Eric1977]

No one has ran in this? I find that very hard to believe.

[LucianM · Accepted solution]

Issue might not be related to user32.dll. If you use Report Generation Toolkit, it might be that MS Office version installed on the computer where exe is running is not 100% compatible with the toolkit. I had issues like this with Office 365 after it received some updates: some methods/property nodes used by the toolkit had more (or less) parameters after the update causing the crash when executed. There was a thread about that somewhere but I am not able to find it. Have you looked into the log files created after the crash? You can find some information about the location of those files in this link

You can also attach the files here, maybe someone will give you a clue.

[Eric1977]

You triggered something to look at which I never even thought it would be an issue. My PC (the development machine) has Excel 365 while the target PC does not.I bet there are just enough inconsistencies where the two software packages just don't mesh.