Hi,

We currently have VC installed on a Windows 7 virtual machine, but my team has just been given a new virtual machine (Windows 10) because my company is in the process of upgrading all the old Win7 machines. I know I can export my existing jobs and re-import them, but I don't want to uninstall VC from our old VM until I have everything up and running on the new VM (which is an excellent time to upgrade to the latest version, since we're a couple of minor versions behind). That means that for a period of a few days, I'd have VC installed on two different machines. Our license is only for a single server, so I'm wondering if there are provisions in the licensing rules that account for situations like this? Or would I have to completely uninstall if from one VM before it even lets me install it on the new VM?

Thanks.

You can not have one license on two different machines, however one solution is that you could download and install the trial version on one in the meantime, since the trial should last for 45 days.

---

Thanks, that seems like a reasonable idea. Once I get it running on the new machine, I assume it's just a matter of deactivating the old machine (Server --> License --> Deactivate) and then activating the new machine?

I've installed the trial version on our new machine, and imported all the settings from the old machine. However, none of my connections work. The old machine had Oracle 11.2 installed; the new one has Oracle 12.1 installed. I've tried creating a new connection like this:



I'm using the Oracle OLEDB provider, because the VC native provider requires that I set up a system DSN. I don't want to do that - I want all the connection settings stored within VC. It's giving me this error:



I've tried various things, such as using different names for the provider:


I've also tried manually registering the DLL file:


It said it was successful, but VC still gives me the above error. Any thoughts on how to fix this?

Thanks.

In the connection wizard, try using "Direct mode" (No oracle client) as shown in the screenshot below


Let me know if that makes a difference

As for your previous question - yes. Just deactivate on the old and reactivate on the new one.

---

Where do I find that option? I don't see it available for me:

Use the guide. Select Oracle->Native-<And then this direct mode.

---

Ok, switching to Native and using the direct mode worked. Unfortunately, it created a brand new connection. I don't want a new connection, because then I have to go through all 50-60 jobs and all their various tasks and manually update the connection for any SQL task. I just want to modify my existing connections, which is really what should be happening when I double-click on an existing connection rather than clicking the "add" button.

Ok, switching to Native and using the direct mode worked. Unfortunately, it created a brand new connection. I don't want a new connection, because then I have to go through all 50-60 jobs and all their various tasks and manually update the connection for any SQL task. I just want to modify my existing connections, which is really what should be happening when I double-click on an existing connection rather than clicking the "add" button.

Does it really create a brand new connection ? It should work to edit the existing connection without it creating a brand new connection ,
What version of VC are you using?

It works to edit it a connection on mine when I tested it

https://www.screencast.com/t/Z0qzLwztV 

---

Thanks, that seems like a reasonable idea. Once I get it running on the new machine, I assume it's just a matter of deactivating the old machine (Server --> License --> Deactivate) and then activating the new machine?

Is this really the solution to activate VC on the new server?