Jump to content

Michael Aivaliotis

Members
  • Posts

    492
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Michael Aivaliotis

  1. Sorry. This is a legacy issue with the VIPM API VIs. We'll be releasing a new version in the next few weeks to address this issue.
  2. Running as Admin is only suggested in order to debug the problem and give us an idea of what the issue is. You should not require to run as Admin. Can you describe your system: What Windows OS 32 vs 64 What language OS How many LV versions and which ones. Also submit your error log
  3. Just want to mention that this fix is built into the new release of VIPM 2012. It is recommended for all to upgrade to this version.
  4. Are you running German, Spanish or French Windows? If so, then read a few posts back to see a fix. If not, please contact us using our contact form and we can provide more assistance.
  5. It seems to be an issue accessing the registry. This is one problem that we have seen by other users but have not been able to isolate and reproduce. If you see the error log it indicates an error accessing the following key: KEY_WOW64_64KEY\SOFTWARE\National Instruments\LabVIEW It may be a permissions issue, but not sure.
  6. Try running the following executable, then try launching VIPM again. Note: This only helps users running VIPM with European languages (German, French etc.) in their Windows OS. setperms2.exe.zip
  7. BadToad, I'm sorry you are having these issues. Can you get us some more information, in order to debug your problem? --> See here.
  8. You need to install the LabVIEW 2009 run-time engine. Can you try reinstalling this?
  9. Please see here for log location and instructions: http://forums.jki.net/topic/1442-how-to-submit-vipm-troubleshooting-logs/
  10. Sorry, you are having these troubles. What localization are you using, meaning, what Country is this Windows 7 installed in? Is it configured for other languages? Some things to do: Right click on the desktop icon and select "run as administrator" to see if it fixes it. Next, please attach troubleshooting logs (zip them). See here for instructions: http://forums.jki.net/topic/1442-how-to-submit-vipm-troubleshooting-logs/
  11. Make sure the project and all the classes are saved to disk.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.