Greetings all, I am currently working with multiple versions of software ranging from v16 to v20. Upon attempting to access a v20 file, I encountered an issue where the enable source protection feature was not activated. To resolve this, I accessed the installation folder and ran the enable source protection tool, successfully enabling this feature for the v20 file. However, when I tried to open a v17 file, I noticed that the enable source protection was still disabled. While the enable source protection feature works when opening v20 files, the same cannot be said for v17 files. How can I go about resolving this issue? Any assistance is greatly appreciated. Thank you.
It appears that there is no project loaded in the image you shared, as indicated by the controller box. Source protection is typically applied on a per-program basis. To enable source protection, you must open a project created in RSLogix V17, not just the software itself. So, without an active project, there is no data to safeguard.
Can you please explain how you managed to successfully resolve this issue?
Hi there! It sounds like you might be dealing with a compatibility issue between the different software versions. Even though the "enable source protection" feature works fine in the v20 files, it might not have been available or configured in the same way in v17. As a workaround, you could perhaps try to open your v17 file directly in the v20 software, if the application supports backwards compatibility. Alternatively, you might want to check if there's a specific enable source protection tool offered for the v17 version or a patch which can update the feature. Hope this helps and you get it figured out soon!
Hello, this sounds like an issue that often arises while managing different versions of software. It might be because each version has its own set of configurations and needs to have source protection enabled individually. If you've enabled it on v20, you'd have to do the same to v17 by accessing its specific installation folder. Alternatively, you may also want to check if there are any compatibility issues between versions that could cause a conflict when trying to enable source protection. I hope this helps and let me know how you get on!
It sounds like you're dealing with some compatibility quirks between the versions. Have you tried checking the settings in the v17 file itself to see if there's a specific option to enable source protection? Sometimes, older versions have different configurations that need to be adjusted. Additionally, you might want to look for any updates or patches for v17, as they sometimes include fixes for these kinds of issues. If all else fails, reaching out to the software's support team for guidance could provide a more tailored solution!
It sounds like you're dealing with a bit of a compatibility issue between the different software versions. Have you tried checking if the enable source protection tool is compatible across all versions? Sometimes, features like that can behave differently depending on version specifics. You might also want to ensure that the correct version is set as the default in your system, or consider reinstalling the tool for the v17 if it’s acting up. It’s a bit tedious, but sometimes a clean slate can help clear up these quirks! Good luck!
It sounds like you’ve already done some thorough troubleshooting! Since the enable source protection feature seems to work for v20 but not for v17, it could be a compatibility issue between the versions. Have you tried creating a new v17 project file after enabling the source protection for v20? Sometimes, changes made in later versions don’t retroactively apply to earlier ones. If that doesn’t work, consider checking if there are updates or patches specifically for v17 that might address this issue, or reaching out to customer support for more tailored assistance. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The enable source protection feature might not be activated by default for files in RSLogix 5000 versions v16 to v20. You can manually enable it using the enable source protection tool in the installation folder.
Answer: Answer: The enable source protection tool might be version-specific and may not be compatible with v17 files. You may need to find an alternative method to enable source protection for v17 files.
Answer: Answer: To resolve this issue, you can try checking for any updates or patches that include support for enabling source protection in v17 files. Alternatively, you can reach out to the software provider or community forums for assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.