Jump to content

Search the Community

Showing results for tags 'vlmclient'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 1 result

  1. Our company has a company-wide network license server for LabVIEW. I have a machine where I installed LabVIEW and everything works dandy there. But nobody else can use it at all. I've already been through plural rounds of local IT shooting in the dark: try this, try that, try something else, do the first thing again. It's all been no use. So does anyone know where I can delve into my own WORKING connection for LabVIEW to its networked license server to learn what it is that my own account does right? A register someplace, a configuration menu, a hidden *.ini file somewhere? Anything like that to tell me how my own, working LabVIEW gets along fine. Then I'd have some positive info for knowing how to fix the license connection for others. Attached is the error message I get when trying to fire up LabVIEW from a different account on the same machine. It finds all the VIs which I wrote just fine. What's failing to load, so I surmise, is some other, more basic part of LabVIEW itself. TIA, Gan Uesli Starling, KY8D Test Enineer
×
×
  • Create New...

Important Information

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