As I was prepping to film additional lessons for my CompactLogix course yesterday, I ran into a completely new Studio 5000 Logix Designer “Fatal Error” that I hadn't run into before.

After I duplicated the issue on two different PCs, each running two different Windows 10 VMs, I was convinced something was wrong with the software and not just my installation.

NOTE: For those who are having this issue and need to fix it asap, use this LINK to scroll down to the details about the fix I implemented.

In fact, over the last few months I've been spending a lot of time in RSLogix 5000 v20, and Studio 5000 Logix Designer v30, creating and refining the code and scenarios for my Compact Basics course's new programming lessons.

Not having run into any issues with either v20 or v30, you can probably imagine that I was a little frustrated during rehearsals for my “Studio 5000 First Look” lesson, when every time I tried to create a v21 project Studio 5000 crashed.

And since I was able to easily duplicate the issue on multiple VMs, I figured it had to be a known bug, so I pointed my browser at Rockwell's Knowledgebase to search for a solution.

Sadly, while I did find two tech notes covering this error, it appears that just being a customer who purchased this expensive software wasn't enough to unlock the solutions to this bug:

Note: While our blog does not have permission to share the contents of locked tech notes, the good news is your local Rockwell distributor or rep should be able to share them with you 🙂

Off Topic: After submitting many and varied messages to Rockwell about how tech notes like these (you know, the ones with information you need to actually get the product you purchased to work) should not be locked, I've come to the conclusion either they don't read customer feedback, or they just don't agree with these sentiments.

Since I had purchased a support contract last summer to gain access to the latest software updates (albeit with delayed access to Studio 5000 updates as I don't own the most expensive editions,) I logged with my account in order to unlock them (links below:)

To summarize what I learned, it appears that installing newer versions of Studio 5000 can break older versions, something software vendors have been struggling with since the introduction of the personal computer.

That said, after reading through the fixes detailed in those tech notes, I found that none of them were too appealing.

But by reading between the lines, and with a little experimentation, I found that I could resolve the issue with a simple change I'll detail below:

How to stop Studio 5000 Logix Designer from causing a Fatal Application Error:

Step 1: Navigate to the “Launcher” directory in your “Studio 5000” installation directory.

On my VM it was: C:\Program Files (x86)\Rockwell Software\Studio 5000\Launcher

Step 2: Next, right click on the Launcher application, then select Properties, and then click on the compatibility tab:

Step 3: Here, set the Launcher to run “as an Administrator,” and then click on Ok:

Step 4: Now when you run Studio 5000, you'll see a “User Account Control” confirmation popup as shown below. I'll leave it up to you if you'd like to make changes to your UAC settings to disable this message:

Select YES to continue and run Studio 5000

Step 5: After you're done with Studio 5000, you'll probably notice this window asking if the issue has been resolved (I clicked on “Yes” which seemed to stop this message reappearing:)

Now while I've just run into this issue myself, I'm sure some of you ran into it months or even years ago.

That being the case, it's likely one of you have come up with a newer or better fix, and if you have we'd all love to hear it!

You can share it with us along with any thoughts, questions, or opinions you have by clicking on the “post a comment or question” link below.

Sincerely,

Shawn Tierney
Automation Instructor and Blogger

Enjoy the benefits of membership! Patreon.com/automation
Check out my affordable courses: TheAutomationSchool.com
Ask me questions by clicking here to go to the comments link
Have an industrial automation news tip? Share it with us here

Avatar
Latest posts by Shawn Tierney (see all)


Click HERE to scroll down to view or leave comments


Forum Comments:
  1. Showing Forum comments 1 of 3
    Stevo31
    Had this problem in the past, but now it is showing up in a different scenario... In version 32, using the "Alarm Manager" any time I attempt to close it or delete any alarm tags / alarm definitions, I get this same dreaded fatal error. I have selected "run as admin" for all of my launchers still to no avail. Anyone else having this problem or know of a solution?
Click HERE to post a forum comment or question

RELATED ARTICLESMORE FROM AUTHOR

4 Blog Comments

  1. It didn’t use to happen to me at all. Then I made the mistake to try and enable the bookmark toolbar, you see when i tried to do that I would get the same Fatal Error, my program would crash but restarting it worked. But my curious self decided i had to be able to enable the bookmarks without crashing studio 5000. I managed to do it (i had to open studio 5000 as an admin, and it allowed me to enable the bookmarks toolbar) problem was after I closed the program. Now, whenever I try to open studio 5000 it sends me that Fatal Error message, I have tried everything I have found online (even your method) but nothing works. I think I have run out of options (Yes, i even uninstalled and reinstalled the software). If i ever manage to fix it, I’ll share it, but if someone already did or has a different methos I would love to hear it.

  2. Hi Didier,
    I also have this issue. It appears to be related to scaling in Windows 10. If my scaling is set to 100% then I can enable and disable the bookmarks. If I shutdown Logix, then change it back to 125%, it will fatal error when starting back up. Looks like I will have to use 100% scaling to use bookmarks for now.
    Regards,
    Jeff

Leave A Blog Reply Here

Please enter your blog comment!
Please enter your name here