Jump to content

TimV

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. That worked, thanks. I think I now have a better understanding of the difference between configuring ACCESS to a private repo, and MANAGING a private repo. I didn't realize before how distinctly different these two concepts are, and the distinctly different configurations required for each.
  2. Thanks Jim for the reply, with screenshots even! I followed your instructions, yet I still have a problem. Rather than MOVE the repository folder to the new server, I COPIED it; with the intention of deleting the old folder later, once I was confident that everything was working properly. I then edited the "Repository Properties" sheet to reflect the new URL, per your screentshot. I am using VIPM 2014.0.0 (build 1963). Still using the VI Repository Manager, I Un-published a package that I no longer wanted to be published. I used Windows Explorer to take a look at the date/time stamps of the files in both the old and new repository folders. The files in new location still had the previous date/time stamps, while the files in the OLD location now had stamps indicating modification at the present time! Still using the VI Repository Manager, I then pulled down the repository selector box and selected "Configure Repositories...". The "Repository Manager" window that displayed indicates that the location of my repository is still at the OLD path! There seems to be no way to edit this "Location" from this dialog; nor can I find ANY place to edit this value. SUGGESTIONS?
  3. I agree that the apparent connection timeout, coupled with apparent success, is probably some sort of a bug. Have you verified that these installs really were successful? In any case, VIPM should really be configured to use a difference port number for EACH version of LabVIEW that you have installed. Sharing a single port MIGHT work as long as you never want VIPM to connect to more than one version of LabVIEW simultaneously, but simultaneous connections might be necessary as you install packages to several LabVIEW versions during a single VIPM session. This has always been true, so it does not explain why sharing a single port used to work for you, but now does not -- perhaps VIPM 2014 changed something in its socket connection logic so that enforcing unique port numbers is now more important than ever.
  4. I need to move our entire internal (private) VIPM repository from a server that is about to be decommissioned, to a different server. Is it as simple as moving the entire repo folder (the folder which contains the "packages" folder, as well as index.rss, index.vipr, index.vipr.zip, and private.ini) to the new server; then reconfiguring each VIPM client's "Subscription Location" to point to the new path? It seems like it should indeed be this easy, but I once had a bad experience after I messed around with a VIPM repo (but this was a very different situation, I actually hacked and edited the repo files themselves -- don't do that!), and so I wish to verify that this is how it should be done. Thanks.
×
×
  • Create New...

Important Information

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