Jump to content

Christopher Nielson

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Christopher Nielson's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I was able to find the solution to my issue above. When starting VIPM I was getting an error accessing the LabVIEW Tools Network Repository. I resolved this issue by turning my Proxy settings from Use System Proxy to No Proxy. However, when No Proxy is selected Login fails. I have to start VIPM with Use System Proxy Settings On, Then Log in to Community Edition, then change the Proxy Settings back to No Proxy and restart VIPM. VIPM then starts correctly: Logged in and no issue accessing the LabVIEW Tools Network.
  2. Sorry to bring up and old thread. I recently installed the latest version of VIPM, 2023.3 (2523). I'm no longer able to login to the community edition. Other people within my company are not having issues and I'm not able to login on my home network either. Any suggestions on how to fix my login issue?
  3. Over the past few months, I have been unable to login to the community edition of VIPM. It used to work but after some LabVIEW update (I don't remember specifically what I updated), I keep getting an error and a LabVIEW cannot authenticate the server error. I have no issues downloading or installing packages; however, I'm trying to use some of the features unlocked by the community edition for making my own packages. I found this old topic (3306-login-fails) and it appears that the issue was resolved, however I'm still having an issue. I have checked and other people within my company have not had any issues. I even have trouble on my home network, so I'm not convinced that it's a corporate firewall issue. I'm using LabVIEW 2018, 2020 and 2023. (all 32-bit versions on Windows 10 PC) I just recently updated VIPM to the latest build (2023.3.2523). I've made sure all LabVIEW 20xx and VI Package manger are allowed through the Windows Firewall. I have a valid connection between VIPM to all versions of LabVIEW and made sure all TCP/IP Ports match. I've verified and even tried changing passwords. I've tried different user accounts. I feel like I've tried everything, and I am out of ideas. Hoping someone will have a suggestion or a fix that I have yet to try! Thank you in advance for your help! Here is the Error message from the log: = Automated Message Start = Error 363507 occurred at 56EBE9C3A96D6A601C8F050B4651CA6D:6530004 Possible reason(s): LabVIEW: (Hex 0x58BF3) LabVIEW could not verify the authenticity of the server. Complete call chain: 56EBE9C3A96D6A601C8F050B4651CA6D:6530004 JKI_API.lvclass:LogIn_Parse_API.vi MainUI.vi VIPM Main Window.vi = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> MainUI.vi = Error Handler Call Chain End = =========== END of VIPM 2023.3 (build 2523) Error Message ===========
×
×
  • Create New...

Important Information

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