Search the Community
Showing results for tags 'activation'.
Help please! I need to get this seat up and running. I recently had to wipe a machine and reinstall windows 7 over the weekend. Our production is running both Vectorworks 2018 and 2016. I installed them both but I can not get them to activate due to a communications problem. This is the first time I've had an issue like this and nothing has changed as far as I know on the our domain server which manages the firewall rules. If this is local to my side, what ports should be open for the station to communicate to the Vectorworks authentication server? I did send an inquire to tech@vectroworks but thought I'd poke the forum incase anyone has any ideas to help me expedite getting this station working.
Hello everyone, I've finally got a work computer and I can't activate my copy of Vectorworks 2019 because of my license code was used on too many other computers. I used to have a external and nomad install of macOS which made me re-activate the software again on every new computer, and probably used many activation allowances. Now I'm finally settled with a personal and a work computer. Is there a way to change the license code and/or reset the activation count? I'll make sure to keep it on my machines only in the future. Thank you very much!
My lappie, poor ole thing, is trying to die a dignified death as we speak. I have to pick up a new machine in a couple hours. what issues should I be aware of when time to move software & license to new machine? I'm thinking drag n drop from one machine to the next but fear that'll fail.
Hi All, Having a bit of trouble with Vectorworks 2018 in our office. We're intermittently getting a problem whereby vwx 2018 gets stuck on first opening at 'Checking Activation'. It seems to take a very long time generally, but sometimes will get stuck and the program will fail to open entirely. This has occurred on several systems, most notably one of the office brand new IMac's, so I'm convinced hardware isn't the problem. It could of course be related to some sort of network configuration issue our end, but this is not a problem anybody has had in the office running 2017. Any ideas?