I am trying to use RSLogix 5000 on my desktop PC Windows 7 Professional 64bit SP1 RSLogix V15-20 Normally we use a thumb drive for the activation key. However on my computer it asks for factory talk activation, which we do not use or have setup. 2 other PCs (same hardware and OS setup) use the thumb drive method with no issues (other than tracking down the thumb drive) The other computer we have RSlogix 5000 on is a Win XP laptop. RSLogix500 works fine with the thumb drive I have tried uninstalling all Rockwell software off of my PC, cleaning out (manually) all Rockwell registry tags, and finding as many folders where any Rockwell files are stored and deleting them. Then did a fresh install of RSLogix 5000 still does not let me activate off of the thumb drive. If anyone has any ideas on this I would greatly appreciate it. Nightline November 19th, 2014 10:32 AM.

Yes at the end of the installation there is a choice. I believe the first time I installed it I put the wrong check/uncheck in. Now I after uninstalling/re-installing it with what my coworker told me is the setting to use I get the same results. I don't know if there is something residual on the computer left from the original installation that is stopping me from being able to activate or whether there is something else going on. I tried everything I know to do to remove any residual traces of the program (registry cleaning, file deletions) MartB November 19th, 2014 11:11 AM. If you're sure you've uninstalled everything and cleaned the registry, then you're probably going to have to call Tech Support to get some help.sorry about that Cleaned the registry best I could. I used the search function, so if there is something in there that does not have 'Rockwell' (it or its parent directory) in it I would have missed it I kinda figured I would have to resort to Tech Support but I was hoping someone has seen this and knew a quick fix, registry tag I missed, or something of that nature EDIT: I thought about trying to modify a.lic file or an.ini file to look in the right place but I am not sure which one acts as the pointer for the license.

That and I do not know exactly how the EVMoveCF.exe, EVMoveCF.jpg (not a picture tho), EVMoveW.exe on the thumb drive actually operate to properly redirect the pointers within the files Ken Roach November 19th, 2014 11:52 AM. Can you clarify exactly what you're doing with the 'thumb drive'? 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'. You might remember using the EVMOVECF utility to place the activation file there. 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'.

That RA activation 'dongle' might also be thought of as a 'thumb drive'; the newer ones also have some storage onboard. For a very long time, PLC logic editors like RSLogix 500 and RSLogix 5000 have supported both EVRSI and FactoryTalk activation methods.

In this article we discuss what you need to know before upgrading to RSLogix 5000 version 20.03. And confirmed v20 only uses FactoryTalk Activation (FTA.). Download Rslogix 5000 V20 Factorytalk Activation Crack. Rslogix 5000 V20 Factorytalk Activation Crack Installer MD5:.

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. At this point you've done a bunch of uninstall/reinstall and registry cleaning, so you may have done more harm than good. Your first step should be to determine which activation method your older computers are actually using. Dlweber November 19th, 2014 12:14 PM. Can you clarify exactly what you're doing with the 'thumb drive'? 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'. You might remember using the EVMOVECF utility to place the activation file there.

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'. That RA activation 'dongle' might also be thought of as a 'thumb drive'; the newer ones also have some storage onboard.

For a very long time, PLC logic editors like RSLogix 500 and RSLogix 5000 have supported both EVRSI and FactoryTalk activation methods. 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.

At this point you've done a bunch of uninstall/reinstall and registry cleaning, so you may have done more harm than good. Your first step should be to determine which activation method your older computers are actually using.

The registry cleaning was after uninstalls and prior to a reinstallation. Yes it is EVMOVECF(W) method I posted the names of the three files in the activation folder in a prior post. 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) Also, I am using the same install DVD that the other computers used so that isn't an issue. Dlweber November 19th, 2014 12:38 PM. It looks like you posted details while I was composing my reply.

My guess is that because you have RSLogix 5000 v20 installed that it is looking for a FactoryTalk Activation. The information that's available to me from the RA Knowledgebase indicates that RSLogix 5000 v20 will not run with EVRSI activation. That information could certainly be wrong.

You can check this by trying to create a v20 application on one of the other computers that has RSLogix 5000 v20 installed. 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. 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. The classic method was to edit the CHECKDRIVES= environment variable. RA's Knowledgebase article 5483 describes the method for doing that in Windows 7 or Windows 2008.

Dlweber November 19th, 2014 12:54 PM. Quote: The V15-20 RSLogix5000 now use an online activation.

You must be connected to the internet to activate it via FactoryTalk Activation. This is only partially correct. RSLogix 5000 v6 through v9 supported EVRSI activation. RSLogix 5000 v10 through v19 supported both EVRSI and FactoryTalk Activation. RSLogix 5000 v20 and higher support only FactoryTalk Activation. While it is easiest to perform FactoryTalk Activation using the Internet, an Internet connection directly to the computer hosting the activation is not absolutely required.

Activation license files can be created for computers that are not connected to the Internet, and transferred to those computers using other means. It is technically possible to create a FactoryTalk Activation license file with a text editor, as long as you can communicate with somebody who.can. contact Rockwell Automation using a computer or a telephone.

Geospark November 19th, 2014 10:36 PM. I think you really need to bite the bullet here and move all your activations to FactoryTalk Activation. 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. It's not as difficult as you think and you should not really need support to do it. We use a dongle to activate 3 separate programming laptops and it's quite easy to add more. Whether you want to do this or not, I'll spell it out for you anyway.

If you choose to do it at a later date you can always come back here. First you need to make sure you have the correct USB Dongle to act as the hardware Host ID.

9509-USB-DONG or 9509-USB-DONG2 The older -DONG model is just a Host ID and has no user memory available. A copy of the license files must reside on each of the computers that will run the software.

The -DONG2 is newer and has 2GB user memory which you can store the licence files on. You can then keep the licence files on the Dongle and when plugged in, FTActivation automatically sees the Host ID and the license files. We have one of each at the moment, but the -DONG model is officially 'no longer available'. So if you have the Dongle sorted. Next you need to migrate your software product, or products, from EVRSI Activations to FactoryTalk Activations. If you want to migrate 500 and 5000 now you'll need to repeat the steps linked below for both product serial numbers, or any others for that matter.

You can do this on any computer that has Internet access. Upgrade Master Disk to FactoryTalk Activation Access Level: Everyone If you don't know your credentials for your software then you're going to have to call support. If the above was successful, your older software activations should now be converted for use with FTActivation. Next you have to download license files for each product. If the computer you want to run the software on does not have Internet access, then do the following.

Plug in the USB Dongle and make sure the HASP drivers are installed correctly. Thank you for that explanation, and I agree it will hold us up down the road, good thing right now we don't have anything all that new or fancy that we really have to worry about v20 or newer (hence I just found this issue two days ago) and (a guess into my bosses head) the reason he plans to have support do it is he is going to piggy back it onto something else, he is gone till Monday, but I can ask him if he wants me to attempt the procedure you gave me All times are GMT -5. The time now is 11:02 PM.

• Apply the official. • Replace the original GAME.EXE file with the one from the File Archive. • Play the Game! MONEY File Archive [1.4 MB] Play Instructions: • Install the game - Full Installation.

Good day All, I'm a newbie to Allen Bradley and have picked up some issues with my Laptop. The license/activation that worked without hassles for the past year is now undetectable, I am sure the license is still on my laptop somewhere but the license activation tool where I went to look after RSlogix 5000 complained, is pointing to 'my documents' for activations. I am under the impression that this is the likely cause of my problem. Could someone assist so that I can get it looking for the activations in the right place again. My local RA Support can only assist me next week when someone becomes available. Any suugestions welcome. There are two different mechanisms for activation of Rockwell Software products.

The older method is called 'Everlock' or 'EVRSI'. It used activation diskettes and a simple activation moving utility that you launch from Start - Programs - Rockwell Software - Utilities - Move Activation (32-bit). That utility is looking for a system file called EVRSI.SYS that contains the activation key. It is always located in the root directory of the drive that contains it (A: or C: or D: or something else). The newer method is called FactoryTalk Activation.

The utility is launched from Start - Programs - Rockwell Software - FactoryTalk Activation - FactoryTalk Activation Tool. This is the multi-tab utility with Get Activations / Current Activations / Rehost Activations / Settings tabs. It is looking for.LIC files, which are simple text files with activation key codes inside them.

The.LIC file path is defined in the Settings tab. The default path is C: Documents and Settings All Users Documents Rockwell Automation Activations. Using and ordinary Windows search for EVRSI.SYS or the.LIC file should help you determine which licensing system you are using.