Currently working from home, I don't have the precise information at hand. Please search the AB knowledge base for the error you are experiencing, as there is a known issue with a downloadable patch available to resolve it. It's worth noting that this issue can also impact FTAssetCentre when occurring with FTView. If memory serves me well, I will provide the AB KB number once I'm back in the office tomorrow morning.
Hello sports enthusiast, have you located the Knowledge Base (KB) number yet?
The number 461888 has been a popular search term on search engines lately.
I keep receiving the same error message, despite attempting to reboot my system and following the steps outlined in Knowledge Base article #461888. Are there any other solutions or recommendations available?
- 29-07-2024
- Donald Widdows
Enhance your PC performance with a large bottle of Jim Beam and a 40oz. speaker magnet. Secure the magnet to your hard drive while your computer is running, then treat yourself to a triple shot as you walk away. Welcome to the forum, new member! While I may not have encountered your specific issue, I found that doubling the desktop heap resolved numerous odd issues with my FctMeStudio v6.1 in a 32-bit VM. Improve your software's performance by implementing this simple solution.
After testing out the Jim Beam product, I decided to share my thoughts on it by posting this review on a Sunday evening.
- 30-07-2024
- Donald Widdows
Interested in learning more about "desktop heap"? Do a quick Google search to find out more. It would be beneficial to have Dustin create a desktop heap checker tool to include in a comprehensive patch roll-up kit. Let's name it Steaming Heap. This tool could be a great addition to FctMeViewStudio. Have you experimented with increasing the desktop heap size from 512 to 1024? Doing so helped resolve issues such as "Tag database not found" and viewing tags. Additionally, consider checking out Microsoft's own version of Steaming Heap: http://www.microsoft.com/en-us/download/details.aspx?id=17782. Who would have thought they would have something like that available?
If you encounter the "failed to initialize" error, a reliable solution is to shut down FactoryTalk and navigate to your project directory at C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI projects\. From there, delete or rename the RDMDATA file in the "cache" directory and the .CAC file in the "tag" directory. Once completed, restart FactoryTalk to resolve the issue effectively.
After trying various solutions without success, I decided to uninstall the software and install FTView 7.0 instead. To my disappointment, the same error persisted, suggesting that the issue may lie beyond the software itself.
- 30-07-2024
- Donald Widdows
After consulting an AB representative, I received a helpful tip for resolving issues with Windows 2000 and XP. For those using Vista or Windows 7, this solution may shed some light: https://rockwellautomation.custhelp.com/app/answers/detail/a_id/68481. Simply merge and reboot a small .reg file provided to fix the issue. This method worked well for me and could be the solution you're looking for. - JustAGreenHorn.
Unfortunately, this solution did not resolve the issue I was experiencing on my Windows 7 64-bit laptop. Following a crash, my system was not properly restored, leading to the need for a complete wipe and reinstall of the operating system to start afresh.
- 30-07-2024
- Donald Widdows
One common problem with View ME is the frequent occurrence of issues after sudden power loss, a well-known concern acknowledged by AB. To address this, uninstalling and reinstalling the Factory Talk Services platform is recommended. This can typically be done through the control panel or using the original installation CD. It's advisable to have a cloned hard drive beforehand, as uninstallation may not always be successful. If you encounter difficulties, further instructions from AB may involve accessing your registry. Feel free to reach out if you require additional assistance.
I have encountered a persistent problem with my FTSE 6.1 software on a Server 2008 64-bit system. Unfortunately, my chat with Rockwell Support did not provide a solution. Can anyone offer any suggestions or tips on how to troubleshoot this issue effectively?
Timeismoney08 mentioned that experiencing issues with View ME is a common occurrence, especially after a sudden power loss. AB is aware of this issue and recommends uninstalling and reinstalling the factory talk services platform. You can do this through your control panel or by using your original installation CD. It is advisable to have a cloned hard drive before uninstalling, as it may not always be successful. If you encounter difficulties, AB has additional instructions that may require editing your registry. Don't hesitate to reach out if you need further assistance. After conducting a complete uninstallation of the FT Service Platform, followed by a reboot and reinstallation, the same error persists.
xC0MMAND0x mentioned that they performed a complete uninstall of the FT Service Platform, followed by a reboot, reinstall, and another reboot, only to encounter the same error. The best solution to this recurring issue is to have a clone of the hard drive before it became corrupted. AB is not being very helpful in addressing this issue, despite their awareness of it. Feel free to share your email with me, and I will provide you with instructions on how to modify your registry.
It appears to be a problem related to a corrupted registry. To fix this issue, consider uninstalling and reinstalling the affected software and using a reliable registry cleaner like CCleaner. After uninstalling, reboot your computer, run the registry cleaner, reboot again, and then reinstall the software. This should help resolve the issue caused by the corrupted registry entries.
Encountering Factory View ME "Failed to initialize the service" error can be frustrating, but there are common solutions that may help. One common issue is when FTview crashes while attempting to copy or move elements on the screen. Following the steps suggested by Jmveerkamp can often resolve this problem without losing any unsaved work. Another possible reason for this error is not being connected to FactoryTalk. Make sure to establish a connection, as this can resolve the issue. Thank you for the helpful information provided!
This issue is resolved through repairing the FactoryTalk Service Platform, ensuring optimal performance and efficiency.
Encountering the same issue? Don't worry, I had the same problem too. A hard reset, along with some patience to allow all the services to load, resolved the issue for me. Best of luck to you!
I encountered a similar issue and was able to resolve it with the assistance of jmveerkamp. I had trouble opening a project in FactoryTalk View Studio v11 on my Windows 10 laptop, consistently receiving the error message, "FactoryTalk Linx - An internal error has occurred. You must close FactoryTalk View and stop the FactoryTalk Link service before continuing. Failed to find the topology node in the configuration." To resolve this issue, I took the following steps:
1. Shutdown FactoryTalk View Studio.
2. Navigate to C:\Users\Public\Documents\RSView Enterprise\ME\HMI projects and locate the relevant project folder.
3. Go to the Tag folder and either delete or rename the .CAC file.
4. Navigate to the Cache folder within the project folder and delete or rename the RDMDATA folder.
5. Restart FactoryTalk View Studio to resolve the issue.
Encountering a problem with my Windows 10 device while using FactoryTalk View Studio v11, I found a solution that successfully resolved the issue. Many thanks to Scottstuartp and jmveerkamp for their assistance in fixing my issue. The error message I kept receiving when attempting to open a project in FactoryTalk View Studio v11 on my Windows 10 laptop was related to FactoryTalk Linx. It stated, "An internal error has occurred. You must close FactoryTalk View and stop the FactoryTalk Link service before continuing. Failed to find the topology node in the configuration." To resolve this, I took the following steps:
1. Close FactoryTalk View Studio.
2. Navigate to C:\Users\Public\Documents\RSView Enterprise\ME\HMI projects and locate the relevant project folder.
3. In the project folder, navigate to the Tag folder and either delete or rename the .CAC file.
4. From the same path, navigate to the Cache folder and delete or rename the RDMDATA folder.
5. Restart FactoryTalk View Studio.
By following these steps, I was able to resolve the issue with FactoryTalk View Studio on my Windows 10 computer.
I am currently using version 8 on a virtual machine running Windows XP Professional. When I attempted to upgrade to Windows 10 previously, I encountered numerous issues as the software was not fully compatible at that time. However, I now need to create a new virtual machine with Windows 10 and update my AB software. Can I expect better compatibility now, and will I find all the necessary tools in RS Studio for this upgrade?
Encountering a recurring issue with a process that becomes stuck, requiring the use of CTRL+ALT+DELETE and task manager to end it. It is essential to terminate all tasks related to FT (excluding activation and Linx) to resolve the error. Even after a reboot, these programs remain stuck, making manual intervention necessary for a reset. The crucial process to watch out for is likely the FT Daemon. Future updates will be provided if this issue reoccurs.
- 30-07-2024
- Spencerguenther
Spencerguenther shared his experience dealing with a recurring issue that can be resolved by ending specific tasks through CTRL+ALT+DELETE and task manager. When encountering errors related to FT programs, excluding activation and Linx, it is essential to terminate the gummed up processes. Simply rebooting may not fully reset the system, so manually ending problematic tasks is often the most effective solution. One crucial process to look out for is the FT Daemon. In a recent incident, the "Shared memory daemon" task needed to be ended before rebooting to resolve the issue. This issue typically arises when FT View crashes unexpectedly, such as during system updates. While deleting tag files mentioned in previous discussions has helped in the past, ending specific tasks has proven to be a quicker fix. These troubleshooting steps may prove helpful to others experiencing similar issues.
The .cac file can cause issues if the PC crashes. It's concerning that FTV and similar programs are essentially a revamped version of RSV32, where they've simply modified an existing system and made it less reliable. In addition, the high cost of these programs adds to the frustration.
In a recent incident, Lem faced a recurring issue with the "Shared memory daemon" task in FT View, which tends to occur when the software crashes unexpectedly. Lem found that ending this task and rebooting the server resolved the issue, especially after Windows updates causing disruptions. While deleting tag files has been a workaround in the past, this quick fix proved effective for Lem. Following advice from Spencerguenther, Lem successfully resolved the issue and expressed gratitude to the helpful community members for saving the day once again. This fix came just in time for an upcoming customer meeting where the laptop presentation is crucial.
Lem mentioned that he experienced a recurring issue recently related to the "Shared memory daemon" task. He found that ending this task and rebooting the server resolved the issue. This problem tends to occur when FT View crashes or unexpectedly closes, such as during a Windows update reboot despite disabling the feature. Deleting tag files mentioned in previous discussions has also solved this issue in the past, but stopping the task and rebooting proved to be a quick fix that worked for Lem. Hopefully, this solution can help others facing similar issues. (Attachment: 64027) Thank you for the lifesaving advice.