Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

TIA Portal and TP700 compile problem.

Created by: ramiv at: 2/11/2013 2:09 PM (7 Replies)

Rating (1)

Thanks 5

8 Entries

2/11/2013 2:09 PM	Rate (0)
ramiv Posts: 55 Rating: (1)	Hi i get the following alarm when i try to compile my HMI Project: Internal ERROR (detail: cannot access DataType property - object type: VIEW_IN).,1,0,3:04:49 PM Now this really does not tell me anything where the problem lies, so anybody have an idea?. Versions as follows: TIA Portal V11 SP2 Update 5 Windows 7 Pro SP1
ramiv Posts: 55 Rating: (1)
Suggestion To thank Quote Answer

2/11/2013 2:32 PM	Rate (0)
0_Einstein Diamond Member Joined: 7/7/2010 Last visit: 1/13/2025 Posts: 15531 Rating: (2465)	ramiv Hi i get the following alarm when i try to compile my HMI Project: Internal ERROR (detail: cannot access DataType property - object type: VIEW_IN).,1,0,3:04:49 PM Now this really does not tell me anything where the problem lies, so anybody have an idea?. Versions as follows: TIA Portal V11 SP2 Update 5 Windows 7 Pro SP1 Maybe the object type VIEW_IN means something to you in your TP600 project? I have had several similar errors that to me were less than helpful. My fix has been to create a new screen, go to the old screen, ctrl-a to select all, ctrl-c to copy all, go to new screen, ctrl-v paste, and then make buttons and plc logic that push the screen to go to the new screen. Then lastly, delete the screen causing problems. Compile and magically it works (most of the time). Once while waiting on Siemens to help correct a compile problem, I simply created a brand new HMI in my existing project, then copied every piece from the original HMI to the new HMI. It took a couple of hours to get it done, but it did compile and work afterwords. The strange part is the response from local Siemens support was they could readily duplicate the problem. After sending to corporate HQ support, suddenly they could not get the problem to appear. Was I shocked? No. I suspected it was a default language issue as I have English as the default language, and of course corporate HQ has Deutsch (German). I have tested broken HMI projects in the past by changing the default language to German, compiles fine, then change back to english and continues to compile fine afterwards. Please submit your project to Siemens via their Support Requestsystem so they can verify it is fixed in V12. They may also find what workaround is possible.
	science guy
Suggestion To thank Quote Answer

2/12/2013 6:42 AM	Rate (0)
ramiv Posts: 55 Rating: (1)	Hi i made changes to several pages before tried to recompile, and therefore cannot be sure which page originally is the reason. I have tried to remove some of the pages, but still i get the same messsage, it seems it moves from page to page, ie something is definitely wrong with the tool. (Also removed some pages that are no longer needed, maybe it is the reason) I am converting an existing OP17 project with 60 pages and ~500 tags, which i thought should be easily done, but it seems it is not.
ramiv Posts: 55 Rating: (1)
Suggestion To thank Quote Answer

2/12/2013 1:31 PM	Rate (0)
ramiv Posts: 55 Rating: (1)	So after i redid the Migration and managed to redo all the pages i was able to repeat the problem after i started to delete old unused pages. But at the moment it is unclear what causes it, i still need to add 8 pages, but now i delete old ones first, and then add the new ones, if the project went over some invisible size limit..
ramiv Posts: 55 Rating: (1)
Suggestion To thank Quote Answer

2/12/2013 2:53 PM	Rate (0)
0_Einstein Diamond Member Joined: 7/7/2010 Last visit: 1/13/2025 Posts: 15531 Rating: (2465)	ramiv So after i redid the Migration and managed to redo all the pages i was able to repeat the problem after i started to delete old unused pages. But at the moment it is unclear what causes it, i still need to add 8 pages, but now i delete old ones first, and then add the new ones, if the project went over some invisible size limit.. Like your migration problem, I had a very similar issue during migration. My fix was to create a 2nd HMI in my project, copy my screens, tags, runtime settings, area coordination configuration. Somehow that copy / paste process cleaned up the ghosts causing crashes in the migrated HMI compiling. Supposedly V12 of the portal improves the migration process. That's what Siemens HQ passed back through local siemens support on my support request.
	science guy
Suggestion To thank Quote Answer

2/6/2014 7:53 PM	Rate (1)
jrh_engineer Posts: 5 Rating: (5)	I just got this error. In project tree right click the name of your HMI, then select: Compile->Software (rebuild all) The software by default compiles incrementally. This makes the compile time faster. However, sometimes the software gets mixed up and does not recoginze a change that is made. If other modules are dependent on those changes it will cause errors. In my case, I renamed a screen. In general, you should do incremental compiles and saves as you do your work. Then, just before downloading the code, do a rebuild all of both PLC and HMI code.
jrh_engineer Posts: 5 Rating: (5)
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users K!ke hRequena sinnaiG

2/7/2014 8:07 AM	Rate (0)
Vishal Shelke Posts: 8 Rating: (0)	Hi, I also got same error yesterday. "Internal ERROR (detail: cannot access DataType property - object type: VIEW_IN)" I have Compile the program. Compile -> Software (rebuild all) My problem is Solved Regards, Vishal Shelke
Vishal Shelke Posts: 8 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users TomDeWou sinnaiG

1/15/2016 12:20 PM	Rate (0)
Min_Moderator Platinum Member Joined: 9/3/2014 Last visit: 3/13/2019 Posts: 4766 Rating: (122)	New question published by Yves_Bosmans is split to a separate thread with the subject TIA Portal V13, internal ERROR. Best regards Min_Moderator

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on