- No acceptable bindings found factorytalk install#
- No acceptable bindings found factorytalk serial#
- No acceptable bindings found factorytalk upgrade#
- No acceptable bindings found factorytalk software#
- No acceptable bindings found factorytalk license#
No acceptable bindings found factorytalk license#
Next you have to download license files for each product.
No acceptable bindings found factorytalk software#
If the above was successful, your older software activations should now be converted for use with FTActivation. If you don't know your credentials for your software then you're going to have to call support.
No acceptable bindings found factorytalk upgrade#
You can do this on any computer that has Internet access.ĥ6477 () - Upgrade Master Disk to FactoryTalk Activation
No acceptable bindings found factorytalk serial#
If you want to migrate 5 now you'll need to repeat the steps linked below for both product serial numbers, or any others for that matter. Next you need to migrate your software product, or products, from EVRSI Activations to FactoryTalk Activations. We have one of each at the moment, but the -DONG model is officially "no longer available". You can then keep the licence files on the Dongle and when plugged in, FTActivation automatically sees the Host ID and the license files. The -DONG2 is newer and has 2GB user memory which you can store the licence files on. A copy of the license files must reside on each of the computers that will run the software. The older -DONG model is just a Host ID and has no user memory available. If you choose to do it at a later date you can always come back here.įirst you need to make sure you have the correct USB Dongle to act as the hardware Host ID. Whether you want to do this or not, I'll spell it out for you anyway. We use a dongle to activate 3 separate programming laptops and it's quite easy to add more.
It's not as difficult as you think and you should not really need support to do it. It's going to hold you back at some point in the near future, so while your in this bit of a pickle, I'd say now is as good a time as any. I think you really need to bite the bullet here and move all your activations to FactoryTalk Activation. RA's Knowledgebase article 5483 describes the method for doing that in Windows 7 or Windows 2008. The classic method was to edit the CHECKDRIVES= environment variable. One of the issues with EVRSI is that the computer needs to know which drive letter to check for the EVRSI.SYS file, and of course with a removable drive the drive letter can vary. You can check the converse issue by trying to create a v19 project (or earlier) on the computer that's asking for FactoryTalk Activation, to see if an earlier version of RSLogix 5000 will run with EVRSI activation. You can check this by trying to create a v20 application on one of the other computers that has RSLogix 5000 v20 installed. That information could certainly be wrong. The information that's available to me from the RA Knowledgebase (LINK) () indicates that RSLogix 5000 v20 will not run with EVRSI activation. My guess is that because you have RSLogix 5000 v20 installed that it is looking for a FactoryTalk Activation. It looks like you posted details while I was composing my reply.
No acceptable bindings found factorytalk install#
The other computers are not older, save the laptop, they just have had the installation done a while ago (probably a few years ago) (I have not been here 3 months and this computer was a mechanical engineers before me so RSLogix was not installed) we all use thumb drive for activation including the laptop, since there is only three of us that manage the PLCs, HMIs, and robots it is a suitable method (for now)Īlso, I am using the same install DVD that the other computers used so that isn't an issue.
Yes it is EVMOVECF(W) method I posted the names of the three files in the activation folder in a prior post. The registry cleaning was after uninstalls and prior to a reinstallation. Your first step should be to determine which activation method your older computers are actually using. RA finally stopped supporting EVRSI with RSLogix 5000 v20, but I think that RSLogix 500 has retained the ability to use the old activation method.Īt this point you've done a bunch of uninstall/reinstall and registry cleaning, so you may have done more harm than good. That RA activation "dongle" might also be thought of as a "thumb drive" the newer ones also have some storage onboard.įor a very long time, PLC logic editors like RSLogix 500 and RSLogix 5000 have supported both EVRSI and FactoryTalk activation methods. RA has been very slowly migrating away from EVRSI to FactoryTalk Activation, which uses a plaintext *.LIC file that's created to be tied to a specific attribute of a computer, like a hard drive Volume ID, the MAC ID of a network adapter, or a special hardware ID of a Rockwell activation "dongle". You might remember using the EVMOVECF utility to place the activation file there. It sounds like you're using the old EVRSI activation method and storing the activation file (EVRSI.SYS) on a removable USB storage device "thumb drive". Can you clarify exactly what you're doing with the "thumb drive" ?
0 kommentar(er)
