Factory Talk Error: Audit Trail

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #19504
    Anonymous
      Karma: 0
      Rank: Padawan

      Good day, 1st time posting.

      I’m using Factory Talk 10 at the moment and trying to create a runtime file in V9.0.

      I get the following ERROR, I’m aware of the warning and patch but the ERROR is preventing me from creating the runtime file.

      Also, I have verified that the Audit Trail in the Startup config is not selected.

      WARNING: To open or convert the runtime application in FactoryTalk View version 9.0 or earlier, install patch. See Rockwell Automation Knowledgebase Answer ID 1041447.
      ERROR: Unsupported feature=Audit Trail; Component type=Startup
      Validation completed with errors. The runtime application has NOT been created.

      I recently updated the latest June patch files and still get the error.

      Thanks in advance.

      #19507
      BadPropBadProp
      Participant
        Karma: 13
        Rank: Padawan

        It still creates the runtime file…

        Directly from Rockwell…

        Summary

        • In FactoryTalk View Studio ME version 10.00 and higher, there is a popup message when creating version 9.00 or earlier runtime files instructing to install a patch:To open or convert the runtime application in FactoryTalk View version
          9.0 or earlier, install patch. See Rockwell Automation Knowledgebase
          Answer ID 1041447.

           

        • Also, the runtime creation Validation Results will also contain a similar message and will appear at the completion of the runtime compile:WARNING: To open or convert the runtime application in FactoryTalk View version 9.0 or earlier, install patch. See Rockwell Automation Knowledgebase Answer ID 1041447.
          Validation completed with warnings. The runtime application has been created.
          CAUTION: Running this application might produce errors at runtime.
        • FactoryTalk View ME v10.0 and higher
        • FactoryTalk View ME v9.0 and lower: Restoring runtime files created in v10 and higher

        This is an expected informational message, not an error. Please read the two bullet points below carefully. If you are using V10 or higher of FactoryTalk View Studio only, there is nothing for you to do:

        Clicking OK on the message will allow the runtime creation to continue.

        • For users with FactoryTalk View Studio version 10.00 or higher this patch does not need to be installed on your PC.
        • For users with FactoryTalk View Studio version 9.00 or lower the specified patches must be installed to restore and develop the application further. For simplicity, just apply the January 2018 or later Patch Roll-up from 1066644 – Patch Roll-up for CPR9 SRx on the PC you intend to restore the .MER file. (The listed patch number in the popup is already included in later patch roll-ups).

        The warning message pop-up can be disabled, by clicking the checkbox on the lower left of the popup window. However, the warning will still be visible in the validation results text file.

        Note: Please disregard the following statement: CAUTION: Running this application might produce errors at runtime. There will be no errors at runtime as a result of this warning.

        #19515
        Anonymous
          Karma: 0
          Rank: Padawan

          Thanks for the response but actually no it doesn’t, I’ve seen the Rockwell posting and it doesn’t cover the audit trail error and also states The runtime application has NOT been created.

          ERROR: Unsupported feature=Audit Trail; Component type=Startup
          Validation completed with errors. The runtime application has NOT been created.

          #19567
          rmartinrmartin
          Participant
            Karma: 16
            Rank: Padawan

            Any chance you’ve found a solution yet? I’m struggling with this issue right now. I’m running version 11.0, trying to create a runtime file in 9.0. I’ve been able to do it a couple times by some combination of restarting things and changing format from .med .apa and .mer. Nothing I can replicate consistantly though. I usually just get this error.

            #19571
            Anonymous
              Karma: 0
              Rank: Padawan

              Yes, make sure you have de-selected all features that are unsupported in the older versions.

              If that doesn’t work and assuming you are running Windows 10, try running FTV Studio ME (VStudio.exe) in Windows 7 Compatibility mode.

               

              #19572
              rmartinrmartin
              Participant
                Karma: 16
                Rank: Padawan

                Are there features other than the audit trail that are unsupported? That’s the only thing the error says and that’s unselected. I have already put VStudio.exe in windows 7 compatibility mode and ran it as administrator. I have also uninstalled and reinstalled the software. I still get the error.

                #19573
                Anonymous
                  Karma: 0
                  Rank: Padawan

                  You still get this ERROR: Unsupported feature=Audit Trail; Component type=Startup?

                  The Audit Trail and CSVExport features were not available until the version 10.00

                  I can’t be sure what else there is, I updated everything to latest revision including July Patches using Factory Talk Updater. Unchecked Audit Trail under System-Startup explorer in FTV Studio ME (see attachment) and changed VStudio.exe to Windows 7 compatibility mode.

                  CSVExport was already unchecked.

                  That worked for me.

                  #19577
                  rmartinrmartin
                  Participant
                    Karma: 16
                    Rank: Padawan

                    I did finally get it to work. I couldn’t access the tech connect article about it. I could only view threads on different forums. I saw several things that said to run vstudio.exe in compatibility mode for windows 7 so I put vstudio in the search bar and went to open file location. That took me to C:\Program Files (x86)\Common Files\Rockwell. That’s not the one you need to change. When someone sent me what the tech connect article said, it shows the path. C:\Program Files (x86)\Rockwell Software\RSView Enterprise. That’s the one you need to run in compatibility mode for windows 7. Now I just need to figure out why I can’t access the tech connect articles.

                    #19875
                    Roy_G_BivRoy_G_Biv
                    Participant
                      Karma: 12
                      Rank: Padawan

                      Not sure this actually adds to the conversation, but it may help others.

                      The solution that worked for me was running vstudio.exe in compatibility mode (windows 7).

                      I’ve found when it says the file is NOT created, its actually not been created. which is probably the reason people are reading this in the first place.

                      #19882
                      sanjeevimanoharansanjeevimanoharan
                      Participant
                        Karma: 14
                        Rank: Padawan

                        Thanks for the help guys. I have FTview 11 on a Windows 10 and the fix that worked for me was running the Vstudio.exe – application troubleshooter for compatibility. It appears to me that the Windows 8 compatibility was automatically chosen for me by the troubleshooter and I couldn’t complain since it worked for me to create a runtime file v5.0 out of a FTview 11. The link for Vstudio for me was “C:\Program Files (x86)\Rockwell Software\RSView Enterprise”. Hope it helps someone. Thanks again.

                        By the way if someone is wondering how to run the application troubleshooter, just right click on Vstudio.exe and its right there for you.

                        Cheers !

                        Sanjeevi

                        Attachments:
                        You must be logged in to view attached files.
                        #19918
                        bsu212bsu212
                        Participant
                          Karma: 15
                          Rank: Padawan

                          I got the same error form what seemed out of the blue, I created a runtime file one day and the very next day made another change and I the error when I went to do another runtime file “ERROR: Unsupported feature=Audit Trail; Component type=Startup Validation completed with errors. The runtime application has NOT been created.”

                          Running in compatibility mode worked for me.  The only thing that changed from on day to another what I think was a mandatory update from the company I work for.  It wasn’t a windows update not sure exactly what it was.

                          Anyway thanks for the great information.

                           

                           

                          #19919
                          Anonymous
                            Karma: 0
                            Rank: Padawan

                            Thanks!

                            #20369
                            bsu212bsu212
                            Participant
                              Karma: 15
                              Rank: Padawan

                              Upgraded my laptop, and forgot all about this….

                              Very frustrating , but thanks again !!

                            Viewing 13 posts - 1 through 13 (of 13 total)
                            • You must be logged in to reply to this topic.