- September 9, 2018 at 8:58 pm #3279
Hey everyone, thought I’d share a little conundrum I faced today with Studio 5000 version 31!
I decided it was time to do a clean install of Windows 10 on my primary development computer to coincide with some hardware upgrades I was making.
My typical workflow with installing Rockwell software is to install the latest packages first that I would be needing (i.e., FTV Studio, Studio 5000) because they are usually pre-packed with the latest FT Services Platform, RSLinx, FTV Activation Manager etc. So I decided that I’d like to take the latest version of Studio 5000 version 31.00.01 for a spin to play with the new UI and features.
So I proceeded to install this package first even though I don’t have any customers currently on that revision (it was more for me to play!) and it went pretty well, no issues.
Now I proceed to try to install the versions of Studio that I ACTUALLY need to support some customers and so I proceeded to version 29.00.01.
This is the error I got:
Turns out my tried and true method of installing Rockwell software has now failed me!
Here’s what I had to do:
- The new version of Studio installs something called FactoryTalk Linx 6.00. This new communication software replaces the old RSLinx Enterprise (here in lies the problem). You will need to uninstall FactoryTalk Linx before installing Studio 5000 version 30 or lower.
- Once FactoryTalk Linx 6.00 is uninstalled proceed to install the lower version of Studio 5000 (in my case version 29.00.01).
- Once installed (and I installed every other Rockwell software I needed that relied on RSLinx Enterprise) reinstall FactoryTalk Linx.
Hope that saves someone else a few strands of hair!November 1, 2018 at 5:50 am #3479Sean TerrellModerator
Karma: 184Rank: Jedi
- Topics: 6
- Replies: 29
- Total Posts: 35
I faced this myself. And this is not the first time, I have had issues with several different versions of Studio doing this on different components. I fought an issue ALL night not long ago that was caused by a C++ redist version. And the kicker was that the version I had on my VM, it WAS THE SAME VERSION the installer was going to install. You know the real issue here is actually not the versioning of Linx or anything else? Its that a Multi-billion dollar American innovation company can’t figure out how to handle dependency and installation package exceptions and just continue with the installation.
But Factory Talk is the reason that I have bee running on virtual machines even before I switched to macOS. I have had too many issues with factory talk suddenly being broken by an update or because I switched my internet connection, or because I spoke a bit too harshly in front of it and its feelings were hurt. I have different VMs with different FT and Rockwell versions on them. If I can’t tell what FW rev some site is… I just use a spreadsheet with a DDC OPC link to poll the system tags.November 1, 2018 at 8:57 am #3483
Hey Sean, you’re absolutely correct…and multiple VMs is the way I usually go. I guess I’m a bit of a hopeless optimist that longs for the day Rockwell software versions will install seamlessly side-by-side…guess I have to wait for the next major release 🙂November 14, 2018 at 2:30 pm #3563Daniel LittletonParticipant
Karma: 12Rank: Padawan
- Topics: 0
- Replies: 1
- Total Posts: 1
The same exact issue here.. Thanks so much for the post.
Never had hair,, but did same me a lot of time. And made some kudos.November 14, 2018 at 3:01 pm #3564
Hi Daniel and welcome to the forums…glad it helped! Visit often and contribute regularly…lots more kudos where those come from! 🙂
You must be logged in to reply to this topic.