Jump to content

LeahE

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Female
  • Location
    UK
  1. Hello JKI, Problem still persists - have checked my firewall logs and there are no dropped packets on the ports. Must be something to do with it being a virtual machine. Here's the VIPM error log, if that's of any use for you to troubleshoot. Some sort of generic error 42. =========== START of VIPM 2019.0.0 (build 2029) Error Message =========== An internal VIPM 2019.0.0 (build 2029) Error has occured on: Tuesday November 05, 2019 at 07:59:59 AM = Automated Message Start = Error 42 occurred at (Timeout value exceeded!) 8B531AEFB0487B775F9C3920D94A1C09:1600001 in CB0223047C730D2BADF940A6F0264CA2->VIPM Configure LV Port.vi->Options.lvlib:VIPM Options Window.vi->VIPM Main Window.vi Possible reason(s): LabVIEW: Generic error. = Automated Message End = = User Defined Message Start = Testing the LV connection from the test connection dialog. = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> Options.lvlib:VIPM Options Window.vi-> VIPM Configure LV Port.vi = Error Handler Call Chain End = =========== END of VIPM 2019.0.0 (build 2029) Error Message =========== It's very frustrating not being able to debug this myself... Would you care to set up a replication on a Hyper-V virtual machine, and see whether you get the error and if so, why? Hyper-V comes with all windows installs anyway, it wouldn't take you long. Many thanks, Leah --- Edit: set up the replication on a non-networked VM. It connected fine. Seeing as it is not a firewall issue, could you suggest some further troubleshooting steps please?
  2. Afraid I'm still stuck on the same issue a week later and it is impeding my ability to get work done. Does anyone have any suggestions? Alternatively, has anyone managed to successfully get VIPM running on a Hyper-V virtual machine? Many thanks, Leah
  3. Good morning, I am having problems connecting LabVIEW 2016.0 and VIPM 2019 on a Windows 10 Enterprise virtual machine. My host machine with the same setup (OS, permissions etc.) works fine. The host just has a few more versions of LabVIEW installed. I'm running out of ideas... this is what I have tried so far: I have followed the instructions on this article but nothing changed. I have checked my firewall and VIPM and LabVIEW are both allowed to make TCP connections on any port. (Same settings as on host machine.) Tried using a different port for both VIPM and LabVIEW I debugged it in command line using: netstat -aon | findstr 3363 -->Get task reference tasklist | findstr [task] I can see that a connection is established between VIPM and LabVIEW on that port (see attached image). But I still get the error message saying 'VIPM could not connect to LabVIEW 2016'. I've increased the timeout. I've run VIPM as administrator I've reverted my VM, reinstalled the software and encountered the same issue Any ideas what else I could try? Could it be something to do with it being a Hyper-V virtual machine, and behaving like a remote session? Many thanks, Leah
×
×
  • Create New...

Important Information

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