01-23-2014 09:01 AM
Hello,
Could anybody help with this error message?
Seems like anything is wrong with NI MAX, in addition, when I do right-click on "Devices and Interfaces" nothing happens...I cannot see the dialog "Create new".
I am with Windows 7 64-bit
Thanks
01-23-2014 12:23 PM
01-24-2014 01:49 AM
Thanks Ray,
But it didn't work, I tried to uninstall Visual Studio, uninstall LabView and install again LabView, but still having the same problem.
01-24-2014 10:29 AM
Did you try re-installing NI MAX? or was that part of the LabVIEW re-install?
01-24-2014 12:08 PM
Yes, everything included in the LabView instalation, LabView and MAX
01-24-2014 02:20 PM
What drivers and versions have you installed with LabVIEW? And does the access violation happen after clicking Tools>>Reset Configuration Data and restarting?
If this is still happening, can you click Send on the crash report window you posted and then Copy/Paste the Report ID here so we can take a look?
Thanks,
01-27-2014 01:18 AM
Hi Zachm,
I have installed the LabView package without any driver, that means, unchecking the option about the drivers when installing, and still having the same problem.
And, for further information, I will tell you that, if I open NI MAX, and do nothing, that means, just open, let it load, and close, then nothing happens, but, when I open and click on the arrow on "Devices and Interfaces", let it load and then I close NI MAX, then it closes and I get the message posten on my first post.
In addition, as I said before, if I try to right-click on "Devices and Interfaces" looking for "Create new...", nothing happens, I do not get any response.
If you need ony other info in order to be able to help me plesae ask me, no problem.
Thanks!
01-27-2014 07:16 AM
P.D: I have already clicked on the "Send" button from the error message like 2 or 3 times, so you may have it somewhere there at NI.
And, about the LabView version:
01-27-2014 07:21 AM
Sorry I forgot the report ID
Report ID : a2a594c7-3954-4462-a29b-a2548e1fdf1d
Thanks for your help.
01-29-2014 10:13 AM
We pulled up your report in our crash database. It looks like Ray is correct. The crash is occurring in a very old (1998) version of PDM.dll. It looks like this dll shipped with Visual Studio 6 and Office 2000. I would recommend finding a way to update that DLL or you could try removing it (making sure to preserve a back-up) if you are not using Visual Studio 6 or Office 2000.