Have a question? Join my community of automation professionals and take part in the discussion! You'll also find my PLC, HMI, and SCADA courses at. 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. 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! Now while I’ve just run into this issue myself, I’m sure some of you ran into it months or even years ago. 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:) 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 4: Now when you run Studio 5000, you’ll see a “User Account Control” confirmation popup as shown below. Step 3: Here, set the Launcher to run “as an Administrator,” and then click on Ok: Step 2: Next, right click on the Launcher application, then select Properties, and then click on the compatibility tab: On my VM it was: C:\Program Files (x86)\Rockwell Software\Studio 5000\Launcher Step 1: Navigate to the “Launcher” directory in your “Studio 5000” installation directory. How to stop Studio 5000 Logix Designer from causing a Fatal Application Error: That said, after reading through the fixes detailed in those tech notes, I found that none of them were too appealing.īut 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: 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |