WCCOAvalarch is crashed!

[eMichx]

Hello,

I'm working on WinCC OA v3.12P27, I have configured a new Archive (#6), and it's working well on the master SCADA server,
but on the slave, the process crashed, and sometimes, when we intent to restart it, all processes are stopped.
Then, we continue to work with this situation, but there's no achive on the slave!

In the log file, it indicates that there's a time difference of 0s! https://www.winccoa.com/fileadmin/image ... larch6.txt
what are the debug options on this process (I have used numbers from 1 to 30! ) , but I don't find any interesting
debug information

regards
Emmanuel

[leoknipp]

Does the process really crash or is it stopped during startup?

Can you please have a look at the PVSS_II.log file and look for the log message written during startup of the archive.
Maybe the archive is not configured correctly and therefore the archive manager is stopped, then the following log message is written:
WCCILdata (0), 2017.07.10 08:43:01.438, SYS, WARNING, 54, Unexpected state, HistArchive, a deleted archive (state = 3) has tried to connect, archive number is =6

Best Regards
Leopold Knipp
Senior Support Specialist

[eMichx]

Hello,

I have extracted the traces from the PVSS_II.log file. The process is stopped, but sometimes, all the process of the project are stopped!
This situation exists only on the slave Scada server. On the master, WCCOAvalarch 6 is working well.
You have indicated a failure due to a wrong configuration, do you have more details?

regards
Emmanuel


Extract from PVSS_II.log
WCCILpmon (1), 2017.07.12 13:26:35.900, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.12\\bin\\WCCOAvalarch.exe -PROJ Alg1Scada -pmonIndex 2 -num 6 -dbg 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30
WCCOAvalarch (6), 2017.07.12 13:26:36.269, SYS, INFO, 1, Manager Start, PROJ, Alg1Scada, V 3.12 - 3.12 platform Windows AMD64 linked at Mar 9 2016 22:11:55
WCCOAvalarch (6), 2017.07.12 13:26:36.320, SYS, INFO, 0, , Opened Port for OleDbProvider: 4905
WCCOAvalarch (6), 2017.07.12 13:26:36.321, SYS, INFO, 3, Trying to connect to, (SYS: 0 Data -num 0 CONN: 1) @ PCCSCADA2L1-1:4897,PCCSCADA2L1:4897
WCCOAvalarch (6), 2017.07.12 13:26:36.335, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 1) @ PCCSCADA2L1 (::1)
WCCILdata (0), 2017.07.12 13:26:36.337, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 8 CONN: 2) @ PCCSCADA2L1 (::1)
WCCILdata (0), 2017.07.12 13:26:36.345, SYS, INFO, 0, , Manager (SYS: 1 Data -num 8 CONN: 2) initialised
WCCILdata (0), 2017.07.12 13:26:36.345, PARAM,INFO, 1, Manager Start, HistOrgMain, connection from archive received - initializing, archive number is: 6
WCCILdata (0), 2017.07.12 13:26:36.346, SYS, WARNING, 54, Unexpected state, HistArchive, a deleted archive (state = 3) has tried to connect, archive number is =6
WCCILdata (0), 2017.07.12 13:26:36.346, PARAM,WARNING, 2, Manager Stop, HistOrgMain, unable to initialize, terminating archive, archive number is: 6

[leoknipp]

The configuration of the archive is not correct, it is marked as "deleted" and can therefore be not started.
At the dp element _ValueArchive_(_2).state.

Which values can be used can be seen in the WinCC OA documentation at Reference tables --> Internal data point types.

Did you make the configuration of the project and the archives while it was not configured redundant?
In this case the settings have not been copied to the datapoints used at server 2 in a redundant system. The configuration might be different at the datapoints for server 1 and server 2, not only for the archive managers, which will cause unexpected errors.

Best Regards
Leopold Knipp
Senior Support Specialist

[eMichx]

Hello,

I will described the principles we are using to build our SCADA project :

At the beginning, we realize the project installation on one server
Note that the config file contains the configuration for redundant system, but the db is empty

Extract from config file :
data = "PCCSCADA1L1-1,PCCSCADA1L1$PCCSCADA2L1-1,PCCSCADA2L1"
event = "PCCSCADA1L1-1,PCCSCADA1L1$PCCSCADA2L1-1,PCCSCADA2L1"

we start a script to build the db with the command :
WCCOAtoolcreateDB -proj %PROJECT% -autofreg -config "D:\\%PROJECT%\\config\\config" -yes -importAscii "D:\\%PROJECT%\\dplist\\ascii_import_temp.txt

The import is done in 2 steps (before and after the start of S7 process). We import all DP and attributs needed for the project

The archive file which containing the archive6 attribute is build with a process which is started one time (first start of the project)
when the BD is ever built. This is the last ASCII import.

The slave configuration is realized thanks the wizard tools existing in the WinCCOA

All seems to be done in a redundant configuration! :dry: which DP attributs are used for archiving redundancy ?


regards
Emmanuel

[leoknipp]

If the archive configuration is made with an ASCII file you have to check if the ASCII file contains the correct parameters for the datapoints for both servers _ValueArchive_ and _ValueArchive__2.

Best Regards
Leopold Knipp
Senior Support Specialist

[eMichx]

Hello,

I have check the file we import. it was like below (it's just an extract)

# ascii dump of database

# DbArchiveInfo
Manager/User ElementName TypeName DetailNr _archive.._type _archive.._archive _archive.._class _archive.._interv _archive.._interv_type _archive.._std_type _archive.._std_tol _archive.._std_time _archive.._round_val _archive.._round_inv
UI (3)/0 System1:SY_TGP_PEF1_BASCULE.status.value DP_SY 45 1
UI (3)/0 System1:SY_TGP_PEF1_BASCULE.status.value DP_SY 1 15 _ValueArchive_6 0 0 0 0 01.01.1970 00:00:00.000 0 0

I have added a new lines, integrating _ValueArchive_6_2 for redundancy, it's looks like
UI (3)/0 System1:SY_TGP_PEF1_BASCULE.status.value DP_SY 1 15 _ValueArchive_6_2 0 0 0 0 01.01.1970 00:00:00.000 0 0
then I have import it, but the Archive6 still stop on slave server
Is there any others changes?
attached, the dp file containing the definition of Archive6

regards
Emmanuel https://www.winccoa.com/fileadmin/image ... alarch.txt

[leoknipp]

The configuration for the _ValueArchive_6(_2) must be the same on both servers and not the configuration of the _archive configs at the dp elements.
When looking at the ASCII file you will see the following difference
DM (0)/0 _ValueArchive_6.state _ValueArchive 1 0x300101 28.07.2016 11:35:43.368
ASC (1)/0 _ValueArchive_6_2.state _ValueArchive 3 0x8300000000000101 25.07.2016 11:59:19.758

The _ValueArchive_6_2.state element has the value "3" which means "deleted" and therefore the archive cannot be started.
I didn't check if there are more differences at the configuration of the archive.

Please check all the settings, also for the other archives.

As mentioned before in this thread if you are using a redundant system the system configuration must be done in redundant configuration, even if the second server is not available at the moment.

Making a single project which is already configured to a redundant one only by adding the entries for data/event in the config file may not be sufficient.

Best Regards
Leopold Knipp
Senior Support Specialist