On starting up RSLogix 500 I was greeted with the message: FATAL ERROR! THE COPY PROTECTION LICENSE FOR THE APPLICATION COULD NOT BE ACQUIRED. After much head scratching, I can only imagine that the IT dept. Have been doing a disk cleanup or something (no one else. So I spent about 3 hours yesterday installing RSL5k on a laptop and when I copied the license file over; it was for a different software serial.

The fix for this is to modify the registry! On 64-Bit systems, these are the keys that need to be modified: HKEY_LOCAL_MACHINE SOFTWARE WOW6432Node Rockwell Software RSLogix 5000.1 Last Version UserInfo Serialnum HKEY_LOCAL_MACHINE SOFTWARE WOW6432Node Rockwell Software RSLogix 5000.1 Support ProductID HKEY_LOCAL_MACHINE SOFTWARE WOW6432Node Rockwell Software RSLogix 5000.1 UserInfo Serialnum Change the serial numbers listed in all 3 of these keys to the correct serial number and then your activation will work. Logix only cares about the first 4 numbers of the serial number. Standard starts with 1203 Pro starts with 2022 Mini starts with 1635 Full starts with 2445 Edit: I forgot to list the paths for the XP registry keys: HKEY_LOCAL_MACHINE SOFTWARE Rockwell Software RSLogix 5000.1 Last Version UserInfo Serialnum HKEY_LOCAL_MACHINE SOFTWARE Rockwell Software RSLogix 5000.1 Support ProductID HKEY_LOCAL_MACHINE SOFTWARE Rockwell Software RSLogix 5000.1 UserInfo Serialnum • • • •.

The 'installation diskette' hackcoder refers to was the old EVRSI activation system. The activation file was not tied to a particular value you enter during installation or to a particular computer. The OP probably has a FactoryTalk activation, which is tied to a particular hardware identifier on the computer.

Raoul's suggestion is right: you need to generate a new *.LIC file that uses a hardware ID on the new computer. Usually you use the MAC ID of your main Ethernet card, or the Volume ID of your C: drive, or a special USB dongle from RA. Creating a new License file for a new computer is called 're-hosting' and you can do it online or by calling Rockwell Automation Technical Support. Can you clarify: Did you just copy a.lic file from the activations folder on your old laptop to your new one, and copied the wrong one? Or did you enter the wrong 10 digit serial number during the installation process? The serial number you enter during installation is arbitrary. So long as it begins with 2022xxxxxx, it doesn't matter.

It's best practice to enter the actual serial number for future software maintenance, but not necessary. If you did the former, you'll have to rehost the activation (.lic file) to either the hard disk number (ABCD-1234) or your NIC.

As a Rockwell FSE, I try not to encourage this workaround, but you can get a hard disk serial number changer pretty easy. I wouldn't recommend it for servers as I have seen issues where maintenance tried this, specifically between redundant HMI servers with the same host ID.

For an engineering workstation, however, it shouldn't be an issue. We get 3 GoldMaster activations, so I use one for my host (laptop) and all my different images have the same Host ID/activation. Rehosting the license should never be an issue though.

I'm virtualizing a Rockwell AssetCentre Server and I'm looking at Disaster Recovery scenarios. This server contains a lot of other Rockwell Software like RSLinx, Logix 5000, Logix 500, and more.

Software activations for Rockwell work in a very strict manner, so much so that I'm concerned about whether its going to be viable to restore the AssetCentre server Virtual Machine to a different host in the event of a system failure. Download Exploring Corporate Strategy 8th Edition there. The software activations are locked to the virtual machine using the serial number of the hard drive.

You can also choose to lock it to the MAC address of the virtual machine. Are either of these two things something that can be customized and edited using VMWare? Will they automatically change if I host the virtual machine using a different Virtual Server? I've looked inside the.vmx files (currently using a mix of VMWare Workstation 7 and VMware ESXi 4.1) and I didn't see anything in either of the files that looked like a MAC addresss or a Hard Disk serial number. The UUID of the disk is in the.vmdk file. For example: # The Disk Data Base #DDB ddb.toolsVersion = '8327' ddb.adapterType = 'lsilogic' ddb.geometry.sectors = '63' ddb.geometry.heads = '255' ddb.geometry.cylinders = '2610' ddb.uuid = '60 00 C2 9f e4 06 d9 4c-13 9a d8 50 77 bb 73 36' ddb.longContentID = '72d1cd8a4fb3119ca80f3870ee90c1b0' ddb.virtualHWVersion = '7' The MAC address can be edited under 'Advanced properties' of your network adapter. It should also be in the.vmx file.

I found this is mine: ethernet0.generatedAddress = '00:0c:29:f3:72:cc' It's possible that it's only saved there once you edit it though. If you move your VM to another location VMWare usually asks you if you moved or copied the VM when you start it. If you say you moved it then all ID's stay the same.

If you say you copied it then VMWare will change the ID's to prevent conflicts. I am also dealing with AssetCentre which we have virtualized in VMware and have bound to the disk serial number. I've been trying to figure out how to display the disk serial number.

Thanks for the information on how to do that within FactoryTalk. I also finally found that just doing a DIR in a command prompt in any folder on that drive shows it at the top. I just cloned our server to another Cluster and it appears that the disk serial number stayed the same. Also, Microsoft Sysinternals provides a free tool VolumeID to change the disk serial number.

I tested it and it did successfully change the serial number which FactoryTalk noticed after rebooting. Based on my testing of the clone I don't think that I will need it, but I wanted to see if it worked. Amf Roadmaster Serial Number Location. So I found out that VMware changes Hard Disk serial number (8 character Alpha-Numeric code somehow bound to a Hard Drive or Volume) when you make a clone, and I haven't found a way to manually change it back. Using the 'DISK_SERIAL_NUM' for the Host ID is a bad idea for Rockwell products running on VMware (even though they will still recommend it). In FactoryTalk Activation Manager, if you click 'Get New Activations' and then click the [.] button under 'Host ID Information' it will show you MAC Address and the 'DISK_SERIAL_NUM' and ask you to choose a Host ID to bind your activation's. Since the MAC Address is the only thing I know of that you can manually configure in ESXi on a virtual machine, we reworked our activation's and now they're all bound to the MAC address of the primary network adapter. Been running.

- AssetCentre - RSLogix 500 (make sure you get the activation Node-Locked) - RSLogix 5000 - RSLinx Classic.with no issues since reworking the activation's.