PDA

View Full Version : RSLogix5000 v20 - Update problem


Marc_U
June 6th, 2012, 05:42 AM
We have been using RSLogix5000 v19, for about a year with no problems.

I have now tried installing the latest update (v20), and now it won't run. Instead I get a fatal error:

Log Extract:
================================================== =============================
Wed Jun 06 10:26:24 2012

Fatal Error!
Application Path: C:\Program Files\Rockwell Software\RSLogix 5000\ENU\v20\Bin\RS5000.Exe
Elapsed execution time: 17 seconds
Version: V20.00.00 (Release)
Source File: unknown
Line Number: -1
Function/Method: unknown
OS Version: Windows XP 32-bit (Service Pack 3 - Build 2600)
Thread Id: 00001314 (4884)
Error 0xc0000005 (-1073741819)
EXCEPTION_ACCESS_VIOLATION - An "access violation" exception was generated.
No project file is currently open.


I can only get RSLogix5000 to work again, by uninstalling the v20 update. However I am left with aftereffect that everytime I boot up my laptop, I get an RS Enterprise error message.
:banghead::banghead:

Can anyone help??, or suggest something???

bosko
June 6th, 2012, 04:46 PM
I will track down what the fix was.

Marc_U
June 15th, 2012, 04:45 AM
As an additional problem, it looks like my "RSView Studio NE" software has also been disabled by the failed RSLogix5000 update.

:smas::smas::banghead::banghead::smas::smas:

ecsiberg
March 17th, 2013, 07:07 PM
exactly the same problem experienced in these days
no idea about the solution at the moment

darkesha
May 2nd, 2013, 09:43 AM
Anyone has any idea whats causing this ?
I am running into same problem.

Marc_U
May 2nd, 2013, 09:56 AM
I am afraid, I still haven't found answer to "RSView Studio ME" problem.

And regarding the RSLogix5000 v.19/v.20 problem, I gave up, and got a new laptop, which installed both v.19 & v.20 without a hitch.

I haven't even attempted to install "RSView Studio ME" on my replacement laptop, in fear that it will foul things up.

darkesha
May 2nd, 2013, 09:58 AM
I kinda don't have that option still new installation is coming up with CLx V20 firmware.

I don't have access to their forums or their knowledge base. It sucks.

darkesha
May 4th, 2013, 07:37 PM
In case it helps someone else as well (it helped me). Response from email support:

...
This is in response to your Rockwell Automation technical support inquiry regarding RSLogix 5000 software.
Please delete ".rnl" file under
C:\Documents and Settings\All Users\Application Data\Rockwell Automation\FactoryTalk Activation (for Windows XP)
C:\ProgramData\Rockwell Automation\FactoryTalk Activation (for Windows Vista or Windows 7)
Reboot computer

If you have still the same issue please
From the local computer, click Start --> Programs --> Rockwell Software --> FactoryTalk Tools --> FactoryTalk Directory Configuration Wizard
Select "network", and give a Windows Admin User credentials
After this the RSLogix 5000 v20.00 software should start without error.

You can also try to repair FACTORYTALK SERVICES PLATFORM.
...

I only needed to get rid of rnl file and it started ok afterwards.

dragon8x007
December 25th, 2013, 02:59 AM
i can find file *.rnl inside C:\ProgramData\Rockwell Automation\FactoryTalk Activation (for Windows Vista or Windows 7) i used win 7 pro 64bit. and follow From the local computer, click Start --> Programs --> Rockwell Software --> FactoryTalk Tools --> FactoryTalk Directory Configuration Wizard
Select "network", and give a Windows Admin User credentials. my laptop send " access denied

dragon8x007
December 25th, 2013, 03:06 AM
sorry i can not find .rnl inside C:\ProgramData\Rockwell Automation\FactoryTalk Activation (for Windows Vista or Windows 7) i used win 7 pro 64bit

DamianInRochester
December 26th, 2013, 08:21 AM
My answer isn't going to help you with what you have already done, but potentially could help you avoid this in the future.

Install these in a VM. Backup/Snapshot the VM prior to any updates. In your situation, you could have simply restored the VM after the v20 update error and been off and running. I guarantee the time you have already spent now far exceeds the cost of the software to implement VMs.

Especially with FT View/ RS View, this piece of software is just too rife with installation problems to risk having it muddle up your host OS.

I know you said you already have a new laptop. It is not too late to start yourself down this path. Especially with RSView.

daba
December 28th, 2013, 08:48 PM
The root cause of all this is Microsoft don't feel inclined to make Windows backward compatible ... It's only software, as VMWare clearly shows it to be.....

Analogy : I buy a new car, but it won't let me make the same journeys I used to. Something to do with atmospheric pressure, altitude, temperature, wind direction, magnetic fields, moon phases, or whatever. So my car dealer says I need to install another engine in the boot (trunk, to you guys over the pond) to go to my gym, and yet another engine to pick the kids up from school. These engines are made by someone else, and it's gonna cost me....

Or I can ask my Gym and the kids' school to relocate to allow my car to go there.

DamianInRochester
December 29th, 2013, 08:18 AM
The root cause of all this is Microsoft don't feel inclined to make Windows backward compatible ... It's only software, as VMWare clearly shows it to be.....

Analogy : I buy a new car, but it won't let me make the same journeys I used to. Something to do with atmospheric pressure, altitude, temperature, wind direction, magnetic fields, moon phases, or whatever. So my car dealer says I need to install another engine in the boot (trunk, to you guys over the pond) to go to my gym, and yet another engine to pick the kids up from school. These engines are made by someone else, and it's gonna cost me....

Or I can ask my Gym and the kids' school to relocate to allow my car to go there.

Microsoft I am sure deserves a lot of the blame. That said as much as we all complain about windows, it has served many of us well over the past 20+ years. It is no small task to have a company that relies on the sale of an OS, to have to juggle making things new and fresh enough to make the changes worth purchasing, having to maintain some level of compatibility to the past regardless of how amazingly fast technology changes (16bit, 32bit, 64 bit) (single core, multi-core), (serial, USB, firewire, wifi, Bluetooth) (VGA,HDMI), (Networking, , , , , , , ) and keeping with the times in regards to how it is used (PC, laptops, tablets, Phones, TVs, etc).

I think though that Rockwell needs to shoulder much of the blame as well, and this is my reasoning.

1) Many other pieces of software written by other manufacturers that do practically the same thing, but don't have near the same issues.

2) Writing the software such that it utilizes features of the OS that are likely to change or be unstable. (I wrote programs back in the 90s that still run fine now on Win7, they still work because they only used the most basic features of the OS)

FactoryTalk/RSView were developed to be way to sensitive to the host. They are far too intertwined into Microsoft's security features. I have always said if they spent half the time they do on the activation software as they did on fixing the issues with the HMI software they would have a much better product.

All that being said, VMs allow us to maintain clusters of stability and time machines that allow us to work in the past when we need to while the future can forge ahead.

robertmee
December 29th, 2013, 08:34 AM
Just to pile on here with other's sentiment, and I like AB products and it's my choice for large integration projects, but Rockwell Software, especially their Factory Talk Suite is the biggest craptastic piece of **** software ever to become accepted in mainstream use. I cringe whenever a customer requests that we use SE for HMI vs Wonderware, and I immediately double my design costs. It's just that buggy, doesn't have near the features of other HMI packages, and is temperamental as hell. Customer's continue to want it ONLY because it's Rockwell, and ONLY because they don't have to deal with rollout of the product. Those customers that actually have to use it, have quickly switched to Wonderware and others.

jlua1
February 7th, 2014, 06:47 PM
sorry i can not find .rnl inside C:\ProgramData\Rockwell Automation\FactoryTalk Activation (for Windows Vista or Windows 7) i used win 7 pro 64bit
The reason you cant see the files using windows 7 is because they are hidden by default. Follow these procedures to unhide them.

Here's how to display hidden files and folders.

Open Folder Options by clicking the Start button Picture of the Start button, clicking Control Panel, clicking Appearance and Personalization, and then clicking Folder Options.

Click the View tab.

Under Advanced settings, click Show hidden files, folders, and drives, and then click OK.

Thanks,
Juan

AceTomato
March 13th, 2014, 07:48 AM
Hi Guys,

Yes I got this weird problem too one day for no reason. I'm on Win 7 Pro 64 bit. Could not open Logix 5000 v 20 or RSView ME 6.1 at all. Complete crash right from the get go with error message about access violations.

1) In the folder option menu Un-Hide (show) all hidden files and folders
2) Go to this folder. C:\ProgramData\Rockwell Automation\FactoryTalk Activation. Note that "ProgramData" is a normally hidden folder. You have it even if you think you can't see it.
3) You'll see a bunch of (hidden) .rnl files delete them from this folder (but save them somewhere else incase other files fail. There is one .rnl file for each Rockwell program which you startup.

Wasif Khawaja
November 30th, 2014, 09:23 PM
I faced the same issue and I deleted *.rnl files as mentioned in this thread but nothing good happened. Then I thought of re-installing RsLogix 5000 v20. I tried to uninstall it but it gave me an error that another program is being installed so you can't install/uninstall anything. But I was not installing anything else. So I was like dafuq and had to resolve this issue first. And to my surprise when I resolved this issue, I did not have to uninstall Rslogix and it was opening as if nothing had happened.
how did I resolve the installer issue? you ask
1- Press "windows+R"
2- Write "services.msc" and press enter
3- Find and double click "windows installer"
4- In "General" tab, you will find "startup type". Note down the current status and select "disabled".
5- Press OK and thats it. (you may later change it to previous status when you are actually about to start any installation)

After I did all these steps I wanted to uninstall RsLogix but just to try my luck I opened RsLogix and it was running all good.

padees
November 30th, 2014, 11:04 PM
If you delete the *.rnl files you have to reboot after that.

At least W7 installer get's jacked once in a while. As you said in your description is to disable it. I did a reboot after that then enabled it, and the world was round again.

I found this fix from a gal with windows Vista.

I also had to repair FT Services Platform, then the water was blue.

Wasif Khawaja
November 30th, 2014, 11:12 PM
I deleted rnl files and rebooted. did it twice. but never worked for me. i just shared what worked for me

ronny_resistor
April 2nd, 2015, 10:16 AM
Kept getting the same Fatal Error. Removed all Windows updates, removed all versions of 5000 (18, 19, 20) and re-installed V20 removed Factorytalk *.rnl file still Fatal error. Decided to sleep on it. Next morning I right clicked the start-up Icon for RSLOGIX5000 V20 and looked carefully to see if it was compatible, no issues there then I noticed that the "run as administrator" was unchecked. I checked it and the Fatal error went away. Amazingly I am the only one on the internet that has this issue and can provide you with this solution. I spent 8 hours scowering the internet and no one has had this problem. You guys are great !!

rmichaelson
April 2nd, 2015, 06:26 PM
Thanks for Ronny-Resistor for the tip...I was having the same issues (fatal error V20.03 on a Win 8 laptop), and simply right-clicked on the RSLLogix5000 icon and ran as administrator...it fired right up.

Kudos to all!

ronny_resistor
April 2nd, 2015, 08:54 PM
After I got my program up and running again, administrator privelage now checked. I tried to create a new processor in V20 each time i was getting another fatal error (different) C++ error, I removed V20 and re-installed it and it is now working.
I think it had to do with Framework 2.0 I may have corrupted V20 hence I tried to re-install it and it worked for me.

BachPhi
January 25th, 2016, 09:24 PM
IF YOU ARE RUNNING WINDOWS 10.

Right click on C:\Program Files (x86)\Rockwell Software\RSLogix 5000\ENU\VXX\Bin\RS5000.exe and Run Compatibility Troubleshooter and save the settings after the test

ricce
February 3rd, 2016, 03:58 PM
Thanks a lot Ronny Resistor, I was with the same problem

Andy_Conn
March 14th, 2016, 01:19 PM
Thanks Ronny.

I know this is an old thread, but someone in this forum is usually at hand to help.

Appreciate it!

tactnuke
March 14th, 2016, 02:43 PM
The best thing I did was go to v24.

shaohaoz
March 30th, 2016, 04:47 PM
Here is my solution after tried almost everything on my laptop for three hours.
My system is win 7 and the program kept on crashing when opening v20 files.
Right click on C:\Program Files (x86)\Rockwell Software\RSLogix 5000\ENU\v20\Bin and Run Compatibility Troubleshooter to manage to start the v20 program and save the settings after that. Right click again and selected the Properties, disable the setting saved in the Compatibility tab.
Then everything goes back to normal.

Birdman89
November 2nd, 2016, 11:40 AM
Thanks ronny_resistor, just wanted to say that "run as administrator" fixed my problem as well in Win7 32-bit. Much appreciated.

Divinitous
November 9th, 2016, 08:37 AM
Thanks ronny_resistor, just wanted to say that "run as administrator" fixed my problem as well in Win7 32-bit. Much appreciated.

Called AB today and was advised to do this as well. It resolved my problem.

Win10 x64

j2002
January 9th, 2017, 07:25 AM
Kept getting the same Fatal Error. Removed all Windows updates, removed all versions of 5000 (18, 19, 20) and re-installed V20 removed Factorytalk *.rnl file still Fatal error. Decided to sleep on it. Next morning I right clicked the start-up Icon for RSLOGIX5000 V20 and looked carefully to see if it was compatible, no issues there then I noticed that the "run as administrator" was unchecked. I checked it and the Fatal error went away. Amazingly I am the only one on the internet that has this issue and can provide you with this solution. I spent 8 hours scowering the internet and no one has had this problem. You guys are great !!

I get registered in this forum only to say THANK YOU

iKhmaiFoSho
January 31st, 2017, 01:25 PM
I too just registered to say Thank You. Running RSLogix as administrator really did the trick & I would've found out without everyone's input, thanks again!!

janner_10
February 1st, 2017, 02:17 AM
IF YOU ARE RUNNING WINDOWS 10.



Get a VM for sanity sake.

DarrenG
February 24th, 2017, 05:31 AM
Kept getting the same Fatal Error. Removed all Windows updates, removed all versions of 5000 (18, 19, 20) and re-installed V20 removed Factorytalk *.rnl file still Fatal error. Decided to sleep on it. Next morning I right clicked the start-up Icon for RSLOGIX5000 V20 and looked carefully to see if it was compatible, no issues there then I noticed that the "run as administrator" was unchecked. I checked it and the Fatal error went away. Amazingly I am the only one on the internet that has this issue and can provide you with this solution. I spent 8 hours scowering the internet and no one has had this problem. You guys are great !!

You absolute hero, thank you very much!! I can only imagine how much more time I would have spent trying to solve this had I not seen your post.

Rgoltsch
April 18th, 2017, 09:12 AM
Thanks to those that found this fix. I wrote up a quick procedure for my guys here at work to quickly fix this issue if it pops up for them. I attached the PDF as a quick guide for those in the future.

Ron

daba
April 18th, 2017, 10:49 AM
Thanks to those that found this fix. I wrote up a quick procedure for my guys here at work to quickly fix this issue if it pops up for them. I attached the PDF as a quick guide for those in the future.

Ron

Excellent work Ron :thumb: :thumb:

pajonec
June 6th, 2017, 04:21 AM
Excellent work thank you! Ron

ScottTheEngineer
June 22nd, 2017, 09:18 AM
Kept getting the same Fatal Error. Removed all Windows updates, removed all versions of 5000 (18, 19, 20) and re-installed V20 removed Factorytalk *.rnl file still Fatal error. Decided to sleep on it. Next morning I right clicked the start-up Icon for RSLOGIX5000 V20 and looked carefully to see if it was compatible, no issues there then I noticed that the "run as administrator" was unchecked. I checked it and the Fatal error went away. Amazingly I am the only one on the internet that has this issue and can provide you with this solution. I spent 8 hours scowering the internet and no one has had this problem. You guys are great !!
Ok that figures. I read your response 5 seconds after hanging up the phone with Rockwell tech support. Run as administrator is the solution.
I got hit with a couple windows updates yesterday.
Interestingly enough I could open some of the PLC's but not all of the PLC's and not the one I need to work on.