Severe errors in logfile - related to tag using Simulation driver

[Smiffy]

I have an S7 driver as driver number 2.
I did have a situation whereby the the S& driver and simulation driver were both running simultaneously.
I stopped the simulation driver. Now I am geiing the following in the log file whenever I open certain tags in the para module.

WCCILevent (0), 2017.06.20 17:05:17.456, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Driver -num 1 CONN: 1), DP_MSG_SIMPLE_REQUEST
WCCILevent (0), 2017.06.20 17:05:17.456, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Driver -num 1 CONN: 1), DP_MSG_SIMPLE_REQUEST
WCCOAui (1), 2017.06.20 17:05:17.471, SYS, SEVERE, 38, Message could not be sent, DP: System1:Ack.:_address.._type, MAN: (SYS: 1 Driver -num 1 CONN: 1), Could not send message DP_MSG_SIMPLE_REQUEST #18661
WCCOAui (1), 2017.06.20 17:05:17.471, SYS, SEVERE, 38, Message could not be sent, DP: System1:Ack.:_cmd_conv.._type, MAN: (SYS: 1 Driver -num 1 CONN: 1), Could not send message DP_MSG_SIMPLE_REQUEST #18661
WCCOAui (1), 2017.06.20 17:05:17.471, SYS, SEVERE, 38, Message could not be sent, DP: System1:Ack.:_msg_conv.._type, MAN: (SYS: 1 Driver -num 1 CONN: 1), Could not send message DP_MSG_SIMPLE_REQUEST #18661
WCCOAui (1), 2017.06.20 17:05:17.471, SYS, SEVERE, 38, Message could not be sent, DP: System1:Ack.:_smooth.._type, MAN: (SYS: 1 Driver -num 1 CONN: 1), Could not send message DP_MSG_SIMPLE_REQUEST #18661

I have checked the tags in the para module that are related to these entries and they do not have any periphreral addresses defined as they are simple HMI tags and do not connect to the controller. So why does OA seem to thing that they have an address and that they are connected to driver number 1?
I have tried deleting the tags in the para module and recreating them, but the problem does not go away.
Something that my be of note is that I had to copy some files from another project to this project. This is because the old project became corrupted when I tried to import a database file that had been edited in excel (this itself an attempt to fix an issue regarding corrupted addressing causing issues with the S7 driver in the old project).

I did a databse dump and searched it and found somthing that sort of relates to the log entires:-
DRV (1)/0 _Stat_Configs_driver_1._address _Statistics_DriverConfigs 125 0x8300000000000101 20.06.2017 14:53:09.221
DRV (1)/0 _Stat_Configs_driver_1._cmd_conv _Statistics_DriverConfigs 15 0x8300000000000101 20.06.2017 14:53:09.221
DRV (1)/0 _Stat_Configs_driver_1._msg_conv _Statistics_DriverConfigs 13 0x8300000000000101 20.06.2017 14:53:09.221
DRV (1)/0 _Stat_Configs_driver_1._smooth _Statistics_DriverConfigs 107 0x8300000000000101 20.06.2017 14:53:09.221
ASC (1)/0 _CtrlDebug_EVENT_0.Command _CtrlDebug "" 0x8300000000080141 16.06.2017 10:28:51.686

These seem to have the same address members. SO is it some sort of diagnostics for the simulation driver that is somehow linked to the tags?

[Gertjan van Schijndel]

The posted error messages have nothing to do with the datapoints you have found.
When you expand a datapoint element the dpTreeView shape sends a message to check which configs are configured on this datapoint element. Since these configs only exist in a driver, these are forwarded to the (stopped) driver. When it does not run, it results in these error messages.

To answer your questions:
1) OA does not think they have an address, but only check if these configs are configured.
2) In this datapoint the driver writes how many configs it has. This information is used in the 'Config' tab of the 'Message and DP statistics' panel, which can be found under 'Event manager connections'.

[Smiffy]

So what do I do about the errors if I am not using the simulation driver?
1) Ignore them?
2) Start the simulation driver, even though I am not using it? Will having both the S7 driver and simulation driver running simultaneously be ok?
3) Delete the "tags" that are using the simulation driver?

[Gertjan van Schijndel]

1) No, always have a driver -num 1 running, so you do not get these errors. It does not matter if it is a simulation or any other driver like S7.
2) Running the simulation driver is fine. It is no problem to have multiple drivers running simultaneously.
3) In this case I have not seen any "tags" that are using the simulation driver, so there is nothing to delete.