Error creating DPE with master Datapoint declared

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
2 posts • Page 1 of 1
andrea.bertorelli
Posts:33
Joined: Wed May 31, 2017 3:58 pm

Error creating DPE with master Datapoint declared

Post by andrea.bertorelli »

Hello. Since yesterday I started having serious problems creating DP from the para. If I have a Master DataPoint with "active" _address properties I sometimes get the errors below.
I'm sure it's not a licensing issue because I deleted all the project tags.

The problem is that from error only if specific variables are active, so for example if the first 5 are active not by error, if I turn them off and only 6 is active by error.

I can't deal with it.

I created the driver connections again, the managers, restarted the project and reinstalled wincc.

Use 3.16 P006 (waiting for P010 I / O field bug resolution) discussed here: viewtopic.php?f=15&t=10580

This error is reapeted for each DPE for each property:

Code: Select all


WCCOAui      (2), 2019.05.31 09:17:54.178, SYS,  WARNING,     0, , Error setting config (477), System1:3.STATUS.SGN_STATUS:_address.._subindex, 0
WCCOAui      (2), 2019.05.31 09:17:54.187, CTRL, WARNING,     5/ctrl, Location of the following log entry: 
    Module: Para_1
    Panel: C:\Siemens\Automation\WinCC_OA\3.16\panels\para.pnl [Datapoint parameterization]
    Object: 10 named: "activeX" of type: DP_TREE
    Script: OnRButtonClk
    Library: C:\Siemens\Automation\WinCC_OA\3.16\scripts\libs\mp.ctl
    Line: 1296


leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Error creating DPE with master Datapoint declared

Post by leoknipp »

I do not understand the problem you have described.
What does the following information mean in detail?
"so for example if the first 5 are active not by error, if I turn them off and only 6 is active by error."

Is the UI running at the server or on a remote machine?
If the UI is not started at the server please check the server logs if there is another error reported.

Best Regards
Leopold Knipp
Senior Support Specialist

2 posts • Page 1 of 1